Cause: RMAN was run with input/output being sent to DBMS_PIPE. An error was encountered while reading from or writing to the pipe. This error should be preceded by information describing the error.

Action: RMAN terminates. Refer to the cause/action for the preceding errors.

RMAN-00575 timeout while trying to write to dbms_pipe

Cause: RMAN was running in DBMS_PIPE mode. A timeout occurred while calling DBMS_PIPE.SEND_MESSAGE. This occurs when the pipe is full and no process has dequeued any of the messages. This is usually caused by death of the process that was talking to RMAN.

Action: This message should be accompanied by one or more other error messages indicating the cause of the error.

RMAN-01006 error signalled during parse

Cause: An error was signalled during parsing.

Action: This message should be accompanied by one or more other error messages indicating the cause of the error.

RMAN-01007 at line number column number file: string

Cause: This is an informational message indicating the line and column where a syntax error was detected.

Action: No action required.

RMAN-01008 the bad identifier was: string

Cause: This is an informational message indicating the identifier token that caused a syntax error.

Action: No action required.

RMAN-02000 wrong message file version (msg number not found)

Cause: The RMANXX.MSB file is not the correct version.

Action: Check that the installation was done correctly. The RMAN binary (executable, load module, whatever it is called on your operating system) and the RMANXX.MSB file must be from the same version, release, and patch level.

RMAN-02001 unrecognized punctuation symbol "string"

Cause: An illegal punctuation character was encountered.

Action: Remove the illegal character.

RMAN-02002 unexpected end of input file reached

Cause: This is probably caused by failure to supply the closing quote for a quoted string.

Action: Correct the input.

RMAN-02003 unrecognized character: string

Cause: An input character that is neither an alpha, digit, or punctuation was encountered.

Action: Remove the character.

RMAN-02004 quoted string too big

Cause: A quoted string longer than 2000 bytes was encountered.

Action: This may be caused by a missing close quote. If so, add the missing quote, otherwise shorten the string.

RMAN-02005 token too big

Cause: A token longer than 1000 bytes was encountered.

Action: Tokens must be separated by white space or punctuation. Either add the missing white space or punctuation, or shorten the token.

RMAN-02006 script line too long

Cause: A line longer than 500 bytes was encountered.

Action: Break the line up into shorter lines.

RMAN-03000 recovery manager compiler component initialization failed

Action: This message should be accompanied by one or more other error messages indicating the cause of the error.

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

RMAN-05003 point-in-time recovery is not allowed for tablespace string

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.

RMAN-05004 target database log mode is NOARCHIVELOG

Cause: An attempt was made to apply TSPITR to a database that is in NOARCHIVELOG mode.

Action: If all required archive log files are available to TSPITR, alter the target database log mode to ARCHIVELOG and retry the TSPITR operation. Otherwise, TSPITR cannot be applied to this database.

RMAN-05005 point-in-time recovery is not allowed for re-created tablespace string

Cause: The requested tablespace has been re-created and is not allowed in point-in-time recovery.

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

RMAN-05500 the auxiliary database must be not mounted when issuing DUPLICATE command

Cause: A DUPLICATE command was issued, but the auxiliary database is mounted.

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

Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the file name 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: number

Cause: An invalid incremental backup level was specified.

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

RMAN-06012 channel: string not allocated

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

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

Action: Add a RELEASE CHANNEL command.

RMAN-06014 command not implemented yet: string

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

Action: Avoid using the command.

RMAN-06015 error while looking up datafilecopy name: string

Cause: An error occurred while looking up the specified datafile copy name in the recovery catalog or target database control file.

Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the file name 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: string

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.

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

Action: Delete the duplicate operand.

RMAN-06019 could not translate tablespace name "string"

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

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 auxiliary database

Cause: This is an informational message.

Action: No action is required.

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

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

Action: Use this option only for datafile and control file restores.

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

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

Action: Use this option only for datafile and control file restores.

RMAN-06023 no backup or copy of datafile number 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: No action required. This is an informational message. See message 6026 for further details.

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

Cause: A control file restore could not proceed because no backup or copy of the control 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: No action required. This is an informational message. See message 6026 for further details.

RMAN-06025 no backup of log thread number seq number scn string found to restore

Cause: An archive log 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: No action required This is an informational message. See message 6026 for further details.

RMAN-06026 some targets not found - aborting restore

Cause: Some of the files specified for restore could not be found. Message 6023, 6024, or 6025 is also issued to indicate which files could not be found. Some common reasons why a file cannot 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 archive log record specifier did not match any archive logs in the recovery catalog.

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

Cause: The CHANNEL, TAG, FROM, PARMS, VALIDATE, or CHECK READONLY 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 archive log 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 control file 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 string not allocated

Cause: An RMAN 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 string, found string

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

Action: Install the correct version of RECOVER.BSQ.

RMAN-06036 datafile number is already restored to file string

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: No action required. 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 number

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 string

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

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

