Oracle Error Messages: 10/04/11

RMAN-06107: WARNING: control file is not current for REPORT NEED BACKUP DAYS

RMAN-06107: WARNING: control file is not current for REPORT NEED BACKUP DAYS

Cause: The REPORT NEED BACKUP DAYS command may report some files as requiring backups when they really do not, because the most current online status of the file is not known unless a current control file is mounted.

Action: No action is required, however, a current control file should be mounted, if possible, to get the most accurate REPORT output.

RMAN-06106: this command requires that target database be mounted

RMAN-06106: this command requires that target database be mounted

Cause: A command was issued that requires the target database to be mounted, but the target database is not mounted.

Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.

RMAN-06423: requested limit of number exceeds vendor limit of number

RMAN-06423: requested limit of number exceeds vendor limit of number

Cause: A SETLIMIT CHANNEL command was used to set the backup piece size limit, but the media management software used by the target database cannot create backup pieces that large.

Action: Specify a smaller backup piece limit.

RMAN-06422: no channels found for SEND command

RMAN-06422: no channels found for SEND command

Cause: No channels with the specified names or device types were found. If no channel qualifiers were specified, then no channels were allocated.

Action: Specify a different channel type or allocate a channel of the desired type.

RMAN-06421: sent command to channel: string

RMAN-06421: sent command to channel: string

Cause: This is an informational message only.

Action: No action is required.

RMAN-06420: some files could not be proxy restored - aborting restore

RMAN-06420: some files could not be proxy restored - aborting restore

Cause: Some of the files to be restored could not be restored by the media management software used by the target database. Message 6419 is issued for each file that cannot be restored.

Action: Contact the media management vendor if you believe that the media management software should support proxy copy of these files. The CROSSCHECK or CHANGE commands can be used to remove these proxy copies from the catalog to prevent the RESTORE command from trying to restore from these proxy backups.

RMAN-06419: file string cannot be proxy restored from handle string

RMAN-06419: file string cannot be proxy restored from handle string

Cause: The media management software used by the target database indicated that it cannot restore the specified file from the specified backup handle.

Action: Consult the media management software documentation to find out why this restriction exists or contact the media management vendor.

RMAN-06418: proxy incremental backups with level lamp;gt; 0 not supported

RMAN-06418: proxy incremental backups with level lamp;gt; 0 not supported

Cause: PROXY was specified for a non-level-zero incremental backup. Proxy backups may only be full or level 0 backups.

Action: Remove one of the conflicting options.

RMAN-06416: PROXY ONLY was specified and some files could not be proxy copied

RMAN-06416: PROXY ONLY was specified and some files could not be proxy copied

Cause: PROXY ONLY was specified, and some of the files to be backed up could not be backed up by the media management software used by the target database. Message 6415 is issued for each file that cannot be proxy copied.

Action: Remove the ONLY option to place the files into a regular backup set, or contact the media management vendor if you believe that the media management software should support proxy copy of these files.

RMAN-06415: file string cannot be proxy backed up

RMAN-06415: file string cannot be proxy backed up

Cause: The PROXY option was specified, but the media management software used by the target database cannot back up the specified file using proxy copy. If PROXY ONLY was specified, then the backup is terminated. If PROXY was specified, then this file will be placed into a non-proxy backup set.

Action: Remove the ONLY option to place the files into a regular backup set, or contact the media management vendor if you believe that the media management software should support proxy copy of this file.

RMAN-06414: target database COMPATIBLE option does not support proxy copy

RMAN-06414: target database COMPATIBLE option does not support proxy copy

Cause: PROXY was specified, and the target database uses a media manager that supports proxy copy, but the COMPATIBLE initialization parameter of the target database must be 8.1.0 or greater to create proxy backups. If the database is downgraded to the earlier release that is specified in the COMPATIBLE parameter, then it will no longer be able to restore proxy backups.

Action: Either take a non-proxy backup or change the target database COMPATIBLE parameter.

RMAN-06413: channel string does not support proxy copy

RMAN-06413: channel string does not support proxy copy

Cause: The channel which was specified for this backup or restore does not support proxy copy. This could be because the media management software used by the target database does not support proxy copy, or because the channel is of type DISK, which never supports proxy copy.

Action: If this is a backup, then either allocate a non-disk channel, or do not use the PROXY option. If this is a restore, then a channel of the same type which created the proxy backup was allocated, but now does not support proxy copy. If proxy copy is no longer supported by the media management software at the target database, the CROSSCHECK command should be used so that those backups will not be considered for further restores.

RMAN-06412: no proxy copy channel found

RMAN-06412: no proxy copy channel found

