Cause: This is a user prompt.

Cause: This is a user prompt.

Cause: This is a user prompt.

Cause: This is a user prompt.

Cause: This is a user prompt.

Cause: This is a user prompt.

Cause: This is a user prompt.

Cause: This is a user prompt.

Cause: This is a user prompt.

Cause: This is a user prompt.

Cause: An error occurred reading user response.

Cause: An incorrect response was entered.

Cause: lpmloadpkg() return an error indication.

Cause: The parser package initialization routine returned an error.

Cause: The arguments supplied to RMAN could not be parsed, or no arguments were supplied at all.

Cause: lpmloadpkg() return an error indication.

Cause: The internal package initialization routine returned an error.

Cause: The TARGET parameter was not specified.

Cause: An error occurred when trying to open the file.

Cause: An error occurred when trying to open the file.

Cause: The parser detected a syntax error.

Cause: The specified user name exceeds the maximum allowable username length.

Cause: The specified password exceeds the maximum allowable password length.

Cause: The SQL*NET host connect string exceeds the maximum allowable length.

Cause: An error occurred while trying to read from STDIN or from the CMDFILE.

Cause: An error occurred when trying to open the file.

Cause: An error occurred while trying to print the error message stack.

Cause: The user typed ^C or ATTN.

Cause: This message precedes an error message stack.

Cause: The end of an inline cmdfile was reached. This is just an informational message.

Cause: Displayed to highlight the error message stack.

Cause: This message is used only when the PIPE option was specified.

Cause: This is an internal error.

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.

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.

Cause: The PIPE and CMDFILE options cannot be used together. When using the PIPE option, RMAN must obtain its input from the input pipe.

Cause: The PIPE option obtains its input from, and writes its output to, an Oracle database pipe in the target database. Therefore, the target database connection must be specified on the command line, so that RMAN can connect to the target database to receive its input from the pipe.

Cause: The pipe that RMAN needs to use for its input or output is either a public pipe or a private pipe that is not owned by SYS. This is a potential security problem, because it allows a non-SYS user to issue commands to RMAN or to retrieve the RMAN output.

Cause: The SCRIPT and CMDFILE options cannot be used together. When using the SCRIPT option, RMAN executes only the specified script.

Cause: An internal error in recovery manager occurred.

Cause: A fatal error has occurred.

Cause: A SCRIPT option was included on the RMAN command line without a specified TARGET database.

Cause: A SCRIPT option was included on the RMAN command line without a specified CATALOG recovery catalog.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: An error was signaled during parsing.

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

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

Cause: A syntax error was signaled during parsing.

Cause: The rmanxx.msb file is not the correct version.

Cause: An illegal punctuation character was encountered.

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

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

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

Cause: A token longer than 1000 bytes was encountered

Cause: a line longer than 500 bytes was encountered

Cause: Parser failed to convert input string to integer

Cause: The RMAN variable specified was either undefined or null

Cause: This is probably caused by failure to supply the closing brace for a stored script in a command file.

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.

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

Cause: The command is not implemented in the current version.

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.

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.

Cause: This is the RMAN banner

Cause: A fatal error occurred during compilation of a command.

Cause: This is the copyright banner

Cause: This message is accompanied by other errors explaining the cause of the failure.

Cause: This is an informational message only.

Cause: A stored script is calling itself or another script which calls itself.

Cause: This is an informational message only.

Cause: The RPCTEST command has determined that RPCs are not executing asynchronously. Instead, they are blocking. This is caused by using a SQL*NET driver that does not support non-blocking UPI.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: Informational message. This precedes error 3012.

Cause: a SET ECHO ON command was issued

Cause: a SET ECHO OFF command was issued

Cause: The option used with the SET command is not valid outside a run block.

Cause: The option used with the SET command is not valid inside of a run block.

Cause: "ALTER SYSTEM ARCHIVE LOG CURRENT" command completed successfully.

Cause: An invalid DEBUG LEVEL was used.

Cause: a DEBUG OFF command was issued

Cause: a DEBUG command was issued

Cause: a SPOOL LOG TO ... command was issued

Cause: a SPOOL TRACE TO ... command was issued

Cause: a SPOOL LOG OFF command was issued

Cause: a SPOOL TRACE TO ... command was issued

Cause: This message is accompanied by other errors explaining the cause of the failure.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is the message prefix with a possible indentation.

Cause: The user interrupted the current job.

Cause: Internal error converting a date.

Cause: A memory allocation request could not be satisfied.

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

Cause: OCI process level initialization failed.

Cause: The call to OCIEnvInit failed.

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

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

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

Cause: Non fatal Oracle error signaled by catalog database. This message should be accompanied by other error message(s) indicating the cause of the error.

Cause: Non fatal Oracle error signaled by target database. This message should be accompanied by other error message(s) indicating the cause of the error.

Cause: Non fatal Oracle error signaled by auxiliary database. This message should be accompanied by other error message(s) indicating the cause of the error.

Cause: No password was provided for the target database.

Cause: No password was provided for the recovery catalog database.

Cause: No password was provided for the auxiliary database.

Cause: A STARTUP command was attempted before connecting to the database.

Cause: The database failed to startup.

Cause: An error was received while setting the session character set in the target database.

Cause: An error was received while initializing the OCI layer.

Cause: This is an additional informational message that indicates the cause of failure.

Cause: The CONNECT clause in the ALLOCATE command has resulted in a connection to a database which is not the same as the one used to connect to the target database.

Cause: The CONNECT clause in the ALLOCATE command has resulted in a connection to a database which is not the same as the one used to connect to the target database.

Cause: The CONNECT clause in the ALLOCATE command has resulted in a connection to a database which is not the same as the one used to connect to the target database.

Cause: The instance could not be started because no default parameter file (either PFILE or SPFILE) could be found. The instance will be started in restricted mode with default parameters.

Cause: Creation of a temporary file failed. If could be that the system does not have enough resources (disk space, memory or similar).

Cause: Opening of a temporary file failed. If could be that the system does not have enough resources (disk space, memory or similar).

Cause: Writing to a temporary file failed. If could be that the system does not have enough resources (disk space, memory or similar).

Cause: This is an informational message only.

Cause: The specified file was included as part of the auxiliary database parameter file. This is an informational message.

Cause: An auxiliary parameter file was specified with SET AUXILIARY INSTANCE PARAMETER FILE command but the specified file cannot be found.

Cause: A password was not provided for the source recovery catalog database.

Cause: Oracle error signaled by source recovery catalog database. This message should be accompanied by other error message(s) indicating the cause of the error.

Cause: Nonfatal Oracle error signaled by source recovery catalog database. This message should be accompanied by other error message(s) indicating the cause of the error.

Cause: An unsupported mode was specified on a target or clone connection.

Cause: A connection specified a mode when no mode is supported for this kind of connection

Cause: Either: -) The control file mounted by the auxiliary database does not have an entry for this data file, therefore file name conversion is not possible. -) A COPY DATAFILE TO AUXNAME command was issued, but no auxname was set for this data file.

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

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

Cause: The SYSTEM, SYSUAX or a tablespace containing rollback segments is not allowed in Tablespace Point-in-Time Recovery.

Cause: An attempt was made to apply Tablespace Point-in-Time Recovery or Pluggable Database Point-in-Time Recovery to a database that is in NOARCHIVELOG mode.

Cause: The requested tablespace has been re-created and is not allowed in Point-in-Time Recovery.

Cause: Standby recover can only be performed for the whole database.

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

Cause: The SKIP clause was specified for non-Tablespace or Table Point-in-Time Recovery.

Cause: The RECOVER...BLOCK command was specified.

Cause: The target database was not opened in read/write mode.