RMAN-06041 cannot switch file number to copy of file number

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: string

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: string

Cause: An error occurred while translating an archive log 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 number 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 control file 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: The command BACKUP BACKUPSET was entered. This command is not yet implemented.

Action: Enter a different command.

RMAN-06050 archivelog thread number sequence number is already on disk as file string

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

Action: No action required. 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 number 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.

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

Action: If a copy of the log is available, then add it to the recovery catalog and/or control file 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 string thread string

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 control file. 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 Customer Support.

RMAN-06056 could not access datafile number

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 control file is not mounted.

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

Cause: The control file 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 ORA-06094.

Action: Refer to message ORA-06094.

RMAN-06069 controlfile is missing the filename for datafile string

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

Action: If the datafile is on disk, then issue ALTER DATABASE RENAME to correct the control file. Otherwise, RESTORE the datafile, and then use SWITCH to make it known to the control file. 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-06070 DBWR could not identify datafile string

Cause: DBWR could not find the specified datafile.

Action: Check the location of your datafile.

RMAN-06071 could not open datafile string

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

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 string

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 string 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 string 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 string 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 string is a different version than contained in the controlfile

Cause: The control file 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 control file 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 string

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

Action: RESTORE a control file 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-06080 SWITCH required for datafile string

Cause: The control file record for this datafile is for an older incarnation of the datafile.

Action: Issue a SWITCH command to update the control file before doing RECOVER.

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 newer release of Recovery Manager may return a more meaningful error message. If you have no newer version of Recovery Manager, contact Oracle Customer Support.

RMAN-06082 datafilecopy tag string is ambiguous

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

Action: Specify the datafile copy by file name rather than by tag.

RMAN-06083 error when loading stored script string

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.

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 archive log 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 archive log backup set.

Action: Use this option only for datafile backup sets.

RMAN-06088 datafile copy string 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 resynchronized with the target database.

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

RMAN-06089 archived log string 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 resynchronized with the target database.

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

RMAN-06090 error while looking up controlfile copy: string

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

Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the file name is entered correctly. If the control file 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 maintenance

Cause: A command was entered that requires a maintenance channel, and no maintenance channel is allocated.

Action: Use ALLOCATE CHANNEL FOR MAINTENANCE before deleting backup pieces, or using the CROSSCHECK or DELETE EXPIRED commands.

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 control file.

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.

Cause: The specified datafile number was dropped and then reused. The control file 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 Customer Support.

RMAN-06094 datafile string 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 control file, 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 string

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

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

RMAN-06096 SWITCH required for newname of datafile string 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 new name take effect before doing RECOVER.

RMAN-06097 text of failing SQL statement: string

Cause: This is an informational message to accompany message 6003 or 6004.

Action: 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 control file is not mounted.

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 control file is mounted.

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

RMAN-06108 changed datafile copy unvailable

Cause: This is an informational message.

Action: No action required.

RMAN-06109 changed archivelog unavailable

Cause: This is an informational message.

Action: No action required.

RMAN-06110 changed controlfile copy unavailable

Cause: This is an informational message.

Action: No action required.

RMAN-06111 changed backup piece unavailable

Cause: This is an informational message.

Action: No action required.

RMAN-06112 changed datafile copy available

Cause: This is an informational message.

Action: No action required.

RMAN-06113 changed archivelog available

Cause: This is an informational message.

Action: No action required.

RMAN-06114 changed controlfile copy available

Cause: This is an informational message.

Action: No action required.

RMAN-06115 changed backup piece available

Cause: This is an informational message.

Action: No action required.

RMAN-06116 datafile copy cannot be found on disk, return code string

Cause: The CHANGE DATAFILECOPY AVAILABLE command was used, but the datafilecopy cannot be found on disk.

Action: If the storage containing the datafilecopy has been removed from the host, restore it and retry the command. If the datafilecopy is permanently gone, then issue the CHANGE DATAFILECOPY DELETE command for this datafile.

RMAN-06117 archivelog cannot be found on disk, return code string

Cause: The CHANGE ARCHIVELOG AVAILABLE command was used, but the archive log cannot be found on disk.

Action: If the storage containing the archive log has been removed from the host, restore it and retry the command. If the archive log is permanently gone, then issue the CHANGE ARCHIVELOG DELETE command for this archive log.

RMAN-06118 control file copy cannot be found on disk, return code string

Cause: The CHANGE CONTROLFILECOPY AVAILABLE command was used, but the control file copy cannot be found on disk.

Action: If the storage containing the control file copy has been removed from the host, restore it and retry the command. If the control file copy is permanently gone, then issue the CHANGE CONTROLFILECOPY DELETE command for this datafile.

RMAN-06119 uncataloged datafile copy

Cause: This is an informational message.

Action: No action required.

RMAN-06120 uncataloged archivelog

Cause: This is an informational message.

Action: No action required.

