32 RMAN-00550 to RMAN-20506

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 preceeds 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 preceeded by information describing the error.

Cause: d 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: An error was signalled 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: 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: 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 release.

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: of the failure.

Cause: informational message only

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

Cause: informational message

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: informational message

Cause: informational message

Cause: Informational message. This preceeds 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: A "ALTER SYSTEM ARCHIVE LOG CURRENT" command completed successfully.

Cause: An invalid DEBUG LEVEL was used.

Cause: a DEBUG OFF comand was issued

Cause: a DEBUG comand was issued

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

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

Cause: a SPOOL LOG OFF comand was issued

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

Cause: informational message

Cause: informational message

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

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: 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: informational message

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: Either: -) The controlfile mounted by the auxiliary database does not have an entry for this datafile, therefore filename conversion is not possible. -) A COPY DATAFILE TO AUXNAME command was issued, but no auxname was set for this datafile.

Cause: RMAN is attempting to use the specified filename 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 tablespace or a tablespace containing rollback segments is not allowed in point-in-time recovery.

Cause: An attempt was made to apply TSPITR 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: SET NEWNAME ... TO NEW is not allowed with TSPITR.

Cause: The BLOCKRECOVER command was specified.

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

Cause: The Auxiliary instance was not in nomount state.

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: RMAN is attempting to use the specified control filename for TSPITR as a restore destination in the auxiliary database, but this name is already in use by the target database.

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 datafiles/archivelogs/ controlfile/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 datafile exists on disk but no incremental backup was found to apply to the datafile 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 DESTIONATION option was specified for a normal recovery. It is only allowed for tablespace 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 ARCHIVELOG DELETION POLICY

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 filename is converted to the name used for the auxiliary database, the converted name is larger than the maximum allowed filename.

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 controlfile is more recent than the last archivelog or the specified point in time.

Cause: SET NEWNAME ... TO NEW is not allowed with the DUPLICATE command.

Cause: informational message

Cause: informational message

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

Cause: DUPLICATE requires that the target database has a current controlfile

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 "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: informational message

Cause: informational message

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

Cause: informational message

Cause: informational message

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

Cause: An invalid incremental backup level was specified.

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

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

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

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

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

Cause: informational message

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

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

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

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

Cause: An archive 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 datafile copies have been made but not cataloged.

Cause: An archive log record specifier did not match any archive logs in the recovery catalog.

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

Cause: The "include current/standby controlfile" option was specified for an archive log backup set.

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

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 datafile to a location other than the original datafile, and Recovery Manager determined that the best candidate for restoring the file is the datafile copy with the same name, therefore the file is already restored and no action need be taken.

Cause: A call to dbms_rcvman returned an error.

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

Cause: The best candidate controlfile 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 datafile to a copy of a different datafile.

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 archive log name to its recovery catalog recid/timestamp. This message should be accompanied by other error message(s) indicating the cause of the error.

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