Cause: The Auxiliary instance was not in NOMOUNT state.

Cause: RMAN is attempting to use the specified control file name for Tablespace Point-in-Time Recovery as a restore destination in the auxiliary database, but this name is already in use by the target database.

Cause: The recovery catalog did not have information about tablespaces with undo segments.

Cause: The recovery catalog did not have information about the tablespaces with undo segments at the specified Point-in-Time. This happened because the current recovery catalog was not in use at the specified Point-in-Time. A list of tablespaces with undo segments was supplied.

Cause: This is an informational message to indicate the RMAN could not successfully restore the files using the specified backups. An attempt was made to restore the data file/archived logs/ control file/SPFILE using a previous existing backup.

Cause: A RECOVER COPY command was not able to proceed because no copy of indicated file was found to recover. Possible causes include the following: 1. no copy of indicated file exists on disk that satisfy the criteria specified in the user's recover operands. 2. copy of indicated data file exists on disk but no incremental backup was found to apply to the data file copy.

Cause: This error message can follow one or more RMAN-5017 or RMAN-5019 error messages.

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

Cause: The AUXILIARY DESTINATION option was specified for a normal recovery. It is only allowed for Tablespace or Table Point-in-Time Recovery.

Cause: The user attempted to modify the configuration which cannot be changed for a BACKUP or STANDBY control file while the mounted control file was either BACKUP or STANDBY. The following configurations can be changed only when connected to primary database instance that has CURRENT/CREATED control file type mounted: CONFIGURE RETENTION POLICY CONFIGURE EXCLUDE CONFIGURE ENCRYPTION CONFIGURE DB_UNIQUE_NAME

Cause: A user-managed auxiliary instance was specified.

Cause: A required TABLESPACE DESTINATION was not specified.

Cause: Accompanying message to 5015.

Cause: Accompanying message to 5015.

Cause: RMAN assumes that the current set of tablespaces with undo segments is the same set that was in use at the specified Point-in-Time. If the set of tablespaces with undo segments changes, the recovery fails. If recovery fails, use the optional UNDO TABLESPACE clause of the RECOVER command to specify the correct set of tablespaces.

Cause: Accompanying message to 5026.

Cause: Accompanying message to 5026.

Cause: The UNDO TABLESPACE clause was specified for non-Tablespace or Table Point-in-Time Recovery.

Cause: The CLONE clause was specified for a Tablespace or Logical Point-in-Time Recovery.

Cause: The DATAPUMP DESTINATION clause was specified for a non-Table Point-in-Time Recovery.

Cause: The specified data file did not have an available backup.

Cause: The above system change number (SCN) would be starting media recovery SCN, if the specified files are restored.

Cause: The above system change number (SCN) identifies the minimum SCN beyond which the media recovery must be performed on the specific data file to clear the media recovery fuzziness for all data file.

Cause: The recovery catalog or target database control file did not have a record of archived logs containing the redo generated after the specified system change number (SCN).

Cause: An attempt was made to set the configuration which cannot be used with FOR DB_UNIQUE_NAME option.

Cause: An attempt was made to set the remote configuration in nocatalog mode.

Cause: No archived logs were found in the control file.

Cause: There was an error while performing Tablespace or Table Point-in-Time Recovery. Some of the restored data files had Oracle Managed Files (OMF) names and were not deleted.

Cause: One or more tablespaces in the recovery set were not found in the control file of the target database.

Cause: Export of metadata received an error from Data Pump.

Cause: Import of metadata received an error from Data Pump.

Cause: Accompanying message to 5040.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: The specified file name was already in use by another data file in the database.

Cause: RESTORE command was issued with a SET UNTIL clause and Flashback Database enabled. The control file was flashed back to the SET UNTIL time.

Cause: This is an informational message only.

Cause: The specified repair was not compatible with this version of Recovery Manager (RMAN).

Cause: AUXILIARY DESTINATION clause was specified while using an user-managed auxiliary instance.

Cause: The specified operand could not be used with RECOVER data file command.

Cause: The specified operand could not be used with RECOVER block command.

Cause: A SYS table was specified to be recovered.

Cause: The specified table was not found in the dictionary at the specified point-in-time.

Cause: The specified table was not found in the data pump views at the specified point-in-time.

Cause: The tablespace that contained the specified table did not allow Tablespace Point-in-Time Recovery.

Cause: Block Specifier was not specified in the command.

Cause: This is an informational message only.

Cause: The image copy that would be rolled forward by the RECOVER COPY command is already more recent than the specified UNTIL time or system change number (SCN).

Cause: Previously encountered errors required corrective action.

Cause: The REMAP TABLE clause was specified for a non-Table Point-in-Time Recovery.

Cause: The REMAP TABLESPACE clause was specified for a non-Table Point-in-Time Recovery.

Cause: The NOTABLEIMPORT clause was specified for a non-Table Point-in-Time Recovery.

Cause: The specified table was already specified to be recovered.

Cause: The same table name for the same user has already been specified for a different table.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: SYS.TS_PITR_CHECK was not empty for recovery set tablespaces.

Cause: The tablespace was found in the control file but the creation system change number (SCN) of the data file(s) is after the specified point-in-time. This can happen if a previous tablespace point-in-time recovery was performed, for the tablespace.

Cause: The tablespace was found in the control file but the creation system change number (SCN) of the data file(s) is after the specified point-in-time.

Cause: The specified remapped object was not recovered.

Cause: The specified tablespace was not recovered. None of the objects being recovered belong to the specified tablespace.

Cause: The new tablespace in the REMAP TABLESPACE clause could not be found in the target database.

Cause: Table Point-in-Time Recovery was specified without a point-in-time specification.

Cause: The same table appeared in another remap specification.

Cause: As requested, Data Pump Import was not performed after the point-in-time recovery was performed.

Cause: The NOTABLEIMPORT clause was specified together with either the REMAP TABLE or REMAP TABLESPACE clause. These clauses are used during importing of the tables and, therefore, are invalid.

Cause: The same tablespace appeared in another remap specification.

Cause: The specified partition was not found in the dictionary at the specified point-in-time.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: The DUMP FILE clause was specified for a non-Table Point-in-Time Recovery.

Cause: This is an informational message only.

Cause: TO NEW was specified for a RESTORE BACKUPPIECE command but DB_FILE_CREATE_DEST was not set for the target database.

Cause: The specified option was used for a cross-platform data file restore.

Cause: FROM PLATFORM clause was specified for a noncross-platform data file restore.

Cause: An UNTIL command was in effect or an UNTIL clause was specified for a cross-platform data file restore.

Cause: The specified option was specified for whole database cross-platform data file restore.

Cause: A restore specification was found when a cross-platform data file specification was expected.

Cause: FOREIGN DATABASE specification was found but the database was not in the correct state.

Cause: During a cross-platform tablespace restore, DUMP FILE was specified without NOIMPORT and database was not open in read/write mode.

Cause: The FROM SERVICE option was supplied but does not apply to restoring archived logs.

Cause: The specified data file could not be accessed from the indicated service.

Cause: The same schema appeared in another remap specification.

Cause: A command that restores SPFILE to the target instance from a service name was requested. Such a command requires a password to be present in the connect string used to connect to the target instance.

Cause: A command that restores SPFILE to the auxiliary instance from a service name was requested. Such a command requires a password to be present in the connect string used to connect to the auxiliary instance.

Cause: A Point-in-Time Recovery was attempted when target database was not open without connection to a recovery catalog. It is necessary that the list of tablespaces with undo segments is provided with the UNDO TABLESPACE clause.

Cause: The Auxiliary instance was not in the NOMOUNT state.

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