RMAN-06121 uncataloged controlfile copy

Cause: This is an informational message.

Action: No action required.

RMAN-06122 CHANGE BACKUPPIECE UNCATALOG not allowed

Cause: The CHANGE BACKUPPIECE UNCATALOG command was entered. This command is not supported.

Action: Enter a different command.

RMAN-06123 operation not supported without the recovery catalog

Cause: A command was used which requires a connection to a recovery catalog database. The command cannot be used when your backup repository is the target database control file.

Action: If a recovery catalog database is available, then connect to the recovery catalog and retry the command, otherwise enter a different command.

RMAN-06124 error while looking up datafilecopy key: number

Cause: An error occurred while looking up the specified datafile copy 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: number

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

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

RMAN-06126 skipping offline file string

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 string

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 string

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: string

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: string

Cause: The snapshot control file 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 control file is current. When the target control file is not current, it is not possible to obtain a datafile's offline/read-only status.

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

RMAN-06132 cannot backup datafile string 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 control file. The control file is not current (it is a backup or a created control file).

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

RMAN-06133 recovery catalog may have obsolete data for datafile string

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

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

RMAN-06134 host command complete

Cause: An operating system command has completed.

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

RMAN-06135 error executing host command: string

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

Action: Correct the offending command.

RMAN-06136 ORACLE error from auxiliary database: string

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 control file 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 control file 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 control file 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 control file.

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 archive log 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 BACKUP

Cause: The DEVICE TYPE option was specified with a LIST COPY, LIST INCARNATION, CROSSCHECK, or DELETE EXPIRED command. This is not permitted because only backup sets may reside on different types of devices and CROSSCHECK and DELETE EXPIRED commands must use the same device type as was specified in the ALLOCATE CHANNEL FOR MAINTENANCE/DELETE command.

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

RMAN-06143 LIKE may only be specified with LIST COPY

Cause: The LIKE option was specified with a list BACKUP or INCARNATION command. This is not permitted because only copies of datafiles or archive logs have file names that may be tested with a LIKE operand.

Action: Remove the LIKE 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 control file 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. This is an informational message.

Action: No action required. To ensure a complete report of obsolete backups, mount a current control file.

RMAN-06146 changes found for file number 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 control file, but the backup contains changes beyond the SCN when the file went offline. This is most likely because the target database control file is not really current, but is a restored copy of an older control file.

Action: Mount a current control file or a backup control file.

RMAN-06147 no obsolete backups found

Cause: A CHANGE or REPORT command could find no files that meet the specified criteria for obsoleteness. This is an informational message.

Action: No action required.

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 value greater than or equal to 1.

RMAN-06149 must have recovery catalog for SET AUXNAME

Cause: A SET AUXNAME 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 AUXNAME command may not be used.

RMAN-06150 auxiliary name for datafile number set to: string

Cause: This message is issued in response to a SET AUXNAME command. This is an informational message.

Action: No action required.

RMAN-06151 datafile string creation scn string

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

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. This is an informational message.

Action: No action required.

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. This is an informational message.

Action: No action required.

RMAN-06155 validation failed for controlfile copy

Cause: The CHANGE CONTROLFILECOPY VALIDATE command found that the control file copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog. This is an informational message.

Action: No action required.

RMAN-06156 validation succeeded for controlfile copy

Cause: The CHANGE CONTROLFILECOPY VALIDATE command found that the control file copy still matches its data in the recovery catalog. This is an informational message.

Action: No action required.

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. This is an informational message.

Action: No action required.

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. This is an informational message.

Action: No action required.

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 control file.

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: number

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

Action: Specify an existing backup set.

RMAN-06161 error when inspecting auxiliary filename: string

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

Action: Correct the auxiliary file name if it is wrong via the SET AUXNAME command.

RMAN-06162 sql statement: string

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

Action: No action required.

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

Cause: This message should be followed by one or more 6162 or 6164 messages.

Action: Refer to the accompanying messages.

RMAN-06164 no channel of required type allocated to recover datafile number

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-06165 datafile string is too old to recover, restore a more recent copy

Cause: The archived logs and/or incremental backup sets required to recover the datafile do not exist, but a more recent backup of the datafile exists which can be recovered.

Action: Issue a RESTORE for the datafile, then reissue the RECOVER command.

RMAN-06166 datafile string cannot be recovered

Cause: Incremental backups or archived redo logs needed to recover the datafile cannot be found, and no recoverable full backup or datafile copy exists.

Action: Use the LIST command to see if there is a backup set or datafile copy that can be made AVAILABLE. If not, then the datafile is unrecoverable. If a full or datafile copy exists, then a point-in-time recovery may be possible.

RMAN-06167 already connected

Cause: A CONNECT command was issued, but RMAN is already connected to the specified database.

Action: RMAN has no DISCONNECT command, so to connect to a different instance, exit RMAN and start it again.

RMAN-06168 no backup pieces with this tag found: string

