Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 05000-05999: KRMR Errors

##### RMAN-05000: SET CLONENAME required for datafile name

Cause: Either:

- The controlfile mounted by the clone database does not have an entry for this datafile, therefore filename conversion is not possible.
- A COPY DATAFILE TO CLONENAME command was issued, but no clone name was set for this datafile.

Action: Use the SET CLONENAME command to specify a filename that the clone database can use as a restore destination.

##### RMAN-05000: SET CLONENAME required for datafile %s

Cause: The controlfile mounted by the clone database does not have an entry for this datafile, therefore filename conversion is not possible.

Action: Use the SET CLONENAME command to specify a filename that the clone database can use as a restore destination.

##### RMAN-05001: clone filename %s conflicts with a file used by the target database

Cause: RMAN is attempting to use the specified filename as a restore destination in the clone database, but this name is already in use by the target database.

Action: Use the SET CLONENAME command to specify a name for the datafile that does not conflict with a filename in use by the target db.

##### RMAN-05002: aborting point-in-time tablespace recovery

Cause: Previously encountered error(s) were issued which require corrective action.

Action: Resolve the error conditions, and then re-issue the RECOVER command.

##### RMAN-05003: point-in-time recovery is not allowed for tablespace name

Cause: The SYSTEM tablespace or a tablespace containing rollback segments is not allowed in point-in-time recovery.

Action: Remove the indicated tablespace from the recovery set and retry the operation.

06000-06999: KRMK Errors

##### RMAN-06000: could not open recovery manager library file: name

Cause: The RECOVER.BSQ file could not be opened.

Action: Check that the file was installed correctly and that the user running RMAN has authority to read the file.

##### RMAN-06001: error parsing job step library

Cause: A syntax error was encountered while parsing RECOVER.BSQ.

Action: Ensure that the correct version of the file is installed and that it has not been modified in any way.

##### RMAN-06002: command not allowed when not connected to a recovery catalog

Cause: A command that is allowed only when a recovery catalog connect string was supplied was attempted.

Action: Avoid using the command, or restart RMAN and supply a recovery catalog connect string via the RCVCAT parameter.

##### RMAN-06003: ORACLE error from target database: name

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

##### RMAN-06004: ORACLE error from recovery catalog database: name

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

##### RMAN-06005: connected to target database: name

Cause: Informational message.

Action: No action required.

##### RMAN-06006: connected to target database: name (not mounted)

Cause: Informational message.

Action: No action required.

##### RMAN-06007: target database not mounted and db_name not set in init.ora

Cause: The target database has not mounted the controlfile, and its INIT.ORA file does not specify the DB_NAME parameter.

Action: MOUNT the target database, or add the DB_NAME parameter to its INIT.ORA and restart the instance.

##### RMAN-06008: connected to recovery catalog database

Cause: Informational message.

Action: No action required.

##### RMAN-06009: using target database controlfile instead of recovery catalog

Cause: Informational message.

Action: No action required.

##### RMAN-06010: error while looking up datafile: name

Cause: An error occurred while looking up the specified datafile in the recovery catalog or target database controlfile.

Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the filename is entered correctly. If the datafile was added recently, then a RESYNC CATALOG must be done to update the recovery catalog.

##### RMAN-06011: invalid level specified: num

Cause: An invalid incremental backup level was specified.

Action: Incremental backup level must be between 0 and 8.

##### RMAN-06012: channel: num not allocated

Cause: A RELEASE or SETLIMIT command was found for a channel identifier that was not yet allocated.

Action: Correct the channel identifier, or add an ALLOCATE CHANNEL command.

##### RMAN-06013: duplicate channel identifier found: name

Cause: A channel identifier was reused without first releasing the channel.

Action: Add a RELEASE CHANNEL command.

##### RMAN-06014: command not implemented yet: name

Cause: Not all commands are implemented for the beta release.

Action: Avoid using the command.

##### RMAN-06015: error while looking up datafilecopy name: name

Cause: An error occurred while looking up the specified datafilecopy name in the recovery catalog or target database controlfile.

Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the filename is entered correctly. If the datafile copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

##### RMAN-06016: duplicate backup operand specified: name

Cause: The specified operand appears more than once in the same backup specifier or backup command.

Action: Delete the duplicate operand.

##### RMAN-06017: initialization of parser failed

Cause: The parser package initialization routine returned an error.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

##### RMAN-06018: duplicate operand specified in backup specification: name

Cause: A backup spec operand appears more than once in a backup specification.

Action: Delete the duplicate operand.

##### RMAN-06019: could not translate tablespace name name

Cause: An error occurred while looking up the specified tablespace name in the recovery catalog or target database controlfile.

Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the tablespace is entered correctly. If the tablespace was added recently, then a RESYNC CATALOG must be done to update the recovery catalog.

##### RMAN-06020: connected to clone database

Cause: This is an informational message.

Action: No action required.

##### RMAN-06021: FROM DATAFILECCOPY/BACKUPSET may not be specified with archivelogs

Cause: The FROM DATAFILECCOPY/BACKUPSET option applies only to datafile and controlfile restores.

Action: Use this option only for datafile and controlfile restores.

##### RMAN-06022: FROM TAG option may not be specified with archivelogs

Cause: The FROM TAG option applies only to datafile and controlfile restores.

Action: Use this option only for datafile and controlfile restores.

##### RMAN-06023: no backup or copy of datafile name found to restore

Cause: A datafile, tablespace, or database restore could not proceed because no backup or copy of the indicated file was found. It may be the case that a backup or copy of this file exists but does not satisfy the criteria specified in the user's restore operands.

Action: None - this is an informational message. See message RMAN-06026 for further details.

##### RMAN-06024: no backup or copy of the controlfile found to restore

Cause: A controlfile restore could not proceed because no backup or copy of the controlfile was found. It may be the case that a backup or copy of this file exists but does not satisfy the criteria specified in the user's restore operands.

Action: None - this is an informational message. See message RMAN-06026 for further details.

##### RMAN-06025: no backup of log thread name seq name scn name found to restore

Cause: An archivelog restore could not proceed because no backup of the indicated archived log was found. It may be the case that a backup of this file exists but does not satisfy the criteria specified in the user's restore operands.

Action: None - this is an informational message. See message RMAN-06026 for further details.

##### RMAN-06026: some targets not found - aborting restore

Cause: Some of the files specified for restore could not be found. Message RMAN-06023, RMAN-06024, or RMAN-06025 is also issued to indicate which files could not be found. Some common reasons why a file can not be restored are that there is no backup or copy of the file that is known to recovery manager, or there are no backups or copies that fall within the criteria specified on the RESTORE command, or some datafile copies have been made but not cataloged.