Cause: The command was attempted on more than one Pluggable Databases. This is not supported.

Cause: This operation was not supported for the Pluggable Database that was specified in the command.

Cause: RMAN attempted to use the specified data file number as a restore destination, but this data file number was already in use by the specified database.

Cause: The AUXILIARY DESTINATION option was not specified for Pluggable Database Point-in-Time Recovery or Flashback Pluggable Database. This is a mandatory option for these commands unless Fast Recovery Area is used.

Cause: Pluggable database specified for this command. This is not supported.

Cause: Specified UNTIL CHANGE was an orphan incarnation of the Pluggable Database.

Cause: Pluggable Database Point-in-Time Recovery or Flashback Pluggable Datdabase was attempted while the Pluggable Database was open.

Cause: Pluggable Database Point-in-Time Recovery was attempted on standby. This is not supported.

Cause: The specified table was present in the dictionary in the target database.

Cause: Import completed with errors.

Cause: RMAN attempted to use the specified data file name as a restore destination for the indicated data file, but this data file name was already in use by the specified database. This can happen during pluggable database point-in-time recovery to recover a dropped tablespace whose data file name was already in use by a pluggable database.

Cause: An instant restore was specified using a data file copy from a different platform.

Cause: The specified fature is not enabled.

Cause: Archive logs were missing for the SCN range.

Cause: This is an informational message only.

Cause: No archive logs or backups were found.

Cause: An error occurred while opening the wallet with the specified password.

Cause: This is an informational message only.

Cause: The disk space required to perform restore exceeded the available space.

Cause: A RESTORE or RECOVER command omitted processing the indicated data file because it was not a plugged in data file.

Cause: The specified option was used for a PREPLUGIN data file restore or recover command. This is not supported.

Cause: Either the FROM SPARSE or FROM NONSPARSE option was specified for an active duplicate. The option is only allowed for nonactive duplicate.

Cause: Either the FROM SPARSE or FROM NONSPARSE option was specified for a restore from service.

Cause: Either the FROM SPARSE or FROM NONSPARSE option was specified for a normal recovery.

Cause: Either the FROM SPARSE or FROM NONSPARSE option was specified for an instant restore.

Cause: Either the FROM SPARSE or FROM NONSPARSE option was specified for an ordinary restore with cross-platform caluse.

Cause: Either the FROM SPARSE or FROM NONSPARSE option was specified for restoring a non data file.

Cause: Either the SPARSE or the NONSPARSE option was specified for a proxy backup.

Cause: Either the SPARSE or NONSPARSE option was specified for an incremental backup.

Cause: An attempt to specify the SPARSE or NONSPARSE option in the BACKUP AS command failed. The BACKUP AS command can only be used to take non-cross-platform FULL or LEVEL 0 backups of data files. However, the option is prohibited for taking inconsistent backups of data files.

Cause: An UNTIL command was in effect or an UNTIL clause was specified for a PREPLUGIN data file restore or recover command. This is not supported.

Cause: During restoration of a foreign data file, either the destination was not provided using the FORMAT option in the RESTORE command or Oracle Managed Files (OMF) were not configured.

Cause: UNTIL AVAILABLE REDO was specified with keywords DATAFILE, TABLESPACE or PLUGGABLE DATABASE.

Cause: An attempt to specify the AS ENCRYPTED or AS DECRYPTED option in a RESTORE command failed. AS ECNRYPTED and AS DECRYPTED can only be specified for tablespace and database objects.

Cause: An attempt to flashback a pluggable database (PDB) or a PDB point-in-time recovery (PITR) across an undo switch system change number (SCN) failed.

Cause: The target database was not opened.

Cause: An RMAN command such as BACKUP, DUPLICATE, FLASHBACK, RECOVER, RESTORE has omitted processing data files belonging to the indicated pluggable database (PDB). This was because the data files belong to the PDB that has been marked excluded from backup and restore operations.

Cause: Pluggable database specified for this command is excluded from backup and restore operations. This is not supported.

Cause: The new schema required for remapping did not exist in the database.

Cause: RECOVER STANDBY DATABASE statement was used to synchronize the standby database from the primary database and the only valid options are FROM SERVICE and PFILE.

Cause: An attempt was made to recover a standby database from a non-standby database.

Cause: SPFILE or PFILE were not provided for the RECOVER STANDBY DATABASE command.

Cause: Flashback was enabled before the standby database was synchronized but could not be reenabled until the standby database was opened.

Cause: Neither FROM SERVICE nor NOREDO clause was provided for the RECOVER STANDBY DATABASE command.

Cause: The Managed Recovery Process was enabled when an attempt was made to run the RECOVER STANDBY DATABASE command.

Cause: An encryption is not supported for duplicating a pluggable database.

Cause: A RESTORE command omitted processing the indicated data file because it was a plugged in data file.

Cause: The AS SPARSE option was used for a non-sparse data file which is not supported.

Cause: Both FROM SERVICE and NOREDO clauses were provided for the RECOVER STANDBY DATABASE command.

Cause: An UNTIL clause was provided with the RECOVER STANDBY DATABASE FROM SERVICE command.

Cause: The previously encountered errors require corrective action.

Cause: The RECOVER STANDBY DATABASE command was attempted while the database was mounted on another instance.

Cause: Recovery Manager (RMAN) attempted to use the specified file name as a restore destination in the auxiliary database, but this name was already in use by the target database. If the auxiliary database instance can access the storage where the target data files are residing, then the target database file gets overwritten causing corruption in the target database.

Cause: This is an informational message only.

Cause: An attempt to specify the USING KEY option in a RESTORE command failed. USING KEY can only be specified with AS ECNRYPTED clause.

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

Cause: Previously encountered errors require corrective action.

Cause: A DUPLICATE command was issued, but the target database control file is not mounted.

Cause: No auxiliary channels were allocated.

Cause: Only one redo log file or group was specified

Cause: When the given file name is converted to the name used for the auxiliary database, the converted name is larger than the maximum allowed file name.

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

Cause: A DUPLICATE FOR STANDBY command was issued, but the checkpoint of the control file is more recent than the last archived log or the specified point-in-time.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: The SYSTEM and SYSAUX tablespaces were not included in the DUPLICATE DATABASE. They must be present.

Cause: Target database did not have a current or standby control file. DUPLICATE requires the target database to have a current or standby control file.

Cause: All tablespaces that have undo information must be included in the duplication.

Cause: A SET UNTIL clause was specified for the command.

Cause: The specified operand appears more than once in the same DUPLICATE option list

Cause: RMAN attempted to use the specified tempfile as a restore destination in the auxiliary database, but this name was already in use by the target database.

Cause: This is an informational message only.

Cause: The SYSTEM and SYSAUX tablespaces were included in the DUPLICATE TABLESPACE command. They were automatically included by the command and did not need to be explicitly named.

Cause: The database name specified in the initialization parameter was not the same as the database name provided in the DUPLICATE command.

Cause: A DUPLICATE was attempted when target database was not open without connection to a recovery catalog. It is necessary that the list of tablespaces with undo segments is provided with the UNDO TABLESPACE clause.

Cause: This is an informational message only.

Cause: Conflicting parameters were provided.

Cause: It was not possible to duplicate offline tablespaces.

Cause: A SKIP TABLESPACE clause was specified for the command.

Cause: A DUPLICATE command omitted processing the indicated data file because it is offline immediate. The tablespace to which this data file belongs will also not be included. See message 5528.

Cause: It was not possible to duplicate a tablespace who had offline immediate tablespaces.

Cause: A DUPLICATE command omitted processing the indicated data file because it is part of a tablespace that has offline immediate data file. See message 5526.