Cause: A tag was used to specify a list of backup pieces, but no backup pieces with this tag could be found.

Cause: This offline range is needed for recovering the specified datafile, but the offline range record has aged out of the current control file and no control file copy with the record could be accessed. At least one control file copy containing the offline range was found in the recovery catalog and was in AVAILABLE status.

Action: Query the RC_CONTROLFILE_COPY view for the names of all control file copies, then issue a CHANGE CONTROLFILECOPY... VALIDATE; command for them. Then reissue the RECOVER command.

RMAN-06171 not connected to target database

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

Action: Issue a CONNECT TARGET command to connect to the target database.

RMAN-06172 not connected to recovery catalog database

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

Action: Issue a CONNECT RCVCAT command to connect to the recovery catalog database. If you are not have a recovery catalog, then you must use the NOCATALOG option when starting RMAN.

RMAN-06173 no set newname command has been issued for datafile string when restore auxiliary

Cause: Auxiliary type was specified for the control file, 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 auxiliary database

Cause: A auxiliary command was issued but no connection to an auxiliary database has been established.

Action: Issue a CONNECT AUXILIARY command to connect to the auxiliary database.

RMAN-06175 deleted script: string

Cause: A DELETE SCRIPT command was executed.

Action: No action required.

RMAN-06176 no recovery required; all files are readonly or offline

Cause: A RECOVER DATABASE command does not need to recover any files because all of the files to be recovered are offline or read only. This can only occur when the SKIP clause includes the system tablespace. This is an informational message.

Cause: A RESTORE command does not need to restore any files, because all of the files to be restored are offline, read only, or are already restored to their correct destinations. This is an informational message.

Action: No action required.

RMAN-06178 datafile number not processed because file is offline

Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is offline clean at the desired point in time. This is an informational message.

Action: No action required.

RMAN-06179 datafile number not processed because file is read only

Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is part of a read-only tablespace at the desired point in time. This is an informational message.

Cause: This version of Recovery Manager is incompatible with the indicated database or the DBMS_BACKUP_RESTORE package installed in the indicated database.

Action: If the database has been upgraded from an earlier version, ensure that the CATXXXX.SQL script has been run successfully. Re-install DBMSBKRS.SQL and PRVTBKRS.PLB if necessary. Otherwise, use a version of RMAN within the range specified in the error message.

RMAN-06186 PL/SQL package string.string version string in string database is too old

Cause: The specified PL/SQL package is a version that is too old to work with this version of the Recovery Manager (RMAN).

Action: If the database indicated is RCVCAT, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN.

RMAN-06187 controlfile copy string 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 resynchronized with the target database.

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

RMAN-06188 cannot use command when connected to target database

Cause: An attempt was made to issue a command that can be used only when there is no connection to the target database.

Action: Avoid using the command, or restart RMAN and use the command before connecting to the target database.

RMAN-06189 current DBID number does not match target mounted database (number)

Cause: SET DBID was used to set a DBID that does not match the DBID of the database to which RMAN is connected.

Action: If the current operation is a restore to copy the database, do not mount the database. Otherwise, avoid using the SET DBID command, or restart RMAN.

RMAN-06190 PL/SQL package string.string version string in string database is not current

Cause: RMAN detected an old version of the specified package. RMAN will execute in backwards-compatible mode.

Action: No action is required, but certain features and bug fixes may not be available when RMAN runs in backwards-compatible mode. If the database is RCVCAT, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN. The files that must be run to upgrade the target or auxiliary database are DBMSRMAN.SQL and PRVTRMAN.PLB.

RMAN-06191 PL/SQL package string.string version string in string database is too new

Cause: RMAN detected an incompatible version of the specified package.

Action: Use a newer version of Recovery Manager. Message 6439 indicates the minimum required version of Recovery Manager.

RMAN-06193 connected to target database (not started)

Cause: The database must be started before any other RMAN commands are issued. This is an informational message.

Action: No action required.

RMAN-06194 target database instance not started

Cause: A command was issued that requires the target database instance be started.

Action: Issue a STARTUP command to start the instance.

RMAN-06195 auxiliary database not started

Cause: A command was issued that requires the auxiliary database instance be started.

Action: Issue a STARTUP AUXILIARY command.

RMAN-06196 Oracle instance started

Cause: A STARTUP command completed successfully. This is an informational message.

Cause: This message is issued in response to a LIST COPY OF ARCHIVELOG command. 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 archived log:

Key: This is the unique key which identifies this archived log in the recovery catalog. This value can be used in a CHANGE command to change the status of the log. If the target database control file is being used as the recovery catalog, then this field is zero.

Thrd: This is the thread number of the log.

Seq: This is the sequence number, within the thread, of the log.

S: This is the status of the file. Possible values are:

A - Available,

U - Unavailable

D - Deleted 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 log was archived or copied. This column will be printed in the default Oracle date format, unless overridden with a NLS_DATE_FORMAT environment variable.