Action: The Recovery Manager LIST command can be used to display the backups and copies that Recovery Manager knows about. Select the files to be restored from that list.

##### RMAN-06027: no archivelogs found that match specification

Cause: An archivelog record specifier did not match any archivelogs in the recovery catalog.

Action: Resubmit the command with a different archivelog record specifier. The Recovery Manager LIST command can be used to display all archivelogs that Recovery Manager knows about.

##### RMAN-06028: duplicate operand specified in restore specification: name

Cause: The CHANNEL, TAG, FROM, VALIDATE, or PARMS option was specified more than once in the restore command or in one of the restore specifications.

Action: Correct and resubmit the command.

##### RMAN-06029: the controlfile may be included only in a datafile backup set

Cause: The INCLUDE CURRENT CONTROLFILE option was specified for an archivelog backup set.

Action: Use this option only for datafile backup sets.

##### RMAN-06030: the DELETE INPUT option may not be used with a datafile backup set

Cause: The DELETE INPUT option was specified for a backup that contains the current controlfile or datafiles.

Action: Remove the option and resubmit the command.

##### RMAN-06031: could not translate database keyword

Cause: An error was received when calling DBMS_RCVMAN.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

##### RMAN-06032: at least 1 channel of TYPE DISK must be allocated to execute a COPY command

Cause: No channel of TYPE DISK was allocated.

Action: Allocate a channel of TYPE DISK and re-issue the command.

##### RMAN-06033: channel name not allocated

Cause: A COPY, BACKUP, or RESTORE command requests a specific channel, but the requested channel has not been allocated.

Action: ALLOCATE the channel, or correct the channel identifier.

##### RMAN-06034: at least 1 channel must be allocated to execute this command

Cause: No channels are allocated.

Action: ALLOCATE a channel.

##### RMAN-06035: wrong version of recover.bsq, expecting num, found num

Cause: The RECOVER.BSQ file is incompatible with the RMAN executable.

Action: Install the correct version of RECOVER.BSQ.

##### RMAN-06036: datafile name is already restored to file name

Cause: A SET NEWNAME command was issued to restore a datafile to a location other than the original datafile, and Recovery Manager determined that the best candidate for restoring the file is the datafile copy with the same name, therefore the file is already restored and no action need be taken.

Action: None - this is an informational message.

##### RMAN-06037: incremental backups feature not implemented

Cause: An incremental backup of a datafile copy was requested.

Action: Change the incremental level to 0, or request a full backup.

##### RMAN-06038: recovery catalog package detected an error

Cause: A call to DBMS_RCVMAN returned an error.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

##### RMAN-06039: no set NEWNAME command has been issued for datafile name

Cause: A SWITCH command was specified for a datafile, but no destination was specified and no SET NEWNAME command has been previously issued for that file. An explicit file to switch to must be specified if no SET NEWNAME command has been issued.

Action: Correct and resubmit the SWITCH command.

##### RMAN-06040: controlfile is already restored to file name

Cause: The best candidate controlfile for restoration is the one that is named in the RESTORE (controlfile) command, hence no action need be taken.

Action: None - this is an informational message.

##### RMAN-06041: cannot switch file name to copy of file name

Cause: An attempt was made to switch a datafile to a copy of a different datafile.

Action: Correct and resubmit the SWITCH command.

##### RMAN-06042: TAG option not supported for archivelog backup sets

Cause: The tag option was supplied but does not apply to this type of backup.

Action: Remove the TAG operand and re-enter the command.

##### RMAN-06043: TAG option not supported for archivelog or current controlfile copies

Cause: The TAG option was supplied but does not apply to this type of copy.

Action: Remove the TAG operand and re-enter the command.

##### RMAN-06044: duplicate operand specified in copy specification: name

Cause: The specified operand appears more than once in the same copy specification.

Action: Remove the redundant operand.

##### RMAN-06045: LEVEL option not supported for archivelog or current controlfile copies

Cause: The LEVEL option was supplied but does not apply to this type of copy.

Action: Remove the LEVEL operand and re-enter the command.

##### RMAN-06046: archivelog name: name

Cause: An error occurred while translating an archivelog name to its recovery catalog recid/timestamp. This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

##### RMAN-06047: duplicate datafile name specified for restoration from copy

Cause: The indicated datafile was specified more than once in the same restore command.

Action: Correct and resubmit the RESTORE command.

##### RMAN-06048: duplicate controlfile specified for restoration from copy

Cause: The controlfile was specified more than once in the same RESTORE command.

Action: Correct and resubmit the RESTORE command.

##### RMAN-06049: backup (backup set...) not implemented yet

Cause: A backup of a backup set was requested.

Action: Feature not implemented yet, so do not use it.

##### RMAN-06050: archivelog thread name sequence name is already on disk as file name

Cause: An archivelog which was requested to be restored (either explicitly or using a range specification) does not need to be restored because it already exists on disk.

Action: None - this is an informational message.

##### RMAN-06051: DELETE INPUT option not implemented yet

Cause: This option was specified in a backup specification.

Action: Remove the DELETE INPUT option.

##### RMAN-06052: no parent backup or copy of datafile name found

Cause: An incremental backup at level 1 or higher could not find any parent backup or copy of the indicated datafile. A level 0 backup of the datafile will be taken automatically.

Action: This is an informational message only.

##### RMAN-06053: unable to perform media recovery because of missing log

Cause: This message is accompanied with another message identifying the missing log. The log would be needed to perform the media recovery, but the log is not on disk and no backup set containing the log is available.

Action: Determine if a backup set containing the log can be made available. If so, then use the CHANGE command to make the backup set available and retry the command. If not, then a point in time recovery up to the missing log is the only alternative.

##### RMAN-06054: media recovery requesting unknown log: thread name scn name

Cause: Media recovery is requesting a log whose existence is not recorded in the recovery catalog or controlfile.

Action: If a copy of the log is available, then add it to the recovery catalog and/or controlfile via a CATALOG command and then retry the RECOVER command. If not, then a point in time recovery up to the missing log is the only alternative.

##### RMAN-06055: could not find log sequence name thread name

Cause: A log which was on disk at the start of media recovery or which should have been restored from a backup set could not be found.

Action: Check the Recovery Manager message log to see if the log was restored by a previous job step. If so, then check the V$ARCHIVED_LOG view to see if the log is listed in the controlfile. If so, then validate that the log exists on disk and is readable. If the log was not restored, or was restored but no record of the log exists in V$ARCHIVED_LOG, then contact Oracle support.

##### RMAN-06056: could not access datafile name

Cause: A backup could not proceed because the datafile header could not be read or the header was not valid.

Action: Make the datafile accessible or skip it.

##### RMAN-06066: the target database must be mounted when issuing a RECOVER command