Cause: It was not possible to convert ASM Oracle Managed Files names using DB_FILE_NAME_CONVERT parameter. RMAN changed these invalid names to the converted disk group name instead.

Cause: A DUPLICATE with FROM ACTIVE DATABASE was specified along with either a SET UNTIL statment or UNTIL clause on the command. This is not supported. A DUPLICATE FROM ACTIVE DATABASE always creates a copy as of the current time.

Cause: A DUPLICATE with FROM ACTIVE DATABASE command was specified while the database was mounted or open read-only. Unless the database is open read/write, the data files cannot be fuzzy.

Cause: The PASSWORD FILE clause of the DUPLICATE command was specified but the FROM ACTIVE DATABASE clause was not. A password file can only be duplicated if the FROM ACTIVE DATABSE clause has been used.

Cause: The specified command is not supported on this type of database. The type of database can be STANDBY, CLONE, or RAC.

Cause: It was not possible to convert ASM Oracle Managed Files names using LOG_FILE_NAME_CONVERT parameter. RMAN changed these invalid names to the converted disk group name instead.

Cause: It was not possible to define all the redo log files. This can occur when LOG_FILE_NAME_CONVERT initialization parameter is defined but fails to match all the names or causes names to be created that are not in valid directories.

Cause: RMAN attempted to use the specified logfile name as a standby redo log file in the auxiliary database, but this name was already in use by the target database.

Cause: A DUPLICATE was attempted when the auxiliary database was started with a server parameter file and the SPFILE sub-clause was specified. RMAN cannot restore the server parameter file if the auxiliary database is already started with a server parameter file.

Cause: The duplicated SPFILE had DB_FILE_NAME_CONVERT set and it has been used to produce data file names for the new database.

Cause: A DUPLICATE TARGET DATABASE was attempted and no connection to the TARGET database was established.

Cause: Recovery catalog did not have archived log records for the specified database. If database is running in NOARCHIVELOG mode, then specify NOREDO.

Cause: Target database was running in archived log mode, but control file did not have any archived log records.

Cause: A DUPLICATE without TARGET and CATALOG connections was attempted specifying an UNTIL clause that was not TIME based.

Cause: A DUPLICATE without TARGET connection was attempted without specifying the database to duplicate.

Cause: DUPLICATE from ACTIVE DATABASE required a connection to the target database.

Cause: The specified point-in-time for duplication without a target connection was ahead of the last time that the data file information was resynced to the recovery catalog. Information about offline and read-only data files might be incorrect.

Cause: A DUPLICATE without TARGET and CATALOG connections was attempted without specifying BACKUP LOCATION.

Cause: This is an informational message only.

Cause: A DUPLICATE TABLESPACE has specified a set of tablespaces that cannot function independently.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: A SYS object was found in one of the skipped tablespaces.

Cause: Objects owned by SYS were found in the tablespaces that would not be duplicated.

Cause: A DUPLICATE without TARGET and CATALOG connections was attempted when INCARNATION was also specified.

Cause: This is an informational message only.

Cause: One or more data files being duplicated could not be restored as no available backups were found.

Cause: SPFILE clause was used but target instance was not started with a server parameter file.

Cause: A DUPLICATE FOR STANDBY ... SPFILE command was issued but DB_UNIQUE_NAME was not provided for the standby database.

Cause: While attempting to apply a PARAMETER_VALUE_CONVERT to the specified parameter value, the resulting string exceeded the maximum length for a value.

Cause: A data file copy from a previous duplicate attempt matching the duplicate name requested was found for the specified data file and will be used instead of restoring the data file from a backup.

Cause: A DUPLICATE with no target connection was attempted, but the recovery catalog did not have information about the tablespaces with undo segments at the specified point in time. It is necessary that the list of tablespaces with undo segments is provided with the UNDO TABLESPACE clause.

Cause: RMAN could not locate a backup of the SPFILE in the specified location that satisfied the specified parameters.

Cause: RMAN could not locate a backup of the SPFILE in the specified location that satisfied the specified parameters.

Cause: RMAN could not locate a backup of the SPFILE in the specified location that satisfied the specified parameters.

Cause: RMAN could not locate a backup of the SPFILE in the specified location that satisfied the specified parameters.

Cause: RMAN could not locate a backup of the SPFILE in the specified location that satisfied the specified parameters.

Cause: RMAN could not locate a backup of the SPFILE in the specified location that satisfied the specified parameters.

Cause: RMAN could not locate a backup of the SPFILE in the specified location that satisfied the specified parameters.

Cause: RMAN could not locate a backup of the SPFILE in the specified location.

Cause: A LOGFILE clause was specified for the command.

Cause: A DORECOVER clause was specified and the duplicate did not specify FOR STANDBY.

Cause: RMAN could not locate a backup of the control file in the specified location that satisfied the specified parameters.

Cause: RMAN could not locate a backup of the control file in the specified location that satisfied the specified parameters.

Cause: RMAN could not locate a backup of the control file in the specified location that satisfied the specified parameters.

Cause: RMAN could not locate a backup of the control file in the specified location that satisfied the specified parameters.

Cause: RMAN could not locate a backup of the control file in the specified location that satisfied the specified parameters.

Cause: RMAN could not locate a backup of the control file in the specified location that satisfied the specified parameters.

Cause: RMAN could not locate a backup of the control file in the specified location that satisfied the specified parameters.

Cause: RMAN could not locate a backup of the control file in the specified location.

Cause: A SKIP READONLY clause was specified for the command.

Cause: A SKIP TABLESPACE clause was specified for the command.

Cause: An OPEN RESTRICTED clause was specified for the command.

Cause: A TABLESPACE clause was specified for the command.

Cause: A NOREDO clause was specified for the command.

Cause: A UNDO TABLESPACE clause was specified for the command.

Cause: This is an informational message only.

Cause: A materialized table was found in one of the skipped tablespaces.

Cause: A materialized index was found in one of the skipped tablespaces.

Cause: Materialized objects found in the tablespaces that would not be duplicated.

Cause: This is an informational message only.

Cause: A sql error was received during the execution of command.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: The tablespace failed to be dropped several times, no more attempts will be made.

Cause: User requested that the new database was not open.

Cause: Server parameter file was not deleted. This message should be accompanied by other error message(s) indicating the cause of the error.

Cause: A PFILE clause was specified for duplicate command, but database was started with a server parameter file causing a conflict.

Cause: SPFILE and PFILE clauses were specified for duplicate command causing a conflict.

Cause: PASSWORD clause was specified when creating a standby database from active database. This is not needed, it is automatic.

Cause: An UNTIL clause in the command or with a SET UNTIL was in effect for an active database duplication.

Cause: An error was received while duplicating the database after the server parameter file was modified by RMAN. An attempt was made to restore original settings to the server parameter file, but the original error was such that it was not possible to restore the settings.

Cause: This is an informational message only.

Cause: A command that restores files to the auxiliary instance from the target instance was requested. Such a command requires that a net service name be present in the connect string used to connect to the target instance.

Cause: A SECTION SIZE clause was specified for the command. This option is valid only when USING BACKUPSET or USING COMPRESSED BACKUPSET option is specified.

Cause: A USING clause was specified for the command. This option is valid only when ACTIVE DATABASE option is specified.

Cause: A SECTION SIZE clause was specified for the command. This option is valid only when ACTIVE DATABASE option is used.

Cause: Duplicate created a server parameter file that coould not be removed because no client parameter file was provided for the command.

Cause: A partitioned table was contained in the tablespaces that were not included in the new database, however the tablespaces cannot be dropped until the table is dropped.

Cause: An active duplication was attempted but no username was provided in the connection to the target database.