Cause: A proxy copy was started, but no allocated channel supports proxy copy. This could be because the media management software used by the target database does not support proxy copy, or because all of the allocated channels are of type DISK, which never support proxy copy.

Action: If this is a backup, then either allocate a non-disk channel, or do not use the PROXY option. If this is a restore, then a channel of the same type which created the proxy backup was allocated, but now does not support proxy copy. If proxy copy is no longer supported by the media management software at the target database, the CROSSCHECK or CHANGE commands should be used so that those backups will not be considered for further restores.

RMAN-06411: backup copies setting out of range (1-4): number

RMAN-06411: backup copies setting out of range (1-4): number

Cause: An attempt was made to set backup copies to an invalid value.

Action: Use a value in the specified range.

RMAN-06410: cannot use command when channels are allocated

RMAN-06410: cannot use command when channels are allocated

Cause: An attempt was made to issue a command that can be used only when there are no allocated channels.

Action: Do not use the command, or de-allocate channels and use the command when no channels are allocated.

RMAN-06409: LIKE clause in LIST BACKUP OF ARCHIVELOG is not supported

RMAN-06409: LIKE clause in LIST BACKUP OF ARCHIVELOG is not supported

Cause: LIST BACKUP OF ARCHIVELOG LIKE was used, which is not supported.

Action: Remove LIKE clause from command.

RMAN-06408: recovery catalog upgraded to version string

RMAN-06408: recovery catalog upgraded to version string

Cause: This is an informational message issued by the UPGRADE CATALOG command. It indicates the version of the recovery catalog schema to which the recovery catalog was just upgraded. Note that this version number may not reflect the version number of your rman executable or target database, because the recovery catalog schema is not changed with each Oracle release.

Action: No action is required.

RMAN-06407: auxiliary instance file string deleted

RMAN-06407: auxiliary instance file string deleted

Cause: This is an informational message only.

Action: No action is required.

RMAN-06406: deleted archive log

RMAN-06406: deleted archive log

Cause: This is an informational message only.

Action: No action is required.

RMAN-06405: database closed

RMAN-06405: database closed

Cause: This is an informational message only.

Action: No action is required.

RMAN-06404: database dismounted

RMAN-06404: database dismounted

Cause: This is an informational message only.

Action: No action is required.

RMAN-06403: could not obtain a fully authorized session

RMAN-06403: could not obtain a fully authorized session

Cause: The most likely cause of this error is that one of the databases to which RMAN had previously connected is not started or has has been shutdown. Other error messages should identify exactly which database is the problem.

Action: Startup the database causing the problem.

RMAN-06402: Oracle instance shut down

RMAN-06402: Oracle instance shut down

Cause: This is an informational message only.

Action: No action is required.

RMAN-06401: database is already started

RMAN-06401: database is already started

Cause: A STARTUP command without the FORCE option was issued, but the target database is already started.

Action: Use the FORCE option if you want to restart the database.

RMAN-06400: database opened

RMAN-06400: database opened

Cause: This is an informational message only.

Action: No action is required.

RMAN-06378: List of Backup Sets

RMAN-06378: List of Backup Sets

Cause: This message is issued in response to a LIST BACKUP command.

Action: No action is required.

RMAN-06306: ====================

RMAN-06306: ====================

Cause: This message is issued in response to a LIST BACKUP DATABASE or TABLESPACE or DATAFILE command when some backups were taken with the PROXY option. If a recovery catalog is in use, then the information comes from the recovery catalog, otherwise it comes from the target database control file. The following fields are shown for each proxy datafile backup. Key: This is the unique key which identifies this proxy backup in the recovery catalog. This value can be used in a CHANGE command to change its status. If the target database control file is being used as the recovery catalog, then this field uniquely identifies this copy in the control file. File: The file number that this file was copied from. Status: This is the status of the file. Possible values are: A - Available U - Unavailable D - Deleted X - Expired Status U will not be used if the target database control file is being used as the recovery catalog. Completion time: This is the date and time when the backup was created. This column will be printed in the default Oracle date format, unless overridden with a NLS_DATE_FORMAT environment variable. Ckp SCN: This is the checkpoint SCN of the backup. The file contains all changes made at or before this SCN. Ckp time: This is the time that the file was last checkpointed. Handle: This is the media manager handle of the proxy backup.

Action: No action is required.

RMAN-06300: Report of files with less than number redundant backups

RMAN-06300: Report of files with less than number redundant backups

Cause: This message is issued when the REPORT NEED BACKUP REDUNDANCY command is used for those files which have less than the specified number of backups which can be used for recovery.

Action: Take another backup of the datafiles listed.

RMAN-06290: Report of database schema

RMAN-06290: Report of database schema