Cause: A RECOVER command was issued, but the target database controlfile is not mounted.

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

##### RMAN-06067: RECOVER DATABASE required with a backup or created controlfile

Cause: The controlfile has been restored from a backup or was created via ALTER DATABASE CREATE CONTROLFILE.

Action: Use the RECOVER DATABASE command to perform the recovery.

##### RMAN-06068: recovery aborted because of missing datafiles

Cause: This error should be accompanied by one or more instances of message RMAN-06094.: Refer to message RMAN-06094.: RMAN-06069: controlfile is missing the filename for datafile name

Cause: Media recovery of a backup controlfile added this datafile to the controlfile, but it does not set the filename because that is unsafe.

Action: If the datafile is on disk, then issue ALTER DATABASE RENAME to correct the controlfile. Otherwise, RESTORE the datafile, and then use SWITCH to make it known to the controlfile. If the tablespace containing this datafile will be dropped, then reissue the RECOVER command with a SKIP clause to skip recovery of this tablespace.

##### RMAN-06071: could not open datafile name

Cause: An error was encountered when trying to open the specified datafile.

Action: Ensure that the datafile exists and is accessible.

##### RMAN-06072: I/O error occurred when reading file header for datafile name

Cause: An I/O error occurred.

Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.

##### RMAN-06073: file header is corrupt for datafile name

Cause: ORACLE detected a corruption in the file header. A media failure has probably occurred.

Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.

##### RMAN-06074: file name is not an ORACLE datafile

Cause: The file header indicates that this file is not a datafile. The file may have been overlaid or corrupted.

Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.

##### RMAN-06075: datafile name does not belong to this database

Cause: The file header indicates that this file belongs to some other ORACLE database.

Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.

##### RMAN-06076: datafile name contains wrong datafile

Cause: The datafile header indicates the file contains a different datafile number.

Action: RESTORE the datafile, and then retry the RECOVER command.

##### RMAN-06077: datafile name is a different version than contained in the controlfile

Cause: The controlfile entry for this datafile specifies a different version of this datafile. Different versions of a datafile can exist when a tablespace is dropped, and a new tablespace is created which reuses the same datafile numbers.

Action: If the datafile is correct, the fix the controlfile by using the SWITCH command. Otherwise, RESTORE the correct version of this datafile and retry the RECOVER command.

##### RMAN-06078: the controlfile is older than datafile name

Cause: The controlfile appears to be older than the specified datafile, but it is not marked as a backup controlfile. This indicates that the controlfile has been replaced with an older version. This error does not occur when a backup controlfile which was created via Recovery Manager or the ALTER DATABASE BACKUP CONTROLFILE command is restored because such controlfiles are marked as backups.

Action: RESTORE a controlfile and perform RECOVER DATABASE.

##### RMAN-06079: database must be mounted to perform recovery

Cause: A RECOVER command was issued, but the target database is not mounted.

Action: Issue ALTER DATABASE MOUNT.

##### RMAN-06081: error reading datafile header for datafile name, code num

Cause: X$KCVFH returned the specified code in the HXERR column when it was queried for the specified datafile.

Action: Ensure the datafile exists and is readable. Using a more recent release of Recovery Manager may return a more meaningful error message. If you do not have a more recent version of Recovery Manager, contact Oracle support.

##### RMAN-06082: datafilecopy tag name is ambiguous

Cause: The specified tag refers to multiple datafile copies belonging to different datafiles.

Action: Specify the datafilecopy by filename rather than by tag.

##### RMAN-06083: error when loading stored script name

Cause: The recovery catalog database returned an error. This error explains the cause of the problem.

Action: Correct the problem and retry.

##### RMAN-06084: the target database may not be mounted when issuing REPLICATE

Cause: A REPLICATE command was issued, but the target database is already mounted.

Action: Dismount the target database controlfile by issuing ALTER DATABASE CLOSE and ALTER DATABASE DISMOUNT via Enterprise Manager or Server Manager.

##### RMAN-06085: must use SET NEWNAME command to restore datafile name

Cause: A RESTORE command for the specified datafile could not find a destination name for the specified datafile.

Action: Add a SET NEWNAME command prior to the RESTORE command to specify the restore destination for this file.

##### RMAN-06086: offline files may only be skipped in a datafile backup set

Cause: The SKIP OFFLINE option was specified for an archivelog backup set.

Action: Use this option only for datafile backup sets.

##### RMAN-06087: read-only files may only be skipped in a datafile backup set

Cause: The SKIP READONLY option was specified for an archivelog backup set.

Action: Use this option only for datafile backup sets.

##### RMAN-06088: datafile copy name not found or out of sync with catalog

Cause: The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database.

Action: Re-catalog the file and retry the operation.

##### RMAN-06089: archived log name not found or out of sync with catalog

Cause: The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database.

Action: Re-catalog the file and retry the operation.

##### RMAN-06090: error while looking up controlfile copy: name

Cause: An error occurred while looking up the specified controlfile copy in the recovery catalog or target database controlfile.

Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the filename is entered correctly. If the controlfile copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

##### RMAN-06091: no channel allocated for delete backup piece

Cause: No channel was allocated before executing the CHANGE BACKUPPIECE DELETE command.

Action: Use ALLOCATE CHANNEL FOR DELETE before deleting backup pieces.

##### RMAN-06092: error while looking up backup piece

Cause: An error occurred while looking up the specified backup piece in the recovery catalog or target database controlfile.

Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the name or key is entered correctly. If the backup piece was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

##### RMAN-06093: recovery catalog contains obsolete version of datafile name

Cause: The specified datafile number was dropped and then reused. The controlfile mounted by the target database contains the newer version of the datafile, but the recovery catalog contains information about only the older version.

Action: Issue a RESYNC command to update the recovery catalog, then reissue the failing command. If the error persists, contact Oracle support.

##### RMAN-06094: datafile name must be restored

Cause: A RECOVER command was issued, and the recovery catalog indicates the specified datafile should be part of the recovery, but this datafile is not listed in the controlfile, and cannot be found on disk.

Action: Issue a RESTORE command for this datafile, using the same UNTIL clause specified to the RECOVER command (if any), then reissue the RECOVER.

##### RMAN-06095: a backup controlfile must be restored to recover datafile name

Cause: The controlfile currently mounted by the target database contains a newer incarnation of a datafile number than the recovery catalog indicates is appropriate for the point-in-time being recovered to.

Action: Restore the controlfile, using the same UNTIL clause specified on the failing RECOVER command, then reissue the command. If no controlfile can be restored, then you should issue a CREATE CONTROLFILE command.

##### RMAN-06096: SWITCH for NEWNAME of datafile name to take effect