Cause: The controlfile 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 archive log which was requested to be restored (either explicitely 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 datafile. A level 0 backup of the datafile 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 existance is not recorded in the recovery catalog or controlfile.

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 datafile header could not be read or the header was not valid.

Cause: "current controlfile" was specified along with "standby controlfile".

Cause: "standby controlfile" was specified along with "current controlfile".

Cause: The archived log was not found. The repository 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 repository.

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

Cause: SKIP INACCESSIBLE option resulted in skipping archivelogs 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 repository.

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

Cause: The user attempted to use two (or more) conflicting operands within the same statement.

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

Cause: The controlfile 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 controlfile added this datafile to the controlfile, but it does not set the filename because that is unsafe.

Cause: DBWR could not find the specified datafile.

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

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 datafile. The file may have been overlaid or corrupted.

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

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

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

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

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

Cause: The controlfile record for this datafile is for an older incarnation of the datafile. A SWITCH command must be issued to update the controlfile before doing RECOVER.

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

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

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 datafile could not find a destination name for the specified datafile.

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

Cause: The SKIP READONLY option was specified for an archive 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 controlfile copy in the recovery catalog or target database controlfile.

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

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

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

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

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

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

Cause: See accompanying error

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

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

Cause: An archive 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 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 controlfile is mounted.

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

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

Cause: An attempte 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: informational message

Cause: informational message

Cause: informational message

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 datafilecopy key in the recovery catalog.

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

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 will not be included in the backup set because it is 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 SKIP OFFLINE and SKIP READONLY options are only permitted when the target database controlfile is current. When the target controlfile is not current, it is not possible to obtain a datafile's offline/readonly status.

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

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

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 controlfile 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 controlfile mounted by the target instance is not current, so the information about the current list of datafiles 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 datafiles, controlfiles or archive 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 controlfile is not current, it may not be possible to determine if a satisfactory backup exists for files which have been offline since the last OPEN RESETLOGS.

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

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: 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: The CHANGE DATAFILE COPY VALIDATE command found that the datafile copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog.

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

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

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

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

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

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

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

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 archive 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 datafile do not exist, but a more recent backup of the datafile exists which can be recovered.

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

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 datafile could not be accessed. The reason codes are: 1 - filename is MISSINGxx in the controlfile 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 datafile 9 - file does not belong to this database 10 - file number is incorrect 12 - wrong file version 15 - controlfile is not current

Cause: This offline range is needed for recovering the specified datafile, but the offline range record has aged out of the current controlfile and no controlfile copy with the record could be accessed. At least 1 controlfile 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 controflile copy. In may be that it does not exist.

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

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

Cause: A DELETE SCRIPT command was executed.

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

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

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

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

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 archive log is larger than MAXSETSIZE will allow.

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

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

Cause: This version of recovery manager is 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: informational message

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: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

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: informational message

Cause: informational message

Cause: informational message

Cause: informational message

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 INCARNATION OF DATABASE command. The following fields are shown for each database that is registered with the recovery catalog: DB Key: This is the unique key which identifies this database in the recovery catalog. Inc Key: This is the unique key which identifies this incarnation of the database in the recovery catalog. DB Name: The name of the database. DB ID: The database ID. This is a number which remains the same for the life of the database, even if the database name is changed. Status: 'YES' if this is the current incarnation of this database, otherwise 'NO'. Reset SCN: SCN of the most recent resetlogs operation. Reset Time: Time of the most recent resetlogs operation.

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 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 datafile: File: The file number. K-bytes: The size of the file. 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. Name: The file name.

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 datafile backup. Key: This is the unique key which identifies this proxy backup in the recovery catalog. This value can be used in a CHANGE command to change its status. If the target database control file is being used as the recovery catalog, then this field uniquely identifies this copy in the controlfile. 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 controlfile is being used as the recovery catalog. Completion time: This is the date and time when the backup was created. This column will be printed in the default Oracle date format, unless overridden with a NLS_DATE_FORMAT environment variable. Ckp SCN: This is the checkpoint SCN of the backup. The file contains all changes made at or before this SCN. Ckp time: This is the time that the file was last checkpointed. Handle: This is the media manager handle of the proxy backup.

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

Cause: informational message

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

Cause: informational message

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: informational message

Cause: informational message

Cause: informational message

Cause: informational message

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

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 release 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: 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: informational message

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 SETLIMIT CHANNEL command was used to set the backup piece size limit, but the media management software used by the target database cannot create backup pieces that large.

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

Cause: informational message

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 deletes the recovery catalog, rendering all database backups unusable, and should be used with care. The command must be entered twice to ensure that this is really what you want to do.

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

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 PL/SQL package specification or body could not be created because of PL/SQL compilation errors.

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

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

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

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: A point-in-time tablespace recovery was attempted, but Enterprise Edition is not installed.

Cause: informational message

Cause: UNTIL scn cannot be more than the last 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 controlfile is not supported. This file will be placed into a non-proxy backup set.

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

Cause: A backupset record specifier did not match an backupset 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 release.

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

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: 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 datafilecopy 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 archivelog cannot be found on disk.

Cause: The CHANGE BACUKPPIECE 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: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: A controlfile 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 controlfile 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 controlfile 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 controlfile autobackup is out of the valid range.

Cause: Restore of a controlfile autobackup was attempted when the database is not mounted.

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

Cause: Controlfile autobackup is not possible without a current controlfile.

Cause: The indicated datafile will not be included in the backup set. It is already backed up on the device requested and file is offline/read-only datafile. 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 backupset will not be copied because it is already backed up on the device requested. Use FORCE option to override backup optimization.

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

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

Cause: The indicated backupset 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: The MAXSETSIZE option was specified for a backup backupset command.

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

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

Cause: A datafile or archived log restore from autobackup was attempted.

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

Cause: KEEP UNTIL support only a future time.

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

Cause: informational message

Cause: informational message

Cause: informational message

Cause: informational message

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 controlfile. This is because information about this backup cannot be permanently stored. (If information is stored just in the controlfile it will be aged out depending on CONTROL_FILE_RECORD_KEEP_TIME initialization parameter.)

Cause: informational message

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

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

Cause: The CHANGE BACKUPSET ... KEEP command was entered, but the BACKUPSET is an incremental backup set. Incremental backup sets 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 on open database. This kind of backup requires archive logs for recovery, so archive logs must be kept.

Cause: The KEEP ... CONSISTENT option was specified but the option is not supported.

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: informational message

Cause: informational message

Cause: The indicated file will not be included in the backup set because it's tablesapce is configured as excluded from backup.

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

Cause: This is a user prompt.

Cause: An incorrect response was entered.

Cause: An error occurred reading user response.

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

Cause: informational message

Cause: informational message

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

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

Cause: A SWITCH command was specified for a datafile, 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 destinatation 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 message was issued in response to a SWITCH command.

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

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

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

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

Cause: The FROM TAG option was specified for datafiles.

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 backupset 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 datafilecopy for the specified datafile could not be found.

Cause: An available datafilecopy for the specified datafile 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 backupset backups where multiple files are combined into a set.

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

Cause: There was a missing parameter to the command.

Cause: There was a missing parameter to the 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 was attempted that requires a higher database compatibility.

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

Cause: Conversion of Oracle data files between the specified platforms was not necessary because the Oracle data file format is already the same on both platforms.

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: 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: 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: The number of files to retrieve from the catalog does not match the number of destinations specified.

Cause: The filename provided was not found in the catalog.

Cause: informational message

Cause: informational message

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

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

Cause: informational message

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 archivelog could not be found on any allocated channel.

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

Cause: The specified controlfilecopy 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: informational message

Cause: informational message

Cause: informational message

Cause: This is a user prompt.

Cause: This is a user prompt.

Cause: This is a user prompt.

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 UNREGISTER DATABASE 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: informational message

Cause: The specified platform name exceeds the maximum allowable platform name.

Cause: The specified backupsets are not found in the repository.

Cause: The specified datafilecopies are not found in the repository.

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

Cause: All files for this backup set were skipped, therefore no backup no backup set was created.

Cause: The executed command requires a SBT channel, but no channels of type SBT were configured or allocated.

Cause: RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST option was specified in BACKUP command, but no or more than one tertiary channel was found. One of the following could have caused this error: 1) All of the allocated channels are of type DISK. 2) No tertiary storage (SBT) channel configured. 3) CHANNEL or DEVICE TYPE option specified is of DISK type. 4) More than one tertiary storage channel allocated or configured and no DEVICE TYPE or CHANNEL option specified.

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

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

