Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
For more information about the Recovery Manager, refer to the Oracle9i Recovery Manager User's Guide and the Oracle9i User-Managed Backup and Recovery Guide.
Cause: LPMLOADPKG() return an error indication.
Action: This message should be accompanied by one or more other error messages indicating the cause of the error.
Cause: The parser package initialization routine returned an error.
Action: This message should be accompanied by one or more other error messages indicating the cause of the error.
Cause: The arguments supplied to RMAN could not be parsed, or no arguments were supplied at all.
Action: This message should be accompanied by one or more other error messages indicating the cause of the error.
Cause: LPMLOADPKG() return an error indication.
Action: This message should be accompanied by one or more other error messages indicating the cause of the error.
Cause: The internal package initialization routine returned an error.
Action: This message should be accompanied by one or more other error messages indicating the cause of the error.
Cause: The TARGET parameter was not specified.
Action: Supply the necessary parameter.
Cause: An error occurred when trying to open the file.
Action: Check that the file name was specified correctly and that the file exists and that the user running RMAN has read permission for the file.
Cause: An error occurred when trying to open the file.
Action: Check that the file name was specified correctly and that the file exists and that the user running RMAN has write permission for the file.
Cause: The parser detected a syntax error.
Action: This message should be accompanied by one or more other error messages indicating the cause of the error.
Cause: The specified username exceeds the maximum allowable username length.
Action: Correct the username.
Cause: The specified password exceeds the maximum allowable password length.
Action: Correct the password.
Cause: The SQL*Net host connect string exceeds the maximum allowable length.
Action: Correct the host string.
Cause: An error occurred while trying to read from STDIN or from the CMDFILE.
Action: Ensure that the CMDFILE is readable. The CMDFILE must be a text file with one line per record.
Cause: An error occurred when trying to open the file.
Action: Check that the file name was specified correctly and that the user running RMAN has write permission for the file.
Cause: An error occurred while trying to print the error message stack.
Action: If the associated error message indicates a condition that can be corrected, do so, otherwise contact Oracle Support Services.
Cause: The user typed ^C or ATTN.
Action: No action required.
Cause: This message precedes an error message stack.
Action: The errors are printed in last-in first-out order. So to interpret them correctly, read from the bottom to the top.
Cause: The end of an inline CMDFILE was reached. This is just an informational message.
Action: No action required.
Action: The errors are printed in last-in first-out order. So to interpret them correctly, read from the bottom to the top.
Cause: This message is used only when the PIPE option was specified.
Action: Enqueue some RMAN input into the pipe.
Cause: This is an internal error
Action: Contact Oracle Support Services.
Cause: RMAN was run with input/output being sent to DBMS_PIPE. An error was encountered while reading from or writing to the pipe. This error should be preceded by information describing the error.
Action: RMAN terminates. Refer to the cause/action for the preceding errors.
Cause: RMAN was running in DBMS_PIPE mode. A timeout occurred while calling DBMS_PIPE.SEND_MESSAGE. This occurs when the pipe is full and no process has dequeued any of the messages. This is usually caused by death of the process that was talking to RMAN.
Action: RMAN will abort.
Cause: The PIPE and CMDFILE options cannot be used together. When using the PIPE option, RMAN must obtain its input from the input pipe.
Action: Remove either the PIPE or CMDFILE option.
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.
Action: Specify the TARGET option on the RMAN command line.
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.
Action: If you are attempting to put data on the RMAN input pipe prior to starting RMAN, so RMAN will process the data on the pipe as soon as it starts, you must be connected as SYS and you must first use the dbms_pipe.create_pipe function to explicitely create the pipe as a private pipe.
Cause: An internal error in Recovery Manager occurred.
Action: Contact Oracle Support Services.
Cause: A fatal error has occurred.
Action: This message should be accompanied by one or more other error messages indicating the cause of the error.
Cause: An error was signalled during parsing.
Action: This message should be accompanied by one or more other error messages indicating the cause of the error.
Cause: This is an informational message indicating the line and column where a syntax error was detected.
Action: No action required.
Cause: This is an informational message indicating the identifier token that caused a syntax error.
Action: No action required.
Cause: The RMANXX.MSB file is not the correct version.
Action: Check that the installation was done correctly. The RMAN binary (executable, load module, whatever it is called on your operating system) and the RMANXX.MSB file must be from the same version, release, and patch level.
Cause: An illegal punctuation character was encountered.
Action: Remove the illegal character.
Cause: This is probably caused by failure to supply the closing quote for a quoted string.
Action: Correct the input.
Cause: An input character that is neither an alpha, digit, or punctuation was encountered.
Action: Remove the character.
Cause: A quoted string longer than 2000 bytes was encountered.
Action: This may be caused by a missing close quote. If so, add the missing quote, otherwise shorten the string.
Cause: A token longer than 1000 bytes was encountered.
Action: Tokens must be separated by white space or punctuation. Either add the missing white space or punctuation, or shorten the token.
Cause: A line longer than 500 bytes was encountered.
Action: Break the line up into shorter lines.
Cause: Parser failed to convert input string to an integer.
Action: values for integer are from 0 to 2147483648. Retry the tcommand using a valid integer value.
Cause: This message should be accompanied by one or more other error messages indicating the cause of the error.
Action: Check the accompanying errors.
Cause: This message should be accompanied by one or more other error messages indicating the cause of the error.
Action: Check the accompanying errors.
Cause: This message should be accompanied by one or more other error messages indicating the cause of the error.
Action: Check the accompanying errors.
Cause: The command is not implemented in the current release.
Action: Avoid using the command.
Cause: This message should be accompanied by one or more other error messages indicating the cause of the error.
Action: Check the accompanying errors.
Cause: This message should be accompanied by one or more other error messages indicating the cause of the error.
Action: Check the accompanying errors.
Cause: This message should be accompanied by other error messages indicating the cause of the error.
Action: Check the accompanying errors.
Cause: This message should be accompanied by one or more other error messages indicating the cause of the error.
Action: Check the accompanying errors.
Cause: A fatal error occurred during compilation of a command.
Action: This message should be accompanied by other errors explaining the cause of the failure.
Cause: This message is accompanied by other errors explaining the cause of the failure.
Action: Check the accompanying errors.
Cause: Informational message only.
Action: No action required.
Cause: A stored script is calling itself or another script which calls itself.
Action: Remove the recursion.
Cause: This is an informational message.
Action: No action required.
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.
Action: Try using a different SQL*Net driver.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: Informational message. This precedes error 3012.
Action: No action required.
Cause: A SET ECHO ON command was issued.
Action: No action required.
Cause: A SET ECHO OFF command was issued.
Action: No action required.
Cause: The option used with the SET command is not valid outside a run block.
Action: Change the SET command or place it inside a run block.
Cause: The option used with the SET command is not valid inside of a run block.
Action: Change the SET command or place it outside a run block.
Cause: A "ALTER SYSTEM ARCHIVE LOG CURRENT" command completed successfully.
Action: No action required; this is an informational message.
Cause: An invalid DEBUG LEVEL was used.
Action: Change the DEBUG LEVEL argument.
Cause: The user interrupted the current job.
Action: No action required.
Cause: An internal error occurred while converting a date.
Action: Contact Oracle Support Services.
Cause: A memory allocation request could not be satisfied.
Action: Increase the amount of memory available to RMAN.
Cause: This message should be accompanied by one or more other error messages indicating the cause of the error.
Action: Check the accompanying errors.
Cause: OCI process level initialization failed.
Action: This error should not normally occur.
Cause: The call to OCIEnvInit failed.
Action: This error should not normally happen. Contact Oracle Support Services.
Cause: An error was received from the recovery catalog database.
Action: The cause of the failure is included in the error message. Correct the cause of the failure and retry the command.
Cause: An error was received from the target database.
Action: The cause of the failure is included in the error message. Correct the cause of the failure and retry the command.
Cause: An error was received from the clone or duplicate database.
Action: The cause of the failure is included in the error message. Correct the cause of the failure and retry the command.
Cause: A warning was received from the recovery catalog database.
Action: The cause of the failure is included in the error message. Correct the cause of the failure and retry the command.
Cause: A warning was received from the target database.
Action: The cause of the failure is included in the error message. Correct the cause of the failure and retry the command.
Cause: A warning was received from the clone or duplicate database.
Action: The cause of the failure is included in the error message. Correct the cause of the failure and retry the command.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: A connection is required before startup.
Action: Connect and retry the command.
Cause: The database failed to start.
Action: The cause of the failure is included in the error message. Correct the cause of the failure and retry the STARTUP command.
Cause: An error was received while setting the session character set in the target database.
Action: This error should not normally happen. Contact Oracle Support Services.
Cause: An error was received while initializing the OCI layer.
Action: This error should not normally happen. Contact Oracle Support Services.
Cause: The CONNECT clause of 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.
Action: Verify that the CONNECT string connects to the same database as the one specified in the TARGET connection for the CONNECT command.
Cause: The CONNECT clause of 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.
Action: Verify that the CONNECT string connects to the same database as the one specified in the TARGET connection for the CONNECT command.
Cause: The CONNECT clause of 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.
Action: Verify that the CONNECT string connects to the same database as the one specified in the TARGET connection for the CONNECT command.
Cause: One of the following:
Action: Use the SET AUXNAME command to specify a file name that the auxiliary database can use as a restore destination.
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.
Action: Use the SET AUXNAME command to specify a name for the datafile that does not conflict with a file name in use by the target database.
Cause: Previously encountered error(s) were issued which require corrective action.
Action: Resolve the error conditions, and then re-issue the RECOVER command.
Cause: The SYSTEM tablespace or a tablespace containing rollback segments is not allowed in point-in-time recovery.
Action: Remove the indicated tablespace from the recovery set and retry the operation.
Cause: An attempt was made to apply TSPITR to a database that is in NOARCHIVELOG mode.
Action: If all required archive log files are available to TSPITR, alter the target database log mode to ARCHIVELOG and retry the TSPITR operation. Otherwise, TSPITR cannot be applied to this database.
Cause: The requested tablespace has been re-created and is not allowed in point-in-time recovery.
Action: Remove the indicated tablespace from the recovery set and retry the operation.
Cause: Standby recover can only be performed for the whole database.
Action: Change the tablespace list to a database specification.
Cause: A command was entered that requires a channel, and no channel is allocated.
Action: Use ALLOCATE CHANNEL before using the command.
Cause: SET NEWNAME ... TO NEW is not allowed with TSPITR.
Action: Set the new name to a specific file name and retry.
Cause: The BLOCKRECOVER command was specified.
Action: Remove the BLOCKRECOVER command.
Cause: The target database was not opened in read write mode.
Action: Open the database in read write mode.
Cause: The Auxiliary instance was not in nomount state.
Action: Open the auxiliary instance 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 421// be started in restricted mode with default parameters.
Action: No action required. This is an informational message.
Cause: Creation of a temporary file failed. It could be that the system does not have enough resources (disk space, memory, or similar).
Action: Verify and free some system resources memory and try again.
Cause: Opening of a temporary file failed. It could be that the system does not have enough resources (disk space, memory, or similar).
Action: Verify and free some system resources memory and try again.
Cause: Writing to a temporary file failed. It could be that the system does not have enough resources (disk space, memory, or similar).
Action: Verify and free some system resources memory and try again.
Cause: A DUPLICATE command was issued, but the auxiliary database is mounted.
Action: Dismount the auxiliary database.
Cause: Previously encountered errors require corrective action.
Action: Resolve the error conditions, and reissue the DUPLICATE TARGET DATABASE command.
Cause: A DUPLICATE command was issued, but the target database control file is not mounted.
Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.
Cause: No auxiliary channels are allocated.
Action: Allocate an auxiliary channel.
Cause: Only one redo log file or group was specified.
Action: Specify at least one more redo log file or group.
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.
Action: Change initialization parameter DB_FILE_NAME_CONVERT to convert to a valid file name.
Cause: This message should be accompanied by other error messages indicating the cause of the error.
Action: Check the accompanying errors.
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.
Action: If an explicit point in time was specified, change it to be at least the controlfile checkpoint; otherwise archive (and backup/copy) the current log.
Cause: SET NEWNAME ... TO NEW is not allowed with the DUPLICATE command.
Action: Set the new name to a specific file name and retry.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: The SYSTEM tablespace must be included in the duplicate database.
Action: Remove the SYSTEM tablespace from the SKIP list and retry the operation.
Cause: DUPLICATE requires that the target database has a current controlfile.
Action: Open the target database and retry operation.
Cause: All tablespaces that have undo information must be included in the duplication.
Action: Remove the specified tablespace from the SKIP list and retry the operation.
Cause: The RECOVER.BSQ file could not be opened.
Action: Check that the file was installed correctly and that the user running RMAN has authority to read the file.
Cause: A syntax error was encountered while parsing RECOVER.BSQ.
Action: Ensure that the correct version of the file is installed and that it has not been modified in any way.
Cause: A command that is allowed only when a recovery catalog connect string was supplied was attempted.
Action: Avoid using the command, or restart RMAN and supply a recovery catalog connect string via the RCVCAT parameter.
Cause: This message should be accompanied by other error messages indicating the cause of the error.
Action: Check the accompanying errors.
Cause: This message should be accompanied by other error messages indicating the cause of the error.
Action: Check the accompanying errors.
Cause: This is an informational message.
Action: No action is required.
Cause: This is an informational message.
Action: No action is required.
Cause: The target database has not mounted the control file, and its INIT.ORA file does not specify the DB_NAME parameter.
Action: MOUNT the target database, or add the DB_NAME parameter to its INIT.ORA file and restart the instance.
Cause: This is an informational message.
Action: No action is required.
Cause: This is an informational message.
Action: No action is required.
Cause: An error occurred while looking up the specified datafile in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the file name is entered correctly. If the datafile was added recently, then a RESYNC CATALOG must be done to update the recovery catalog.
Cause: An invalid incremental backup level was specified.
Action: Incremental backup level must be between 0 and 8.
Cause: A RELEASE or SETLIMIT command was found for a channel identifier that was not yet allocated.
Action: Correct the channel identifier, or add an ALLOCATE CHANNEL command.
Cause: A channel identifier was reused without first releasing the channel.
Action: Add a RELEASE CHANNEL command.
Cause: Not all commands are implemented for the beta release.
Action: Avoid using the command.
Cause: An error occurred while looking up the specified datafile copy name in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the file name is entered correctly. If the datafile copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.
Cause: The specified operand appears more than once in the same backup specifier or backup command.
Action: Delete the duplicate operand.
Cause: The parser package initialization routine returned an error.
Action: This message should be accompanied by other error messages indicating the cause of the error.
Cause: A backup specification operand appears more than once in a backup specification.
Action: Delete the duplicate operand.
Cause: An error occurred while looking up the specified tablespace name in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the tablespace is entered correctly. If the tablespace was added recently, then a RESYNC CATALOG must be done to update the recovery catalog.
Cause: This is an informational message.
Action: No action is required.
Cause: The FROM DATAFILECCOPY/BACKUPSET option applies only to datafile and control file restores.
Action: Use this option only for datafile and control file restores.
Cause: A datafile, tablespace, or database restore could not proceed because no backup or copy of the indicated file was found. It may be the case that a backup or copy of this file exists but does not satisfy the criteria specified in the user's restore operands.
Action: No action required. This is an informational message. See message 6026 for further details.
Cause: A control file restore could not proceed because no backup or copy of the control file was found. It may be the case that a backup or copy of this file exists but does not satisfy the criteria specified in the user's restore operands.
Action: No action required. This is an informational message. See message 6026 for further details.
Cause: An archive log restore could not proceed because no backup of the indicated archived log was found. It may be the case that a backup of this file exists but does not satisfy the criteria specified in the user's restore operands.
Action: No action required This is an informational message. See message 6026 for further details.
Cause: Some of the files specified for restore could not be found. Message 6023, 6024, or 6025 is also issued to indicate which files could not be found. Some common reasons why a file cannot be restored are that there is no backup or copy of the file that is known to Recovery Manager, or there are no backups or copies that fall within the criteria specified on the RESTORE command, or some datafile copies have been made but not cataloged.
Action: The Recovery Manager LIST command can be used to display the backups and copies that Recovery Manager knows about. Select the files to be restored from that list.
Cause: An archive log record specifier did not match any archive logs in the recovery catalog.
Action: Resubmit the command with a different archive log record specifier. The RMAN LIST command can be used to display all archive logs that Recovery Manager knows about.
Cause: The CHANNEL, TAG, FROM, PARMS, VALIDATE, or CHECK READONLY option was specified more than once in the restore command or in one of the restore specifications.
Action: Correct and resubmit the command.
Cause: The INCLUDE CURRENT/STANDBY CONTROLFILE option was specified for an archive log backup set.
Action: Use this option only for datafile backup sets.
Cause: The DELETE INPUT option was specified for a backup that contains the current control file or datafiles.
Action: Remove the option and resubmit the command.
Cause: An error was received when calling DBMS_RCVMAN.
Action: This message should be accompanied by other error messages indicating the cause of the error.
Cause: No channel of TYPE DISK was allocated.
Action: Allocate a channel of TYPE DISK and re-issue the command.
Cause: An RMAN command requests a specific channel, but the requested channel has not been allocated.
Action: ALLOCATE the channel, or correct the channel identifier.
Cause: No channels are allocated.
Action: ALLOCATE a channel.
Cause: The RECOVER.BSQ file is incompatible with the RMAN executable.
Action: Install the correct version of RECOVER.BSQ.
Cause: A SET NEWNAME command was issued to restore a datafile to a location other than the original datafile, and Recovery Manager determined that the best candidate for restoring the file is the datafile copy with the same name, therefore the file is already restored and no action need be taken.
Action: No action required. This is an informational message.
Cause: An incremental backup of a datafile copy was requested.
Action: Change the incremental level to 0, or request a full backup.
Cause: A call to DBMS_RCVMAN returned an error.
Action: This message should be accompanied by other error messages indicating the cause of the 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.
Action: Correct and resubmit the SWITCH command.
Cause: The best candidate control file for restoration is the one that is named in the RESTORE (control file) command, hence no action need be taken.
Action: No action required. This is an informational message.
Cause: An attempt was made to switch a datafile to a copy of a different datafile.
Action: Correct and resubmit the SWITCH command.
Cause: The tag option was supplied but does not apply to this type of backup.
Action: Remove the TAG operand and re-enter the command.
Cause: The tag option was supplied but does not apply to this type of copy.
Action: Remove the TAG operand and re-enter the command.
Cause: The specified operand appears more than once in the same copy specification.
Action: Remove the redundant operand.
Cause: The LEVEL option was supplied but does not apply to this type of copy.
Action: Remove the LEVEL operand and re-enter the command.
Cause: An error occurred while translating an archive log name to its recovery catalog RECID/timestamp. This message should be accompanied by other error messages indicating the cause of the error.
Action: Check the accompanying errors.
Cause: The indicated datafile was specified more than once in the same restore command.
Action: Correct and resubmit the RESTORE command.
Cause: The control file was specified more than once in the same RESTORE command.
Action: Correct and resubmit the RESTORE command.
Cause: The check logical option was supplied but does not apply to this type of copy.
Action: Remove the CHECK LOGICAL operand and re-enter the command.
Cause: An archive log which was requested to be restored (either explicitly or via a range specification) does not need to be restored because it already exists on disk.
Action: No action required. This is an informational message.
Cause: This option was specified in a backup specification.
Action: Remove the DELETE INPUT option.
Cause: An incremental backup at level 1 or higher could not find any parent backup or copy of the indicated datafile. A level 0 backup of the datafile will be taken automatically.
Action: This is an informational message only.
Cause: This message is accompanied with another message identifying the missing log. The log would be needed to perform the media recovery, but the log is not on disk and no backup set containing the log is available.
Action: Determine if a backup set containing the log can be made available. If so, then use the CHANGE command to make the backup set available and retry the command. If not, then a point in time recovery up to the missing log is the only alternative.
Cause: Media recovery is requesting a log whose existence is not recorded in the recovery catalog or control file.
Action: If a copy of the log is available, then add it to the recovery catalog and/or control file via a CATALOG command and then retry the RECOVER command. If not, then a point in time recovery up to the missing log is the only alternative.
Cause: A log which was on disk at the start of media recovery or which should have been restored from a backup set could not be found.
Action: Check the Recovery Manager message log to see if the log was restored by a previous job step. If so, then check the V$ARCHIVED_LOG view to see if the log is listed in the control file. If so, then validate that the log exists on disk and is readable. If the log was not restored, or was restored but no record of the log exists in V$ARCHIVED_LOG, then contact Oracle Support Services.
Cause: A backup or copy could not proceed because the datafile header could not be read or the header was not valid.
Action: Make the datafile accessible or skip it.
Cause: "current controlfile" was specified along with "standby controlfile".
Action: Remove "current controlfile" or "standby controlfile" from the backup specification.
Cause: "standby controlfile" was specified along with "current controlfile".
Action: Remove "standby controlfile" or "current controlfile" from the backup specification.
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.
Action: If the archived log has been removed with an outside utility and the archivelog has already been backed up, then you can synchronize the repository by running CROSSCHECK ARCHIVELOG ALL. If the archivelog has not been previously backed up, then you should take a full backup of the database and archivelogs to preserve recoverability. Previous backups are not fully recoverable.
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 was made OFFLINE [DROP].
Action: If there is no backup of skipped datafiles and the tablespace has to be recoverable without ALL archive logs since datafile creation, then you should make these datafiles available for backup.
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.
Action: If the archived log has been removed with an outside utility and the archivelog has already been backed up, then you can synchronize the repository by running CROSSCHECK ARCHIVELOG ALL. If the archivelog has not been previously backed up, then you should take a full backup of the database and archivelogs to preserve recoverability. Previous backups are not fully recoverable.
Cause: A backup command requested a backup of the SPFILE, but no SPFILE was used to start the instance.
Action: Create an SPFILE and re-start the instance using the SPFILE or modify the command.
Cause: DBID is not found in the recovery catalog.
Action: Verify that the DBID is correct and restart the command.
Cause: A RECOVER command was issued, but the target database control file is not mounted.
Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.
Cause: The control file has been restored from a backup or was created via ALTER DATABASE CREATE CONTROLFILE.
Action: Use the RECOVER DATABASE command to perform the recovery.
Cause: This error should be accompanied by one or more instances of message RMAN-06094.
Action: Refer to message RMAN-06094.
Cause: Media recovery of a backup control file added this datafile to the control file, but it does not set the file name because that is unsafe.
Action: If the datafile is on disk, then issue ALTER DATABASE RENAME to correct the control file. Otherwise, RESTORE the datafile, and then use SWITCH to make it known to the control file. If the tablespace containing this datafile will be dropped, then reissue the RECOVER command with a SKIP clause to skip recovery of this tablespace.
Cause: DBWR could not find the specified datafile.
Action: Check the location of your datafile.
Cause: An error was encountered when trying to open the specified datafile.
Action: Ensure that the datafile exists and is accessible.
Cause: Oracle detected a corruption in the file header. A media failure has probably occurred.
Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.
Cause: The file header indicates that this file is not a datafile. The file may have been overlaid or corrupted.
Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.
Cause: The file header indicates that this file belongs to some other Oracle database.
Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.
Cause: The datafile header indicates the file contains a different datafile number.
Action: RESTORE the datafile, and then retry the RECOVER command.
Cause: The control file entry for this datafile specifies a different version of this datafile. Different versions of a datafile can exist when a tablespace is dropped, and a new tablespace is created which reuses the same datafile numbers.
Action: If the datafile is correct, the fix the control file by using the SWITCH command. Otherwise, RESTORE the correct version of this datafile and retry the RECOVER command.
Cause: The control file appears to be older than the specified datafile, but it is not marked as a backup control file. This indicates that the control file has been replaced with an older version. This error does not occur when a backup control file which was created via Recovery Manager or the ALTER DATABASE BACKUP CONTROLFILE command is restored because such control files are marked as backups.
Action: RESTORE a control file and perform RECOVER DATABASE.
Cause: A RECOVER command was issued, but the target database is not mounted.
Action: Issue ALTER DATABASE MOUNT.
Cause: The control file record for this datafile is for an older incarnation of the datafile.
Action: Issue a SWITCH command to update the control file before doing RECOVER.
Cause: X$KCVFH returned the specified code in the HXERR column when it was queried for the specified datafile.
Action: Ensure the datafile exists and is readable. Using a newer release of Recovery Manager may return a more meaningful error message. If you have no newer version of Recovery Manager, contact Oracle Support Services.
Cause: The specified tag refers to multiple datafile copies belonging to different datafiles.
Action: Specify the datafile copy by file name rather than by tag.
Cause: The recovery catalog database returned an error. This error explains the cause of the problem.
Action: Correct the problem and retry.
Cause: A REPLICATE command was issued, but the target database is already mounted.
Action: dismount the target database control file by issuing ALTER DATABASE CLOSE and ALTER DATABASE DISMOUNT via Enterprise Manager or Server Manager.
Cause: A RESTORE command for the specified datafile could not find a destination name for the specified datafile.
Action: Add a SET NEWNAME command prior to the RESTORE command to specify the restore destination for this file.
Cause: The SKIP OFFLINE option was specified for an archive log backup set.
Action: Use this option only for datafile backup sets.
Cause: The SKIP READONLY option was specified for an archive log backup set.
Action: Use this option only for datafile backup sets.
Cause: The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynchronized with the target database.
Action: Re-catalog the file and retry the operation.
Cause: The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynchronized with the target database.
Action: Re-catalog the file and retry the operation.
Cause: An error occurred while looking up the specified control file copy in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the file name is entered correctly. If the control file copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.
Cause: A command was entered that requires a maintenance channel, and no maintenance channel is allocated, or none of the appropriate type.
Action: Use ALLOCATE CHANNEL FOR MAINTENANCE before deleting backup pieces, or using the CROSSCHECK or DELETE EXPIRED commands. Proxy copies require a non-DISK channel.
Cause: An error occurred while looking up the specified backup piece in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the name or key is entered correctly. If the backup piece was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.
Cause: The specified datafile number was dropped and then reused. The control file mounted by the target database contains the newer version of the datafile, but the recovery catalog contains information about only the older version.
Action: Issue a RESYNC command to update the recovery catalog, then reissue the failing command. If the error persists, contact Oracle Support Services.
Cause: A RECOVER command was issued, and the recovery catalog indicates the specified datafile should be part of the recovery, but this datafile is not listed in the control file, and cannot be found on disk.
Action: Issue a RESTORE command for this datafile, using the same UNTIL clause specified to the RECOVER command (if any), then reissue the RECOVER.
Cause: The control file currently mounted by the target database contains a newer incarnation of the datafile than the recovery catalog indicates is appropriate for the point-in-time being recovered to.
Action: Restore the control file, using the same UNTIL clause specified on the failing RECOVER command, then reissue the command. If no control file can be restored, then you should issue a CREATE CONTROLFILE command.
Cause: A SET NEWNAME was issued for this datafile, but no SWITCH command was issued before the RECOVER command.
Action: Issue a SWITCH command to make the new name take effect before doing RECOVER.
Cause: This is an informational message to accompany message 6003 or 6004.
Action: No action required.
Cause: A BACKUP command was issued, but the target database control file is not mounted.
Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.
Cause: See accompanying error.
Action: 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.
Action: No action required. This is an informational message. See message 6026 for further details.
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.
Action: No action required. This is an informational message. See message 6026 for further details.
Cause: An archive log restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore.
Action: No action required. This is an informational message. See message 6026 for further details.
Cause: The indicated qualifier appears more than once in a REPORT qualifier list.
Action: Delete the duplicate qualifier.
Cause: This message is issued in response to a SET AUXNAME FOR datafile TO NULL command. This is an informational message.
Action: No action required.
Cause: The indicated qualifier appears more than once in a LIST qualifier list.
Action: Delete the duplicate qualifier.
Cause: A command was issued that requires the target database to be mounted, but the target database is not mounted.
Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.
Cause: The REPORT NEED BACKUP DAYS command may report some files as requiring backups when they really do not, because the most current online status of the file is not known unless a current control file is mounted.
Action: No action required, however, a current control file should be mounted, if possible, to get the most accurate REPORT output.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: The CHANGE DATAFILECOPY AVAILABLE command was used, but the datafilecopy cannot be found on disk.
Action: If the storage containing the datafilecopy has been removed from the host, restore it and retry the command. If the datafilecopy is permanently gone, then issue the CHANGE DATAFILECOPY DELETE command for this datafile.
Cause: The CHANGE ARCHIVELOG AVAILABLE command was used, but the archive log cannot be found on disk.
Action: If the storage containing the archive log has been removed from the host, restore it and retry the command. If the archive log is permanently gone, then issue the CHANGE ARCHIVELOG DELETE command for this archive log.
Cause: The CHANGE CONTROLFILECOPY AVAILABLE command was used, but the control file copy cannot be found on disk.
Action: If the storage containing the control file copy has been removed from the host, restore it and retry the command. If the control file copy is permanently gone, then issue the CHANGE CONTROLFILECOPY DELETE command for this datafile.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: The CHANGE BACKUPPIECE/BACKUPSET .. UNCATALOG command was entered. The UNCATALOG operation is not supported with backup pieces.
Action: Use CHANGE BACKUPPIECE/BACKUPSET .. DELETE instead.
Cause: A command was used which requires a connection to a recovery catalog database. The command cannot be used when your backup repository is the target database control file.
Action: If a recovery catalog database is available, then connect to the recovery catalog and retry the command, otherwise enter a different command.
Cause: An error occurred while looking up the specified datafile copy key in the recovery catalog.
Action: This error is accompanied by other errors describing the reason for the failure.
Cause: An error occurred while looking up the specified archive log key in the recovery catalog.
Action: This error is accompanied by other errors describing the reason for the failure.
Cause: The indicated file will not be included in the backup set because it is offline and the SKIP OFFLINE option was specified.
Action: No action required. This is an informational message only.
Cause: The indicated file will not be included in the backup set because it is read only and the SKIP READONLY option was specified.
Action: No action required. This is an informational message only.
Cause: The indicated file will not be included in the backup set because it could not be read, and the SKIP INACCESSIBLE option was specified.
Action: No action required. This is an informational message only.
Cause: The specified channel ID is invalid. DELETE and DEFAULT are reserved channel names and may not be specified by users.
Action: Specify a different channel ID.
Cause: The snapshot control file name was not set, so RMAN set it to the default value.
Action: No action required. This is an informational message only.
Cause: The SKIP OFFLINE and SKIP READONLY options are only permitted when the target database control file is current. When the target control file is not current, it is not possible to obtain a datafile's offline/read-only status.
Action: Remove the skip option or mount a current control file on the target database.
Cause: A backup command was issued that includes the specified datafile, but the datafile is not listed in the control file. The control file is not current (it is a backup or a created control file).
Action: Recover the control file to make it current, then retry the backup command.
Cause: A RESTORE UNTIL was issued, and the recovery catalog choose an older incarnation of the datafile than is listed in the control file.
Action: If the recovery catalog has correct data for the datafile, then restore a backup control file using the same UNTIL clause, then retry the datafile restore. Otherwise, restore a backup of the incarnation of the datafile listed in the control file.
Cause: An operating system command has completed.
Action: No action required. This is an informational message.
Cause: A host command returned a non-zero return code.
Action: Correct the offending command.
Cause: This message should be accompanied by other error messages indicating the cause of the error.
Action: Check the accompanying errors.
Cause: A REPORT SCHEMA at_clause command was issued, but there is no recovery catalog database.
Action: If you are not using a recovery catalog, then you may only issue the REPORT SCHEMA command with no at_clause.
Cause: A REPORT SCHEMA with no at_clause was issued, and there is no recovery catalog, and there is also no control file mounted at the target database, so there is no place to get the information about the current list of files comprising the database.
Action: Use a recovery catalog or mount a control file at the target database.
Cause: A REPORT SCHEMA with no at_clause was issued, and there is no recovery catalog, and the control file mounted by the target instance is not current, so the information about the current list of datafiles may not be current.
Action: Use a recovery catalog or mount a current control file.
Cause: The TAG option was specified with LIST INCARNATION. This is not permitted because there is no TAG associated with a database incarnation.
Action: Remove the TAG option and re-run the LIST command.
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.
Action: Remove the ARCHIVELOG LIKE option and re-run the command.
Cause: The DEVICE TYPE option was specified with a LIST COPY, LIST INCARNATION, CROSSCHECK, or DELETE EXPIRED command. This is not permitted because only backup sets may reside on different types of devices and CROSSCHECK and DELETE EXPIRED commands must use the same device type as was specified in the ALLOCATE CHANNEL FOR MAINTENANCE/DELETE command.
Action: Remove the DEVICE TYPE option and re-run the command.
Cause: The LIKE option was specified with a RMAN command. This is not permitted because only copies of datafiles, control files, or archive logs have file names that may be tested with a LIKE operand.
Action: Remove the LIKE option and re-run the RMAN command.
Cause: The FROM or UNTIL option was specified with LIST INCARNATION. This is not permitted because there is no time associated with a database incarnation.
Action: Remove the FROM or UNTIL option and re-run the LIST command.
Cause: A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. If the mounted control file is not current, it may not be possible to determine if a satisfactory backup exists for files which have been offline since the last OPEN RESETLOGS. This is an informational message.
Action: No action required. To ensure a complete report of obsolete backups, mount a current control file.
Cause: A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. A backup was found for a file which is shown as offline in the target database control file, but the backup contains changes beyond the SCN when the file went offline. This is most likely because the target database control file is not really current, but is a restored copy of an older control file.
Action: Mount a current control file or a backup control file.
Cause: A CHANGE or REPORT command could find no files that meet the specified criteria for obsoleteness. This is an informational message.
Action: No action required.
Cause: The REDUNDANCY operand specified for a CHANGE or REPORT OBSOLETE command was zero.
Action: Specify a REDUNDANCY operand value greater than or equal to 1.
Cause: This message is issued in response to a SET AUXNAME command. This is an informational message.
Action: No action required.
Cause: This is an informational message. It should be accompanied by other messages.
Action: No action required.
Cause: The CHANGE VALIDATE command may not be performed on a backup piece.
Action: The CHANGE VALIDATE command may only be performed on datafile copies and archived logs. To verify the contents of a backup set, use the VALIDATE BACKUPSET command, which must be use inside of an RMAN RUN command.
Cause: The CHANGE DATAFILE COPY VALIDATE command found that the datafile copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog. This is an informational message.
Action: No action required.
Cause: The CHANGE DATAFILE COPY VALIDATE command found that the datafile copy still matches its data in the recovery catalog. This is an informational message.
Action: No action required.
Cause: The CHANGE CONTROLFILECOPY VALIDATE command found that the control file copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog. This is an informational message.
Action: No action required.
Cause: The CHANGE CONTROLFILECOPY VALIDATE command found that the control file copy still matches its data in the recovery catalog. This is an informational message.
Action: No action required.
Cause: The CHANGE ARCHIVELOG VALIDATE command found that the archived log could not be found or no longer contains the same data, so its record was deleted from the recovery catalog. This is an informational message.
Action: No action required.
Cause: The CHANGE ARCHIVED LOG VALIDATE command found that the archived log still matches its data in the recovery catalog. This is an informational message.
Action: No action required.
Cause: An error occurred while looking up the specified backup set in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the key is entered correctly. If the backup set was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.
Cause: No backup pieces for the requested backup set were found in the recovery catalog, or the target database control file.
Action: Specify an existing backup set.
Cause: This error is accompanied by other errors explaining the cause.
Action: Correct the auxiliary file name if it is wrong via the SET AUXNAME command.
Cause: This is the SQL statement about to be executed for a SQL command. This is an informational message.
Action: No action required.
Cause: This message should be followed by one or more 6162 or 6164 messages.
Action: Refer to the accompanying 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.
Action: Use the LIST command to determine which device type is needed, then allocate a channel of that type.
Cause: The archived logs and/or incremental backup sets required to recover the datafile do not exist, but a more recent backup of the datafile exists which can be recovered.
Action: Issue a RESTORE for the datafile, then reissue the RECOVER command.
Cause: Incremental backups or archived redo logs needed to recover the datafile cannot be found, and no recoverable full backup or datafile copy exists.
Action: Use the LIST command to see if there is a backup set or datafile copy that can be made AVAILABLE. If not, then the datafile is unrecoverable. If a full or datafile copy exists, then a point-in-time recovery may be possible.
Cause: A CONNECT command was issued, but RMAN is already connected to the specified database.
Action: RMAN has no DISCONNECT command, so to connect to a different instance, exit RMAN and start it again.
Cause: A tag was used to specify a list of backup pieces, but no backup pieces with this tag could be found.
Action: Make sure the tag is specified correctly.
Cause: The specified datafile could not be accessed. The reason codes are:
Action: If the error can be corrected, do so and retry the operation. The SKIP option can be used to ignore this error during a backup.
Cause: This offline range is needed for recovering the specified datafile, but the offline range record has aged out of the current control file and no control file copy with the record could be accessed. At least one control file copy containing the offline range was found in the recovery catalog and was in AVAILABLE status.
Action: Query the RC_CONTROLFILE_COPY view for the names of all control file copies, then issue a CHANGE CONTROLFILECOPY... VALIDATE; command for them. Then reissue the RECOVER command.
Cause: A command was issued but no connection to the target database has been established.
Action: Issue a CONNECT TARGET command to connect to the target database.
Cause: A restore could not proceed because no autobackup was found or the 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 controlfile copy. It may be that it does not exist.
Action: Modify autobackup search criteria or verify the handle.
Cause: Auxiliary type was specified for the control file, but no SET NEWNAME command has been previously issued for a datafile.
Action: Issue SET NEWNAME command for every datafile in the recovery set.
Cause: A auxiliary command was issued but no connection to an auxiliary database has been established.
Action: Issue a CONNECT AUXILIARY command to connect to the auxiliary database.
Cause: A DELETE SCRIPT command was executed.
Action: No action required.
Cause: A RECOVER DATABASE command does not need to recover any files because all of the files to be recovered are offline or read only. This can only occur when the SKIP clause includes the system tablespace. This is an informational message.
Action: No action required.
Cause: A RESTORE command does not need to restore any files, because all of the files to be restored are offline, read only, or are already restored to their correct destinations. This is an informational message.
Action: No action required.
Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is offline clean at the desired point in time. This is an informational message.
Action: No action required.
Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is part of a read-only tablespace at the desired point in time. This is an informational message.
Action: No action required.
Cause: A BACKUP command with INCREMENTAL LEVEL > 0 was specified.
Action: Use FULL or INCREMENTAL LEVEL=0.
Cause: Attempt to allocate more than one channel in a job.
Action: Remove all except one ALLOCATE CHANNEL command.
Cause: A BACKUP ARCHIVELOG command specified the SETSIZE operand too low. The specified archive log is larger than SETSIZE will allow.
Action: Increase the SETSIZE limit.
Cause: A BACKUP DATAFILE(copy) command specified the SETSIZE operand too low. The specified datafile is larger than SETSIZE will allow.
Action: Increase the SETSIZE limit.
Cause: A backup command specifies the same datafile or copy of a datafile multiple times.
Action: Eliminate the duplicates.
Cause: This version of Recovery Manager is incompatible with the indicated database or the DBMS_BACKUP_RESTORE package installed in the indicated database.
Action: If the database has been upgraded from an earlier version, ensure that the CATXXXX.SQL script has been run successfully. Re-install DBMSBKRS.SQL and PRVTBKRS.PLB if necessary. Otherwise, use a version of RMAN within the range specified in the error message.
Cause: The specified PL/SQL package is a version that is too old to work with this version of the Recovery Manager (RMAN).
Action: If the database indicated is RCVCAT, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN.
Cause: The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynchronized with the target database.
Action: Re-catalog the file and retry the operation.
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.
Action: Dismount the database or restart RMAN and use the command before connecting to the target database.
Cause: SET DBID was used to set a DBID that does not match the DBID of the database to which RMAN is connected.
Action: If the current operation is a restore to copy the database, do not mount the database. Otherwise, avoid using the SET DBID command, or restart RMAN.
Cause: RMAN detected an old version of the specified package. RMAN will execute in backwards-compatible mode.
Action: No action is required, but certain features and bug fixes may not be available when RMAN runs in backwards-compatible mode. If the database is RCVCAT, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN. The files that must be run to upgrade the target or auxiliary database are DBMSRMAN.SQL and PRVTRMAN.PLB.
Cause: RMAN detected an incompatible version of the specified package.
Action: Use a newer version of Recovery Manager. Message 6439 indicates the minimum required version of Recovery Manager.
Cause: Input size for maxpiecesize or maxsetsize was out of range.
Action: Specify a valid size and retry the command.
Cause: The database must be started before any other RMAN commands are issued. This is an informational message.
Action: No action required.
Cause: A command was issued that requires the target database instance be started.
Action: Issue a STARTUP command to start the instance.
Cause: A command was issued that requires the auxiliary database instance be started.
Action: Issue a STARTUP AUXILIARY command.
Cause: A STARTUP command completed successfully. This is an informational message.
Action: No action required.
Cause: See RMAN-06203.
Action: No action required.
Cause: See RMAN-06203.
Action: No action required.
Cause: See RMAN-06203.
Action: No action required.
Cause: This message is issued in response to a LIST COPY OF ARCHIVELOG command. If a recovery catalog is in use, then the information comes from the recovery catalog, otherwise it comes from the target database control file. The following fields are shown for each archived log:
'U' will not be used if the target database control file is being used as the recovery catalog.
Action: No action required.
Cause: See RMAN-06213.
Action: No action required.
Cause: See RMAN-06213.
Action: No action required.
Cause: See RMAN-06213.
Action: No action required.
Cause: This message is issued in response to a LIST COPY OF DATABASE/TABLESPACE/DATAFILE command. If a recovery catalog is in use, then the information comes from the recovery catalog, otherwise it comes from the target database control file. The following fields are shown for each datafile copy:
'U' will not be used if the target database control file is being used as the recovery catalog.
Action: No action required.
Cause: See RMAN-06223.
Action: No action required.
Cause: See RMAN-06223.
Action: No action required.
Cause: See RMAN-06223.
Action: No action required.
Cause: This message is issued in response to a LIST BACKUP OF ARCHIVELOG command. If a recovery catalog is in use, then the information comes from the recovery catalog, otherwise it comes from the target database control file. To be included in the report, at least one complete copy of the backup set must exist. If the DEVICE TYPE option is specified on the report command, then the list includes only those backup sets which reside on the specified devices, otherwise all available backup sets are listed. The following fields are shown for each archive log which is included in a backup set:
Action: No action required.
Cause: See RMAN-06233.
Action: No action required.
Cause: See RMAN-06233.
Action: No action required.
Cause: See RMAN-06233.
Action: No action required.
Cause: This message is issued in response to a LIST BACKUP OF DATABASE/TABLESPACE/DATAFILE command. If a recovery catalog is in use, then the information comes from the recovery catalog, otherwise it comes from the target database control file. To be included in the report, at least one complete copy of the backup set must exist. If the DEVICE TYPE option is specified on the report command, then the list includes only those backup sets which reside on the specified devices, otherwise all available backup sets are listed. The following fields are shown for each datafile which is included in a backup set:
Action: No action required.
Cause: See RMAN-06249.
Action: No action required.
Cause: See RMAN-06249.
Action: No action required.
Cause: See RMAN-06249.
Action: No action required.
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:
Action: No action required.
Cause: See RMAN-06253.
Action: See RMAN-06253.
Cause: See RMAN-06253.
Action: See RMAN-06253.
Cause: See RMAN-06253.
Action: See RMAN-06253.
Cause: An unlogged change (such as 'create table unrecoverable') has been made to this file, and the most recent backup of the file does not contain those changes.
Action: Take a backup of this file. If this file is lost before a backup is taken, then the unlogged modifications will be lost. The message indicates whether a full backup is required or whether a incremental backup will suffice.
Cause: See RMAN-06263.
Action: See RMAN-06263.
Cause: See RMAN-06263.
Action: See RMAN-06263.
Cause: See RMAN-06263.
Action: See RMAN-06263.
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 incremental backups during recovery.
Action: To reduce the number of incremental backups which would be used during recovery of this datafile, take a new full backup of this file now.
Cause: See RMAN-06273.
Action: See RMAN-06273.
Cause: See RMAN-06273.
Action: See RMAN-06273.
Cause: See RMAN-06273.
Action: See RMAN-06273.
Cause: This message is issued in response to the REPORT NEED BACKUP DAYS command for those files which need more than the specified number of days' archived logs for recovery.
Action: To reduce the number of log files needed for recovery of this datafile, take a new full or incremental backup now.
Cause: See RMAN-06285.
Action: See RMAN-06285.
Cause: See RMAN-06285.
Action: See RMAN-06285.
Cause: See RMAN-06285.
Action: See RMAN-06285.
Cause: See RMAN-06285.
Action: See RMAN-06285.
Cause: See RMAN-06285.
Action: See RMAN-06285.
Cause: This message is issued in response to the REPORT OBSOLETE command. Each of the files listed is obsolete because it is more redundant than the level of redundancy specified in the REPORT command.
Action: No action required.
Cause: See RMAN-06293.
Action: See RMAN-06293.
Cause: See RMAN-06293.
Action: See RMAN-06293.
Cause: See RMAN-06293.
Action: See RMAN-06293.
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:
Action: No action required.
Cause: See RMAN-06303.
Action: See RMAN-06303.
Cause: See RMAN-06303.
Action: See RMAN-06303.
Cause: See RMAN-06303.
Action: See RMAN-06303.
Cause: This message is issued when the REPORT NEED BACKUP REDUNDANCY command is used for those files which have less than the specified number of backups which can be used for recovery.
Action: Take another backup of the datafiles listed.
Cause: See RMAN-06313.
Action: See RMAN-06313.
Cause: See RMAN-06313.
Action: See RMAN-06313.
Cause: See RMAN-06313.
Action: See RMAN-06313.
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.
Status 'U' will not be used if the target database control file is being used as the recovery catalog.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: A STARTUP command without the FORCE option was issued, but the target database is already started.
Action: Use the FORCE option if you want to restart the database.
Cause: This is an informational message.
Action: No action required.
Cause: The most likely cause of this error is that one of the databases to which RMAN had previously connected is not started or has been shut down. Other error messages should identify exactly which database is the problem.
Action: Start the database that is causing the problem.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message issued by the UPGRADE CATALOG command. It indicates the version of the recovery catalog schema to which the recovery catalog was just upgraded. Note that this version number may not reflect the version number of your RMAN executable or target database, because the recovery catalog schema is not changed with each Oracle release.
Action: No action required.
Cause: LIST BACKUP OF ARCHIVELOG LIKE was used, which is not supported.
Action: Remove LIKE clause from command.
Cause: An attempt was made to issue a command that can be used only when there are no allocated channels.
Action: Do not use the command, or de-allocate channels and use the command when no channels are allocated.
Cause: An attempt was made to set duplexing to an invalid value.
Action: Use a value in the specified range.
Cause: A proxy copy was started, but no allocated channel supports proxy copy. This could be because the media management software used by the target database does not support proxy copy, or because all of the allocated channels are of type DISK, which never support proxy copy.
Action: If this is a backup, then either allocate a non-disk channel, or do not use the PROXY option. If this is a restore, then a channel of the same type which created the proxy backup was allocated, but now does not support proxy copy. If proxy copy is no longer supported by the media management software at the target database, the CROSSCHECK or CHANGE commands should be used so that those backups will not be considered for further restores.
Cause: The channel which was specified for this backup or restore does not support proxy copy. This could be because the media management software used by the target database does not support proxy copy, or because the channel is of type DISK, which never supports proxy copy.
Action: If this is a backup, then either allocate a non-disk channel, or do not use the PROXY option. If this is a restore, then a channel of the same type which created the proxy backup was allocated, but now does not support proxy copy. If proxy copy is no longer supported by the media management software at the target database, the CROSSCHECK command should be used so that those backups will not be considered for further restores.
Cause: PROXY was specified, and the target database uses a media manager that supports proxy copy, but the COMPATIBLE initialization parameter of the target database must be 8.1.0 or greater to create proxy backups. If the database is downgraded to the earlier release that is specified in the COMPATIBLE parameter, then it will no longer be able to restore proxy backups.
Action: Either take a non-proxy backup or change the target database COMPATIBLE parameter.
Cause: The PROXY option was specified, but the media management software used by the target database cannot back up the specified file using proxy copy. If PROXY ONLY was specified, then the backup is terminated. If PROXY was specified, then this file will be placed into a non-proxy backup set.
Action: Remove the ONLY option to place the files into a regular backup set, or contact the media management vendor if you believe that the media management software should support proxy copy of this file.
Cause: PROXY ONLY was specified, and some of the files to be backed up could not be backed up by the media management software used by the target database. Message 6415 is issued for each file that cannot be proxy copied.
Action: Remove the ONLY option to place the files into a regular backup set, or contact the media management vendor if you believe that the media management software should support proxy copy of these files.
Cause: The BACKUP PROXY ARCHIVELOG command was entered. Proxy backup of archive logs is not yet supported.
Action: Enter a different command.
Cause: PROXY was specified for a non-level-zero incremental backup. Proxy backups may only be full or level 0 backups.
Action: Remove one of the conflicting options.
Cause: The media management software used by the target database indicated that it cannot restore the specified file from the specified backup handle.
Action: Consult the media management software documentation to find out why this restriction exists or contact the media management vendor.
Cause: Some of the files to be restored could not be restored by the media management software used by the target database. Message 6419 is issued for each file that cannot be restored.
Action: Contact the media management vendor if you believe that the media management software should support proxy copy of these files. The CROSSCHECK or CHANGE commands can be used to remove these proxy copies from the catalog to prevent the RESTORE command from trying to restore from these proxy backups.
Cause: This is an informational message.
Action: No action required.
Cause: No channels with the specified names or device types were found. If no channel qualifiers were specified, then no channels were allocated.
Action: Specify a different channel type or allocate a channel of the desired type.
Cause: A SETLIMIT CHANNEL command was used to set the backup piece size limit, but the media management software used by the target database cannot create backup pieces that large.
Action: Specify a smaller backup piece limit.
Cause: An error occurred while looking up the specified proxy copy in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the name or key is entered correctly. If the proxy copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.
Cause: This is an informational message.
Action: No action required.
Cause: The CREATE CATALOG or UPGRADE CATALOG command was used, but the userid that was supplied in the RCVCAT connect string does not have the RECOVERY_CATALOG_OWNER role granted as a DEFAULT role.
Action: Grant the RECOVERY_CATALOG_OWNER role to the recovery catalog owner.
Cause: The CREATE CATALOG command cannot be used when the recovery catalog already exists.
Action: Use the UPGRADE CATALOG command to upgrade your recovery catalog to the most current release without losing any existing backup data. Use the DROP CATALOG command to remove an existing recovery catalog.
Cause: A recovery catalog database connection has been made, but the recovery catalog tables and views have not been installed.
Action: If you incorrectly typed the recovery catalog owner USERID, then correct the userid and reconnect to the recovery catalog. If this is the first time that you have signed on to Recovery Manager with this recovery catalog owner userid, then use the CREATE CATALOG command to create the recovery catalog schema.
Cause: The indicated database is not compatible with this version of the Recovery Manager (RMAN). Other messages have also been issued which detail the cause of the error.
Action: See the other messages. If the database is RCVCAT, then you may be able to use the CREATE CATALOG or UPGRADE CATALOG commands to correct the problem. If the database is TARGET or AUXILIARY, then you must either upgrade the target database or use a newer version of the RMAN executable.
Cause: A recovery catalog connection was made to userid SYS. The recovery catalog must be created in a userid other than SYS.
Action: Specify a different userid in the RCVCAT connect string.
Cause: This is an informational message issued by the CREATE CATALOG command.
Action: No action required.
Cause: This is an informational message issued by the DROP CATALOG command.
Action: No action required.
Cause: An error was received from the recovery catalog database while it was being installed. Another error message shows the error message from the server.
Action: The most common reasons for failure to install the recovery catalog are:
Cause: Some errors were received from the recovery catalog database while removing the recovery catalog.
Action: Correct the error(s) and retry the command. Note that the Recovery Manager intercepts and ignores common errors, such as 'object not found', which can happen while removing a partially installed recovery catalog. Only serious errors will be displayed while removing the recovery catalog.
Cause: This is an informational message issued by the UPGRADE CATALOG and DROP CATALOG commands.
Action: No action required.
Cause: The DROP CATALOG command deletes the recovery catalog, rendering all database backups unusable, and should be used with care. The command must be entered twice to ensure that this is really what you want to do.
Action: If you really want to remove the recovery catalog, then enter the DROP CATALOG command again.
Cause: The DROP CATALOG command was entered, but the recovery catalog was created by a newer version of the Recovery Manager (RMAN). This version of RMAN may not be able to drop the entire recovery catalog.
Action: Use the version of RMAN which most recently created or upgraded the recovery catalog.
Cause: Recovery Manager requires the DBMS_RCVMAN package in the SYS schema of the indicated database. Normally this package is installed during database creation.
Action: To re-create the package, run the files DBMSRMAN.SQL and PRVTRMNS.PLB.
Cause: This message indicates the minimum version of Recovery Manager required to use the package which was specified in message 6191.
Action: A newer version of RMAN must be used with this package.
Cause: The recovery catalog is already at a version level that is greater than this version of the Recovery Manager. The UPGRADE CATALOG command is not needed.
Action: Either upgrade to a more recent Recovery Manager, or continue to use the current version. Message 6191 will be issued if the recovery catalog is too new to work with this version of Recovery Manager.
Cause: The UPGRADE CATALOG command alters the recovery catalog schema. Although the recovery catalog is designed to be compatible with older versions of the Recovery Manager (RMAN), it is possible that an upgrade will remove support for older versions of RMAN.
Action: If you really want to upgrade the recovery catalog, then enter the UPGRADE CATALOG command again. If you are not going to use an older version of RMAN with this recovery catalog, then compatibility is not an issue. If you plan to also continue using an older version of RMAN with this recovery catalog then, before upgrading, consult Oracle9i Database Migration or the migration guide for the current Oracle release to determine if upgrading to the current version of the recovery catalog will remove support for older versions of RMAN.
Cause: An error was received from the recovery catalog database while upgrading the recovery catalog.
Action: Correct the error and retry the command. Note that the Recovery Manager intercepts and ignores common errors, such as 'column already exists,' which can happen if the recovery catalog has already been partially upgraded. Only serious errors will be displayed while upgrading the recovery catalog.
Cause: During the CREATE CATALOG or UPGRADE CATALOG command, the indicated PL/SQL package specification or body could not be created because of PL/SQL compilation errors.
Action: The PL/SQL packages used by the recovery catalog are located in the RECOVER.BSQ library file, and should never be modified. Make sure that the RECOVER.BSQ file has not been modified or damaged, and then if this error persists, contact Oracle Support Services. Connect to the recovery catalog owner and query the USER_ERRORS view to find out the details of the compilation errors.
Cause: The CONNECT CATALOG command was used after the user had already specified the NOCATALOG option.
Action: Re-start RMAN if you wish to use a recovery catalog.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message issued by the UPGRADE CATALOG command. It indicates the version to which the indicated package was just upgraded. Note that this version number may not reflect the version number of your RMAN executable or target database, because the recovery catalog packages are not changed with each Oracle release.
Action: No action required.
Cause: An attempt was made to use LIST ... RECOVERABLE ... with OF CONTROLFILE or OF ARCHIVELOG.
Action: Remove the RECOVERABLE keyword and try again.
Cause: The SET DUPLEX command was specified.
Action: Remove the SET DUPLEX command.
Cause: A point-in-time tablespace recovery was attempted, but Enterprise Edition is not installed.
Action: Do not do point-in-time tablespace recovery.
Cause: This is an informational message only.
Action: No action required.
Cause: UNTIL scn cannot be more than the last scn of the last archived log.
Action: Check the UNTIL scn.
Cause: BACKUP VALIDATE and PROXY were specified in the same backup command.
Action: Remove the incompatible option.
Cause: A backupset record specifier did not match a backupset on device DISK in the recovery catalog.
Action: Resubmit the command with a different backupset record specifier. The rman LIST command can be used to display all backupsets that Recovery Manager knows about.
Cause: BACKUP BACKUPSET and PROXY were specified in the same backup command.
Action: Resolve the conflict.
Cause: BACKUP BACKUPSET and VALIDATE were specified in the same backup command.
Action: To VALIDATE BACKUPSET use 'validate' or 'restore validate' command.
Cause: The configuration is not implemented in the current release.
Action: Avoid using the command.
Cause: Unsupported configuration string is stored in recovery catalog or target database controlfile.
Action: Check compatibility matrix rman executable and target database and recover catalog. Use dbms_backup_restore.deleteConfig to remove problematic configuration.
Cause: An error was received when calling dbms_rcvman.
Action: This message should be accompanied by other error messages indicating the cause of the error.
Cause: The DBA specified doesn't belong to the mentioned tablespace.
Action: Check the DBA.
Cause: An error was received when calling dbms_rcvman.
Action: This message should be accompanied by other error messages indicating the cause of the error.
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.
Action: Remove the DEVICE TYPE option and re-run the command, or Remove all ALLOCATE commands and re-run the script so that channels are automatically allocated.
Cause: Device type configuration was not found in recovery catalog.
Action: Set up device type configuration using configure command for required device type.
Cause: Channel ID was used on ALLOCATE/RELEASE command.
Action: Use other channel id that does not belong to reserved channel ID's namespace.
Cause: RELEASE CHANNEL was used without allocating any maintenance channels.
Action: Allocate maintenance channel before executing this command.
Cause: Parallelism for the device type in CONFIGURE PARALLELISM command is out of range.
Action: Enter value of parallelism that is within the allowed range.
Cause: Channel number entered in CONFIGURE CHANNEL command is out of range.
Action: Enter channel number within allowed range for this device and retry the command.
Cause: CONFIGURE CHANNEL command entered has configuration value greater than 1024 bytes.
Action: Reduce the length of CONFIGURE CHANNEL command options.
Cause: The CHANGE DATAFILECOPY AVAILABLE command was used, but the datafilecopy cannot be found on disk.
Action: If the storage containing the datafilecopy has been removed from the host, then restore it and retry the command. If the datafilecopy is permanently gone, then issue the CHANGE DATAFILECOPY DELETE command for this datafile.
Cause: The CHANGE CONTROLFILECOPY AVAILABLE command was used, but the control file copy cannot be found on disk.
Action: If the storage containing the control file copy has been removed from the host, then restore it and retry the command. If the control file copy is permanently gone, then issue the CHANGE CONTROLFILECOPY DELETE command for this control file.
Cause: The CHANGE ARCHIVELOG AVAILABLE command was used, but the archivelog cannot be found on disk.
Action: If the storage containing the archivelog has been removed from the host, then restore it and retry the command. If the archivelog is permanently gone, then issue the CHANGE ARCHIVELOG DELETE command for this archivelog.
Cause: The CHANGE BACUKPPIECE AVAILABLE command was used, but the backup piece cannot be found on the storage medium.
Action: If the storage containing the backup piece has been removed from the host, then restore it and retry the command. If the backup piece is permanently gone, then issue the CHANGE BACKUPPIECE DELETE command for this backup piece.
Cause: The CHANGE PROXY AVAILABLE command was used, but the proxy copy cannot be found on disk.
Action: If the storage containing the proxy copy has been removed from the host, then restore it and retry the command. If the proxy copy is permanently gone, then issue the CHANGE PROXY DELETE command for this proxy copy.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: A controlfile or SPFILE restore from autobackup was attempted and other restore options were used.
Action: Do not specify any other options for the controlfile autobackup restore.
Cause: Target channel configuration could not be used for clone channel as it contains CONNECT option.
Action: Setup clone channel configuration using CONFIGURE CLONE command for required channel number and device type.
Cause: No more controlfile autobackups are possible during this day.
Action: This is a warning message. No action is required.
Cause: A controlfile autobackup format cannot have more than one reserved format specifier.
Action: Specify only one reserved format specifier or use an alternative format.
Cause: A reserved format specifier was not specified for the controlfile autobackup format.
Action: Add a specifier to 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.
Action: Specify SET UNTIL TIME to indicate the day to start the restore of a controlfile autobackup.
Cause: The specified parameter for restoring a controlfile autobackup is out of the valid range.
Action: Change the parameter value to a valid number or do not specify it.
Cause: Restore of a controlfile autobackup was attempted when the database is not mounted.
Action: Specify the DBID of the database using SET DBID or mount the database.
Cause: A controlfile restore was attempted when the database is mounted or open and no alternate destination was specified.
Action: Specify an alternate destination with the TO clause or dismount the database.
Cause: Controlfile autobackup is not possible without a current controlfile.
Action: This is a warning message. No action is required.
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.
Action: No action required.
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.
Action: No action required.
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.
Action: No action required.
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.
Action: No action required.
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.
Action: No action required.
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.
Action: No action required.
Cause: Multiple backup copies and PROXY option were specified in BACKUP command.
Action: Resolve the conflict.
Cause: The MAXSETSIZE option was specified for a backup backupset command.
Action: Remove the option and resubmit the command.
Cause: This is an informational message, appearing when an archivelog was found out of sync with catalog database.
Action: No Action Required.
Cause: MAXSETSIZE configured or specified in backup command should be greater than database blocksize.
Action: Specify a larger MAXSETSIZE limit.
Cause: A datafile or archived log restore from autobackup was attempted.
Action: Do not specify DATAFILE or ARCHIVELOG for restore from autobackup.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: KEEP UNTIL support only a future time.
Action: Correct the time and retry the command.
Cause: The KEEP option is not supported for archive logs.
Action: Either remove KEEP option and retry the command or don't specify archive logs for this backup.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
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 the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter.
Action: If a recovery catalog database is available, then connect to the recovery catalog and retry the command. Otherwise, use a different KEEP option.
Cause: This is an informational message.
Action: No Action Required.
Cause: Command DELETE OBSOLETE and REPORT OBSOLETE requires that either:
Action: Either configure RMAN retention policy with CONFIGURE command or specify it at the end of DELETE/REPORT command.
Cause: The KEEP option was specified for an incremental backup.
Action: Remove the option and resubmit the command.
Cause: The KEEP option is not supported for backup of backup sets.
Action: Either remove KEEP option and retry the command or don't specify backup sets for this backup.
Cause: The CHANGE BACKUPPIECE ... KEEP command was entered. KEEP attributes cannot be specified for backup pieces.
Action: Use CHANGE BACKUPSET ... KEEP instead.
Cause: The CHANGE ARCHIVELOG ... KEEP command was entered. KEEP attributes cannot be specified for archive logs.
Action: Use CHANGE BACKUPSET ... KEEP instead.
Cause: The CHANGE BACKUPSET ... KEEP command was entered, but the BACKUPSET contains archive logs. Backup sets with archive logs cannot have KEEP attributes.
Action: Do not specify backup set with archive logs for the CHANGE BACKUPSET ... KEEP command.
Cause: The CHANGE BACKUPSET ... KEEP command was entered, but the BACKUPSET is an incremental backup set. Incremental backup sets cannot have KEEP attributes.
Action: Do not specify backup set with archive logs for the CHANGE BACKUPSET ... KEEP command.
Cause: The REDUNDANCY operand specified for the retention policy was zero.
Action: Specify a REDUNDANCY operand of 1 or greater.
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.
Action: Remove the KEEP ... NOLOGS option and resubmit the command.
Cause: The KEEP ... CONSISTENT option was specified but the option is not supported.
Action: Remove the option and resubmit the command.
Cause: LIST COPY OF SPFILE was used, which is not supported because SPFILE cannot have a copy.
Action: Remove SPFILE from the command.
Cause: The BACKUP UP ... TIMES option was used as a qualifier. This option is supported only for archived logs.
Action: Remove the option and resubmit the command.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: The indicated file will not be included in the backup set because it's tablespace is configured as excluded from backup.
Action: No action required.
Cause: The indicated options conflict with each other or appear more than once in a LIST command.
Action: remove the duplicate/conflicting option from the command.
Cause: This is a user prompt.
Action: Answer the question to proceed.
Cause: An incorrect response was entered.
Action: Enter a correct response.
Cause: An error occurred reading user response.
Action: No action required. This is an informational message.
Cause: The SYSTEM tablespace must be included in whole database backup.
Action: Remove the SYSTEM tablespace from the CONFIGURE ... EXCLUDE and retry the operation.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: The clone database initialization parameter file does not specify the DB_NAME parameter.
Action: Add the DB_NAME parameter to the clone database initialization parameter file and restart the instance.
Cause: An error occurred while looking up the specified datafilecopy in the recovery catalog or target database controlfile.
Action: This error is accompanied by other errors describing the reason for the failure. If the datafilecopy was created during a RESTORE with a new name, then ensure that the RESTORE completed successfully.
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, then the file must be restored before issuing a SWITCH command.
Action: Correct and resubmit the SWITCH command.
Cause: The SET NEWNAME ... TO NEW option was specified but the OMF destination initialization parameter DB_CREATE_FILE_DEST is not set.
Action: Supply a full name to the SET NEWNAME command or set DB_CREATE_FILE_DEST at the target database.
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.
Action: Use the ALTER TABLESPACE ... END BACKUP statement, at the target database server, to take the files out of backup mode.
Cause: An incomplete recovery session was started, but the file is newer than the UNTIL TIME clause.
Action: Check the UNTIL TIME clause or restore the file from a sufficient old backup.
Cause: An incomplete recovery session was started, but the file is newer than the UNTIL clause.
Action: Check the UNTIL clause or restore the file from a sufficient old backup.
Cause: Restore of the specified archived log failed because the size of the archived log is larger than MAXSIZE specified in the RECOVERY command.
Action: Specify a larger MAXSIZE limit. See message RMAN-06558 for further details.
Cause: This is an informational message only.
Action: No action required. See message RMAN-06557 for further details.
Cause: The MAXSIZE parameter is out of range.
Action: Specify a valid size and retry the command.
Cause: Backup set size is bigger than MAXSIZE limit, so it will be read more than once. This can cause slower restore performance.
Action: Increase the MAXSIZE parameter and retry the command.
Cause: Recovery failed because it requires disk space larger than MAXSIZE specified in the RECOVERY command.
Action: Increase the MAXSIZE parameter and retry the command.
Cause: This is aninformational message.
Action: No action required.
Cause: RESTORE CONTROLFILE or RESTORE SPFILE was specified without the FROM AUTOBACKUP option when RMAN is not connected to the recovery catalog.
Action: If the recovery catalog is available, then connect to the recovery catalog and retry the restore. If the recovery catalog is not available, then the following is the procedure to restore controlfile or SPFILE:
Cause: A restore of the SPFILE from autobackup was attempted when the instance is started with SPFILE and no alternate destination was specified.
Action: Specify an alternate destination with the TO clause.
Cause: The RMAN client caught a transient error and will automatically retry several times.
Action: No action required. This is an informational message.
Cause: A datafile copy operation completed successfully.
Action: No action required. This is an informational message only.
Cause: All of the backup pieces have been successfully applied, but X$DBMS_BACKUP_RESTORE indicates that the restore conversation is not complete. This usually means that the backup set contained corrupt data.
Action: Restore the files from a different backup set, if possible. The Recovery Manager CHANGE BACKUPPIECE UNAVAILABLE can be used to prevent Recovery Manager from attempting to restore from the corrupt backup piece(s).
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: The record that identifies the source file for a copy or backup database does not contain the same data as is stored in the recovery catalog.
Action: Perform a full resync and retry the operation. If the problem persists, then contact Oracle Support Services.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: The record identifying the named file was no longer present in the target database control file, and repeated attempts to inspect the file were unsuccessful in creating the record. This could be because the circular-reuse section of the control file which holds information about the specified type of file is too small and there is other database activity which is causing the record to be overwritten before it can be used.
Action: Try increasing either the size of the control file circular-reuse section for this file type (datafile copy or archived log, as indicated in the error message, or the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter. If neither of those remedies works then contact Oracle Support Services.
Cause: This is an internal error that should never be issued.
Action: Contact Oracle Support Services.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: The specified datafile has not had its checkpoint advanced since the previous backup, therefore it does not need a new incremental backup.
Action: This message is informational only.
Cause: All datafiles for this incremental backup set were skipped, therefore no backup set is created.
Action: This message is informational only.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No Action Required.
Cause: All backupsets specified has no pieces. Therefore, no backup set is created.
Action: This message is informational only.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: Some blocks were not recovered due to errors.
Action: See trace file for details of the problem.
Cause: This is an informational message to indicate the server found a corrupted block in an archivelog and had to switch to another archivelog with same logseq in alternate archivelog destination to get corresponding un-corrupted block.
Action: If backup is done with delete input option, then nothing needs to be done. Otherwise, delete the archivelog that has corrupted blocks as recovery on applying this log would fail. alert log contains name of the log that has corrupted blocks.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: This is an informational message.
Action: No Action Required.
Cause: The requested autobackup does not contain a SPFILE. This is because the instance was not started with a SPFILE when the autobackup was created.
Action: No Action Required. RMAN will try three older autobackups before signaling ORA-19687.
Cause: The routine deleteArchivedLog() could not delete an archived redo log on the target instance.
Action: Check the accompanying file specification and the associated error messages. The file specification indicates what archived redo log on the target instance RMAN was trying to delete and the error messages indicate why RMAN was unable to delete it. Resolve the problem by first confirming that the archived redo log in question has been backed up, do the deletion manually, and then do a crosscheck so that RMAN is aware of the deletion.
Cause: A BACKUP command does not need to backup controlfile autobackup pieces, because they already exist.
Action: This is an informational message. No action required.
Cause: This is an informational message to alert the user that an archivelog that should have been deleted was not as it has not been applied to the standby database. The next message identifies the archivelog.
Action: Archivelog can be deleted after it has been applied to standby database.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: This is an informational message.
Action: No action required.
Cause: An invalid target connect string was supplied.
Action: Specify a valid connect string and re-run the job.
Cause: An invalid recovery catalog connect string was supplied.
Action: Specify a valid connect string and re-run the job.
Cause: The specified Oracle error was received. This message should be accompanied by other error messages indicating the cause of the error.
Action: Check the accompanying errors.
Cause: Recovery manager was unable to connect to the target database. This message should be accompanied by other error messages indicating the cause of the error.
Action: Ensure that the target database is started and that the connect string is valid.
Cause: Recovery manager was unable to connect to the recovery catalog. This message should be accompanied by other error messages indicating the cause of the error.
Action: Ensure that the recovery catalog is started and that the connect string is valid.
Cause: An error was received while trying to open a cursor. This message should be accompanied by other error messages indicating the cause of the error.
Action: If the associated Oracle error message indicates a condition that can be corrected, then correct the condition. Otherwise, contact Oracle Support Services.
Cause: An error message was received while running the specified SQL statement.
Action: If the associated Oracle error message indicates a condition that can be corrected, then correct the condition. Otherwise, contact Oracle Support Services.
Cause: An error was received while trying to close a cursor. This message should be accompanied by other error messages indicating the cause of the error.
Action: If the associated Oracle error message indicates a condition that can be corrected, then correct the condition. Otherwise, contact Oracle Support Services.
Cause: An error was received while trying to create a channel context. This message should be accompanied by other error messages indicating the cause of the error.
Action: If the associated Oracle error message indicates a condition that can be corrected, then correct the condition. Otherwise, contact Oracle Support Services.
Cause: An error was received while disconnecting from Oracle. This message should be accompanied by other error messages indicating the cause of the error. This is an informational message.
Action: No action required.
Cause: Recovery Manager's channel context had an error while checking to see if a remote procedure call had completed. This message should be accompanied by other error messages indicating the cause of the error.
Action: If other error messages indicate a condition that can be corrected, then correct the condition. Otherwise, contact Oracle Support Services.
Cause: Recovery Manager could not synchronize properly with a remote procedure call. This is an internal error that should not be issued.
Action: Contact Oracle Support Services.
Cause: An error occurred while initializing the KGU subsystem. This is an internal error that should not be issued.
Action: Contact Oracle Support Services.
Cause: An error occurred while initializing the PL/SQL subsystem. This is an internal error that should not be issued.
Action: Contact Oracle Support Services.
Cause: PL/SQL error.
Action: The text of this message will be issued by the PL/SQL subsystem.
Cause: An error occurred while compiling a PL/SQL program. This is an internal error that should not be issued.
Action: Contact Oracle Support Services.
Cause: An error occurred while creating a PL/SQL run time context. This is an internal error that should not be issued.
Action: Contact Oracle Support Services.
Cause: An error was received during inter-step cleanup of a channel context. This is an internal error that should not be issued.
Action: Contact Oracle Support Services.
Cause: An error was received while initializing the Recovery Manager execution layer in preparation for running a job. This message should be accompanied by other error messages indicating the cause of the error.
Action: If other error messages indicate a condition that can be corrected, then correct the condition. Otherwise, contact Oracle Support Services.
Cause: An error was received while waiting for a remote RPC to complete. The error occurred in the system-dependent sleep routine. This is an internal error that should not be issued.
Action: Contact Oracle Support Services.
Cause: The Recovery Manager internal RPC router received a package name that it could not understand. This is an internal error that should not be issued.
Action: Contact Oracle Support Services.
Cause: The Recovery Manager could not create the RPC polling context which is required to test for RPC completion. This message should be accompanied by other error messages indicating the cause of the error.
Action: If other error messages indicate a condition that can be corrected, then correct the condition. Otherwise, contact Oracle Support Services.
Cause: The Recovery Manager could not enable the target database connection to test for RPC completion. This is an internal error that should not be issued.
Action: Contact Oracle Support Services.
Cause: A network error occurred while attempting to register the target database connection to test for RPC completion. This is an internal error that should not be issued.
Action: The message numbers are issued by the SQL*Net layer. Contact Oracle Support Services.
Cause: Recovery Manager could not locate a necessary context area while attempting to register the target database connection to test for RPC completion. This is an internal error that should not be issued.
Action: Contact Oracle Support Services.
Cause: A network error occurred while waiting for a remote RPC to complete. This is an internal error that should not be issued.
Action: The message numbers are issued by the SQL*Net layer. Contact Oracle Support Services.
Cause: PL/SQL returned an unexpected return code while executing one channel program. This is an internal error that should not be issued.
Action: Contact Oracle Support Services.
Cause: An RPC to a target database instance was issued, but was not observed to start within 5 timeouts.
Action: This error is probably accompanied by other error messages giving the precise cause of the failure.
Cause: An RPC to the target database or recovery catalog database encountered an error.
Action: This error is accompanied with the error message from the server where the error occurred.
Cause: An unhandled PL/SQL exception occurred during a job step.
Action: This error is accompanied by the error messages describing the exception.
Cause: PL/SQL detected a problem during the compilation of a job step.
Action: This error message is accompanied by the error messages describing the exception.
Cause: PL/SQL detected an unhandled exception during execution of a job step, but no further information available
Action: Contact Oracle Support Services.
Cause: A call to a remote package resulted in an exception.
Action: The exception should indicate what went wrong.
Cause: This is just an informational message. It should be preceded by message 10030.
Action: No action required.
Cause: This is an debugging message and can be ignored.
Action: No action required.
Cause: The database connection for the specified channel no longer exists. Either the session was terminated by some external means or the channel terminated because of an internal error.
Action: Check for an Oracle trace file for detailed information on why the session terminated.
Cause: This error should be accompanied by other errors giving the cause of the polling error.
Action: No action required.
Cause: The database connection does not support asynchronous operation, so RMAN will not multi-task work among multiple channels. Multiple channels can still be allocated, but they will not run work concurrently.
Action: Use a connection type that supports asynchronous operations.
Cause: Recovery manager message file is out of date.
Action: Make sure that the Recovery Manager error message file is current and installed in the correct location.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: SET_DUPLEX=ON was specified, but %c was not part of the format.
Action: Include %c in format, or use %U.
Cause: This message should be accompanied by other error messages indicating the cause of the error.
Action: See accompanying messages.
Cause: An ALLOCATE CHANNEL command could not be processed.
Action: This message should be accompanied by other error messages indicating the cause of the error.
Cause: This message should be accompanied by other error messages indicating the cause of the error.
Action: See accompanying messages.
Cause: The maximum number of RMAN channels has been exceeded. Note that one channel is reserved for RMAN.
Action: Allocate fewer channels. Contact Oracle Support Services if you have a need for more channels in a single job.
Cause: There was at least 1 backup set that could not be accessed by any of the allocated channels.
Action: Allocate additional channels on other nodes of the cluster.
Cause: There was at least 1 backup set that could not be accessed by any of the allocated channels.
Action: Allocate additional channels on other nodes of the cluster.
Cause: This message should be accompanied by other error messages indicating the cause of the error.
Action: See accompanying messages.
Cause: Configuration for default device type not consistent.
Action: Re-run CONFIGURE DEFAULT DEVICE TYPE command to set device type.
Cause: Configuration for device parallelism is not consistent.
Action: Re-run CONFIGURE PARALLELISM command for device to set parallelism.
Cause: Configuration for the channel is not consistent.
Action: Re-run CONFIGURE CHANNEL command to configure this channel.
Cause: Configuration for the channel is not consistent.
Action: Re-run CONFIGURE CHANNEL command to configure the channel.
Cause: This is an informational message. Parallelism for the device is less than the associated channel number.
Action: To use this configuration, increase parallelism for this device. to clear this configuration, use CONFIGURE CHANNEL ... CLEAR command.
Cause: This is an informational message.
Action: No action required.
Cause: No copies of the specified backupset key can be accessed on any of the allocated channels.
Action: Allocate additional channels on other nodes of the cluster, or if the backup pieces have been deleted, then use the CROSSCHECK BACKUP command to correct the recovery catalog entries.
Cause: A job step encountered an error and could not recover.
Action: This error should be followed by other errors indicating the cause of the problem.
Cause: Target database is not found in the recovery catalog.
Action: Make sure that the target database is registered in the recovery catalog.
Cause: Target database is already registered in the recovery catalog.
Action: If the target database is really registered, there is no need to register it again. Note that the recovery catalog enforces that all databases have a unique DBID. If the new database was created by copying files from an existing database, it will have the same DBID as the original database and cannot be registered in the same recovery catalog.
Cause: Resetlogs change# and/or time of the target database does not match any database incarnation in the recovery catalog.
Action: If target database was opened with resetlogs option then use RESET DATABASE to register the new incarnation.
Cause: Name of the target database does not match the one stored in the recovery catalog. This is an internal error.
Action: Contact Oracle Support Services.
Cause: Two or more databases in the recovery catalog match the DB_NAME initialization parameter of the instance and the target database is not mounted, so RMAN cannot get its DBID.
Action: Mount the target database then retry the operation.
Cause: The target database instance is not started or the value of the DB_NAME initialization parameter is not set.
Action: Start the instance and make sure that the value of the DB_NAME initialization parameter is set.
Cause: This an internal error.
Action: Contact Oracle Support Services.
Cause: The database incarnation key was not specified.
Action: Specify a valid database incarnation key.
Cause: This incarnation is already registered in the recovery catalog. This is an informational message.
Action: No action required.
Cause: Database incarnation does not match any database incarnation in the recovery catalog.
Action: Specify a valid database incarnation key.
Cause: The database incarnation that matches the resetlogs change# and time of the mounted target database control file is not the current incarnation of the database.
Action: If RESET DATABASE TO INCARNATION key was used to make an old incarnation current, then restore the target database from a backup that matches the incarnation and mount it. You will need to do STARTUP NOMOUNT before you can restore the control file using RMAN. Otherwise use RESET DATABASE TO INCARNATION key to make the intended incarnation current in the recovery catalog.
Cause: This an internal error.
Action: Contact Oracle Support Services.
Cause: This an internal error.
Action: Contact Oracle Support Services.
Cause: Another operation that needs the snapshot control file is in progress.
Action: Try again later if necessary.
Cause: This procedure cannot be called while a resync is in progress. This is an internal error.
Action: Contact Oracle Support Services.
Cause: This procedure can only be called in a resync. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The checkpoint change# is less than the one of the previous resync or the checkpoint change# is null.
Action: Make sure that the right control file is used.
Cause: The control file sequence is less than the one of the previous resync.
Action: Make sure that the right control file is used.
Cause: The control file has not changed since the previous resync.
Action: No action required since the recovery catalog is in synchronization.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: SET_DUPLEX=ON was specified, but character was not part of the format.
Action: Include character in format, or use number.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The specified datafile is not found in the recovery catalog.
Action: Make sure that the datafile name is correct and that the recovery catalog is up-to-date.
Cause: The specified tablespace is not found in the recovery catalog.
Action: Make sure that the tablespace name is correct and that the recovery catalog is up-to-date.
Cause: This procedure cannot be called when name translation is in progress. This is an internal error.
Action: Contact Oracle Support Services.
Cause: getDatafile procedure was called before translateTablespace. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The sequence# was NULL. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The specified log sequence does not exists in log history of the current database incarnation.
Action: Check the THREAD and LOGSEQ. If the database needs to be recovered to a log sequence number before the current database incarnation, use RESET DATABASE TO INCARNATION command first.
Cause: UNTIL TIME cannot be less than the database creation time or RESETLOGS time.
Action: Check the UNTIL TIME. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command.
Cause: UNTIL CHANGE cannot be less than the database RESETLOGS change.
Action: Check the UNTIL CHANGE. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command.
Cause: Two datafiles have the same name. This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: FROM TIME cannot be less than the database creation time or RESETLOGS time.
Action: Check the FROM TIME. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The datafile does not exist or did not exist at until time/SCN. This is an internal error for restore database or tablespace.
Action: Check the datafile name or number. Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The specified control file is not in the recovery catalog or it has been marked deleted.
Action: Check the file name.
Cause: More than one control file copy in the recovery catalog matches the specified name.
Action: Use the control file copy key to uniquely specify the control file copy.
Cause: The specified datafile name is not the name of a datafile that is currently part of the target database, or an UNTIL clause has been specified and the file name was for a different datafile at the time specified by the UNTIL clause than it is now.
Action: Use a datafile number to specify the datafile you want to RESTORE or RECOVER.
Cause: The specified datafile is not in the recovery catalog or it has been marked deleted.
Action: Check the datafile copy name or key.
Cause: More than one control file copy in the recovery catalog match the specified name.
Action: Use the datafile copy key to uniquely specify the datafile copy.
Cause: The specified TAG does not match any datafile copy in the recovery catalog.
Action: Check the tag.
Cause: The specified archived log was not found in the recovery catalog or it has been marked deleted.
Action: Check the archived log name or key.
Cause: More than one archived log in the recovery catalog match the specified name.
Action: Use the archived log key to uniquely specify the archived log.
Cause: No archive logs in the specified archive log range could be found.
Action: Check the archive log specifier.
Cause: The specified offline was not found in the recovery catalog.
Action: Check that the recovery catalog is current.
Cause: The specified backup piece is not in the recovery catalog or it has been marked deleted.
Action: Check the backup piece handle or key.
Cause: More than one backup piece in the recovery catalog match the specified handle.
Action: Use the backup piece key to uniquely specify the backup piece.
Cause: An illegal incremental backup level was requested.
Action: Valid incremental backup levels are 1 through 4. Specify a valid level.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
Cause: No available backup or copy that could be used as the parent of the incremental backup was found in the recovery catalog.
Action: Take a level 0 backup or copy of the datafile first.
Cause: More than 8 device types were allocated.
Action: Make sure that the job allocates at most 8 different device types.
Cause: The version of the recovery catalog tables does not work with this version of the DBMS_RCVCAT package.
Action: Check that the recovery catalog packages and schema are installed correctly. The UPGRADE CATALOG command can be used to upgrade the recovery catalog tables and packages to the most current version.
Cause: The version of the recovery catalog tables does not work with this version of the DBMS_RCVMAN package.
Action: Check that the recovery catalog packages and schema are installed correctly. The UPGRADE CATALOG command can be used to upgrade the recovery catalog tables and packages to the most current version.
Cause: An operation that requires a recovery catalog was requested, but no recovery catalog is in use.
Action: If a recovery catalog is available, restart RMAN and specify the a connect string for the recovery catalog database via the RCVCAT parameter.
Cause: The specified proxy copy is not in the recovery catalog or it has been marked deleted.
Action: Check the proxy copy handle or key.
Cause: More than one proxy copy in the recovery catalog matches the specified handle.
Action: Use the proxy copy key to uniquely specify the proxy copy.
Cause: A CREATE SCRIPT or DELETE SCRIPT specified a script name that could not be found.
Action: Check the script name.
Cause: A CREATE SCRIPT was issued, but a script with the specified name already exists.
Action: Use a different name or use REPLACE SCRIPT.
Cause: A RESTORE or RECOVER of a datafile was requested, but recovery of the datafile would require applying redo logs that were generated before the most recent OPEN RESETLOGS.
Action: If a full backup or datafilecopy from the current database incarnation exists, then ensure that it is marked AVAILABLE and that a channel of the correct device type is allocated. It may also be necessary to remove the FROM BACKUPSET, FROM DATAFILECOPY, or FROM TAG operands if these have been specified.
Cause: A DELETE EXPIRED command was run, but the object was actually found to exist. This means the recovery catalog or controlfile is out of sync.
Action: Run CROSSCHECK.
Cause: A DELETE command was run without the EXPIRED option, but the object doesn't exist. This means the recovery catalog or controlfile is out of sync.
Action: Run CROSSCHECK.
Cause: The corruption list is empty.
Action: Make sure that one or more blocks are marked corrupt in V$COPY_CORRUPTION and V$BACKUP_CORRUPTION, and that the recovery catalog is up-to-date.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