Cause: A SET NEWNAME was issued for this datafile, but no SWITCH command was issued before the RECOVER command.

Action: Issue a SWITCH command to make the NEWNAME take effect before doing RECOVER.

##### RMAN-06097: text of failing SQL statement: name

Cause: This is an informational message to accompany message RMAN-06003 or RMAN-06004.: No action required.

##### RMAN-06098: the target database must be mounted when issuing a BACKUP command

Cause: A BACKUP command was issued, but the target database controlfile is not mounted.

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

##### RMAN-06100: no channel to restore a backup or copy of datafile name

Cause: A datafile, tablespace, or database restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore.

Action: None - this is an informational message. See message RMAN-06026 for further details.: RMAN-06101: no channel to restore a backup or copy of the controlfile

Cause: A controlfile restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore.

Action: None - this is an informational message. See message RMAN-06026 for further details.: RMAN-06102: no channel to restore a backup or copy of log thread name seq num scn num

Cause: An archivelog restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore.

Action: None - this is an informational message. See message RMAN-06026 for further details.: RMAN-06103: duplicate qualifier found in REPORT command: name

Cause: The indicated qualifier appears more than once in a REPORT qualifier list.

Action: Delete the duplicate qualifier and retry the operation.

##### RMAN-06104: only one of LIKE or ALL may be specified with LIST command

Cause: Only one name specifier (like or all) may be specified in the LIST command qualifier list.

Action: Correct and resubmit the command.

##### RMAN-06105: duplicate qualifier found in LIST command: name

Cause: The indicated qualifier appears more than once in a LIST qualifier list.

Action: Delete the duplicate qualifier and retry the operation.

##### 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 controlfile by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.

##### RMAN-06107: warning - controlfile 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 controlfile is mounted.

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

##### RMAN-06124: error while looking up datafilecopy key: name

Cause: An error occurred while looking up the specified datafilecopy key in the recovery catalog.

Action: This error is accompanied by other errors describing the reason for the failure.

##### RMAN-06125: error while looking up archivelog key: name

Cause: An error occurred while looking up the specified archivelog key in the recovery catalog.

Action: This error is accompanied by other errors describing the reason for the failure.

##### RMAN-06126: skipping offline file name

Cause: The indicated file will not be included in the backup set because it is offline and the SKIP OFFLINE option was specified.

Action: No action required. This is an informational message only.

##### RMAN-06127: skipping read only file name

Cause: The indicated file will not be included in the backup set because it is read only and the SKIP READONLY option was specified.

Action: No action required. This is an informational message only.

##### RMAN-06128: skipping inaccessible file name

Cause: The indicated file will not be included in the backup set because it could not be read, and the SKIP INACCESSIBLE option was specified.

Action: No action required. This is an informational message only.

##### RMAN-06129: invalid reserved channel ID: num

Cause: The specified channel id is invalid. DELETE and DEFAULT are reserved channel names and may not be specified by users.

Action: Specify a different channel ID.

##### RMAN-06130: snapshot controlfile name set to: name

Cause: The snapshot controlfile name was not set, so RMAN set it to the default value.

Action: No action required. This is an informational message only.

##### RMAN-06131: skip offline/readonly only allowed with current controlfile

Cause: The SKIP OFFLINE and SKIP READONLY options are only permitted when the target database controlfile is current. When the target controlfile is not current, it is not possible to obtain a datafile's offline/readonly status.

Action: Remove the skip option or mount a current controlfile on the target database.

##### RMAN-06132: cannot backup datafile name because it is not in the controlfile

Cause: A backup command was issued that includes the specified datafile, but the datafile is not listed in the controlfile. The controlfile is not current (it is a backup or a created controlfile).

Action: Recover the controlfile to make it current, then retry the backup command.

##### RMAN-06133: recovery catalog may have obsolete data for datafile name

Cause: A RESTORE UNTIL was issued, and the recovery catalog choose an older incarnation of the datafile than is listed in the controlfile.

Action: If the recovery catalog has correct data for the datafile, then restore a backup controlfile using the same UNTIL clause, then retry the datafile restore. Otherwise, restore a backup of the incarnation of the datafile listed in the controlfile.

##### RMAN-06134: host command complete

Cause: An operating system command has completed.

Action: None - this is an informational message.

##### RMAN-06135: error executing host command: name

Cause: A host command returned a non-zero return code.

Action: Correct the offending command.

##### RMAN-06136: ORACLE error from clone database: name

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

##### RMAN-06137: must have recovery catalog for REPORT SCHEMA AT TIME

Cause: A 'REPORT SCHEMA at_clause' command was issued, but there is no recovery catalog database.

Action: If you are not using a recovery catalog, then you may only issue the 'REPORT SCHEMA' command with no at_clause.

##### RMAN-06138: controlfile not mounted - must specify AT clause with REPORT command

Cause: A 'REPORT SCHEMA' with no at_clause was issued, and there is no recovery catalog, and there is also no controlfile mounted at the target database, so there is no place to get the information about the current list of files comprising the database.

Action: Use a recovery catalog or mount a controlfile at the target database.

##### RMAN-06139: warning - controlfile is not current for REPORT SCHEMA

Cause: A 'REPORT SCHEMA' with no at_clause was issued, and there is no recovery catalog, and the controlfile mounted by the target instance is not current, so the information about the current list of datafiles may not be current.

Action: Use a recovery catalog or mount a current controlfile.

##### RMAN-06140: cannot specify TAG option with LIST INCARNATION

Cause: The TAG option was specified with LIST INCARNATION. This is not permitted because there is no TAG associated with a database incarnation.

Action: Remove the TAG option and re-run the LIST command.

##### RMAN-06141: cannot specify TAG option with ARCHIVELOG list

Cause: The TAG option was specified with an ARCHIVELOG list. This is not permitted because there is no TAG associated with archivelog copies or backup sets.

Action: Remove the TAG option and re-run the LIST command.

##### RMAN-06142: DEVICE TYPE may only be specified with LIST BACKUPSET

Cause: The DEVICE TYPE option was specified with a list COPY or INCARNATION command. This is not permitted because only backup sets may reside on different types of devices.

Action: Remove the DEVICE TYPE option and re-run the LIST command.

##### RMAN-06143: ALL or LIKE may only be specified with LIST COPY

Cause: The ALL or LIKE option was specified with a list BACKUPSET or INCARNATION command. This is not permitted because only copies of datafiles or archivelogs have filenames that may be tested with a LIKE operand.

Action: Remove the LIKE or ALL option and re-run the LIST command.

##### RMAN-06144: FROM or UNTIL may not be specified with LIST INCARNATION

Cause: The FROM or UNTIL option was specified with LIST INCARNATION. This is not permitted because there is no time associated with a database incarnation.