Cause: The target database has a new incarnation that has not already been seen by the recovery catalog. This usually happens because a point-in-time recovery was done. RMAN has made the necessary updates to the recovery catalog.

Cause: The routine createRmanStatusRow() or createRmanOutputRow() could add new row into V$RMAN_STATUS or V$RMAN_OUTPUT.

Cause: Informational message only.

Cause: The backupset was specified with AS COMPRESSED BACKUPSET.

Cause: This is informational message displayed when PARTIAL option of DURATION option was specified on the backup command and backup could not be completed with in the given duration time.

Cause: This is informational message displayed when PARTIAL option of DURATION option was specified on the backup command and backup could not be completed with in the given duration time.

Cause: This is informational message displayed when PARTIAL option of DURATION option was specified on the backup command and backup could not be completed with in the given duration time.

Cause: This is informational message displayed when PARTIAL option of DURATION option was specified on the backup command and backup could not be completed with in the given duration time.

Cause: This option was specified in a backup command specification for BACKUP BACKUPSET or BACKUP CURRENT CONTROLFILE command.

Cause: RMAN allocated more than one channel for a job, but the job will not run in parallel on these channels because parallelism require Enterprise Edition.

Cause: RMAN allocated more than one channel for a job, but the job will not run in parallel on these channels because parallelism require Enterprise Edition.

Cause: Recover database was called with TEST and PARALLEL option

Cause: Recover database was called with PARALLEL and NOPARALLEL option

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

Cause: informational message

Cause: informational message

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

Cause: This is a user prompt.

Cause: informational message

Cause: informational message

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