Cause: An active duplication was attempted but no username was provided in the connection to the auxiliary database.

Cause: An active duplication was attempted but the usernames provided in the connection to the target and auxiliary database are not the same.

Cause: An active duplication was attempted but no password was provided in the connection to the target database.

Cause: An active duplication was attempted but no password was provided in the connection to the auxiliary database.

Cause: An active duplication was attempted but the passwords provided in the connection to the target and auxiliary database are not the same.

Cause: SKIP PLUGGABLE DATABASE and DUPLICATE PLUGGABLE DATABASE were both specified in the same command. These options are incompatible and cannot be used together.

Cause: The CDB$ROOT and PDB$SEED databases were not included in the DUPLICATE DATABASE. They must be present.

Cause: The specified operand refers to same PLUGGABLE DATABASE in the DUPLICATE option list.

Cause: The specified operand refers to same PLUGGABLE DATABASE in the DUPLICATE option list.

Cause: A SKIP PLUGGABLE DATABASE clause was specified for the command.

Cause: This is an informational message only.

Cause: The password file location did not exist for the target database instance.

Cause: The password file location did not exist for the auxiliary database instance.

Cause: An uneven number of patterns was specified.

Cause: The data file name corresponding to the specified data file number was not found in the control file or recovery catalog.

Cause: A command was attempted that can be performed only in the root container.

Cause: A DUPLICATE with FROM ACTIVE DATABASE command was specified while the database was mounted or closed. To perform active database duplication of pluggable databases, the target database must be open in read-only or read/write mode.

Cause: A DUPLICATE with FROM ACTIVE DATABASE command was specified while the database was mounted or closed. To perform active duplication of pluggable databases, the clone database must be open in read/write mode.

Cause: The pluggable database being duplicated did not exist on the target database.

Cause: A DUPLICATE PLUGGABLE DATABASE with FROM ACTIVE DATABASE command was specified while the pluggable database was mounted or closed. When using the DUPLICATE command with pluggable databases, the specified target pluggable database must be open in read-only or read/write mode.

Cause: The pluggable database specified in the DUPLICATE command was already in existence on the clone database.

Cause: A LOGFILE clause was specified, but this clause is not supported for duplicating pluggable database.

Cause: A USING COPY clause was specified, but this clause is not supported for duplicating pluggable database.

Cause: A SKIP READONLY clause was specified, but this clause is not supported for duplicating pluggable database.

Cause: A FOR FARSYNC clause was specified, but this clause is not supported for duplicating pluggable database.

Cause: A FOR STANDBY clause was specified, but this clause is not supported for duplicating pluggable database.

Cause: A PFILE/SPFILE clause was specified, but this clause is not supported for duplicating pluggable database.

Cause: A SKIP TABLESPACE clause was specified, but this clause is not supported for duplicating pluggable database.

Cause: A SKIP PLUGGABLE DATABASE clause was specified, but this clause is not supported for duplicating pluggable database.

Cause: A OPEN RESTRICTED clause was specified, but this clause is not supported for duplicating pluggable database.

Cause: A TABLESPACE clause was specified, but this clause is not supported for duplicating pluggable database.

Cause: A PASSWORDFILE clause was specified, but this clause is not supported for duplicating pluggable database.

Cause: A NOREDO clause was specified, but this clause is not supported for duplicating pluggable database.

Cause: A UNDO TABLESPACE clause was specified, but this clause is not supported for duplicating pluggable database.

Cause: A BACKUP LOCATION clause was specified, but this clause is not supported for duplicating pluggable database.

Cause: For DUPLICATE pluggable databases, the specified target database must have change tracking enabled.

Cause: Duplicate pluggable database is allowed only for active duplication.

Cause: An AS ENCRYPTED or AS DECRYPTED clause was specified, but this clause is not supported for duplicating a pluggable database.

Cause: A DORECOVER clause was specified, but this clause is not supported for duplicating a pluggable database.

Cause: A UNTIL SCN or TO RESTORE POINT clause was specified, but this clause is not supported for duplicating a pluggable database.

Cause: A NOREMOVE clause was specified, but this clause is not supported for duplicating a pluggable database.

Cause: A NOCHECK clause was specified, but this clause is not supported for duplicating a pluggable database.

Cause: A FORCE clause was specified, but this clause is not supported for duplicating a pluggable database.

Cause: A NOOPEN clause was specified, but this clause is not supported for duplicating a pluggable database.

Cause: For DUPLICATE pluggable databases (PDBs) or point-in-time recovery of application root PDB or application PDB, the specified target database did not have local undo enabled.

Cause: For DUPLICATE pluggable databases, the specified clone instance SPFILE REMOTE_RECOVERY_FILE_DEST parameter was NULL.

Cause: This is an information message only.

Cause: There were multiple database IDs present in the BACKUP LOCATION specified. RMAN did not know which database ID to use for the DUPLICATE command.

Cause: This is an information message only.

Cause: The XML file did not exist or has an invalid format.

Cause: XML file has an invalid format.

Cause: Disk and non-disk channels were allocated for the BACKUP LOCATION FROM FILE option in the DUPLICATE command. Only one channel type can be used when using this option.

Cause: The data file was missing. The excluded tablespace was treated as a skipped tablespace but not dropped after DUPLICATE with the existing CONFIGURE EXCLUDE FOR TABLESPACE command was issued.

Cause: The "recover.bsq" file could not be opened.

Cause: A syntax error was encountered while parsing "recover.bsq".

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

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.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: The target database has not mounted the control file, and its "init.ora" file does not specify the DB_NAME parameter.

Cause: This is an informational message only.

Cause: This is an informational message only.

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

Cause: An invalid incremental backup level was specified.

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

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

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

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

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

Cause: The parser package initialization routine returned an error.

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

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

Cause: This is an informational message only.

Cause: The FROM DATAFILECOPY/BACKUPSET option applies only to data file and control file restores.

Cause: An invalid incremental backup level was specified for an image copy.

Cause: A data file, 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.

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.

Cause: An archived log restore 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.

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 can not be restored are that there is no backup or copy of the file that is known to recovery manager, or there are no backups or copies that fall within the criteria specified on the RESTORE command, or some data file copies have been made but not cataloged.

Cause: An archived log record specifier did not match any archived logs in the recovery catalog or target database control file.

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

Cause: The "include current/standby control file" option was specified for an archived log backup set.

Cause: The DELETE [ALL] INPUT option was specified for a backup that contains the current control file or data file.

Cause: An error was received when calling DBMS_RCVMAN

Cause: No channel of TYPE DISK was allocated.

Cause: An rman command requests a specific channel, but the requested channel has not been allocated.

Cause: No channels were allocated.

Cause: The "recover.bsq" file is incompatible with the RMAN executable.

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

Cause: A call to DBMS_RCVMAN returned an error.

Cause: A SWITCH command was specified for a data file, 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.

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

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

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

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

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

Cause: An error occurred while translating an archived log name to its recovery catalog RECID/time stamp. This message should be accompanied by other error message(s) indicating the cause of the error.

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

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

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

Cause: An archived 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.

Cause: This option was specified in a backup specification.

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

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.

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

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.

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

Cause: "current control file" was specified along with "standby control file".

Cause: "standby control file" was specified along with "current control file".

Cause: The archived log was not found. The recovery catalog or target database control file thinks it does exist. If the archived log has in fact been lost and there is no backup, then the database is no longer recoverable across the point-in-time covered by the archived log. This may occur because the archived log was removed by an outside utility without updating the recovery catalog or target database control file.

Cause: SKIP INACCESSIBLE or SKIP OFFLINE option resulted in skipping data file during BACKUP. If the data file has in fact been lost and there is no backup, then the tablespace is no longer recoverable without ALL archived logs since data file creation. This may occur because the data file was deleted by an outside utility or the data file is made OFFLINE [DROP].