Action: Remove the FROM or UNTIL option and re-run the LIST command.

##### RMAN-06145: controlfile is not current - obsolete file list may be incomplete

Cause: A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. If the mounted controlfile is not current, it may not be possible to determine if a satisfactory backup exists for files which have been offline since the last OPEN RESETLOGS.

Action: No action need be taken - this is an informational message only. To ensure a complete report of obsolete backups, mount a current controlfile.

##### RMAN-06146: changes found for file %d beyond offline SCN

Cause: A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. A backup was found for a file which is shown as offline in the target database controlfile, but the backup contains changes beyond the SCN when the file went offline. This is most likely because the target database controlfile is not really current, but is a restored copy of an older controlfile.

Action: Mount a current controlfile or a backup controlfile.

##### RMAN-06147: no obsolete backups found

Cause: A CHANGE or REPORT command could find no files that meet the specified criteria for obsoleteness.

Action: None - this is an informational message.

##### RMAN-06148: redundancy count must be greater than zero

Cause: The REDUNDANCY operand specified for a CHANGE or REPORT OBSOLETE command was zero.

Action: Specify a REDUNDANCY operand of 1 or greater.

##### RMAN-06149: must have recovery catalog for SET CLONENAME

Cause: A 'SET CLONENAME' command was issued, but there is no recovery catalog database.

Action: If a recovery catalog exists, then specify the RCVCAT option when starting Recovery Manager, otherwise the 'SET CLONENAME' command may not be used.

##### RMAN-06150: clone name for datafile name set to:name

Cause: This message is issued in response to a SET CLONENAME command.

Action: None - this is an informational message.

##### RMAN-06151: datafile name creation scn name

Cause: This is an informational message. It should be accompanied by other messages.

Action: none

##### RMAN-06152: CHANGE VALIDATE not supported for backup pieces or backup sets.

Cause: The CHANGE VALIDATE command may not be performed on a backup piece.

Action: The CHANGE VALIDATE command may only be performed on datafile copies and archived logs. To verify the contents of a backup set, use the VALIDATE BACKUPSET command, which must be use inside of an RMAN RUN command.

##### RMAN-06153: validation failed for datafile copy

Cause: The CHANGE DATAFILE COPY VALIDATE command found that the datafile copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog.

Action: None - this is an informational message.

##### RMAN-06154: validation succeeded for datafile copy

Cause: The CHANGE DATAFILE COPY VALIDATE command found that the datafile copy still matches its data in the recovery catalog.

Action: None - this is an informational message.

##### RMAN-06155: validation failed for controlfile copy

Cause: The CHANGE CONTROLFILECOPY VALIDATE command found that the controlfile copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog.

Action: None - this is an informational message.

##### RMAN-06156: validation succeeded for controlfile copy

Cause: The CHANGE CONTROLFILECOPY VALIDATE command found that the controlfile copy still matches its data in the recovery catalog.

Action: None - this is an informational message.

##### RMAN-06157: validation failed for archived log

Cause: The CHANGE ARCHIVELOG VALIDATE command found that the archived log could not be found or no longer contains the same data, so its record was deleted from the recovery catalog.

Action: None - this is an informational message.

##### RMAN-06158: validation succeeded for archived log

Cause: The CHANGE ARCHIVED LOG VALIDATE command found that the archived log still matches its data in the recovery catalog.

Action: None - this is an informational message.

##### RMAN-06159: error while looking up backup set

Cause: An error occurred while looking up the specified backup set in the recovery catalog or target database controlfile.

Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the key is entered correctly. If the backup set was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

##### RMAN-06160: no backup pieces found for backup set key: name

Cause: No backup pieces for the requested backup set were found in the recovery catalog, or the target database controlfile.

Action: Specify an existing backup set.

##### RMAN-06161: error when inspecting clone filename: name

Cause: This error is accompanied by other errors explaining the cause.

Action: Correct the clonename if it is wrong via the SET CLONENAME command.

##### RMAN-06162: sql statement: name

Cause: This is the SQL statement about to be executed for a SQL command.

Action: None, informational message only.

##### RMAN-06163: some datafiles cannot be recovered, aborting the RECOVER command

Cause: This message should be followed by one or more RMAN-06162 or RMAN-06164 messages.: Use the additional messages to pinpoint the error.

##### RMAN-06164: no channel of required type allocated to recover datafile name

Cause: A RECOVER command could not proceed because incremental backup sets or archive log backup sets exist on a device type that has not been allocated.

Action: Use the LIST command to determine which device type is needed, then allocate a channel of that type.

##### RMAN-06173: no SET NEWNAME command has been issued for datafile name when restore clone

Cause: Clone type was specified for the controlfile, but no SET NEWNAME command has been previously issued for a datafile.

Action: Issue SET NEWNAME command for every datafile in the recovery set.

##### RMAN-06174: not connected to clone database

Cause: A clone command was issued but no connection to the clone database has been established.

Action: Issue a CONNECT CLONE command to connect to the clone database.

##### RMAN-06175: deleted script: name

Cause: A DELETE SCRIPT command was executed.

Action: No action required.

##### RMAN-07000: execution layer initialization failed

Cause: The initialization failed.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

##### RMAN-07001: could not open channel num

Cause: An ALLOCATE CHANNEL command could not be processed.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

##### RMAN-07004: unhandled exception during command execution on channel name

Cause: An error occurred during command execution.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

##### RMAN-07005: error during channel cleanup

Cause: An error occurred while releasing resources associated with the specified channel.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

##### RMAN-07006: unhandled exception during cleanup on channel name

Cause: An exception handling error occurred on the specified channel.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

##### RMAN-07007: cannot allocate more than num channels

Cause: The maximum number of RMAN channels has been exceeded. Note that one channel is reserved for RMAN.

Action: Allocate fewer channels. Contact Oracle if you have a need for more channels in a single job.

##### RMAN-08000: channel num: copied datafile number num

Cause: A datafile copy operation completed successfully.

Action: No action required. This is an informational message only.

##### RMAN-08001: restore not complete

Cause: All of the backup pieces have been successfully applied, but X$DBMS_BACKUP_RESTORE indicates that the restore conversation is not complete. This usually means that the backup set contained corrupt data.

Action: Restore the files from a different backup set, if possible. The Recovery Manager CHANGE BACKUPPIECE UNAVAILABLE can be used to prevent Recovery Manager from attempting to restore from the corrupt backup piece(s).

##### RMAN-08032: channel num: recid num stamp name does not match recovery catalog

Cause: The record that identifies the source file for a copy or backup database does not contain the same data as is stored in the recovery catalog.

Action: Perform a full resync and retry the operation. If the problem persists, then contact Oracle.