Cause: This message is issued in response to a LIST COPY OF DATABASE/TABLESPACE/DATAFILE command. 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 datafile copy:

Key: This is the unique key which identifies this datafile copy in the recovery catalog. This value can be used in a CHANGE command to change the status of the copy. 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. S: This is the status of the file. Possible values are:

A - Available

U - Unavailable

D - Deleted 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 datafile copy 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 datafile copy. The file contains all changes made at or before this SCN.

Cause: This message is issued in response to a LIST BACKUP OF ARCHIVELOG command. If a recovery catalog is in use, then the information comes from the recovery catalog, otherwise it comes from the target database control file. To be included in the report, at least one complete copy of the backup set must exist. If the DEVICE TYPE option is specified on the report command, then the list includes only those backup sets which reside on the specified devices, otherwise all available backup sets are listed. The following fields are shown for each archive log which is included in a backup set:

Key: This is the unique key which identifies this backup set in the recovery catalog. If the target database control file is being used as the recovery catalog, then this field is a unique identifier which identifies this backup set in the target database control file.

Thrd: This is the thread number of the log.

Seq: This is the sequence number, within the thread, of the log.

Completion time: This is the date and time when the backup set was created. This column will be printed in the default Oracle date format, unless overridden with a NLS_DATE_FORMAT environment variable.

Cause: This message is issued in response to a LIST BACKUP OF DATABASE/TABLESPACE/DATAFILE command. If a recovery catalog is in use, then the information comes from the recovery catalog, otherwise it comes from the target database control file. To be included in the report, at least one complete copy of the backup set must exist. If the DEVICE TYPE option is specified on the report command, then the list includes only those backup sets which reside on the specified devices, otherwise all available backup sets are listed. The following fields are shown for each datafile which is included in a backup set:

Key: This is the unique key which identifies this backup set in the recovery catalog. If the target database control file is being used as the recovery catalog, then this field is a unique identifier which identifies this backup set in the target database control file.

File: The file number of the file that was backed up.

Type: The type of backup. Possible values are:

Full: full (or an incremental level 0) backup.

Incremental: incremental backup

Cumulative: cumulative incremental backup

LV: This is the incremental backup level.

Completion time: This is the date and time when the backup set was created. This column will be printed in the default Oracle date format, unless overridden with a NLS_DATE_FORMAT environment variable.

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-06260 Report of files that need more than number incrementals during recovery

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.

Cause: This message is issued in response to a LIST BACKUP DATABASE/TABLESPACE/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.

S: 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 required.

RMAN-06400 database opened

Cause: This is an informational message.

Action: No action required.

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-06402 Oracle instance shut down

Cause: This is an informational message.

Action: No action required.

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 been shut down. Other error messages should identify exactly which database is the problem.

Action: Start the database that is causing the problem.

RMAN-06404 database dismounted

Cause: This is an informational message.

Action: No action required.

RMAN-06405 database closed

Cause: This is an informational message.

Action: No action required.

RMAN-06406 deleted archivelog

Cause: This is an informational message.

Action: No action required.

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 required.

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-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-06411 duplex setting out of range (1-4): number

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

Action: Use a value in the specified range.

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-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-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-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-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.

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-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-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-06421 sent command to channel: string

Cause: This is an informational message.

Action: No action required.

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-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-06424 error while looking up proxy copy

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

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 proxy copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06425 datafile_pathname_not_available

Cause: This is an informational message.

Action: No action required.

RMAN-06426 RECOVERY_CATALOG_OWNER role must be granted to user string

Cause: The CREATE CATALOG or UPGRADE CATALOG command was used, but the userid that was supplied in the RCVCAT connect string does not have the RECOVERY_CATALOG_OWNER role granted as a DEFAULT role.

Action: Grant the RECOVERY_CATALOG_OWNER role to the recovery catalog owner.

RMAN-06427 recovery catalog already exists

Cause: The CREATE CATALOG command cannot be used when the recovery catalog already exists.

Action: Use the UPGRADE CATALOG command to upgrade your recovery catalog to the most current release without losing any existing backup data. Use the DROP CATALOG command to remove an existing recovery catalog.

RMAN-06428 recovery catalog is not installed

Cause: A recovery catalog database connection has been made, but the recovery catalog tables and views have not been installed.

Action: If you incorrectly typed the recovery catalog owner USERID, then correct the userid and reconnect to the recovery catalog. If this is the first time that you have signed on to Recovery Manager with this recovery catalog owner userid, then use the CREATE CATALOG command to create the recovery catalog schema.

RMAN-06429 string database is not compatible with this version of RMAN

Cause: The indicated database is not compatible with this version of the Recovery Manager (RMAN). Other messages have also been issued which detail the cause of the error.