Cause: SKIP INACCESSIBLE option resulted in skipping archived logs during BACKUP. If the archived log has in fact been lost and there is no backup, then the database is no longer recoverable across the point-in-time covered by the archived log. This may occur because archived log was removed by an outside utility without updating the recovery catalog or target database control file.

Cause: A backup command requested a backup of the SPFILE, but no SPFILE was used to startup the instance.

Cause: DBID is not found in the recovery catalog.

Cause: RESTORE/RECOVER command was issued and there were no backup available for the data file.

Cause: An attempt was made to use two (or more) conflicting operands within the same statement.

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

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

Cause: This error should be accompanied by one or more instances of message ORA-06094.

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

Cause: DBWR could not find the specified data file.

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

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

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

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

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

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

Cause: The control file appears to be older than the specified data file, 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.

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

Cause: The control file record for this data file is for an older incarnation of the data file. A SWITCH command must be issued to updated the control file before doing RECOVER.

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

Cause: The specified tag refers to multiple data file copies belonging to different data files.

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

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

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

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

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

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

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

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

Cause: A command was entered that requires a maintenance channel, and no maintenance channel is allocated, or none of the appropriate type.

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

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

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

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

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

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

Cause: See accompanying error.

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

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

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

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

Cause: The NOT BACKED UP clause of the BACKUP command specified 0 times.

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

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

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.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: An attempt was made to crosscheck an object which is unavailable.

Cause: An attempt was made to DELETE EXPIRED an object which is not expired.

Cause: An attempt was made to recover the database, but some files had no backup, and were not present in the control file at the beginning of the restore. This happens when the control file used during the recovery is a backup control file taken before the creation of some of the files that had no backup. In this situation, the control file that is used must be taken before the creation of all files that have no backup. This will enable RMAN to automatically re-create all of the files that had no backup.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: The CHANGE BACKUPSET .. UNCATALOG command was entered. The UNCATALOG operation is not supported with backup set.

Cause: A command was used which requires a connection to a recovery catalog database or the target database to be mounted. The command cannot be used when no backup repository is available.

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

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

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

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

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.

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

Cause: The target database control file was not current. 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 data file's offline or read-only status.

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

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

Cause: An operating system command has completed.

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

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

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

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.

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 data files may not be current.

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

Cause: The ARCHIVELOG LIKE option was specified with RESTORE. This is not permitted because recovery catalog contains only those records that are not deleted from disk.

Cause: The DEVICE TYPE option was specified with a command that does not support it.

