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