Action: See the other messages. If the database is RCVCAT, then you may be able to use the CREATE CATALOG or UPGRADE CATALOG commands to correct the problem. If the database is TARGET or AUXILIARY, then you must either upgrade the target database or use a newer version of the RMAN executable.

RMAN-06430 recovery catalog userid cannot be SYS

Cause: A recovery catalog connection was made to userid SYS. The recovery catalog must be created in a userid other than SYS.

Action: Specify a different userid in the RCVCAT connect string.

RMAN-06431 recovery catalog created

Cause: This is an informational message issued by the CREATE CATALOG command.

Action: No action required.

RMAN-06432 recovery catalog dropped

Cause: This is an informational message issued by the DROP CATALOG command.

Action: No action required.

RMAN-06433 error installing recovery catalog

Cause: An error was received from the recovery catalog database while it was being installed. Another error message shows the error message from the server.

Action: The most common reasons for failure to install the recovery catalog are:

Lack of space in the recovery catalog database: allocate more space, use the DROP CATALOG command to remove any partially installed recovery catalog, and retry the command.

Object already exists: This is caused by a partial recovery catalog installation. Use the DROP CATALOG command to remove the partially installed recovery catalog and retry the command.

RMAN-06434 some errors occurred while removing recovery catalog

Cause: Some errors were received from the recovery catalog database while removing the recovery catalog.

Action: Correct the error(s) and retry the command. Note that the Recovery Manager intercepts and ignores common errors, such as 'object not found', which can happen while removing a partially installed recovery catalog. Only serious errors will be displayed while removing the recovery catalog.

RMAN-06435 recovery catalog owner is string

Cause: This is an informational message issued by the UPGRADE CATALOG and DROP CATALOG commands.

Cause: The DROP CATALOG command deletes the recovery catalog, rendering all database backups unusable, and should be used with care. The command must be entered twice to ensure that this is really what you want to do.

Action: If you really want to remove the recovery catalog, then enter the DROP CATALOG command again.

RMAN-06437 cannot drop catalog - catalog is newer than this RMAN

Cause: The DROP CATALOG command was entered, but the recovery catalog was created by a newer version of the Recovery Manager (RMAN). This version of RMAN may not be able to drop the entire recovery catalog.

Action: Use the version of RMAN which most recently created or upgraded the recovery catalog.

RMAN-06438 error executing package DBMS_RCVMAN in string database

Cause: Recovery Manager requires the DBMS_RCVMAN package in the SYS schema of the indicated database. Normally this package is installed during database creation.

Action: To re-create the package, run the files DBMSRMAN.SQL and PRVTRMNS.PLB.

RMAN-06439 RMAN must be upgraded to version string to work with this package

Cause: This message indicates the minimum version of Recovery Manager required to use the package which was specified in message 6191.

Cause: The recovery catalog is already at a version level that is greater than this version of the Recovery Manager. The UPGRADE CATALOG command is not needed.

Action: Either upgrade to a more recent Recovery Manager, or continue to use the current version. Message 6191 will be issued if the recovery catalog is too new to work with this version of Recovery Manager.

Cause: The UPGRADE CATALOG command alters the recovery catalog schema. Although the recovery catalog is designed to be compatible with older versions of the Recovery Manager (RMAN), it is possible that an upgrade will remove support for older versions of RMAN.

Action: If you really want to upgrade the recovery catalog, then enter the UPGRADE CATALOG command again. If you are not going to use an older version of RMAN with this recovery catalog, then compatibility is not an issue. If you plan to also continue using an older version of RMAN with this recovery catalog then, before upgrading, consult Oracle8i Migration or the migration guide for the current Oracle release to determine if upgrading to the current version of the recovery catalog will remove support for older versions of RMAN.

RMAN-06443 error upgrading recovery catalog

Cause: An error was received from the recovery catalog database while upgrading the recovery catalog.

Action: Correct the error and retry the command. Note that the Recovery Manager intercepts and ignores common errors, such as 'column already exists,' which can happen if the recovery catalog has already been partially upgraded. Only serious errors will be displayed while upgrading the recovery catalog.

RMAN-06444 string created with compilation errors

Cause: During the CREATE CATALOG or UPGRADE CATALOG command, the indicated PL/SQL package specification or body could not be created because of PL/SQL compilation errors.

Action: The PL/SQL packages used by the recovery catalog are located in the RECOVER.BSQ library file, and should never be modified. Make sure that the RECOVER.BSQ file has not been modified or damaged, and then if this error persists, contact Oracle Customer Support. Connect to the recovery catalog owner and query the USER_ERRORS view to find out the details of the compilation errors.

RMAN-06445 cannot connect to recovery catalog after NOCATALOG has been used

Cause: The CONNECT CATALOG command was used after the user had already specified the NOCATALOG option.

Action: Re-start RMAN if you wish to use a recovery catalog.

RMAN-06446 changed proxy copy unavailable

Cause: This is an informational message.

Action: No action required.

RMAN-06447 changed proxy copy available