Cause: The LIKE option was specified with a RMAN command. This is not permitted because only copies of data files, control files or archived logs have file names that may be tested with a LIKE operand.

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.

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.

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 system change number(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.

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

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

Cause: A BACKUP DATABASE command was issued, but the target database was in NOARCHIVELOG mode and was open in READ/WRITE mode.

Cause: This message is issued in response to a CONFIGURE AUXNAME command.

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

Cause: An attempt was made to specify an invalid copy number in the VALIDATE or RESTORE VALIDATE command.

Cause: The CHANGE DATAFILECOPY VALIDATE command discovered that the data file copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog or target database control file.

Cause: The CHANGE DATAFILECOPY VALIDATE command discovered that the data file copy still matches its data in the recovery catalog or target database control file.

Cause: The CHANGE CONTROLFILECOPY VALIDATE command discovered 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 or target database control file.

Cause: The CHANGE CONTROLFILECOPY VALIDATE command discovered that the control file copy still matches its data in the recovery catalog or target database control file.

Cause: The CROSSCHECK ARCHIVELOG command determined that the archived log could not be found or no longer contained the same data, so its record was marked expired.

Cause: The CROSSCHECK ARCHIVELOG command or VALIDATE HEADER option determined that the archived log still matches its data.

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

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

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

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

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

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

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

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

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

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

Cause: The specified data file could not be accessed. The reason codes are: 1 - file name is MISSINGxx in the control file 2 - file is offline 3 - file is not verified 4 - DBWR could not find the file 5 - unable to open file 6 - I/O error during read 7 - file header is corrupt 8 - file is not a data file 9 - file does not belong to this database 10 - file number is incorrect 12 - wrong file version 15 - control file is not current

Cause: This offline range is needed for recovering the specified data file, 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 1 control file copy containing the offline range was found in the recovery catalog and was in AVAILABLE status.

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

Cause: A restore could not proceed because no AUTOBACKUP was found or specified handle is not a valid copy or backup piece. In case of restore from AUTOBACKUP, it may be the case that a backup exists, but it does not satisfy the criteria specified in the user's restore operands. In case of restore from handle, it may be the handle is not a backup piece or control file copy. In may be that it does not exist.

Cause: Auxiliary type was specified for the control file, but no SET NEWNAME command has been previously issued for a data file.

Cause: An auxiliary command was issued but no connection to a auxiliary database has been established.

Cause: A DELETE SCRIPT command was executed.

Cause: An attempt was made to recover files that were offline or read-only or excluded. A RECOVER DATABASE command does not need to recover any files because all of the files to be recovered are offline or read-only or excluded. This can only occur when the SKIP clause includes the SYSTEM tablespace or all files are excluded from backup, restore, and recover. All data files of a proxy pluggable database are implicitly excluded.

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

Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated data file because it is offline clean at the desired point-in-time.

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

Cause: A BACKUP command with INCREMENTAL LEVEL > 0 was specified.

Cause: Attempt to allocate more than 1 channel in a job.

Cause: A BACKUP ARCHIVELOG command specified the MAXSETSIZE operand too low. The specified archived log is larger than MAXSETSIZE will allow.

Cause: A BACKUP DATAFILE(copy) command specified the MAXSETSIZE operand too low. The specified data file is larger than MAXSETSIZE will allow.

Cause: A backup command specifies the same data file or copy of a data file multiple times.

Cause: This version of recovery manager was incompatible with the indicated database or the DBMS_BACKUP_RESTORE package installed in the indicated database.

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

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

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

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

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

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

Cause: Input size for MAXPIECESIZE or MAXSETSIZE was out of range.

Cause: This is an informational message only.

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

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

Cause: A STARTUP command completed successfully.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: A command that moves files from the target instance to the auxiliary instance was requested. Such a command requires a net service name be present in the connect string used to connect to the auxiliary instance.

Cause: This is an informational message only.

Cause: This is an informational message only.

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

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

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

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

Cause: This message is issued in response to a LIST DB_UNIQUE_NAME command. The following fields are shown for each database that is known to the recovery catalog: DB Key: This is the unique key which identifies this database in the recovery catalog. DB Name: The name of the database. DB ID: The database ID. This is a number which remains the same for the life of the database, even if the database name is changed. DB_UNIQUE_NAME: db_unique_name value for the database.

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

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.

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

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

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

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

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 the REPORT SCHEMA command. The report shows the physical schema of the database at the indicated time. The following fields are shown for each data file and tempfile: File: The file number. Size(MB): The size of the file in mega bytes. Tablespace: The name of the tablespace which contains this file. RB segs: YES if this file is part of a tablespace containing rollback segments, otherwise NO. Datafile/Tempfile Name: The file name. Maxsize(MB): Maximum file size to which file can be extended

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

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 data file backup. Key: This is the unique key which identifies this proxy backup in the recovery catalog. This value can be used in a CHANGE command to change its status. If the target database control file is being used as the recovery catalog, then this field uniquely identifies this copy in the control file. File: The file number that this file was copied from. Status: This is the status of the file. Possible values are: A - Available U - Unavailable D - Deleted X - Expired Status 'U' will not be used if the target database control file is being used as the recovery catalog. Completion time: This is the date and time when the backup was created. This column will be printed in the default Oracle date format, unless overridden with a NLS_DATE_FORMAT environment variable. Ckp SCN: This is the checkpoint system change number (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.

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

Cause: This is an informational message only.

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

Cause: This is an informational message only.

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

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

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

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

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

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

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.

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.

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 version that is specified in the COMPATIBLE parameter, then it will no longer be able to restore proxy backups.

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.

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.

Cause: The command that was entered cannot be used while connected to a virtual private catalog.

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

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

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.

Cause: This is an informational message only.

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

Cause: A 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.

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

Cause: This is an informational message only.

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

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

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

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.

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

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

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

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.

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

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

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.

Cause: Recovery Manager requires the DBMS_RCVMAN package in the SYS schema of the indicated database. Normally this package is installed during database creation. To re-create the package, run the files dbmsrman.sql and prvtrmns.plb.

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

Cause: This is an informational message issued by the DROP CATALOG command, when connected to a virtual private catalog. Note that dropping a virtual private catalog does not delete any data, because the catalog data is owned by the base catalog.

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.

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

Cause: During the CREATE CATALOG or UPGRADE CATALOG command, the indicated object could not be created due to errors.

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

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

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

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

Cause: The SET COPIES or CONFIGURE BACKUP COPIES command was used to create more than one copy of each backup piece, but Enterprise Edition is not installed.

Cause: Tablespace Point-in-Time Recovery was attempted, but Enterprise Edition is not installed.

Cause: This is an informational message only.

Cause: UNTIL SCN cannot be more than the last system change number (SCN) of the last archived log

Cause: The RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST was specified with AS COPY.

Cause: BACKUP <VALIDATE|DURATION> and PROXY were specified in the same backup command.

Cause: The PROXY option was specified, but proxy copy of control file is not supported. This file will be placed into a non-proxy backup set.

Cause: The PROXY option was specified, but proxy copy of control file is not supported. This file will be placed into a non-proxy backup set.

Cause: A backup set record specifier did not match an backup set on device DISK in the recovery catalog.

Cause: The PROXY option was specified, but proxy copy of backup set is not supported. This file will be placed into a non-proxy backup set.

Cause: BACKUP BACKUPSET and VALIDATE were specified in the same backup command.

Cause: The configuration is not implemented in the current version.

Cause: Unsupported configuration string is stored in recovery catalog or target database control file.

Cause: An error was received when calling DBMS_RCVMAN

Cause: The DBA specified doesn't belong to the mentioned tablespace

Cause: An error was received when calling DBMS_RCVMAN

Cause: The DEVICE TYPE option was specified with a BACKUP, RESTORE, RECOVER, DUPLICATE, CHANGE, VALIDATE, CROSSCHECK, or DELETE EXPIRED command. This option is allowed only when automatically allocated channels are used.

Cause: Device type configuration was not found in recovery catalog

Cause: Channel id was used on ALLOCATE/RELEASE command.

Cause: A SET DATABASE command was specified when connected to target database or not connected to an auxiliary instance.

Cause: RELEASE CHANNEL was used without allocating any maintenance channels.

Cause: Parallelism for the device type in CONFIGURE PARALLELISM command is out of range

Cause: Channel number entered in CONFIGURE CHANNEL command is out of range.

Cause: CONFIGURE CHANNEL command entered has configuration value greater than 1024 bytes.

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

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

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

Cause: The CHANGE BACKUPPIECE AVAILABLE command was used, but the backup piece cannot be found on the storage medium.

Cause: The CHANGE PROXY AVAILABLE command was used, but the proxy copy cannot be found on disk.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: A control file or SPFILE restore from AUTOBACKUP was attempted and other restore options were used.

Cause: Target channel configuration could not be used for clone channel as it contains CONNECT option.

Cause: No more control file AUTOBACKUPS are possible in this day.

Cause: A CONTROLFILE AUTOBACKUP FORMAT cannot have more than one reserved format specifier.

Cause: A reserved format specifier was not specified for the CONTROLFILE AUTOBACKUP FORMAT

Cause: For restoring a control file AUTOBACKUP only SET UNTIL TIME can be used. It is not possible to translate the others to a precise day.

Cause: The specified parameter for restoring a control file AUTOBACKUP is out of the valid range.

Cause: Restore of a control file AUTOBACKUP or ADVISE FAILURE was attempted when the database is not mounted.

Cause: A control file restore was attempted when the database is mounted or open and no alternate destination was specified.

Cause: Control file AUTOBACKUP is not possible without a current control file.

Cause: The indicated data file will not be included in the backup set. It is already backed up on the device requested and file is offline/read-only data file. Use the FORCE option to override backup optimization.

Cause: The indicated log file will not be included in the backup set because it is already backed up on the device requested. Use FORCE option to override backup optimization.

Cause: The indicated backup set will not be copied because it is already backed up on the device requested. Use FORCE option to override backup optimization.

Cause: The indicated data file will not be included in the backup set. It is already been backed up once, or before the since time specified.

Cause: Some archived logs were not be backed up because they were already backed up on the device requested.

Cause: The indicated backup set will not be backed up. It has already been backed up on the device once, or before the since time specified.

Cause: Multiple backup copies and PROXY option were specified in BACKUP command.

Cause: SET DBID was used to set a DBID that translated into a database name that does not match newly specified database name or a previous SET DATABASE set a different database name.

Cause: The MAXSETSIZE option was specified for a backup backup set command.

Cause: This is an informational message, appearing when an archived log was found out of sync with catalog database.

Cause: MAXSETSIZE configured or specified in backup command should be greater than database block size.

Cause: A data file or archived log restore from AUTOBACKUP was attempted.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: KEEP UNTIL support only a future time.

Cause: The KEEP option is not supported for archived logs.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: The KEEP FOREVER option was used, but it requires a connection to a recovery catalog database. The KEEP FOREVER option cannot be used when the backup repository is the target database control file. This is because information about this backup cannot be permanently stored. (If information is stored just in the control file it will be aged out depending on CONTROL_FILE_RECORD_KEEP_TIME initialization parameter.)

Cause: This is an informational message only.

Cause: Command DELETE OBSOLETE and REPORT OBSOLETE requires that either: * RMAN retention policy is not NONE or, * RMAN retention policy is specified with REPORT/DELETE command.

Cause: The KEEP option was specified for a incremental backup.

Cause: The KEEP option is not supported for backup of backup sets.

Cause: The CHANGE BACKUPPIECE ... KEEP command was entered. KEEP attributes cannot be specified for backup pieces.

Cause: The CHANGE ARCHIVELOG ... KEEP command was entered. KEEP attributes cannot be specified for archived logs.

Cause: The CHANGE BACKUPSET ... KEEP command was entered, but the BACKUPSET contained archived logs. Backup sets with archived logs cannot have KEEP attributes.

Cause: The REDUNDANCY operand specified for the retention policy was zero.

Cause: The KEEP ... NOLOGS option was specified for a backup or copy of files in a fuzzy state. This kind of backup requires archived logs for recovery, so archived logs must be kept.

Cause: This is an informational message only. An archivelog backup will be created and kept so the specified backup can be recovered to a consistent state.

Cause: LIST COPY OF SPFILE was used, which is not supported because SPFILE cannot have a copy.

Cause: The BACKUP UP ... TIMES option was used as a qualifier. This option is supported only for archived logs.

Cause: The CHANGE BACKUP... KEEP command was entered. KEEP attributes cannot be specified for copies and backup pieces in a single command.

Cause: The is an informational message.

Cause: Invalid time was specified in the KEEP UNTIL clause. The KEEP UNTIL clause only supports future time until the year 2120.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: The indicated file will not be included in the backup set because its tablespace is configured as excluded from backup.

Cause: The indicated options conflict with each other or appear more than once in a LIST command.

Cause: The SYSTEM tablespace must be included in whole database backup.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: The clone database "init.ora" file does not specify the DB_NAME parameter.

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

Cause: A SWITCH command was specified for a data file, but the newname was set to NEW and the file was not restored. If newname is set to NEW, the file must be restored before issuing a SWITCH command.

Cause: The SET NEWNAME ... TO NEW option was specified but the OMF destination init parameter DB_CREATE_FILE_DEST is not set.

Cause: A file which is being backed up or copied is in backup mode. RMAN will back up the file anyway, but files do not need to be put into backup mode before backing them up with RMAN.

Cause: An incomplete recovery session was started, but the file is in newer than the UNTIL TIME clause.

Cause: An incomplete recovery session was started, but the file is newer than the UNTIL clause.

Cause: Restore of the specified archived log failed because the size of the archived log is larger than available disk space.

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

Cause: The MAXSIZE parameter is out of range.

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

Cause: The recovery failed because it requires more disk space. One of the following could have caused this error: 1) The MAXSIZE option is used but is not large enough to restore files. 2) Files should be restored to recovery area, but available disk space is not large enough to restore files.