Cause: This message is issued in response to the REPORT SCHEMA command. The report shows the physical schema of the database at the indicated time. The following fields are shown for each datafile and temporary file: File: The file number. Size(MB): The size of the file in mega bytes. Tablespace: The name of the tablespace which contains this file. RB segs: YES if this file is part of a tablespace containing rollback segments, otherwise NO. Datafile or Tempfile Name: The file name. Maxsize(MB): Maximum file size to which file can be extended

Action: No action is required.

RMAN-06280: Report of obsolete backups and copies

RMAN-06280: Report of obsolete backups and copies

Cause: This message is issued in response to the REPORT OBSOLETE command. Each of the files listed is obsolete because it is more redundant than the level of redundancy specified in the REPORT command.

Action: Depending on your needs, you might need to take new backups.

RMAN-06275: invalid number of days specified for report : string days

RMAN-06275: invalid number of days specified for report : string days

Cause: This message is issued in response to the REPORT NEED RECOVERY WINDOW OF n DAYS or REPORT NEED BACKUP DAYS n command when an invalid number of days was specified in input command.

Action: The number of days specified in REPORT command must be greater than zero.

RMAN-06274: Report of files that must be backed up to satisfy number days recovery window

RMAN-06274: Report of files that must be backed up to satisfy number days recovery window

Cause: This message is issued in response to the REPORT NEED RECOVERY WINDOW OF n DAYS command for those files that must be backed up to satisfy specified retention policy.

Action: To satisfy specified recovery window for this datafile, take a new full or incremental backup now.

RMAN-06270: Report of files whose recovery needs more than number days of archived logs

RMAN-06270: Report of files whose recovery needs more than number days of archived logs

Cause: This message is issued in response to the REPORT NEED BACKUP DAYS command for those files which need more than the specified number of days archived logs for recovery.

Action: To reduce the number of log files needed for recovery of this datafile, take a new full or incremental backup now.

RMAN-06263: %-4s string string

RMAN-06263: %-4s string string

Cause: This message is issued in response to the REPORT NEED BACKUP INCREMENTAL command, for those files which would use more than the specified number of incrementals during recovery.

Action: To reduce the number of incremental backups which would be used during recovery of this datafile, take a new full backup of this file now.

RMAN-06250: Report of files that need backup due to unrecoverable operations

RMAN-06250: Report of files that need backup due to unrecoverable operations

Cause: An unlogged change (such as create table unrecoverable ) has been made to this file, and the most recent backup of the file does not contain those changes.

Action: Take a backup of this file. If this file is lost before a backup is taken, then the unlogged modifications will be lost. The message indicates whether a full backup is required or whether a incremental backup will suffice.

RMAN-06246: List of Database Incarnations

RMAN-06246: List of Database Incarnations

Cause: This message is issued in response to a LIST INCARNATION OF DATABASE command. The following fields are shown for each database that is registered with the recovery catalog: DB Key: This is the unique key which identifies this database in the recovery catalog. Inc Key: This is the unique key which identifies this incarnation of the database in the recovery catalog. DB Name: The name of the database. DB ID: The database ID. This is a number which remains the same for the life of the database, even if the database name is changed. Status: YES if this is the current incarnation of this database, otherwise NO . Reset SCN: SCN of the most recent resetlogs operation. Reset Time: Time of the most recent resetlogs operation.

Action: No action is required.

RMAN-06230: List of Stored Scripts in Recovery Catalog

RMAN-06230: List of Stored Scripts in Recovery Catalog

Cause: This message is issued in response to a LIST SCRIPT NAMES command. The following fields are shown for each script that is stored in the recovery catalog: Header indicating to what database the script belongs. Script Name: name of the script. Description: comment associated with this script.

Action: No action is required.

RMAN-06226: Automatic instance removed

RMAN-06226: Automatic instance removed

Cause: This is an informational message only.

Action: No action is required.

RMAN-06225: shutting down automatic instance string

RMAN-06225: shutting down automatic instance string

Cause: This is an informational message only.

Action: No action is required.

RMAN-06224: Automatic instance created

RMAN-06224: Automatic instance created

Cause: This is an informational message only.

Action: No action is required.

RMAN-06223: starting up automatic instance string

RMAN-06223: starting up automatic instance string

Cause: This is an informational message only.

Action: No action is required.

RMAN-06221: Removing automatic instance

RMAN-06221: Removing automatic instance

Cause: RMAN is removing the automatic auxiliary instance that was created for this command.

Action: No action is required.

RMAN-06220: Creating automatic instance, with SID= string

RMAN-06220: Creating automatic instance, with SID= string

Cause: No connection to the auxiliary instance was provided, but the command requires an auxiliary instance.

Action: No action is required unless you want to create a permanent database, in which case you should stop the command and re-run it, providing an auxiliary instance connection.