Cause: This is an informational message.

Action: No action required.

RMAN-06448 uncataloged proxy copy

Cause: This is an informational message.

Action: No action required.

RMAN-06449 deleted proxy copy

Cause: This is an informational message.

Action: No action required.

RMAN-06450 crosschecked proxy copy: found to be 'string'

Cause: This is an informational message.

Action: No action required.

RMAN-06451 proxy copy handle=string recid=string stamp=string

Cause: This is an informational message.

Action: No action required.

RMAN-06452 stringpackage upgraded to version string

Cause: This is an informational message issued by the UPGRADE CATALOG command. It indicates the version to which the indicated package 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 packages are not changed with each Oracle release.

Action: No action required.

RMAN-06453 RECOVERABLE may only be used with datafile objects

Cause: An attempt was made to use LIST ... RECOVERABLE ... with OF CONTRLFILE or OF ARCHIVELOG.

Action: Remove the RECOVERABLE keyword and try again.

RMAN-07000 execution layer initialization failed

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

Action: See accompanying messages.

RMAN-07001 could not open channel string

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-07003 unrecoverable error during command execution

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

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

Action: See accompanying messages.

RMAN-07005 error during channel cleanup

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

Action: See accompanying messages.

RMAN-07006 unhandled exception during cleanup on channel string

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

Action: See accompanying messages.

RMAN-07007 cannot allocate more than number 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 Customer Support if you have a need for more channels in a single job.

RMAN-08000 channel string: copied datafile string

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).

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 Customer Support.

RMAN-08033 channel string: including datafilecopy of datafile string in backupset

Cause: This is an informational message.

Action: No action required.

RMAN-08034 full resync skipped, target database not mounted

Cause: This is an informational message.

Action: No action required.

RMAN-08035 partial resync skipped, target database not mounted

Cause: This is an informational message.

Action: No action required.

RMAN-08036 channel string: could not create controlfile record for stringstring

Cause: The record identifying the named file was no longer present in the target database control file, and repeated attempts to inspect the file were unsuccessful in creating the record. This could be because the circular-reuse section of the control file 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 control file 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 Customer Support.

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 Customer Support.

RMAN-10006 error running sql statement: string

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 Customer Support.

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 Customer Support.

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 Customer Support.

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. This is an informational message.

Action: No action required.

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 Customer Support.

Cause: Recovery Manager could not synchronize properly with a remote procedure call. This is an internal error that should not be issued.

Action: Contact Oracle Customer Support.

RMAN-10012 KGU error: string

Cause: An error occurred while initializing the KGU subsystem. This is an internal error that should not be issued.

Action: Contact Oracle Customer Support.

RMAN-10013 error initializing PL/SQL

Cause: An error occurred while initializing the PL/SQL subsystem. This is an internal error that should not be issued.

Action: Contact Oracle Customer Support.

RMAN-10014 PL/SQL error number on line number column number: string

Cause: PL/SQL error.

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

RMAN-10015 error compiling PL/SQL program

Cause: An error occurred while compiling a PL/SQL program. This is an internal error that should not be issued.

Action: Contact Oracle Customer Support.

RMAN-10016 error creating PL/SQL runtime context

Cause: An error occurred while creating a PL/SQL run time context. This is an internal error that should not be issued.

Action: Contact Oracle Customer 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 Customer Support.

RMAN-10018 error cleaning up channel context

Cause: An error was received during inter-step cleanup of a channel context. This is an internal error that should not be issued.

Action: Contact Oracle Customer 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 Customer Support.

RMAN-10022 error in system-dependant sleep routine

Cause: An error was received while waiting for a remote RPC to complete. The error occurred in the system-dependent sleep routine. This is an internal error that should not be issued.

Action: Contact Oracle Customer Support.

RMAN-10023 RPC attempted to unrecognized package

Cause: The Recovery Manager internal RPC router received a package name that it could not understand. This is an internal error that should not be issued.

Action: Contact Oracle Customer 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 Customer 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. This is an internal error that should not be issued.

Cause: Recovery Manager could not locate a necessary context area while attempting to register the target database connection to test for RPC completion. This is an internal error that should not be issued.

Action: Contact Oracle Customer Support.

RMAN-10028 network error number-number occurred during remote RPC

Cause: An network error occurred while waiting for a remote RPC to complete. This is an internal error that should not be issued.

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

Action: No action required.

RMAN-11000 message number number 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-11001 Oracle Error: string

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-11002 could not open a cursor to the target database

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-11003 failure during parse/execution of SQL statement: string

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-11004 format requires %c when duplexing

Cause: SET_DUPLEX=ON was specified, but %c was not part of the format.

Action: Include %c in format, or use %U.

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: 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: 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# and/or time of the target database does not match any database incarnation in the recovery catalog.

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

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. This is an internal error.

Action: Contact Oracle Customer 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: The target database instance is not started or the value of the DB_NAME initialization parameter is not set.

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