##### RMAN-08036: channel num: could not create controlfile record for name name

Cause: The record identifying the named file was no longer present in the target database controlfile, and repeated attempts to inspect the file were unsuccessful in creating the record. This could be because the circular-reuse section of the controlfile which holds information about the specified type of file is too small and there is other database activity which is causing the record to be overwritten before it can be used.

Action: Try increasing either the size of the controlfile circular-reuse section for this file type (datafile copy or archived log, as indicated in the error message, or the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter. If neither of those remedies works then contact Oracle.

##### RMAN-08037: channel name: unexpected validation return code num

Cause: This is an internal error that should never be issued.

Action: Contact Oracle Worldwide Support.

##### RMAN-08056: channel num: skipping datafile num because it has not changed

Cause: The specified datafile has not had its checkpoint advanced since the previous backup, therefore it does not need a new incremental backup.

Action: No action required. This is an informational message only.

##### RMAN-08057: channel num: backup cancelled because all files were skipped

Cause: All datafiles for this incremental backup set were skipped, therefore no backup set is created.

Action: No action required. This is an informational message only.

##### RMAN-10000: error parsing target database connect string name

Cause: An invalid target connect string was supplied.

Action: Specify a valid connect string and re-run the job.

##### RMAN-10001: error parsing recovery catalog connect string name

Cause: An invalid recovery catalog connect string was supplied.

Action: Specify a valid connect string and re-run the job.

##### RMAN-10002: ORACLE error: num

Cause: The specified Oracle error was received.

Action: This message should be accompanied by other error message(s) indicating the cause of the error. Check the accompanying errors.

##### RMAN-10003: unable to connect to target database using connect string name

Cause: Recovery manager was unable to connect to the target database.

Action: This message should be accompanied by other error message(s) indicating the cause of the error. Ensure that the target database is started, and that the connect string is valid.

##### RMAN-10004: unable to connect to recovery catalog using connect string: name

Cause: Recovery manager was unable to connect to the recovery catalog.

Action: Ensure that the recovery catalog is started, and that the connect string is valid. This message should be accompanied by other error message(s) indicating the cause of the error.

##### RMAN-10005: error opening cursor

Cause: An error was received while trying to open a cursor. This message should be accompanied by other error message(s) indicating the cause of the error.

Action: If the associated Oracle error message indicates a condition that can be corrected, do so, otherwise contact Oracle Worldwide Support.

##### RMAN-10006: error running sql statement:name

Cause: An error message was received while running the SQL statement shown.

Action: If the associated Oracle error message indicates a condition that can be corrected, do so, otherwise contact Oracle.

##### RMAN-10007: error closing cursor

Cause: An error was received while trying to close a cursor. This message should be accompanied by other error message(s) indicating the cause of the error.

Action: If the associated Oracle error message indicates a condition that can be corrected, do so, otherwise contact Oracle.

##### RMAN-10008: could not create channel context

Cause: An error was received while trying create a channel context. This message should be accompanied by other error message(s) indicating the cause of the error.

Action: If the associated Oracle error message indicates a condition that can be corrected, do so, otherwise contact Oracle.

##### RMAN-10009: error logging off of Oracle

Cause: An error was received while disconnecting from Oracle. This message should be accompanied by other error message(s) indicating the cause of the error.

Action: No action required. This message is informational only.

##### RMAN-10010: error while checking for RPC completion

Cause: Recovery Manager's channel context had an error while checking to see if a remote procedure call had completed. This message should be accompanied by other error message(s) indicating the cause of the error.

Action: If other error messages indicate a condition that can be corrected, do so, otherwise contact Oracle.

##### RMAN-10011: synchronization error while polling for rpc name, action=name

Cause: Recovery Manager could not synchronize properly with a remote procedure call.

Action: This is an internal error that should not be issued. Contact Oracle Worldwide Support.

##### RMAN-10012: KGU error: name

Cause: An error occurred while initializing the KGU subsystem.

Action: This is an internal error that should not be issued. Contact Oracle Worldwide Support.

##### RMAN-10013: error initializing PL/SQL

Cause: An error occurred while initializing the PL/SQL subsystem.

Action: This is an internal error that should not be issued. Contact Oracle Worldwide Support.

##### RMAN-10014: PL/SQL error name on line num column num: name

Cause: This is a PL/SQL error.

Action: The text of this message will be issued by the PL/SQL subsystem. See the PL/SQL error message manual.

##### RMAN-10015: error compiling PL/SQL program

Cause: An error occurred while compiling a PL/SQL program.

Action: This is an internal error that should not be issued. Contact Oracle Worldwide Support.

##### RMAN-10016: error creating PL/SQL runtime context

Cause: An error occurred while creating a PL/SQL runtime context.

Action: This is an internal error that should not be issued. Contact Oracle Worldwide Support.

##### RMAN-10017: error initializing channel context

Cause: An error was received while trying initialize a channel context. This message should be accompanied by other error message(s) indicating the cause of the error.

Action: If other error messages indicate a condition that can be corrected, do so, otherwise contact Oracle Worldwide Support.

##### RMAN-10018: error cleaning up channel context

Cause: An error was received during inter-step cleanup of a channel context.

Action: This is an internal error that should not be issued. Contact Oracle Worldwide Support.

##### RMAN-10020: error initializing Recovery Manager execution layer

Cause: An error was received while initializing the Recovery Manager execution layer in preparation for running a job. This message should be accompanied by other error message(s) indicating the cause of the error.

Action: If other error messages indicate a condition that can be corrected, do so, otherwise contact Oracle Worldwide Support.

##### RMAN-10022: error in system-dependent sleep routine

Cause: An error was received while waiting for a remote RPC to complete. The error occurred in the system-dependent sleep routine.

Action: This is an internal error that should not be issued. Contact Oracle Worldwide Support.

##### RMAN-10023: RPC attempted to unrecognized package

Cause: The Recovery Manager internal RPC router received a package name that it could not understand.

Action: This is an internal error that should not be issued. Contact Oracle Worldwide Support.

##### RMAN-10024: error setting up for RPC polling

Cause: The Recovery Manager could not create the RPC polling context which is required to test for RPC completion. This message should be accompanied by other error message(s) indicating the cause of the error.

Action: If other error messages indicate a condition that can be corrected, do so, otherwise Contact Oracle Worldwide Support.

##### RMAN-10025: connection is already registered for events

Cause: The Recovery Manager could not enable the target database connection to test for RPC completion.

Action: This is an internal error that should not be issued. Contact Oracle Worldwide Support.

##### RMAN-10026: network error name-num occurred registering connection

Cause: An network error occurred while attempting to register the target database connection to test for RPC completion.

Action: This is an internal error that should not be issued. The message numbers are issued by the Net8 layer. Contact Oracle Worldwide Support.

##### RMAN-10027: could not locate network layer context

Cause: Recovery Manager could not locate a necessary context area while attempting to register the target database connection to test for RPC completion.

Action: This is an internal error that should not be issued. Contact Oracle Worldwide Support.

##### RMAN-10028: network error name-num occurred during remote RPC

Cause: An network error occurred while waiting for a remote RPC to complete.

Action: This is an internal error that should not be issued. The message numbers are issued by the Net8 layer. Contact Oracle Worldwide Support.

##### RMAN-10029: unexpected return code num from PL/SQL execution

Cause: PL/SQL returned an unexpected return code while executing one channel program.

Action: This is an internal error that should not be issued. Contact Oracle Worldwide Support.

##### RMAN-10030: RPC call appears to have failed to start on channel num

Cause: An RPC to a target database instance was issued, but was not observed to start within 5 timeouts.

Action: This error is probably accompanied by other error messages giving the precise cause of the failure.

##### RMAN-10031: ORA-num occurred during call to name.name

Cause: An RPC to the target database or recovery catalog database encountered an error.

Action: This error is accompanied with the error message from the server where the error occurred.

##### RMAN-10032: unhandled exception during execution of job step num: name

Cause: An unhandled PL/SQL exception occurred during a job step.

Action: This error is accompanied by the error messages describing the exception.

##### RMAN-10033: error during compilation of job step num: name

Cause: PL/SQL detected a problem during the compilation of a job step.

Action: This error message is accompanied by the error messages describing the exception.

##### RMAN-10034: unhandled exception during execution of job step num, error unknown

Cause: PL/SQL detected an unhandled exception during execution of a job step, but no further information is available.

Action: Contact Oracle Worldwide Support.

##### RMAN-10035: exception raised in RPC: name

Cause: A call to a remote package resulted in an exception.

Action: The exception should indicate what went wrong.

##### RMAN-10036: RPC call ok on channel num

Cause: This is just an informational message. It should be preceded by message RMAN-10030.: No action required.

##### RMAN-10037: RPC anomaly detected on channel num, upinblt=num

Cause: This is an debugging message and can be ignored.

Action: No action required.

##### RMAN-10038: database session for channel num terminated unexpectedly

Cause: The database connection for the specified channel no longer exists. Either the session was terminated by some external means or the channel terminated because of an internal error.

Action: Check for an Oracle trace file for detailed information on why the session terminated.

##### RMAN-10039: error encountered while polling for RPC completion on channel num

Cause: This error should be accompanied by other errors giving the cause of the polling error.

Action: No action required.

##### RMAN-11000: message number num not found in recovery manager message file

Cause: Recovery manager message file is out of date.

Action: Make sure that the recovery manager error message file is current and installed in the correct location.

##### RMAN-20000: abnormal termination of job step

Cause: A job step encountered an error and could not recover. This error should be followed by other errors indicating the cause of the problem.

Action: This error should be followed by other errors indicating the cause of the problem.

##### RMAN-20001: target database not found in recovery catalog

Cause: The target database is not found in the recovery catalog.

Action: Make sure that the target database is registered in the recovery catalog.

##### RMAN-20002: target database already registered in recovery catalog

Cause: The target database is already registered in the recovery catalog.

Action: If the target database is really registered, there is no need to register it again. Note that the recovery catalog enforces that all databases have a unique DBID. If the new database was created by copying files from an existing database, it will have the same DBID as the original database and cannot be registered in the same recovery catalog.

##### RMAN-20003: target database incarnation not found in recovery catalog

Cause: Resetlogs change number and/or time of the target database does not match any database version in the recovery catalog.

Action: If the target database was opened with the resetlogs option, then use RESET DATABASE to register the new version.

##### RMAN-20004: target database name does not match name in recovery catalog

Cause: Name of the target database does not match the one stored in the recovery catalog.

Action: This is an internal error, call Oracle Worldwide Support.

##### RMAN-20005: target database name is ambiguous

Cause: Two or more databases in the recovery catalog match the DB_NAME initialization parameter of the instance and the target database is not mounted, so RMAN cannot get its DBID.

Action: Mount the target database then retry the operation.

##### RMAN-20006: target database name is missing

Cause: Target database instance is not started or the DB_NAME initialization parameter is not set.

Action: Start the instance and make sure that the DB_NAME parameter is set.

##### RMAN-20008: database incarnation key is missing

Cause: The database incarnation key was not specified.

Action: Specify a valid database incarnation key.

##### RMAN-20009: database incarnation already registered

Cause: This incarnation of the database is already registered in the recovery catalog.

Action: Informational only. No action required.

##### RMAN-20010: database incarnation not found

Cause: Database incarnation does not match any database incarnation in the recovery catalog.

Action: Specify a valid database incarnation key.

##### RMAN-20011: target database incarnation is not current in recovery catalog

Cause: The database incarnation that matches the RESETLOGS CHANGE number and the time of the mounted target database controlfile does not correspond to the current incarnation of the database.

Action: If RESET DATABASE TO INCARNATION key was used to make an old incarnation current, then restore the target database from a backup that matches the incarnation and mount it. You will need to do STARTUP NOMOUNT before you can restore the controlfile using RMAN. Otherwise use RESET DATABASE TO INCARNATION key make the intended incarnation current in the recovery catalog.

##### RMAN-20029: cannot make a snapshot controlfile

Cause: Another operation that needs the snapshot controlfile is in progress.

Action: Wait until the other operation completes. Then retry the operation.

##### RMAN-20032: checkpoint change# too low

Cause: The recovery catalog has already been resynced from a controlfile that has a higher checkpoint change number. If this is RESYNC CATALOG command then the mounted controlfile has been restored from an old backup. If this RESYNC CATALOG FROM CONTROLFILECOPY command the specified controlfile copy is too old.

Action: If the right controlfile was mounted or specified then RESYNC is not needed. Otherwise mount or specify the correct controlfile and try again.

##### RMAN-20033: controlfile sequence# too low

Cause: The recovery catalog has already been resynced from a controlfile that has a higher checkpoint sequence#. If this is RESYNC CATALOG command then the mounted controlfile has been restored from an old backup. If this RESYNC CATALOG FROM CONTROLFILECOPY command the specified controlfile copy is too old.

Action: If the right controlfile was mounted or specified then RESYNC is not needed. Otherwise mount or specify the correct controlfile and try again.

##### RMAN-20034: resync not needed

Cause: The control file has not changed since the previous resync.

Action: Informational only. No action is needed because the recovery catalog is in sync.

##### RMAN-20201: datafile not found in the recovery catalog

Cause: The specified datafile is not found in the recovery catalog.

Action: Make sure that the datafile name is correct and that the recovery catalog is up-to-date.

##### RMAN-20202: tablespace not found in the recovery catalog

Cause: The specified tablespace is not found in the recovery catalog.

Action: Make sure that the tablespace name is correct and that the recovery catalog is up-to-date.

##### RMAN-20206: log sequence not found in the recovery catalog

Cause: The specified log sequence does not exists in log history of the current database incarnation.

Action: Check the THREAD and LOGSEQ. If the database needs to be recovered to a log sequence number before the current database incarnation, use RESET DATABASE TO INCARNATION command first.

##### RMAN-20207: UNTIL TIME is before resetlogs time

Cause: UNTIL TIME can not be less than the database creation time or resetlogs time.

Action: Check the UNTIL TIME. If the database needs to be restored to an old incarnation, use RESET DATABASE TO INCARNATION command.

##### RMAN-20208: UNTIL change is before resetlogs change

Cause: UNTIL change can not be earlier than the database RESETLOGS change.

Action: Check the UNTIL change. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command.

##### RMAN-20209: duplicate datafile name

Cause: Two datafiles have the same name. This is an internal error.

Action: Contact Oracle Worldwide Support.

##### RMAN-20210: invalid archived log range, thread number is null

Cause: This is an internal error.

Action: Contact Oracle Worldwide Support. This is an internal error

##### RMAN-20215: backup set is missing

Cause: This is an internal error.

Action: Contact Oracle Worldwide Support. This is an internal error

##### RMAN-20216: backup piece is missing

Cause: This is an internal error.

Action: Contact Oracle Worldwide Support. this is an internal error

##### RMAN-20217: datafile not part of the database

Cause: The datafile does not exists or did not exist at until time/scn

Action: Check the datafile name or number. This is an internal error for restore database or tablespace.

##### RMAN-20218: datafile not found in recovery catalog

Cause: This is an internal error.

Action: Contact Oracle Worldwide Support.

##### RMAN-20220: controlfile copy not found in the recovery catalog

Cause: The specified controlfile is not in the recovery catalog or it has been marked deleted.

Action: Check that the filename is correct and retry the operation.

##### RMAN-20221: ambiguous controlfile copy name

Cause: More than one controlfile copy in the recovery catalog matches the specified name.

Action: Use the controlfile copy key to uniquely specify the controlfile copy (not implemented in Beta2).

##### RMAN-20222: datafile name not found in recovery catalog or is ambiguous

Cause: Either:

the specified datafile name is not the name that currently exists in the target database an UNTIL clause was specified and the filename does not correspond to the datafile

Action: Use a datafile number to specify the datafile you want to RESTORE or RECOVER.

##### RMAN-20230: datafile copy not found in the recovery catalog

Cause: The specified datafile is not in the recovery catalog or it has been marked deleted.

Action: Check the datafile copy name or key.

##### RMAN-20231: ambiguous datafilecopy name

Cause: More than one controlfile copy in the recovery catalog matches the specified name.

Action: Use the datafile copy key to uniquely specify the datafile copy.

##### RMAN-20232: tag does not match any datafile copy in the recovery catalog

Cause: The specified TAG does not match any datafile copy in the recovery catalog.

Action: Check the tag.

##### RMAN-20240: archived log not found in the recovery catalog

Cause: The specified archived log was not found in the recovery catalog or it has been marked deleted.

Action: Check the archived log name or key.

##### RMAN-20241: ambiguous archived log name

Cause: More than one archived log in the recovery catalog match the specified name.

Action: Use the archived log key to uniquely specify the archived log.

##### RMAN-20242: specification does not match any archivelog in the recovery catalog

Cause: No archivelogs in the specified archivelog range could be found.

Action: Check the archive log specifier.

##### RMAN-20250: offline range not found in the recovery catalog

Cause: The specified offline was not found in the recovery catalog.

Action: Check that the recovery catalog is current.

##### RMAN-20260: backup piece not found in the recovery catalog

Cause: The specified backup piece is not in the recovery catalog or it has been marked deleted.

Action: Check the backup piece handle or key.

##### RMAN-20261: ambiguous backup piece handle

Cause: More than one backup piece in the recovery catalog matches the specified handle.

Action: Use the backup piece key to uniquely specify the backup piece.

##### RMAN-20270: invalid incremental backup level

Cause: An illegal incremental backup level was requested.

Action: Valid incremental backup levels are 1 through 4. Specify a valid level.

##### RMAN-20271: invalid incremental cumulative option

Cause: An internal error occurred.

Action: Contact Oracle Worldwide Support.

##### RMAN-20272: no parent backup found for the incremental backup

Cause: No available backup or copy that could be used as the parent of the incremental backup was found in the recovery catalog.

Action: Perform a level 0 incremental backup or copy of the datafile first.

##### RMAN-20280: too many device types

Cause: More than 8 device types were allocated.

Action: Make sure that the job allocates at most 8 different device types.

##### RMAN-20298: DBMS_RCVCAT package not compatible with the recovery catalog

Cause: The installed versions of the recovery catalog and the DBMS_RCVCAT package are incompatible.

Action: Check that the recovery catalog packages and schema are installed correctly. It may be necessary to run an upgrade script to upgrade the recovery catalog schema.

##### RMAN-20299: DBMS_RCVMAN package not compatible with the recovery catalog

Cause: The installed versions of the recovery catalog and the DBMS_RCVMAN package are incompatible.

Action: Check that the recovery catalog packages and schema are installed correctly. It may be necessary to run an upgrade script to upgrade the recovery catalog schema.

##### RMAN-20300: operation not supported without the recovery catalog

Cause: An operation that requires a recovery catalog was requested, but no recovery catalog is in use.

Action: If a recovery catalog is available, restart RMAN and specify the a connect string for the recovery catalog database via the RCVCAT parameter.

##### RMAN-20400: stored script not found

Cause: A CREATE SCRIPT or DELETE SCRIPT specified a script name that could not be found.

Action: Check the script name.

##### RMAN-20401: script already exists

Cause: A CREATE SCRIPT was issued, but a script with the specified name already exists.

Action: Use a different name for the script or use REPLACE SCRIPT.

##### RMAN-20501: redo logs from parent database incarnation cannot be applied

Cause: A RESTORE or RECOVER of a datafile was requested, but recovery of the datafile would require applying redo logs that were generated before the most recent OPEN RESETLOGS.

Action: If a full backup or datafilecopy from the current database incarnation exists, ensure that it is marked AVAILABLE, and that a channel of the correct device type is allocated. It may also be necessary to remove the FROM BACKUPSET or FROM DATAFILECOPY or FROM TAG operands if these have been specified.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index