Cause: A backup set is read more than once. Multiple reads of a backup set can slow restore performance. One of the following could have caused this: 1) The MAXSIZE option is used but is not large enough to restore files. 2) Files should be restored to a recovery area, but the available disk space is not large enough to restore files.

Cause: RESTORE CONTROLFILE or RESTORE SPFILE was specified without the FROM AUTOBACKUP option when RMAN is not connected to the recovery catalog.

Cause: A restore of the SPFILE from AUTOBACKUP was attempted when the instance is started with SPFILE and no alternate destination was specified.

Cause: The RMAN client caught a transient error and will automatically retry several times.

Cause: RESETLOGS CHANGE# and/or time of the target database doesn't match any database incarnation in the control file.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: SET DBID or SET DATABASE was used to specify the target database name which does not match specified database name in DUPLICATE command.

Cause: This message was issued in response to a SWITCH command.

Cause: The SWITCH command with the option TO COPY was specified but the data file has no valid copy to switch to.

Cause: The SWITCH command with the option TO COPY was specified, but data file is not offline and database is open.

Cause: The DBID in the DUPLICATE command did not match the previously specified DBID in the SET DBID command.

Cause: The platform id found in the data file header was not recognized.

Cause: The platform specified in the command did not match the platform found in the data file header.

Cause: The FROM TAG option was specified for data files.

Cause: The FOR RECOVER OF option was specified without specifying INCREMENTAL LEVEL > 0.

Cause: The specified option was specified for a backup as copy command.

Cause: This option was specified and it is not supported.

Cause: The backup set was specified with AS COPY.

Cause: No channel of TYPE DISK was allocated.

Cause: DISK and non DISK channels were allocated for a backup command. Configuration indicates to produce image copies to DISK, however due to the mixed channel types BACKUPSETS will be created on DISK.

Cause: An available data file copy for the specified data file could not be found.

Cause: An available data file copy for the specified data file could not be found.

Cause: This error message was accompanied by an additional error message or messages indicating the cause of the error.

Cause: An uneven number of patterns was specified.

Cause: The DB_FILE_NAME_CONVERT option was specified without AS COPY. This is not permitted for backup set backups where multiple files are combined into a set.

Cause: The system tablespaces could not be transported to other platforms.

Cause: ALLOW INCONSISTENT was specified in a non cross-platform backup command.

Cause: The platform name was not recognized.

Cause: The platform name was not recognized.

Cause: The platform name specified did not match the name of the database performing the conversion.

Cause: A command or option was used that requires a higher database compatibility than is currently set at the target database.

Cause: Conversion of Oracle data files between the specified platforms was not supported.

Cause: A conversion was attempted on a tablespace which is not read-only.

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

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

Cause: The TO DESTINATION option was specified for non-disk device.

Cause: RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST option was specified in BACKUP command on disk device without specifying TO DESTINATION option.

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

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

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

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

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

Cause: The AS COPY option was specified for non-disk device.

Cause: This messages is issued when the control file records were re-used before resyncing to catalog database.

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

Cause: Incompabitle options were specified on CONFIGURE ARCHIVELOG DELETION POLICY command.

Cause: The connect identifier for the specified DB_UNIQUE_NAME initialization parameter was not configured.

Cause: The DB_UNIQUE_NAME initialization parameter string was too long.

Cause: Resync was performed remotely for the specified DB_UNIQUE_NAME initialization parameter without connecting to it as target database. This type of remote resync has limitations. For example, RMAN output cannot be resynced. Please refer to RMAN documentation for a complete set of limitations.

Cause: V$RMAN_OUTPUT contents were not rescyned when the RESYNC CATALOG FROM DB_UNIQUE_NAME command was executed."

Cause: UNTIL TIME was more than the last NEXT TIME of the last archived log.

Cause: This version of Oracle Recovery Manager (RMAN) was incompatible with either the indicated database or the DBMS_BACKUP_RESTORE package installed in the indicated database.

Cause: The Oracle Recovery Manager (RMAN) client version did not match the catalog schema version number for the database.

Cause: DISK channel was allocated when the FROM FILE option was specified.

Cause: Incorrect syntax or invalid commands were found.

Cause: An error was encountered when trying to construct the full pathname for the specified file.

Cause: An error was encountered when trying to initialize the specified file for input.

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

Cause: A text script contained a line longer than the permitted maximum length.

Cause: An error was encountered when trying to close the specified file.

Cause: An error was encountered when trying to initialize the specified file for output.

Cause: An attempt was made to write to a file system that was full.

Cause: An attempt was made to list the scripts in the catalog, but no scripts could be found in the specified recovery catalog.

Cause: An attempt was made to call a script that could not be found in the target database or as a global script in the specified catalog.

Cause: Connection to a TARGET database was not specified.

Cause: Recovery Manager determined that this file is already restored. Use FORCE option to override this optimization.

Cause: Auxiliary instance file was not deleted. This message should be accompanied by other error message(s) indicating the cause of the error.

Cause: A BACKUP command does not need to backup any files, because all of the files to backup are already backed up.

Cause: sort area size too small to execute RMAN commands.

Cause: The specified archived log could not be found on any allocated channel.

Cause: The specified data file copy could not be found on any allocated channel.

Cause: The specified control file copy could not be found on any allocated channel.

Cause: A SPFILE restore could not proceed because no backup of the SPFILE 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.

Cause: A SPFILE restore could not proceed because the backup on a device type that was not allocated for restore.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: This is an informational message only.

Cause: The UNREGISTER DATABASE command was used with a database name that does not match the name of the database to which RMAN is connected.

Cause: The UNREGISTER DATABASE command was used with a database name that is ambiguous.

Cause: The UNREGISTER DATABASE command was used with a database name that was not found in the recovery catalog.

Cause: The command failed because of the following: o RMAN is not connected to the target database o The database name is not specified in the command o DBID is not set with the SET DBID command

Cause: This is an informational message only.

Cause: The specified platform name exceeded the maximum allowed platform name.

Cause: The specified backup sets were not found in the recovery catalog or target database control file.

Cause: The specified data file copies were not found in the recovery catalog or target database control file.

Cause: The indicated data file copy was not included in the backup set because it was already backed up on the device requested.

Cause: There were no files or all files were skipped for this backup set, therefore no backup set was created.