RMAN-20007 target database id is missing

Cause: This an internal error.

Action: Contact Oracle Customer Support.

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 is already registered in the recovery catalog. This is an informational message.

Action: 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# and time of the mounted target database control file is not 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 control file using RMAN. Otherwise use RESET DATABASE TO INCARNATION key to make the intended incarnation current in the recovery catalog.

RMAN-20020 database incarnation not set

Cause: This an internal error.

Action: Contact Oracle Customer Support.

RMAN-20021 database not set

Cause: This an internal error.

Action: Contact Oracle Customer Support.

RMAN-20029 cannot make a snapshot controlfile

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

Action: Try again later if necessary.

RMAN-20030 resync in progress

Cause: This procedure cannot be called while a resync is in progress. This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20031 resync not started

Cause: This procedure can only be called in a resync. This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20032 checkpoint change# too low

Cause: The checkpoint change# is less than the one of the previous resync or the checkpoint change# is null.

Action: Make sure that the right control file is used.

RMAN-20033 controlfile sequence# too low

Cause: The control file sequence is less than the one of the previous resync.

Action: Make sure that the right control file is used.

RMAN-20034 resync not needed

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

Action: No action required since the recovery catalog is in synchronization.

RMAN-20035 invalid high recid

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20036 invalid record order

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20037 invalid last recid

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20040 tablespace resync not started

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20041 tablespace resync not completed

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20042 invalid tablespace creation change#

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20043 invalid tablespace create time

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20044 invalid tablespace name

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20050 datafile resync not started

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20051 datafile resync not completed

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20052 invalid datafile create SCN

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20053 invalid datafile create time

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20054 invalid datafile ts#

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20061 thread resync not started

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20070 invalid log history sequence#

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20071 invalid log history low SCN

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20080 invalid archived log name

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20085 invalid offline range file#

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20086 invalid offline range offline_scn

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20087 invalid offline range online_scn

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20090 invalid backup set type

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20091 invalid backup set level

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20092 invalid backup set completion time

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20093 invalid backup piece number

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20094 missing backup set

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20095 invalid backup/copy controlfile checkpoint scn

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20096 invalid backup/copy datafile file#

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20097 invalid backup/copy datafile create scn

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20098 invalid backup redo log low scn

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20100 invalid status

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20101 datafile copy missing

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20102 archived log missing

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20103 controlfile copy missing

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20104 backup piece missing

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20105 datafile missing

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20106 proxy copy missing

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20200 invalid restore source

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

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-20203 translation in progress

Cause: This procedure cannot be called when name translation is in progress. This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20204 translation not started

Cause: getDatafile procedure was called before translateTablespace. This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20205 incomplete UNTIL clause

Cause: The sequence# was NULL. This is an internal error.

Action: Contact Oracle Customer Support.

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 cannot 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 the RESET DATABASE TO INCARNATION command.

RMAN-20208 UNTIL CHANGE is before RESETLOGS change

Cause: UNTIL CHANGE cannot be less 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 Customer Support.

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

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20211 FROM TIME is before RESETLOGS time

Cause: FROM TIME cannot be less than the database creation time or RESETLOGS time.

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

RMAN-20212 ambiguous proxy copy recid

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20215 backup set is missing

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20216 backup piece is missing

Cause: This is an internal error.

Action: Contact Oracle Customer Support.

RMAN-20217 datafile not part of the database

Cause: The datafile does not exist or did not exist at until time/SCN. This is an internal error for restore database or tablespace.

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

Action: Check the file name.

RMAN-20221 ambiguous controlfile copy name

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

Action: Use the control file copy key to uniquely specify the control file copy.

RMAN-20222 datafilename not found in recovery catalog or is ambiguous

Cause: The specified datafile name is not the name of a datafile that is currently part of the target database, or an UNTIL clause has been specified and the file name was for a different datafile at the time specified by the UNTIL clause than it is now.

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 control file copy in the recovery catalog match 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 archive logs in the specified archive log 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 match the specified handle.

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

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

Action: Take a level 0 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 version of the recovery catalog tables does not work with this version of the DBMS_RCVCAT package.

Action: Check that the recovery catalog packages and schema are installed correctly. The UPGRADE CATALOG command can be used to upgrade the recovery catalog tables and packages to the most current version.

RMAN-20299 DBMS_RCVMAN package not compatible with the recovery catalog

Cause: The version of the recovery catalog tables does not work with this version of the DBMS_RCVMAN package.

Action: Check that the recovery catalog packages and schema are installed correctly. The UPGRADE CATALOG command can be used to upgrade the recovery catalog tables and packages to the most current version.

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-20310 proxy copy not found in the recovery catalog

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

Action: Check the proxy copy handle or key.

RMAN-20311 ambiguous proxy copy handle

Cause: More than one proxy copy in the recovery catalog matches the specified handle.

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

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.

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 datafile copy 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.