Skip Headers

Oracle® Database Error Messages
10g Release 1 (10.1)
Part Number B10744-02
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Master Index
Master Index		 Go to Feedback page
Feedback
Go to previous page
Previous		 Go to next page
Next
 

33 RMAN-00550 to RMAN-20506

RMAN-00550: parser package failed to load
Cause: lpmloadpkg() return an error indication.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
RMAN-00551: initialization of parser package failed
Cause: The parser package initialization routine returned an error.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
RMAN-00552: syntax error in command line arguments
Cause: The arguments supplied to RMAN could not be parsed, or no arguments were supplied at all.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
RMAN-00553: internal recovery manager package failed to load
Cause: lpmloadpkg() return an error indication.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
RMAN-00554: initialization of internal recovery manager package failed
Cause: The internal package initialization routine returned an error.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
RMAN-00555: target database connect string must be specified
Cause: The TARGET parameter was not specified.
Action: Supply the necessary parameter.
RMAN-00556: could not open CMDFILE "string"
Cause: An error occurred when trying to open the file.
Action: Check that the filename was specified correctly and that the file exists and that the user running RMAN has read permission for the file.
RMAN-00557: could not open MSGLOG "string"
Cause: An error occurred when trying to open the file.
Action: Check that the filename was specified correctly and that the file exists and that the user running RMAN has write permission for the file.
RMAN-00558: error encountered while parsing input commands
Cause: The parser detected a syntax error.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
RMAN-00562: username too long
Cause: The specified user name exceeds the maximum allowable username length.
Action: Correct the username.
RMAN-00563: password too long
Cause: The specified password exceeds the maximum allowable password length.
Action: Correct the password.
RMAN-00564: host data too long
Cause: The SQL*NET host connect string exceeds the maximum allowable length.
Action: Correct the host string.
RMAN-00565: unable to read input file
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 1 line per record.
RMAN-00566: could not open TRACE "string"
Cause: An error occurred when trying to open the file.
Action: Check that the filename was specified correctly and that the user running RMAN has write permission for the file.
RMAN-00567: Recovery Manager could not print some error messages
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.
RMAN-00568: user interrupt received
Cause: The user typed ^C or ATTN.
Action: no action required
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
Cause: This message preceeds 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.
RMAN-00570: **end-of-file**
Cause: The end of an inline cmdfile was reached. This is just an informational message.
Action: no action required
RMAN-00571: ===========================================================
Cause: Displayed to highlight the 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.
RMAN-00572: waiting for dbms_pipe input
Cause: This message is used only when the PIPE option was specified.
Action: enqueue some RMAN input into the pipe
RMAN-00573: dbms_pipe.next_item_time returned unknown type code: number
Cause: This is an internal error
Action: contact Oracle Customer Support.
RMAN-00574: rman aborting due to errors read/writing dbms_pipe
Cause: RMAN was run with input/output being sent to dbms_pipe. An error was encountered while reading from or writing to the pipe. This error should be preceeded by information describing the error.
Action: RMAN terminates. Refer to the cause/action for the preceding errors.
RMAN-00575: timeout while trying to write to dbms_pipe
Cause: d by death of the process that was talking to rman.
Action: RMAN will abort.
RMAN-00576: PIPE cannot be used with CMDFILE
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.
RMAN-00577: PIPE requires that TARGET be specified on the command line
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.
RMAN-00578: pipe string is not private and owned by SYS
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.
RMAN-00579: SCRIPT cannot be used with CMDFILE
Cause: The SCRIPT and CMDFILE options cannot be used together. When using the SCRIPT option, RMAN executes only the specified script.
Action: Remove either the SCRIPT or CMDFILE option.
RMAN-00600: internal error, arguments [string] [string] [string] [string] [string]
Cause: An internal error in recovery manager occurred.
Action: Contact Oracle Customer Support.
RMAN-00601: fatal error in recovery manager
Cause: A fatal error has occurred.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
RMAN-00700: SCRIPT requires that TARGET be specified on the command line
Cause: A SCRIPT option was included on the RMAN command line without a specified TARGET database.
Action: Specify the TARGET option on the RMAN command line.
RMAN-00701: SCRIPT requires that CATALOG be specified on the command line
Cause: A SCRIPT option was included on the RMAN command line without a specified CATALOG recovery catalog.
Action: Specify the CATALOG option on the RMAN command line.
RMAN-01006: error signalled during parse
Cause: An error was signalled during parsing.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
RMAN-01007: at line number column number file: string
Cause: This is an informational message indicating the line and column where a syntax error was detected.
Action: no action required
RMAN-01008: the bad identifier was: string
Cause: This is an informational message indicating the identifier token that caused a syntax error.
Action: no action required
RMAN-02000: wrong message file version (msg number not found)
Cause: The rmanxx.msb file is not the correct version.
Action: Check that the installation was done correctly. The RMAN binary (executable, load module, whatever it is called on your O/S) and the rmanxx.msb file must be from the same version, release, and patch level.
RMAN-02001: unrecognized punctuation symbol "string"
Cause: An illegal punctuation character was encountered.
Action: Remove the illegal character.
RMAN-02002: unexpected end of input file reached
Cause: This is probably caused by failure to supply the closing quote for a quoted string.
Action: Correct the input.
RMAN-02003: unrecognized character: string
Cause: An input character that is neither an alpha, digit, or punctuation was encountered.
Action: Remove the character.
RMAN-02004: quoted string too big
Cause: A quoted string longer than 2000 bytes was encountered.
Action: This may be caused by a missing close quote. If so, add the missing quote, otherwise shorten the string.
RMAN-02005: token too big
Cause: A token longer than 1000 bytes was encountered
Action: Tokens must be separated by whitespace or punctuation. Either add the missing whitespace or punctuation, or shorten the token.
RMAN-02006: script line too long
Cause: a line longer than 500 bytes was encountered
Action: break the line up into shorter lines
RMAN-02007: Integer value overflow
Cause: Parser failed to convert input string to integer
Action: Acceptable values for integer are from 0 to 2147483648. Retry command using valid integer value.
RMAN-03000: recovery manager compiler component initialization failed
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-03001: recovery manager command sequencer component initialization failed
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-03002: failure of string command at string
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-03003: command not implemented yet: string
Cause: The command is not implemented in the current release.
Action: Avoid using the command.
RMAN-03004: fatal error during execution of command
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-03008: error while performing automatic resync of recovery catalog
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-03009: failure of string command on string channel at string
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-03010: fatal error during library cache pre-loading
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-03011: Recovery Manager: Release string string
Cause: This is the RMAN banner
Action: no action required
RMAN-03012: fatal error during compilation of command
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.
RMAN-03013: Copyright (c) 1995, 2003, Oracle Corporation. All rights reserved.
Cause: This is the copyright banner
Action: no action required
RMAN-03014: implicit resync of recovery catalog failed
Cause: of the failure.
Action: no action required
RMAN-03015: error occurred in stored script string
Cause: informational message only
Action: no action required
RMAN-03017: recursion detected in stored script string
Cause: A stored script is calling itself or another script which calls itself.
Action: Remove the recusion.
RMAN-03018: asynchronous RPCs are working correctly
Cause: informational message
Action: no action required
RMAN-03019: asynchronous RPCs are NOT working
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.
RMAN-03020: asynhronous RPC test will take 1 minute
Cause: informational message
Action: no action required
RMAN-03023: executing command: string
Cause: informational message
Action: no action required
RMAN-03028: fatal error code for command string : number
Cause: Informational message. This preceeds error 3012.
Action: no action required
RMAN-03029: echo set on
Cause: a SET ECHO ON command was issued
Action: no action required
RMAN-03030: echo set off
Cause: a SET ECHO OFF command was issued
Action: no action required
RMAN-03031: this option of set command needs to be used inside a run block
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.
RMAN-03032: this option of set command needs to be used outside of 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.
RMAN-03033: current log archived
Cause: A "ALTER SYSTEM ARCHIVE LOG CURRENT" command completed successfully.
Action: None, this is an informational message.
RMAN-03034: LEVEL number is invalid. LEVEL must be between string and string
Cause: An invalid DEBUG LEVEL was used.
Action: Change the DEBUG LEVEL argument.
RMAN-03035: Debugging turned off
Cause: a DEBUG OFF comand was issued
Action: no action required
RMAN-03036: Debugging set to level=number, types=string
Cause: a DEBUG comand was issued
Action: no action required
RMAN-03037: Spooling started in log file: string
Cause: a SPOOL LOG TO ... comand was issued
Action: no action required
RMAN-03038: Spooling started in trace file: string
Cause: a SPOOL TRACE TO ... comand was issued
Action: no action required
RMAN-03039: Spooling for log turned off
Cause: a SPOOL LOG OFF comand was issued
Action: no action required
RMAN-03040: Spooling for trace turned off
Cause: a SPOOL TRACE TO ... comand was issued
Action: no action required
RMAN-03090: Starting string at string
Cause: informational message
Action: no action required
RMAN-03091: Finished string at string
Cause: informational message
Action: no action required
RMAN-03098: RMAN-number: stringstring
Cause: This is the message prefix with a possible indentation.
Action: no action required
RMAN-03099: job cancelled at user request
Cause: The user interrupted the current job.
Action: None.
RMAN-03999: Oracle error occurred while while converting a date: ORA-number: string
Cause: Internal error converting a date.
Action: Contact Oracle Customer Support.
RMAN-04000: memory allocation failure
Cause: A memory allocation request could not be satisified.
Action: Increase the amount of memory available to RMAN.
RMAN-04001: heap initialization failure
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-04002: ocipi failed, ORA-string
Cause: OCI process level initialization failed.
Action: This error should not normally occur.
RMAN-04003: ociinit failed
Cause: The call to OCIEnvInit failed.
Action: This error should not normally happen. Contact Oracle Customer Support.
RMAN-04004: error from recovery catalog database: string
Cause: Oracle error signaled by catalog database. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-04005: error from target database: string
Cause: Oracle error signaled by target database. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-04006: error from auxiliary database: string
Cause: Oracle error signaled by auxiliary database. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-04007: WARNING from recovery catalog database: string
Cause: Non fatal Oracle error signaled by catalog database. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-04008: WARNING from target database: string
Cause: Non fatal Oracle error signaled by target database. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-04009: WARNING from auxiliary database: string
Cause: Non fatal Oracle error signaled by auxiliary database. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-04010: target database Password:
Cause: No password was provided for the target database.
Action: Provide target database password.
RMAN-04011: recovery catalog database Password:
Cause: No password was provided for the recovery catalog database.
Action: Provide recovery catalog database password.
RMAN-04012: auxiliary database Password:
Cause: No password was provided for the auxiliary database.
Action: Provide auxiliary database password.
RMAN-04013: must connect before startup
Cause: A STARTUP command was attempted before connecting to the database.
Action: Connect to database before attempting STARTUP command.
RMAN-04014: startup failed: string
Cause: The database failed to startup.
Action: The cause of the failure is included in the error message. Correct the cause of the failure and retry the startup command.
RMAN-04015: error setting target database character set to string
Cause: An error was received while setting the session character set in the target database.
Action: This error should not normally happen. Contact Oracle Customer Support.
RMAN-04016: could not get OCI error handle
Cause: An error was received while initializing the OCI layer.
Action: This error should not normally happen. Contact Oracle Customer Support.
RMAN-04020: target database name "string" does not match channel's name: "string"
Cause: The CONNECT clause in the ALLOCATE command has resulted in a connection to a database which is not the same as the one used to connect to the target database.
Action: Verify that the CONNECT string connects to the same database as the one specified in the TARGET connection for the CONNECT command.
RMAN-04021: target database DBID string does not match channel's DBID string
Cause: The CONNECT clause in the ALLOCATE command has resulted in a connection to a database which is not the same as the one used to connect to the target database.
Action: Verify that the CONNECT string connects to the same database as the one specified in the TARGET connection for the CONNECT command.
RMAN-04022: target database mount id string does not match channel's mount id string
Cause: The CONNECT clause in the ALLOCATE command has resulted in a connection to a database which is not the same as the one used to connect to the target database.
Action: Verify that the CONNECT string connects to the same database as the one specified in the TARGET connection for the CONNECT command.
RMAN-04024: trying to start the Oracle instance without parameter files ...
Cause: The instance could not be started because no default parameter file (either PFILE or SPFILE) could be found. The instance will be started in restricted mode with default parameters.
Action: None - this is an informational message.
RMAN-04025: unable to generate a temporary file
Cause: Creation of a temporary file failed. If 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.
RMAN-04026: unable to open a temporary file: "string"
Cause: Opening of a temporary file failed. If 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.
RMAN-04027: unable to write to a temporary file: "string"
Cause: Writing to a temporary file failed. If 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.
RMAN-04031: initialization parameters used for automatic instance: string
Cause: informational message
Action: no action required
RMAN-04032: using contents of file string
Cause: The specified file was included as part of the auxiliary database parameter file. This is an informational message.
Action: no action required
RMAN-04033: cannot open auxiliary parameter file string
Cause: An auxiliary parameter file was specified with SET AUXILIARY INSTANCE PARAMETER FILE command but the specified file cannot be found.
Action: Set the parameter file to an existen file or retry the command without setting AUXILIARY INSTANCE PARAMETER FILE.
RMAN-05000: CONFIGURE AUXNAME required for datafile string
Cause: Either: -) The controlfile mounted by the auxiliary database does not have an entry for this datafile, therefore filename conversion is not possible. -) A COPY DATAFILE TO AUXNAME command was issued, but no auxname was set for this datafile.
Action: Use the CONFIGURE AUXNAME command to specify a filename that the auxiliary database can use as a restore destination.
RMAN-05001: auxiliary filename string conflicts with a file used by the target database
Cause: RMAN is attempting to use the specified filename as a restore destination in the auxiliary database, but this name is already in use by the target database.
Action: Use the CONFIGURE AUXNAME command to specify a name for the datafile that does not conflict with a filename in use by the target db.
RMAN-05002: aborting point-in-time tablespace recovery
Cause: Previously encountered error(s) were issued which require corrective action.
Action: Resolve the error conditions, and then re-issue the RECOVER command.
RMAN-05003: point-in-time recovery is not allowed for tablespace string
Cause: The SYSTEM tablespace or a tablespace containing rollback segments is not allowed in point-in-time recovery.
Action: Remove the indicated tablespace from the recovery set and retry the operation.
RMAN-05004: target database log mode is NOARCHIVELOG
Cause: An attempt was made to apply TSPITR to a database that is in NOARCHIVELOG mode.
Action: If all required archive log files are available to TSPITR, alter the target database log mode to ARCHIVELOG and retry the TSPITR operation. Otherwise, TSPITR cannot be applied to this database.
RMAN-05005: point-in-time recovery is not allowed for re-created tablespace string
Cause: The requested tablespace has been re-created and is not allowed in point-in-time recovery.
Action: Remove the indicated tablespace from the recovery set and retry the operation.
RMAN-05006: cannot recover clone standby single tablespaces
Cause: Standby recover can only be performed for the whole database.
Action: Change the tablespace list to a database specification.
RMAN-05007: no channel allocated
Cause: A command was entered that requires a channel, and no channel is allocated.
Action: Use ALLOCATE CHANNEL before using the command
RMAN-05008: SET NEWNAME TO NEW not allowed (datafile string)
Cause: SET NEWNAME ... TO NEW is not allowed with TSPITR.
Action: Set the new name to a specific file name and retry.
RMAN-05009: Block Media Recovery requires Enterprise Edition
Cause: The BLOCKRECOVER command was specified.
Action: Remove the BLOCKRECOVER command.
RMAN-05010: target database must be opened in READ WRITE mode for TSPITR
Cause: The target database was not opened in read write mode.
Action: Open the database in read write mode.
RMAN-05011: auxiliary instance must be in nomount state for TSPITR
Cause: The Auxiliary instance was not in nomount state.
Action: Open the auxiliary instance in nomount state.
RMAN-05012: trying to start the Oracle instance without parameter files ...
Cause: The instance could not be started because no default parameter file (either PFILE or SPFILE) could be found. The instance will be started in restricted mode with default parameters.
Action: None - this is an informational message.
RMAN-05013: auxiliary control filename string conflicts with a file used by the target database
Cause: RMAN is attempting to use the specified control filename for TSPITR as a restore destination in the auxiliary database, but this name is already in use by the target database.
Action: Set control_files parameter in the auxiliary instance to a name that does not conflict with a filename in use by the target database.
RMAN-05016: failover to previous backup
Cause: This is an informational message to indicate the RMAN could not successfully restore the files using the specified backups. An attempt was made to restore the datafiles/archivelogs/ controlfile/SPFILE using a previous existing backup.
Action: See accompnaying additional error messages indicating the cause of the failover.
RMAN-05017: no copy of datafile number found to recover
Cause: A RECOVER COPY command was not able to proceed because no copy of indicated file was found to recover. Possible causes include the following:

1. no copy of indicated file exists on disk that satisfy the criteria specified in the user's recover operands.

2. copy of indicated datafile exists on disk but no incremental backup was found to apply to the datafile copy.

Action: One of the following:

1. Use or correct TAG specification to recover a different datafile copy.

2. Use BACKUP FOR RECOVER OF COPY command to create necessary incremental backup or copy.

RMAN-05018: some datafile copies cannot be recovered, aborting the RECOVER command
Cause: This error message can follow one or more RMAN-5017 or RMAN-5019 error messages.
Action: See RMAN-5017 or RMAN-5019 error messages documentation for more information.
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile number
Cause: A RECOVER COPY command could not proceed because incremental backup sets exist on a device type that has not been allocated.
Action: Use the LIST command to determine which device type is needed, then allocate a channel of that type.
RMAN-05020: cannot specify AUXILIARY DESTIONATION option for normal recovery
Cause: The AUXILIARY DESTIONATION option was specified for a normal recovery. It is only allowed for tablespace point in time recovery.
Action: Remove the AUXILIARY DESTIONATION option and re-run the RECOVER command.
RMAN-05021: this configuration cannot be changed for a BACKUP or STANDBY control file
Cause: The user attempted to modify the configuration which cannot be changed for a BACKUP or STANDBY control file while the mounted control file was either BACKUP or STANDBY. The following configurations can be changed only when connected to primary database instance that has CURRENT/CREATED control file type mounted: CONFIGURE RETENTION POLICY CONFIGURE EXCLUDE CONFIGURE ARCHIVELOG DELETION POLICY
Action: Connect to primary database instance and execute the command.
RMAN-05500: the auxiliary database must be not mounted when issuing a DUPLICATE command
Cause: A DUPLICATE command was issued, but the auxiliary database is mounted.
Action: Dismount the auxiliary database.
RMAN-05501: aborting duplication of target database
Cause: Previously encountered errors require corrective action.
Action: Resolve the error conditions, and reissue the DUPLICATE TARGET DATABASE command.
RMAN-05502: the target database must be mounted when issuing a DUPLICATE 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.
RMAN-05503: at least one auxiliary channel must be allocated to execute this command
Cause: No auxiliary channels were allocated.
Action: Allocate an auxiliary channel.
RMAN-05504: at least two redo log files or groups must be specified for this command
Cause: Only one redo log file or group was specified
Action: Specify at least one more redo log file or group
RMAN-05505: auxiliary filename conversion of 'string' exceeds maximum length of string
Cause: When the given filename is converted to the name used for the auxiliary database, the converted name is larger than the maximum allowed filename.
Action: Change initialization parameter DB_FILE_NAME_CONVERT to convert to a valid filename.
RMAN-05506: error during recursive execution
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-05507: standby controlfile checkpoint (string) is more recent than duplication point in time (string)
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.
RMAN-05508: SET NEWNAME TO NEW not allowed (datafile string)
Cause: SET NEWNAME ... TO NEW is not allowed with the DUPLICATE command.
Action: Set the new name to a specific file name and retry.
RMAN-05510: Duplicate finished
Cause: informational message
Action: no action required
RMAN-05511: Datafile string skipped by request
Cause: informational message
Action: no action required
RMAN-05512: tablespace string cannot be skipped from duplication
Cause: The SYSTEM and SYSAUX tablespaces were not included in the duplicate database. They must be present.
Action: Remove the SYSTEM and/or SYSAUX tablespace from the SKIP list and retry the operation.
RMAN-05513: cannot duplicate, controlfile is not current or backup
Cause: DUPLICATE requires that the target database has a current controlfile
Action: Open the target database and retry operation
RMAN-05514: tablespace string has undo information, cannnot skip
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.
RMAN-05515: Duplicate for standby does not allow the use of SET UNTIL
Cause: A SET UNTIL clause was specified for the command.
Action: Remove the SET UNTIL clause and try again.
RMAN-06000: could not open recovery manager library file: string
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.
RMAN-06001: error parsing job step library
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.
RMAN-06002: command not allowed when not connected to a recovery catalog
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 CATALOG parameter.
RMAN-06003: ORACLE error from target database: string
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-06004: ORACLE error from recovery catalog database: string
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-06005: connected to target database: string (DBID=string)
Cause: informational message
Action: no action required
RMAN-06006: connected to target database: string (not mounted)
Cause: informational message
Action: no action required
RMAN-06007: target database not mounted and db_name not set in init.ora
Cause: The target database has not mounted the controlfile, 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" and restart the instance.
RMAN-06008: connected to recovery catalog database
Cause: informational message
Action: no action required
RMAN-06009: using target database controlfile instead of recovery catalog
Cause: informational message
Action: no action required
RMAN-06010: error while looking up datafile: string
Cause: An error occurred while looking up the specified datafile in the recovery catalog or target database controlfile.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the filename is entered correctly. If the datafile was added recently, then a RESYNC CATALOG must be done to update the recovery catalog.
RMAN-06011: invalid level specified: number
Cause: An invalid incremental backup level was specified.
Action: Incremental backup level must be between 0 and 4.
RMAN-06012: channel: string not allocated
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.
RMAN-06013: duplicate channel identifier found: string
Cause: A channel identifier was reused without first releasing the channel.
Action: Add a RELEASE CHANNEL command.
RMAN-06014: command not implemented yet: string
Cause: Not all commands are implemented for the beta release.
Action: Avoid using the command.
RMAN-06015: error while looking up datafilecopy name: string
Cause: An error occurred while looking up the specified datafilecopy name in the recovery catalog or target database controlfile.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the filename is entered correctly. If the datafilevopy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.
RMAN-06016: duplicate backup operand specified: string
Cause: The specified operand appears more than once in the same backup specifier or backup command.
Action: Delete the duplicate operand.
RMAN-06017: initialization of parser failed
Cause: The parser package initialization routine returned an error.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
RMAN-06018: duplicate operand specified in backup specification: string
Cause: A backup specification operand appears more than once in a backup specification.
Action: Delete the duplicate operand.
RMAN-06019: could not translate tablespace name "string"
Cause: An error occurred while looking up the specified tablespace name in the recovery catalog or target database controlfile.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the tablespace is entered correctly. If the tablespace was added recently, then a RESYNC CATALOG must be done to update the recovery catalog.
RMAN-06020: connected to auxiliary database (not started)
Cause: informational message
Action: no action required
RMAN-06021: FROM DATAFILECCOPY/BACKUPSET may not be specified with archive logs
Cause: The FROM DATAFILECCOPY/BACKUPSET option applies only to datafile and controlfile restores.
Action: Use this option only for datafile and controlfile restores.
RMAN-06022: invalid level specified for image copy: number
Cause: An invalid incremental backup level was specified for an image copy.
Action: Incremental backup level must be 0 for image copies.
RMAN-06023: no backup or copy of datafile number found to restore
Cause: A datafile, tablespace, or database restore could not proceed because no backup or copy of the indicated file was found. It may be the case that a backup or copy of this file exists but does not satisfy the criteria specified in the user's restore operands.
Action: None - this is an informational message. See message 6026 for further details.
RMAN-06024: no backup or copy of the controlfile found to restore
Cause: A controlfile restore could not proceed because no backup or copy of the controlfile was found. It may be the case that a backup or copy of this file exists but does not satisfy the criteria specified in the user's restore operands.
Action: None - this is an informational message. See message 6026 for further details.
RMAN-06025: no backup of log thread number seq number lowscn string found to restore
Cause: An archive log restore restore could not proceed because no backup of the indicated archived log was found. It may be the case that a backup of this file exists but does not satisfy the criteria specified in the user's restore operands.
Action: None - this is an informational message. See message 6026 for further details.
RMAN-06026: some targets not found - aborting restore
Cause: Some of the files specified for restore could not be found. Message 6023, 6024, or 6025 is also issued to indicate which files could not be found. Some common reasons why a file can not be restored are that there is no backup or copy of the file that is known to recovery manager, or there are no backups or copies that fall within the criteria specified on the RESTORE command, or some datafile copies have been made but not cataloged.
Action: The Recovery Manager LIST command can be used to display the backups and copies that Recovery Manager knows about. Select the files to be restored from that list.
RMAN-06027: no archive logs found that match specification
Cause: An archive log record specifier did not match any archive logs in the recovery catalog.
Action: Resubmit the command with a different archive log record specifier. The rman LIST command can be used to display all archive logs that Recovery Manager knows about.
RMAN-06028: duplicate operand specified in restore specification: string
Cause: The CHANNEL, TAG, FROM, PARMS, VALIDATE, DEVICE TYPE or CHECK READONLY option was specified more than once in the restore command or in one of the restore specifications.
Action: Correct and resubmit the comand.
RMAN-06029: the controlfile may be included only in a datafile backup set
Cause: The "include current/standby controlfile" option was specified for an archive log backup set.
Action: Use this option only for datafile backup sets.
RMAN-06030: the DELETE [ALL] INPUT option may not be used with a datafile backup set
Cause: The DELETE [ALL] INPUT option was specified for a backup that contains the current controlfile or datafiles.
Action: Remove the option and resubmit the command.
RMAN-06031: could not translate database keyword
Cause: An error was received when calling dbms_rcvman
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
RMAN-06032: at least 1 channel of TYPE DISK must be allocated to execute a COPY command
Cause: No channel of TYPE DISK was allocated.
Action: Allocate a channel of TYPE DISK and re-issue the command.
RMAN-06033: channel string not allocated
Cause: An rman command requests a specific channel, but the requested channel has not been allocated.
Action: ALLOCATE the channel, or correct the channel identifier.
RMAN-06034: at least 1 channel must be allocated to execute this command
Cause: No channels were allocated.
Action: ALLOCATE a channel.
RMAN-06035: wrong version of recover.bsq, expecting string, found string
Cause: The "recover.bsq" file is incompatible with the RMAN executable.
Action: Install the correct version of recover.bsq.
RMAN-06036: datafile number is already restored to file string
Cause: A SET NEWNAME command was issued to restore a datafile to a location other than the original datafile, and Recovery Manager determined that the best candidate for restoring the file is the datafile copy with the same name, therefore the file is already restored and no action need be taken.
Action: None - this is an informational message.
RMAN-06038: recovery catalog package detected an error
Cause: A call to dbms_rcvman returned an error.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
RMAN-06039: no set newname command has been issued for datafile number
Cause: A SWITCH command was specified for a datafile, but no destination was specified and no SET NEWNAME command has been previously issued for that file. An explicit file to switch to must be specified if no SET NEWNAME command has been issued.
Action: Correct and resubmit the SWITCH command.
RMAN-06040: controlfile is already restored to file string
Cause: The best candidate controlfile for restoration is the one that is named in the RESTORE (controlfile) command, hence no action need be taken.
Action: None - this is an informational message.
RMAN-06041: cannot switch file number to copy of file number
Cause: An attempt was made to switch a datafile to a copy of a different datafile.
Action: Correct and resubmit the SWITCH command.
RMAN-06042: PLUS ARCHIVELOG option is not supported with non-datafile backups
Cause: The PLUS ARCHIVELOG option was supplied but does not apply to this type of backup.
Action: Remove the PLUS ARCHIVELOG operand and re-enter the command.
RMAN-06043: TAG option not supported for archive log copies
Cause: The tag option was supplied but does not apply to this type of copy.
Action: Remove the TAG operand and re-enter the command
RMAN-06045: LEVEL option not supported for archive log or current/standby controlfile copies
Cause: The LEVEL option was supplied but does not apply to this type of copy.
Action: Remove the LEVEL operand and re-enter the command.
RMAN-06046: archive log name: string
Cause: An error occurred while translating an archive log name to its recovery catalog recid/timestamp. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-06047: duplicate datafile number specified for restoration from copy
Cause: The indicated datafile was specified more than once in the same restore command.
Action: Correct and resubmit the RESTORE command.
RMAN-06048: duplicate controlfile specified for restoration from copy
Cause: The controlfile was specified more than once in the same RESTORE command.
Action: Correct and resubmit the RESTORE command.
RMAN-06049: CHECK LOGICAL option not supported for archive log or current/standby controlfile copies
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
RMAN-06050: archive log thread number sequence number is already on disk as file string
Cause: An archive log which was requested to be restored (either explicitely or via a range specification) does not need to be restored because it already exists on disk.
Action: None - this is an informational message
RMAN-06051: DELETE INPUT option not implemented yet
Cause: This option was specified in a backup specification.
Action: Remove the DELETE INPUT option.
RMAN-06052: no parent backup or copy of datafile number found
Cause: An incremental backup at level 1 or higher could not find any parent backup or copy of the indicated datafile. A level 0 backup of the datafile will be taken automatically.
Action: informational message
RMAN-06053: unable to perform media recovery because of missing log
Cause: This message is accompanied with another message identifying the missing log. The log would be needed to perform the media recovery, but the log is not on disk and no backup set containing the log is available.
Action: Determine if a backup set containing the log can be made available. If so, then use the CHANGE command to make the backup set available and retry the command. If not, then a point in time recovery up to the missing log is the only alternative.
RMAN-06054: media recovery requesting unknown log: thread string seq string lowscn string
Cause: Media recovery is requesting a log whose existance is not recorded in the recovery catalog or controlfile.
Action: If a copy of the log is available, then add it to the recovery catalog and/or controlfile 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 and database can be opened using ALTER DATABASE OPEN RESETLOGS command.
RMAN-06055: could not find log sequence string thread string
Cause: A log which was on disk at the start of media recovery or which should have been restored from a backup set could not be found.
Action: Check the Recovery Manager message log to see if the log was restored by a previous job step. If so, then check the V$ARCHIVED_LOG view to see if the log is listed in the controlfile. If so, then validate that the log exists on disk and is readable. If the log was not restored, or was restored but no record of the log exists in V$ARCHIVED_LOG, then contact Oracle Customer Support.
RMAN-06056: could not access datafile number
Cause: A backup 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.
RMAN-06057: a standby controlfile cannot be included along with a current controlfile
Cause: "current controlfile" was specified along with "standby controlfile".
Action: Remove "current controlfile" or "standby controlfile" from backup specification.
RMAN-06058: a current controlfile cannot be included along with a standby controlfile
Cause: "standby controlfile" was specified along with "current controlfile".
Action: Remove "standby controlfile" or "current controlfile" from backup specification.
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
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.
RMAN-06060: WARNING: skipping datafile compromises tablespace string recoverability
Cause: SKIP INACCESSIBLE or SKIP OFFLINE option resulted in skipping datafiles during BACKUP. If the datafile has in fact been lost and there is no backup, then the tablespace is no longer recoverable without ALL archive logs since datafile creation. This may occur because the datafile was deleted by an outside utility or the datafile is made OFFLINE [DROP].
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.
RMAN-06061: WARNING: skipping archivelog compromises recoverability
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.
RMAN-06062: can not backup SPFILE because the instance was not started with SPFILE
Cause: A backup command requested a backup of the SPFILE, but no SPFILE was used to startup the instance.
Action: Create an SPFILE and re-start the instance using the SPFILE or modify the command.
RMAN-06063: DBID is not found in the recovery catalog
Cause: DBID is not found in the recovery catalog.
Action: Verify that the DBID is correct and restart the command.
RMAN-06064: creating datafile fno=string name=string
Cause: RESTORE/RECOVER command was issued and there were no backup available for the datafile.
Action: informational message
RMAN-06065: The backup operand [string] conflicts with another specified operand.
Cause: The user attempted to use two (or more) conflicting operands within the same statement.
Action: Remove one or both of the conflicting operands.
RMAN-06066: the target database must be mounted when issuing a RECOVER command
Cause: A RECOVER command was issued, but the target database controlfile is not mounted.
Action: Mount the target database controlfile by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.
RMAN-06067: RECOVER DATABASE required with a backup or created controlfile
Cause: The controlfile has been restored from a backup or was created via ALTER DATABASE CREATE CONTROLFILE.
Action: Use the RECOVER DATABASE command to perform the recovery.
RMAN-06068: recovery aborted because of missing datafiles
Cause: This error should be accompanied by one or more instances of message ORA-06094.
Action: Refer to message ORA-06094.
RMAN-06069: the filename for datafile string is missing in the controlfile
Cause: Media recovery of a backup controlfile added this datafile to the controlfile, but it does not set the filename because that is unsafe.
Action: If the datafile is on disk, then issue ALTER DATABASE RENAME to correct the controlfile. Otherwise, RESTORE the datafile, and then use SWITCH to make it known to the controlfile. If the tablespace containing this datafile will be dropped, then reissue the RECOVER command with a SKIP clause to skip recovery of this tablespace.
RMAN-06070: DBWR could not identify datafile string
Cause: DBWR could not find the specified datafile.
Action: Ensure that the datafile exists and is accessible.
RMAN-06071: could not open datafile string
Cause: An error was encountered when trying to open the specified datafile.
Action: Ensure that the datafile exists and is accessible.
RMAN-06073: file header is corrupt for datafile string
Cause: ORACLE detected a corruption in the file header. A media failure has probably occurred.
Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.
RMAN-06074: file string is not an ORACLE datafile
Cause: The file header indicates that this file is not a datafile. The file may have been overlaid or corrupted.
Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.
RMAN-06075: datafile string does not belong to this database
Cause: The file header indicates that this file belongs to some other ORACLE database.
Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.
RMAN-06076: datafile string contains wrong datafile
Cause: The datafile header indicates the file contains a different datafile number.
Action: RESTORE the datafile, and then retry the RECOVER command.
RMAN-06077: datafile string is a different version than contained in the controlfile
Cause: The controlfile entry for this datafile specifies a different version of this datafile. Different versions of a datafile can exist when a tablespace is dropped, and a new tablespace is created which reuses the same datafile numbers.
Action: If the datafile is correct, the fix the controlfile by using the SWITCH command. Otherwise, RESTORE the correct version of this datafile and retry the RECOVER command.
RMAN-06078: the controlfile is older than datafile string
Cause: The controlfile appears to be older than the specified datafile, but it is not marked as a backup controlfile. This indicates that the controlfile has been replaced with an older version. This error does not occur when a backup controlfile which was created via Recovyer Manager or the ALTER DATABASE BACKUP CONTROLFILE command is restored because such controlfiles are marked as backups.
Action: RESTORE a controlfile and perform RECOVER DATABASE.
RMAN-06079: database must be mounted to perform recovery
Cause: A RECOVER command was issued, but the target database is not mounted.
Action: Issue ALTER DATABASE MOUNT.
RMAN-06080: SWITCH required for datafile string
Cause: The controlfile record for this datafile is for an older incarnation of the datafile. A SWITCH command must be issued to update the controlfile before doing RECOVER.
Action: Issue SWITCH command then retry RECOVER.
RMAN-06081: error reading datafile header for datafile string, code string
Cause: X$KCVFH returned the specified code in the hxerr column when it was queried for the specified datafile.
Action: Ensure the datafile exists and is readable. Using a newer release of Recovery Manager may return a more meaningful error message. If you have no newer version of Recovery Manager, contact Oracle Customer Support.
RMAN-06082: datafilecopy tag string is ambiguous
Cause: The specified tag refers to multiple datafile copies belonging to different datafiles.
Action: Specify the datafilecopy by filename rather than by tag.
RMAN-06083: error when loading stored script string
Cause: The recovery catalog database returned an error. This error explains the cause of the problem.
Action: Correct the problem and retry.
RMAN-06084: the target database may not be mounted when issuing REPLICATE
Cause: A REPLICATE command was issued, but the target database is already mounted.
Action: dismount the target database controlfile by issuing ALTER DATABASE CLOSE and ALTER DATABASE DISMOUNT via Enterprise Manager or Server Manager.
RMAN-06085: must use SET NEWNAME command to restore datafile string
Cause: A RESTORE command for the specified datafile could not find a destination name for the specified datafile.
Action: Add a SET NEWNAME command prior to the RESTORE command to specify the restore destination for this file.
RMAN-06086: offline files may only be skipped in a datafile backup set
Cause: The SKIP OFFLINE option was specified for an archive log backup set.
Action: Use this option only for datafile backup sets.
RMAN-06087: read-only files may only be skipped in a datafile backup set
Cause: The SKIP READONLY option was specified for an archive log backup set.
Action: Use this option only for datafile backup sets.
RMAN-06088: datafile copy string not found or out of sync with catalog
Cause: The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database.
Action: Re-catalog the file and retry the operation.
RMAN-06089: archived log string not found or out of sync with catalog
Cause: The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database.
Action: Re-catalog the file and retry the operation.
RMAN-06090: error while looking up controlfile copy: string
Cause: An error occurred while looking up the specified controlfile copy in the recovery catalog or target database controlfile.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the filename is entered correctly. If the controlfile copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.
RMAN-06091: no channel allocated for maintenance (of an appropriate type)
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.
RMAN-06092: error while looking up backup piece
Cause: An error occurred while looking up the specified backup piece in the recovery catalog or target database controlfile.
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.
RMAN-06093: recovery catalog contains obsolete version of datafile string
Cause: The specified datafile number was dropped and then reused. The controlfile mounted by the target database contains the newer version of the datafile, but the recovery catalog contains information about only the older version.
Action: Issue a RESYNC command to update the recovery catalog, then reissue the failing command. If the error persists, contact Oracle Customer Support.
RMAN-06094: datafile string must be restored
Cause: A RECOVER command was issued, and the recovery catalog indicates the specified datafile should be part of the recovery, but this datafile is not listed in the controlfile, and cannot be found on disk.
Action: Issue a RESTORE command for this datafile, using the same UNTIL clause specified to the RECOVER command (if any), then reissue the RECOVER.
RMAN-06095: a backup controlfile must be restored to recover datafile string
Cause: The controfile currently mounted by the target database contains a newer incarnation of the datafile than the recovery catalog indicates is appropriate for the point-in-time being recovered to.
Action: Restore the controlfile, using the same UNTIL clause specified on the failing RECOVER command, then reissue the command. If no controlfile can be restored, then you should issue a CREATE CONTROLFILE command.
RMAN-06096: SWITCH required for newname of datafile string to take effect
Cause: A SET NEWNAME was issued for this datafile, but no SWITCH command was issued before the RECOVER command.
Action: Issue a SWITCH command to make the newname take effect before doing RECOVER.
RMAN-06098: the target database must be mounted when issuing a BACKUP command
Cause: A BACKUP command was issued, but the target database controlfile is not mounted.
Action: Mount the target database controlfile by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.
RMAN-06099: error occurred in source file: string, line: number
Cause: See accompanying error
Action: See accompanying error
RMAN-06100: no channel to restore a backup or copy of datafile number
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: None - this is an informational message. See message 6026 for further details.
RMAN-06101: no channel to restore a backup or copy of the controlfile
Cause: A controlfile restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore.
Action: None - this is an informational message. See message 6026 for further details.
RMAN-06102: no channel to restore a backup or copy of log thread number seq number lowscn string
Cause: An archive log restore restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore.
Action: None - this is an informational message. See message 6026 for further details.
RMAN-06103: duplicate qualifier found in REPORT command: string
Cause: The indicated qualifier appears more than once in a REPORT qualifier list.
Action: delete the duplicate qualifier
RMAN-06105: duplicate qualifier found in LIST command: string
Cause: The indicated qualifier appears more than once in a LIST qualifier list.
Action: delete the duplicate qualifier
RMAN-06106: this command requires that target database be mounted
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 controlfile by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.
RMAN-06107: WARNING: controlfile is not current for REPORT NEED BACKUP DAYS
Cause: The REPORT NEED BACKUP DAYS command may report some files as requiring backups when they really do not, because the most current online status of the file is not known unless a current controlfile is mounted.
Action: no action required, however, a current controlfile should be mounted, if possible, to get the most accurate REPORT output.
RMAN-06108: changed datafile copy unvailable
Cause: informational message
Action: no action required
RMAN-06109: changed archive log unavailable
Cause: informational message
Action: no action required
RMAN-06110: changed controlfile copy unavailable
Cause: informational message
Action: no action required
RMAN-06111: changed backup piece unavailable
Cause: informational message
Action: no action required
RMAN-06112: changed datafile copy available
Cause: informational message
Action: no action required
RMAN-06113: changed archive log available
Cause: informational message
Action: no action required
RMAN-06114: changed controlfile copy available
Cause: informational message
Action: no action required
RMAN-06115: changed backup piece available
Cause: informational message
Action: no action required
RMAN-06116: cannot crosscheck unavailable object
Cause: An attempt was made to crosscheck an object which is unavailable.
Action: Make object available and try again or don't crosscheck object.
RMAN-06117: cannot do DELETE EXPIRED on an object which is not expired
Cause: An attempte was made to DELETE EXPIRED an object which is not expired.
Action: Remove EXPIRED keyword, crosscheck object, or don't delete object.
RMAN-06118: a backup controlfile older than SCN string must be used for this recovery
Cause: An attempt was made to recover the database, but some files had no backup, and were not present in the control file at the beginning of the restore. This happens when the control file used during the recovery is a backup control file taken before the creation of some of the files that had no backup. In this situation, the control file that is used must be taken before the creation of all files that have no backup. This will enable RMAN to automatically re-create all of the files that had no backup.
Action: Restore a controlfile that was backed up before the specified SCN. The following RMAN commands can be used to do this: SET UNTIL SCN <x>;(where <x> is the SCN displayed in the message) RESTORE CONTROLFILE;
RMAN-06119: uncataloged datafile copy
Cause: informational message
Action: no action required
RMAN-06120: uncataloged archive log
Cause: informational message
Action: no action required
RMAN-06121: uncataloged controlfile copy
Cause: informational message
Action: no action required
RMAN-06122: CHANGE .. UNCATALOG not supported for BACKUPSET
Cause: The CHANGE BACKUPSET .. UNCATALOG command was entered. The UNCATALOG operation is not supported with backup set.
Action: Use CHANGE BACKUPSET .. DELETE instead.
RMAN-06123: operation not supported without the recovery catalog or mounted controlfile
Cause: A command was used which requires a connection to a recovery catalog database or the target database to be mounted. The command cannot be used when no backup repository is available.
Action: If a recovery catalog database is available, then connect to the recovery catalog and retry the command, otherwise enter a different command.
RMAN-06124: error while looking up datafilecopy key: number
Cause: An error occurred while looking up the specified datafilecopy key in the recovery catalog.
Action: This error is accompanied by other errors describing the reason for the failure.
RMAN-06125: error while looking up archive log key: number
Cause: An error occurred while looking up the specified archive log key in the recovery catalog.
Action: This error is accompanied by other errors describing the reason for the failure.
RMAN-06126: skipping offline file string
Cause: The indicated file will not be included in the backup set because it is offline and the SKIP OFFLINE option was specified.
Action: no action required
RMAN-06127: skipping read-only file string
Cause: The indicated file will not be included in the backup set because it is read only and the SKIP READONLY option was specified.
Action: no action required
RMAN-06128: skipping inaccessible file string
Cause: The indicated file will not be included in the backup set because it could not be read, and the SKIP INACCESSIBLE option was specified.
Action: no action required
RMAN-06129: invalid reserved channel ID: string
Cause: The specified channel id is invalid. DELETE and DEFAULT are reserved channel names and may not be specified by users.
Action: Specify a different channel ID.
RMAN-06131: skip offline/readonly only allowed with current controlfile
Cause: The SKIP OFFLINE and SKIP READONLY options are only permitted when the target database controlfile is current. When the target controlfile is not current, it is not possible to obtain a datafile's offline/readonly status.
Action: Remove the skip option or mount a current controlfile on the target database.
RMAN-06132: cannot backup datafile string because it is not in the controlfile
Cause: A backup command was issued that includes the specified datafile, but the datafile is not listed in the controlfile. The controlfile is not current (it is a backup or a created controlfile).
Action: Recover the controlfile to make it current, then retry the backup command.
RMAN-06133: recovery catalog may have obsolete data for datafile string
Cause: A RESTORE UNTIL was issued, and the recovery catalog choose an older incarnation of the datafile than is listed in the controlfile.
Action: If the recovery catalog has correct data for the datafile, then restore a backup controlfile using the same UNTIL clause, then retry the datafile restore. Otherwise, restore a backup of the incarnation of the datafile listed in the controlfile.
RMAN-06134: host command complete
Cause: An operating system command has completed.
Action: None - this is an informational message.
RMAN-06135: error executing host command: string
Cause: A host command returned a non-zero return code.
Action: Correct the offending command.
RMAN-06136: ORACLE error from auxiliary database: string
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-06137: must have recovery catalog for REPORT SCHEMA AT TIME
Cause: A 'REPORT SCHEMA at_clause' command was issued, but there is no recovery catalog database.
Action: If you are not using a recovery catalog, then you may only issue the 'REPORT SCHEMA' command with no at_clause.
RMAN-06138: controlfile not mounted - must specify AT clause with REPORT command
Cause: A 'REPORT SCHEMA' with no at_clause was issued, and there is no recovery catalog, and there is also no controlfile 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 controlfile at the target database.
RMAN-06139: WARNING: controlfile is not current for REPORT SCHEMA
Cause: A 'REPORT SCHEMA' with no at_clause was issued, and there is no recovery catalog, and the controlfile 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 controlfile.
RMAN-06140: cannot specify TAG option with LIST INCARNATION
Cause: The TAG option was specified with LIST INCARNATION. This is not permitted because there is no TAG associated with a database incarnation.
Action: Remove the TAG option and re-run the LIST command.
RMAN-06141: cannot specify ARCHIVELOG LIKE option with RESTORE
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.
RMAN-06142: DEVICE TYPE cannot be specified with this command
Cause: The DEVICE TYPE option was specified with a command that does not support it.
Action: Remove the DEVICE TYPE option and re-run the command.
RMAN-06143: LIKE may only be specified with COPY
Cause: The LIKE option was specified with a RMAN command. This is not permitted because only copies of datafiles, controlfiles or archive logs have file names that may be tested with a LIKE operand.
Action: Remove the LIKE option and re-run the RMAN command.
RMAN-06144: FROM or UNTIL may not be specified with LIST INCARNATION
Cause: The FROM or UNTIL option was specified with LIST INCARNATION. This is not permitted because there is no time associated with a database incarnation.
Action: Remove the FROM or UNTIL option and re-run the LIST command.
RMAN-06145: controlfile is not current - obsolete file list may be incomplete
Cause: A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. If the mounted controlfile is not current, it may not be possible to determine if a satisfactory backup exists for files which have been offline since the last OPEN RESETLOGS.
Action: No action need be taken - this is an informational message only. To ensure a complete report of obsolete backups, mount a current controlfile.
RMAN-06146: changes found for file number beyond offline SCN
Cause: A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. A backup was found for a file which is shown as offline in the target database controlfile, but the backup contains changes beyond the SCN when the file went offline. This is most likely because the target database controlfile is not really current, but is a restored copy of an older controlfile.
Action: Mount a current controlfile or a backup controlfile.
RMAN-06147: no obsolete backups found
Cause: A CHANGE or REPORT command could find no files that meet the specified criteria for obsoleteness.
Action: None - this is an informational message.
RMAN-06148: redundancy count must be greater than zero
Cause: The REDUNDANCY operand specified for a CHANGE or REPORT OBSOLETE command was zero.
Action: Specify a REDUNDANCY operand of 1 or greater.
RMAN-06150: auxiliary name for datafile number set to: string
Cause: This message is issued in response to a CONFIGURE AUXNAME command.
Action: None - this is an informational message.
RMAN-06151: datafile string creation scn string
Cause: This is an informational message. It should be accompanied by other messages.
Action: none
RMAN-06153: validation failed for datafile copy
Cause: The CHANGE DATAFILE COPY VALIDATE command found that the datafile copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog.
Action: None - this is an informational message.
RMAN-06154: validation succeeded for datafile copy
Cause: The CHANGE DATAFILE COPY VALIDATE command found that the datafile copy still matches its data in the recovery catalog.
Action: None - this is an informational message.
RMAN-06155: validation failed for controlfile copy
Cause: The CHANGE CONTROLFILECOPY VALIDATE command found that the controlfile copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog.
Action: None - this is an informational message.
RMAN-06156: validation succeeded for controlfile copy
Cause: The CHANGE CONTROLFILECOPY VALIDATE command found that the controlfile copy still matches its data in the recovery catalog.
Action: None - this is an informational message.
RMAN-06157: validation failed for archived log
Cause: The CHANGE ARCHIVELOG VALIDATE command found that the archived log could not be found or no longer contains the same data, so its record was deleted from the recovery catalog.
Action: None - this is an informational message.
RMAN-06158: validation succeeded for archived log
Cause: The CHANGE ARCHIVED LOG VALIDATE command found that the archived log still matches its data in the recovery catalog.
Action: None - this is an informational message.
RMAN-06159: error while looking up backup set
Cause: An error occurred while looking up the specified backup set in the recovery catalog or target database controlfile.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the key is entered correctly. If the backup set was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.
RMAN-06160: no backup pieces found for backup set key: number
Cause: No backup pieces for the requested backup set were found in the recovery catalog, or the target database controlfile.
Action: Specify an existing backup set.
RMAN-06161: error when inspecting auxiliary filename: string
Cause: This error is accompanied by other errors explaining the cause.
Action: Correct the auxiliary filename if it is wrong via the CONFIGURE AUXNAME command.
RMAN-06162: sql statement: string
Cause: This is the sql statement about to be executed for a SQL command.
Action: None, informational message only.
RMAN-06163: some datafiles cannot be recovered, aborting the RECOVER command
Cause: This message should be followed by one or more 6162 or 6164 messages.
Action: Check the accompanying errors.
RMAN-06164: WARNING: no channel of required type allocated to recover datafile number
Cause: A RECOVER command could not proceed because incremental backup sets or archive log backup sets exist on a device type that has not been allocated.
Action: Use the LIST command to determine which device type is needed, then allocate a channel of that type.
RMAN-06165: datafile string is too old to recover, restore a more recent copy
Cause: The archived logs and/or incremental backup sets required to recover the datafile do not exist, but a more recent backup of the datafile exists which can be recovered.
Action: Issue a RESTORE for the datafile, then reissue the RECOVER command.
RMAN-06166: datafile string cannot be recovered
Cause: Incremental backups or archived redo logs needed to recover the datafile cannot be found, and no recoverable full backup or datafile copy exists.
Action: Use the LIST command to see if there is a backup set or datafile copy that can be made AVAILABLE. If not, then the datafile is unrecoverable. If a full or datafile copy exists, then a point-in-time recovery may be possible.
RMAN-06167: already connected
Cause: a CONNECT command was issued, but RMAN is already connected to the specified database.
Action: RMAN has no DISCONNECT command, so to connect to a different instance, exit RMAN and start it again.
RMAN-06168: no backup pieces with this tag found: string
Cause: A tag was used to specify a list of backup pieces, but no backup pieces with this tag could be found.
Action: Make sure the tag is specified correctly.
RMAN-06169: could not read file header for datafile string error reason string
Cause: The specified datafile could not be accessed. The reason codes are: 1 - filename is MISSINGxx in the controlfile 2 - file is offline 3 - file is not verified 4 - DBWR could not find the file 5 - unable to open file 6 - I/O error during read 7 - file header is corrupt 8 - file is not a datafile 9 - file does not belong to this database 10 - file number is incorrect 12 - wrong file version 15 - controlfile is not current
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.
RMAN-06170: no controlfile copy found with offline range recid string stamp string datafile string
Cause: This offline range is needed for recovering the specified datafile, but the offline range record has aged out of the current controlfile and no controlfile copy with the record could be accessed. At least 1 controlfile copy containing the offline range was found in the recovery catalog and was in AVAILABLE status.
Action: Query the rc_controlfile_copy view for the names of all controlfile copies, then issue a CHANGE CONTROLFILECOPY ... VALIDATE; command for them. Then reissue the RECOVER command.
RMAN-06171: not connected to target database
Cause: A command was issued but no connection to the target database has been established.
Action: Issue a CONNECT TARGET command to connect to the target database.
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
Cause: A restore could not proceed because no autobackup was found or specified handle is not a valid copy or backup piece. In case of restore from autobackup, it may be the case that a backup exists, but it does not satisfy the criteria specified in the user's restore operands. In case of restore from handle, it may be the handle is not a backup piece or controflile copy. In may be that it does not exist.
Action: Modify autobackup search criteria or verify the handle.
RMAN-06173: no set newname command has been issued for datafile string when restore auxiliary
Cause: Auxiliary type was specified for the controlfile, but no SET NEWNAME command has been previously issued for a datafile.
Action: Issue SET NEWNAME command for every datafile in the recovery set.
RMAN-06174: not connected to auxiliary database
Cause: An auxiliary command was issued but no connection to a auxiliary database has been established.
Action: Issue a CONNECT AUXILIARY command to connect to the auxiliary database.
RMAN-06175: deleted script: string
Cause: A DELETE SCRIPT command was executed.
Action: None, informational message only.
RMAN-06176: no recovery required; all files are readonly or offline
Cause: A RECOVER DATABASE command does not need to recover any files because all of the files to be recovered are offline or read only. This can only occur when the SKIP clause includes the system tablespace.
Action: None, informational message only
RMAN-06177: restore not done; all files readonly, offline, or already restored
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.
Action: None, informational message only
RMAN-06178: datafile number not processed because file is offline
Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is offline clean at the desired point in time.
Action: None, informational message only
RMAN-06179: datafile number not processed because file is read-only
Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is part of a read-only tablespace at the desired point in time.
Action: None, informational message only
RMAN-06180: incremental backups require Enterprise Edition
Cause: A BACKUP command with INCREMENTAL LEVEL > 0 was specified.
Action: Use FULL, or INCREMENTAL LEVEL 0.
RMAN-06181: multiple channels require Enterprise Edition
Cause: Attempt to allocate more than 1 channel in a job.
Action: Remove all except one ALLOCATE CHANNEL command.
RMAN-06182: archive log larger than MAXSETSIZE: thread string seq string string
Cause: A BACKUP ARCHIVELOG command specified the MAXSETSIZE operand too low. The specified archive log is larger than MAXSETSIZE will allow.
Action: Increase MAXSETSIZE limit.
RMAN-06183: datafile or datafilecopy larger than MAXSETSIZE: file# string string
Cause: A BACKUP DATAFILE(copy) command specified the MAXSETSIZE operand too low. The specified datafile is larger than MAXSETSIZE will allow.
Action: Increase MAXSETSIZE limit.
RMAN-06184: duplicate object in backup specifier: string string
Cause: A backup command specifies the same datafile or copy of a datafile multiple times.
Action: Eliminate the duplicates.
RMAN-06185: Recovery Manager incompatible with string database: RMAN number.number.number to number.number.number required
Cause: This version of recovery manager is incompatible with the indicated database or the dbms_backup_restore package installed in the indicated database.
Action: If the database has been upgraded from an earlier version, ensure that the catxxxx.sql script has been run successfully. Re-install dbmsbkrs.sql and prvtbkrs.plb if necessary. Otherwise, use a version of RMAN within the range specified in the error message.
RMAN-06186: PL/SQL package string.string version string in string database is too old
Cause: The specified PL/SQL package is a version that is too old to work with this version of the Recovery Manager (RMAN).
Action: If the database indicated is CATALOG, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN.
RMAN-06187: controlfile copy string not found or out of sync with catalog
Cause: The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database.
Action: Re-catalog the file and retry the operation.
RMAN-06188: cannot use command when connected to a mounted target database
Cause: An attempt was made to issue a command that can be used only when there is no connection to the target database or when the target database is not mounted.
Action: Dismount the database or restart RMAN and use the command before connecting to the target database.
RMAN-06189: current DBID number does not match target mounted database (number)
Cause: SET DBID was used to set a DBID that does not match the DBID of the database to which RMAN is connected.
Action: If the current operation is a restore to copy the database, do not mount the database. Otherwise, avoid using the SET DBID command, or restart RMAN.
RMAN-06190: PL/SQL package string.string version string in string database is not current
Cause: RMAN detected an old version of the specified package. RMAN will execute in backwards-compatible mode.
Action: No action is required, but certain features and bug-fixes may not be available when RMAN runs in backwards-compatible mode. If the database is CATALOG, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN. The files that must be run to upgrade the target or auxiliary database are dbmsrman.sql and prvtrman.plb.
RMAN-06191: PL/SQL package string.string version string in string database is too new
Cause: RMAN detected an incompatible version of the specified package.
Action: Use a newer version of recovery manager. Message 6439 indicates the minimum required version of recovery manager.
RMAN-06192: maximum value for MAXPIECESIZE or MAXSETSIZE must be between 1 Kb and 2048 Gb
Cause: Input size for MAXPIECESIZE or MAXSETSIZE was out of range.
Action: Specify a valid size and retry the command.
RMAN-06193: connected to target database (not started)
Cause: informational message
Action: The database must be started before any other RMAN commands are issued.
RMAN-06194: target database instance not started
Cause: A command was issued that requires the target database instance be started.
Action: Issue a STARTUP command to start the instance.
RMAN-06195: auxiliary database not started
Cause: A command was issued that requires the auxiliary database instance be started.
Action: Issue a STARTUP AUXILIARY command.
RMAN-06196: Oracle instance started
Cause: A STARTUP command completed successfully.
Action: None, this is an informational message.
RMAN-06197: Total System Global Area string bytes
Cause: informational message
Action: no action required
RMAN-06198: %-24s string bytes
Cause: informational message
Action: no action required
RMAN-06199: database mounted
Cause: informational message
Action: no action required
RMAN-06200: Changed string objects to AVAILABLE status
Cause: informational message
Action: no action required
RMAN-06201: Deleted string objects
Cause: informational message
Action: no action required
RMAN-06202: Deleted string EXPIRED objects
Cause: informational message
Action: no action required
RMAN-06203: Changed KEEP options for string objects
Cause: informational message
Action: no action required
RMAN-06204: Changed string objects to UNAVAILABLE status
Cause: informational message
Action: no action required
RMAN-06205: Uncataloged string objects
Cause: informational message
Action: no action required
RMAN-06206: Crosschecked string objects
Cause: informational message
Action: no action required
RMAN-06207: WARNING: string objects could not be deleted for string channel(s) due
Cause: informational message
Action: no action required
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
Cause: informational message
Action: no action required
RMAN-06209: List of failed objects
Cause: informational message
Action: no action required
RMAN-06210: List of Mismatched objects
Cause: informational message
Action: no action required
RMAN-06211: ==========================
Cause: informational message
Action: no action required
RMAN-06212: Object Type Filename/Handle
Cause: informational message
Action: no action required
RMAN-06213: --------------- ---------------------------------------------------
Cause: informational message
Action: no action required
RMAN-06214: %-15s string
Cause: informational message
Action: no action required
RMAN-06220: Creating automatic instance
Cause: No connection to the auxiliary instance was provided, but the command requires an auxiliary instance.
Action: no action required unless you want to create a permanent database, in which case you should stop the command and re-run it, providing an auxiliary instance connection.
RMAN-06221: Removing automatic instance
Cause: RMAN is removing the automatic auxiliary instance that was created for this command.
Action: no action required
RMAN-06223: starting up automatic instance string
Cause: informational message
Action: no action required
RMAN-06224: Automatic instance created
Cause: informational message
Action: no action required
RMAN-06225: shuting down automatic instance string
Cause: informational message
Action: no action required
RMAN-06226: Automatic instance removed
Cause: informational message
Action: no action required
RMAN-06230: List of Stored Scripts in Recovery Catalog
Cause: This message is issued in response to a LIST SCRIPT NAMES command. The following fields are shown for each script that is stored in the recovery catalog: Header indicating to what database the script belongs. Script Name: name of the script. Description: comment associated with this script.
Action: no action required
RMAN-06246: List of Database Incarnations
Cause: This message is issued in response to a LIST INCARNATION OF DATABASE command. The following fields are shown for each database that is registered with the recovery catalog: DB Key: This is the unique key which identifies this database in the recovery catalog. Inc Key: This is the unique key which identifies this incarnation of the database in the recovery catalog. DB Name: The name of the database. DB ID: The database ID. This is a number which remains the same for the life of the database, even if the database name is changed. Status: 'YES' if this is the current incarnation of this database, otherwise 'NO'. Reset SCN: SCN of the most recent resetlogs operation. Reset Time: Time of the most recent resetlogs operation.
Action: no action required
RMAN-06250: Report of files that need backup due to unrecoverable operations
Cause: An unlogged change (such as 'create table unrecoverable') has been made to this file, and the most recent backup of the file does not contain those changes.
Action: Take a backup of this file. If this file is lost before a backup is taken, then the unlogged modifications will be lost. The message indicates whether a full backup is required or whether a incremental backup will suffice.
RMAN-06263: %-4s string string
Cause: This message is issued in response to the REPORT NEED BACKUP INCREMENTAL command, for those files which would use more than the specified number of incrementals during recovery.
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.
RMAN-06270: Report of files whose recovery needs more than number days of archived logs
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.
RMAN-06280: Report of obsolete backups and copies
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: Depending on your needs, you might need to take new backups.
RMAN-06290: Report of database schema
Cause: This message is issued in response to the REPORT SCHEMA command. The report shows the physical schema of the database at the indicated time. The following fields are shown for each datafile: File: The file number. K-bytes: The size of the file. Tablespace: The name of the tablespace which contains this file. RB segs: YES if this file is part of a tablespace containing rollback segments, otherwise NO. Name: The file name.
Action: no action required
RMAN-06300: Report of files with less than number redundant backups
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.
RMAN-06306: ====================
Cause: This message is issued in response to a LIST BACKUP DATABASE/TABLESPACE/DATAFILE command when some backups were taken with the PROXY option. If a recovery catalog is in use, then the information comes from the recovery catalog, otherwise it comes from the target database control file. The following fields are shown for each proxy datafile backup. Key: This is the unique key which identifies this proxy backup in the recovery catalog. This value can be used in a CHANGE command to change its status. If the target database control file is being used as the recovery catalog, then this field uniquely identifies this copy in the controlfile. File: The file number that this file was copied from. Status: This is the status of the file. Possible values are: A - Available U - Unavailable D - Deleted X - Expired Status 'U' will not be used if the target database controlfile is being used as the recovery catalog. Completion time: This is the date and time when the backup was created. This column will be printed in the default Oracle date format, unless overridden with a NLS_DATE_FORMAT environment variable. Ckp SCN: This is the checkpoint SCN of the backup. The file contains all changes made at or before this SCN. Ckp time: This is the time that the file was last checkpointed. Handle: This is the media manager handle of the proxy backup.
Action: no action required
RMAN-06378: List of Backup Sets
Cause: This message is issued in response to a LIST BACKUP command.
Action: no action required
RMAN-06400: database opened
Cause: informational message
Action: no action required
RMAN-06401: database is already started
Cause: A STARTUP command without the FORCE option was issued, but the target database is already started.
Action: Use the FORCE option if you want to restart the database.
RMAN-06402: Oracle instance shut down
Cause: informational message
Action: no action required
RMAN-06403: could not obtain a fully authorized session
Cause: The most likely cause of this error is that one of the databases to which RMAN had previously connected is not started or has has been shutdown. Other error messages should identify exactly which database is the problem.
Action: Startup the database causing the problem.
RMAN-06404: database dismounted
Cause: informational message
Action: no action required
RMAN-06405: database closed
Cause: informational message
Action: no action required
RMAN-06406: deleted archive log
Cause: informational message
Action: no action required
RMAN-06407: auxiliary instance datafile string deleted
Cause: informational message
Action: no action required
RMAN-06408: recovery catalog upgraded to version string
Cause: This is an informational message issued by the UPGRADE CATALOG command. It indicates the version of the recovery catalog schema to which the recovery catalog was just upgraded. Note that this version number may not reflect the version number of your rman executable or target database, because the recovery catalog schema is not changed with each Oracle release.
Action: no action required
RMAN-06409: LIKE clause in LIST BACKUP OF ARCHIVELOG is not supported
Cause: LIST BACKUP OF ARCHIVELOG LIKE was used, which is not supported.
Action: Remove LIKE clause from command.
RMAN-06410: cannot use command when channels are allocated
Cause: An attempt was made to issue a command that can be used only when there are no allocated channels.
Action: Do not use the command, or de-allocate channels and use the command when no channels are allocated.
RMAN-06411: backup copies setting out of range (1-4): number
Cause: An attempt was made to set backup copies to an invalid value.
Action: Use a value in the specified range.
RMAN-06412: no proxy copy channel found
Cause: A proxy copy was started, but no allocated channel supports proxy copy. This could be because the media management software used by the target database does not support proxy copy, or because all of the allocated channels are of type DISK, which never support proxy copy.
Action: If this is a backup, then either allocate a non-disk channel, or do not use the PROXY option. If this is a restore, then a channel of the same type which created the proxy backup was allocated, but now does not support proxy copy. If proxy copy is no longer supported by the media management software at the target database, the CROSSCHECK or CHANGE commands should be used so that those backups will not be considered for further restores.
RMAN-06413: channel string does not support proxy copy
Cause: The channel which was specified for this backup or restore does not support proxy copy. This could be because the media management software used by the target database does not support proxy copy, or because the channel is of type DISK, which never supports proxy copy.
Action: If this is a backup, then either allocate a non-disk channel, or do not use the PROXY option. If this is a restore, then a channel of the same type which created the proxy backup was allocated, but now does not support proxy copy. If proxy copy is no longer supported by the media management software at the target database, the CROSSCHECK command should be used so that those backups will not be considered for further restores.
RMAN-06414: target database COMPATIBLE option does not support proxy copy
Cause: PROXY was specified, and the target database uses a media manager that supports proxy copy, but the COMPATIBLE initialization parameter of the target database must be 8.1.0 or greater to create proxy backups. If the database is downgraded to the earlier release that is specified in the COMPATIBLE parameter, then it will no longer be able to restore proxy backups.
Action: Either take a non-proxy backup or change the target database COMPATIBLE parameter.
RMAN-06415: file string cannot be proxy backed up
Cause: The PROXY option was specified, but the media management software used by the target database cannot back up the specified file using proxy copy. If PROXY ONLY was specified, then the backup is terminated. If PROXY was specified, then this file will be placed into a non-proxy backup set.
Action: Remove the ONLY option to place the files into a regular backup set, or contact the media management vendor if you believe that the media management software should support proxy copy of this file.
RMAN-06416: PROXY ONLY was specified and some files could not be proxy copied
Cause: PROXY ONLY was specified, and some of the files to be backed up could not be backed up by the media management software used by the target database. Message 6415 is issued for each file that cannot be proxy copied.
Action: Remove the ONLY option to place the files into a regular backup set, or contact the media management vendor if you believe that the media management software should support proxy copy of these files.
RMAN-06418: proxy incremental backups with level > 0 not supported
Cause: PROXY was specified for a non-level-zero incremental backup. Proxy backups may only be full or level 0 backups.
Action: Remove one of the conflicting options.
RMAN-06419: file string cannot be proxy restored from handle string
Cause: The media management software used by the target database indicated that it cannot restore the specified file from the specified backup handle.
Action: Consult the media management software documentation to find out why this restriction exists or contact the media management vendor.
RMAN-06420: some files could not be proxy restored - aborting restore
Cause: Some of the files to be restored could not be restored by the media management software used by the target database. Message 6419 is issued for each file that cannot be restored.
Action: Contact the media management vendor if you believe that the media management software should support proxy copy of these files. The CROSSCHECK or CHANGE commands can be used to remove these proxy copies from the catalog to prevent the RESTORE command from trying to restore from these proxy backups.
RMAN-06421: sent command to channel: string
Cause: informational message
Action: no action required
RMAN-06422: no channels found for SEND command
Cause: No channels with the specified names or device types were found. If no channel qualifiers were specified, then no channels were allocated.
Action: Specify a different channel type or allocate a channel of the desired type.
RMAN-06423: requested limit of number exceeds vendor limit of number
Cause: A SETLIMIT CHANNEL command was used to set the backup piece size limit, but the media management software used by the target database cannot create backup pieces that large.
Action: Specify a smaller backup piece limit.
RMAN-06424: error while looking up proxy copy
Cause: An error occurred while looking up the specified proxy copy in the recovery catalog or target database controlfile.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the name or key is entered correctly. If the proxy copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.
RMAN-06425: <datafile pathname not available>
Cause: informational message
Action: no action required
RMAN-06426: RECOVERY_CATALOG_OWNER role must be granted to user string
Cause: The CREATE CATALOG or UPGRADE CATALOG command was used, but the userid that was supplied in the CATALOG connect string does not have the RECOVERY_CATALOG_OWNER role granted as a DEFAULT role.
Action: Grant the RECOVERY_CATALOG_OWNER role to the recovery catalog owner.
RMAN-06427: recovery catalog already exists
Cause: The CREATE CATALOG command cannot be used when the recovery catalog already exists.
Action: Use the UPGRADE CATALOG command to upgrade your recovery catalog to the most current release without losing any existing backup data. Use the DROP CATALOG command to remove an existing recovery catalog.
RMAN-06428: recovery catalog is not installed
Cause: A recovery catalog database connection has been made, but the recovery catalog tables and views have not been installed.
Action: If you mis-typed the recovery catalog owner userid, then correct the userid and reconnect to the recovery catalog. If this is the first time that you have signed on to Recovery Manager with this recovery catalog owner userid, then use the CREATE CATALOG command to create the recovery catalog schema.
RMAN-06429: %s database is not compatible with this version of RMAN
Cause: The indicated database is not compatible with this version of the Recovery Manager (RMAN). Other messages have also been issued which detail the cause of the error.
Action: See the other messages. If the database is CATALOG, then you may be able to use the CREATE CATALOG or UPGRADE CATALOG commands to correct the problem. If the database is TARGET or AUXILIARY, then you must either upgrade the target database or use a newer version of the RMAN executable.
RMAN-06430: recovery catalog userid cannot be SYS
Cause: A recovery catalog connection was made to userid SYS. The recovery catalog must be created in a userid other than SYS.
Action: Specify a different userid in the CATALOG connect string.
RMAN-06431: recovery catalog created
Cause: This is an informational message issued by the CREATE CATALOG command.
Action: no action required
RMAN-06432: recovery catalog dropped
Cause: This is an informational message issued by the DROP CATALOG command.
Action: no action required
RMAN-06433: error installing recovery catalog
Cause: An error was received from the recovery catalog database while it was being installed. Another error message shows the error message from the server.
Action: The most common reasons for failure to install the recovery catalog are:

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

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

RMAN-06434: some errors occurred while removing recovery catalog
Cause: Some errors were received from the recovery catalog database while removing the recovery catalog.
Action: Correct the error(s) and retry the command. Note that the Recovery Manager intercepts and ignores common errors, such as 'object not found', which can happen while removing a partially installed recovery catalog. Only serious errors will be displayed while removing the recovery catalog.
RMAN-06435: recovery catalog owner is string
Cause: This is an informational message issued by the UPGRADE CATALOG and DROP CATALOG commands.
Action: no action required
RMAN-06436: enter DROP CATALOG command again to confirm catalog removal
Cause: The DROP CATALOG command deletes the recovery catalog, rendering all database backups unusable, and should be used with care. The command must be entered twice to ensure that this is really what you want to do.
Action: If you really want to remove the recovery catalog, then enter the DROP CATALOG command again.
RMAN-06437: cannot drop catalog - catalog is newer than this RMAN
Cause: The DROP CATALOG command was entered, but the recovery catalog was created by a newer version of the Recovery Manager (RMAN). This version of RMAN may not be able to drop the entire recovery catalog.
Action: Use the version of RMAN which most recently created or upgraded the recovery catalog.
RMAN-06438: error executing package DBMS_RCVMAN in string database
Cause: Recovery Manager requires the DBMS_RCVMAN package in the SYS schema of the indicated database. Normally this package is installed during database creation. To re-create the package, run the files dbmsrman.sql and prvtrmns.plb.
Action: re-create the DBMS_RCVMAN package in the SYS schema.
RMAN-06439: RMAN must be upgraded to version string to work with this package
Cause: This message indicates the minimum version of recovery manager required to use the package which was specified in message 6191.
Action: A newer version of RMAN must be used with this package.
RMAN-06441: cannot upgrade catalog - catalog is already newer than this RMAN
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.
RMAN-06442: enter UPGRADE CATALOG command again to confirm catalog upgrade
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 the Migration Guide for the current Oracle release to determine if upgrading to the current version of the recovery catalog will remove support for older versions of RMAN.
RMAN-06443: error upgrading recovery catalog
Cause: An error was received from the recovery catalog database while upgrading the recovery catalog.
Action: Correct the error and retry the command. Note that the Recovery Manager intercepts and ignores common errors, such as 'column already exists,' which can happen if the recovery catalog has already been partially upgraded. Only serious errors will be displayed while upgrading the recovery catalog.
RMAN-06444: %s created with compilation errors
Cause: During the CREATE CATALOG or UPGRADE CATALOG command, the indicated PL/SQL package specification or body could not be created because of PL/SQL compilation errors.
Action: The PL/SQL packages used by the recovery catalog are located in the RECOVER.BSQ library file, and should never be modified. Make sure that the RECOVER.BSQ file has not been modified or damaged, and then if this error persists, contact Oracle support. Connect to the recovery catalog owner and query the USER_ERRORS view to find out the details of the compilation errors.
RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been used
Cause: The CONNECT CATALOG command was used after the user had already specified the NOCATALOG option.
Action: Re-start rman if you wish to use a recovery catalog.
RMAN-06446: changed proxy copy unavailable
Cause: informational message
Action: no action required
RMAN-06447: changed proxy copy available
Cause: informational message
Action: no action required
RMAN-06448: uncataloged proxy copy
Cause: informational message
Action: no action required
RMAN-06449: deleted proxy copy
Cause: informational message
Action: no action required
RMAN-06450: crosschecked proxy copy: found to be 'string'
Cause: informational message
Action: no action required
RMAN-06451: proxy copy handle=string recid=string stamp=string
Cause: informational message
Action: no action required
RMAN-06452: %s package upgraded to version string
Cause: This is an informational message issued by the UPGRADE CATALOG command. It indicates the version to which the indicated package was just upgraded. Note that this version number may not reflect the version number of your rman executable or target database, because the recovery catalog packages are not changed with each Oracle release.
Action: no action required
RMAN-06453: RECOVERABLE may only be used with datafile objects
Cause: An attempt was made to use LIST ... RECOVERABLE .. with OF CONTROLFILE or OF ARCHIVELOG.
Action: Remove the RECOVERABLE keyword and try again.
RMAN-06454: duplexed backups require Enterprise Edition
Cause: The SET COPIES or CONFIGURE BACKUP COPIES command was used to create more than one copy of each backup piece, but Enterprise Edition is not installed.
Action: Do not attempt to create more than one copy of each backup piece.
RMAN-06455: point-in-time tablespace recovery requires Enterprise Edition
Cause: A point-in-time tablespace recovery was attempted, but Enterprise Edition is not installed.
Action: Do not do point-in-time tablespace recovery.
RMAN-06456: command is obsolete
Cause: informational message
Action: no action required
RMAN-06457: UNTIL scn (string) is ahead of last scn in archived logs (string)
Cause: UNTIL scn cannot be more than the last scn of the last archived log
Action: Check the UNTIL scn.
RMAN-06458: AS COPY option cannot be used with RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST
Cause: The RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST was specified with AS COPY.
Action: Remove the AS COPY option and resubmit the command.
RMAN-06459: BACKUP <VALIDATE|DURATION> is not supported with PROXY
Cause: BACKUP <VALIDATE|DURATION> and PROXY were specified in the same backup command.
Action: Remove the incompatible option.
RMAN-06460: Controlfile copy string cannot be backed up by proxy.
Cause: The PROXY option was specified, but proxy copy of controlfile is not supported. This file will be placed into a non-proxy backup set.
Action: No action required. This is an informational message.
RMAN-06461: Current controlfile cannot be backed up by proxy.
Cause: The PROXY option was specified, but proxy copy of controlfile is not supported. This file will be placed into a non-proxy backup set.
Action: No action required. This is an informational message.
RMAN-06462: no backupsets found on device DISK that match specification
Cause: A backupset record specifier did not match an 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.
RMAN-06463: Backup set key string cannot be backed up by proxy.
Cause: The PROXY option was specified, but proxy copy of backup set is not supported. This file will be placed into a non-proxy backup set.
Action: No action required. This is an informational message.
RMAN-06464: BACKUP BACKUPSET is not supported with VALIDATE option
Cause: BACKUP BACKUPSET and VALIDATE were specified in the same backup command.
Action: To VALIDATE BACKUPSET use 'validate' or 'restore validate' command.
RMAN-06465: configuration not implemented: string
Cause: The configuration is not implemented in the current release.
Action: Avoid using the command.
RMAN-06466: error parsing configuration string (string)
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 dbsm_backup_restore.deleteConfig to remove problematic configuration.
RMAN-06467: could not translate DBA: number
Cause: An error was received when calling dbms_rcvman
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
RMAN-06468: Invalid Data Block Address: number
Cause: The DBA specified doesn't belong to the mentioned tablespace
Action: Check the DBA
RMAN-06469: could not translate corruption list
Cause: An error was received when calling dbms_rcvman
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
RMAN-06470: DEVICE TYPE is supported only when automatic channels are used
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.
RMAN-06471: no configuration found to allocate channels for string
Cause: Device type configuration was not found in recovery catalog
Action: Setup device type configuration using configure command for required device type
RMAN-06472: channel id string is automatically allocated
Cause: Channel id was used on ALLOCATE/RELEASE command.
Action: Use other channel id that does not belong to reserved channel id's namespace
RMAN-06474: maintenance channels are not allocated
Cause: RELEASE CHANNEL was used without allocating any maintenance channels.
Action: Allocate maintenance channel before executing this command.
RMAN-06475: parallelism setting out of range (1-254): number
Cause: Parallelism for the device type in CONFIGURE PARALLELISM command is out of range
Action: Enter value of parallelism that are within the allowed range.
RMAN-06476: channel number out of range (1-254): number
Cause: Channel number entered in CONFIGURE CHANNEL command is out of range.
Action: Enter channel number within allowed range and retry the command. for this device and retry the command
RMAN-06477: configuration value length exceeds 1024
Cause: CONFIGURE CHANNEL command entered has configuration value greater than 1024 bytes.
Action: Reduce the length of CONFIGURE CHANNEL command options
RMAN-06478: WARNING: datafile copy 'string' cannot be found on disk
Cause: The CHANGE DATAFILECOPY AVAILABLE command was used, but the datafilecopy cannot be found on disk.
Action: If the storage containing the datafilecopy has been removed from the host, restore it and retry the command. If the datafilecopy is permanently gone, then issue the CHANGE DATAFILECOPY DELETE command for this datafile.
RMAN-06479: WARNING: control file copy 'string' cannot be found on disk
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 control file.
RMAN-06480: WARNING: archivelog 'string' cannot be found on disk
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, restore it and retry the command. If the archivelog is permanently gone, then issue the CHANGE ARCHIVELOG DELETE command for this archivelog.
RMAN-06481: WARNING: backup piece 'string' cannot be found on the storage medium
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, restore it and retry the command. If the backup piece is permanently gone, then issue the CHANGE BACKUPPIECE DELETE command for this backup piece.
RMAN-06482: WARNING: proxy copy 'string' cannot be found on the storage medium
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, restore it and retry the command. If the proxy copy is permanently gone, then issue the CHANGE PROXY DELETE command for this proxy copy.
RMAN-06483: changed datafile copy expired
Cause: informational message
Action: no action required
RMAN-06484: changed controlfile copy expired
Cause: informational message
Action: no action required
RMAN-06485: changed archivelog expired
Cause: informational message
Action: no action required
RMAN-06486: changed backup piece expired
Cause: informational message
Action: no action required
RMAN-06487: changed proxy copy expired
Cause: informational message
Action: no action required
RMAN-06488: restore from autobackup does not allow any other modifiers
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.
RMAN-06489: no configuration found to allocate clone channel number for device type string
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
RMAN-06490: WARNING: limit of autobackups for the day has been reached
Cause: No more controlfile autobackups are possible in this day.
Action: This is a warning message, no action is required.
RMAN-06491: controlfile autobackup format "string" contains more than one "string" format specifier
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.
RMAN-06492: controlfile autobackup format "string" must specify a "string" format specifier
Cause: A reserved format specifier was not specified for the controlfile autobackup format.
Action: Add a specifier to the controlfile autobackup format.
RMAN-06493: only UNTIL TIME clause is allowed when performing a restore from autobackup, found: string
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.
RMAN-06494: %s = string is out of range (string-string)
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.
RMAN-06495: must explicitly specify DBID with SET DBID command
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.
RMAN-06496: must use the TO clause when the database is mounted or open
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.
RMAN-06497: WARNING: controlfile is not current, controlfile autobackup skipped
Cause: Controlfile autobackup is not possible without a current controlfile.
Action: This is a warning message, no action is required.
RMAN-06498: skipping datafile string; already backed up string time(s)
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
RMAN-06499: skipping archive log file string; already backed up string time(s)
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
RMAN-06500: skipping backupset key string; already backed up string time(s)
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
RMAN-06501: skipping datafile string; already backed up on string
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
RMAN-06502: skipping archive log file string; already backed on string
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
RMAN-06503: skipping backupset key string; already backed up on string
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
RMAN-06504: PROXY option with multiple backup copies is not supported
Cause: Multiple backup copies and PROXY option were specified in BACKUP command.
Action: Resolve the conflict.
RMAN-06506: the MAXSETSIZE option cannot be used with a backup backupset
Cause: The MAXSETSIZE option was specified for a backup backupset command.
Action: Remove the option and resubmit the command.
RMAN-06507: trying alternate file for archivelog thread number, sequence number
Cause: This is an informational message, appearing when an archivelog was found out of sync with catalog database.
Action: no action required
RMAN-06508: MAXSETSIZE string kbytes should be greater than blocksize string bytes
Cause: MAXSETSIZE configured or specified in backup command should be greater than database blocksize.
Action: Specify a larger MAXSETSIZE limit.
RMAN-06509: only SPFILE or controlfile can be restored from autobackup
Cause: A datafile or archived log restore from autobackup was attempted.
Action: Do not specify DATAFILE or ARCHIVELOG for restore from autobackup.
RMAN-06510: RMAN retention policy is set to recovery window of number days
Cause: informational message
Action: no action required
RMAN-06511: RMAN retention policy is set to redundancy number
Cause: informational message
Action: no action required
RMAN-06512: copy will be obsolete on date string
Cause: informational message
Action: no action required
RMAN-06513: copy will never be obsolete
Cause: informational message
Action: no action required
RMAN-06514: archived logs required to recover from this copy will not be kept
Cause: informational message
Action: no action required
RMAN-06515: archived logs required to recover from this copy will expire when this copy expires
Cause: informational message
Action: no action required
RMAN-06516: time specified in KEEP UNTIL clause must be be after today
Cause: KEEP UNTIL support only a future time.
Action: Correct the time and retry the command.
RMAN-06517: KEEP option is not supported for archive log backups
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.
RMAN-06518: backup will be obsolete on date string
Cause: informational message
Action: no action required
RMAN-06519: backup will never be obsolete
Cause: informational message
Action: no action required
RMAN-06520: archived logs required to recover from this backup will not be kept
Cause: informational message
Action: no action required
RMAN-06521: archived logs required to recover from this backup will expire when this backup expires
Cause: informational message
Action: no action required
RMAN-06522: KEEP FOREVER option is not supported without the recovery catalog
Cause: The KEEP FOREVER option was used, but it requires a connection to a recovery catalog database. The KEEP FOREVER option cannot be used when the backup repository is the target database controlfile. This is because information about this backup cannot be permanently stored. (If information is stored just in the controlfile it will be aged out depending on CONTROL_FILE_RECORD_KEEP_TIME initialization parameter.)
Action: If a recovery catalog database is available, then connect to the recovery catalog and retry the command, otherwise use a different KEEP option. 6523, 1, "unused"
RMAN-06524: RMAN retention policy will be applied to the command
Cause: informational message
Action: no action required
RMAN-06525: RMAN retention policy is set to none
Cause: Command DELETE OBSOLETE and REPORT OBSOLETE requires that either:

* RMAN retention policy is not NONE or,

* RMAN retention policy is specified with REPORT/DELETE command.

Action: Either configure RMAN retention policy with CONFIGURE command or specify it at the end of DELETE/REPORT command.
RMAN-06526: KEEP option cannot be used with incremental backup
Cause: The KEEP option was specified for a incremental backup.
Action: Remove the option and resubmit the command.
RMAN-06527: KEEP option is not supported for backup of backup sets
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.
RMAN-06528: CHANGE ... KEEP not supported for BACKUPPIECE
Cause: The CHANGE BACKUPPIECE ... KEEP command was entered. KEEP attributes cannot be specified for backup pieces.
Action: Use CHANGE BACKUPSET ... KEEP instead.
RMAN-06529: CHANGE ... KEEP not supported for ARCHIVELOG
Cause: The CHANGE ARCHIVELOG ... KEEP command was entered. KEEP attributes cannot be specified for archive logs.
Action: Use CHANGE BACKUPSET ... KEEP instead.
RMAN-06530: CHANGE ... KEEP not supported for backup set which contains archive logs
Cause: The CHANGE BACKUPSET ... KEEP command was entered, but the BACKUPSET contains archive logs. Backup sets with archive logs cannot have KEEP attributes.
Action: Do not specify backup set with archive logs for the CHANGE BACKUPSET ... KEEP command.
RMAN-06531: CHANGE ... KEEP not supported for incremental BACKUPSET
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 specificy backup set with archive logs for the CHANGE BACKUPSET ... KEEP command.
RMAN-06532: redundancy count must be greater than zero
Cause: The REDUNDANCY operand specified for the retention policy was zero.
Action: Specify a REDUNDANCY operand of 1 or greater.
RMAN-06533: KEEP ... NOLOGS option is not supported when database is open
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.
RMAN-06534: KEEP ... CONSISTENT option is not supported
Cause: The KEEP ... CONSISTENT option was specified but the option is not supported.
Action: Remove the option and resubmit the command.
RMAN-06535: LIST COPY OF SPFILE is not supported
Cause: LIST COPY OF SPFILE was used, which is not supported because SPFILE cannot have a copy.
Action: Remove SPFILE from the command.
RMAN-06536: BACKED UP ... TIMES option is supported only for archived logs
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.
RMAN-06537: CHANGE ... KEEP not supported for BACKUP
Cause: The CHANGE BACKUP... KEEP command was entered. KEEP attributes cannot be specified for copies and backup pieces in a single command.
Action: Use CHANGE BACKUPSET ... KEEP instead.
RMAN-06540: tablespace string will be excluded from future whole database backups
Cause: informational message
Action: no action required
RMAN-06541: tablespace string will be included in future whole database backups
Cause: informational message
Action: no action required
RMAN-06542: file string is excluded from whole database backup
Cause: The indicated file will not be included in the backup set because it's tablesapce is configured as excluded from backup.
Action: no action required
RMAN-06543: duplicate or conflicting LIST options: string and string
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.
RMAN-06544: Do you really want to delete the above objects (enter YES or NO)?
Cause: This is a user prompt.
Action: Answer the question to proceed.
RMAN-06545: "string" is an invalid response - please re-enter.
Cause: An incorrect response was entered.
Action: Enter a correct response.
RMAN-06546: Error occurred getting response - assuming NO response
Cause: An error occurred reading user response.
Action: None - informational message.
RMAN-06547: tablespace SYSTEM cannot be excluded from whole database backup
Cause: The SYSTEM tablespace must be included in whole database backup.
Action: Remove the SYSTEM tablespace from the CONFIGURE ... EXCLUDE and retry the operation.
RMAN-06548: connected to auxiliary database: string (DBID=string)
Cause: informational message
Action: no action required
RMAN-06549: connected to auxiliary database: string (not mounted)
Cause: informational message
Action: no action required
RMAN-06550: clone database not mounted and db_name not set in init.ora
Cause: The clone database "init.ora" file does not specify the DB_NAME parameter.
Action: Add the DB_NAME parameter to the clone database "init.ora" and restart the instance.
RMAN-06551: error while looking up datafilecopy for file number: string
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, ensure that the RESTORE completed successfully.
RMAN-06552: newname for datafile number was set to NEW, but file was not restored
Cause: A SWITCH command was specified for a datafile, but the newname was set to NEW and the file was not restored. If newname is set to NEW, the file must be restored before issuing a SWITCH command.
Action: Correct and resubmit the SWITCH command.
RMAN-06553: DB_CREATE_FILE_DEST must be set for SET NEWNAME ... TO NEW
Cause: The SET NEWNAME ... TO NEW option was specified but the OMF destinatation init 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.
RMAN-06554: WARNING: file string is in backup mode
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.
RMAN-06555: datafile string must be restored from backup created before string
Cause: An incomplete recovery session was started, but the file is in newer than the UNTIL TIME clause.
Action: Check the UNTIL TIME clause or restore the file from a sufficient old backup.
RMAN-06556: datafile string must be restored from backup older than scn string
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.
RMAN-06557: unable to restore archived log thread number, sequence number
Cause: Restore of the specified archived log failed because the size of the archived log is larger than available disk space.
Action: One of the following: 1) Increase the MAXSIZE parameter and retry the command. 2) Free up disk space in the recovery area.
RMAN-06558: archived log size of number kb is bigger than available space of number kb
Cause: This message should be followed by one or more 6557 messages.
Action: Check the accompanying errors.
RMAN-06559: MAXSIZE must be larger than 1 kb
Cause: The MAXSIZE parameter is out of range.
Action: Specify a valid size and retry the command.
RMAN-06560: WARNING: backup set with key number will be read number times
Cause: This message should be followed by one or more 6562 messages.
Action: Check the accompanying messages.
RMAN-06561: available space must be larger than number kb
Cause: The recovery failed because it requires more disk space. One of the following could have caused this error: 1) The MAXSIZE option is used but is not large enough to restore files. 2) Files should be restored to recovery area, but available disk space is not large enough to restore files.
Action: One of the following: 1) Increase the MAXSIZE parameter and retry the command. 2) Free up disk space in the recovery area.
RMAN-06562: available space of number kb needed to avoid reading the backup set multiple times
Cause: A backup set is read more than once. Multiple reads of a backup set can slow restore performance. One of the following could have caused this: 1) The MAXSIZE option is used but is not large enough to restore files. 2) Files should be restored to a recovery area, but the available disk space is not large enough to restore files.
Action: One of the following: 1) Increase the MAXSIZE parameter and retry the command. 2) Free up disk space in the recovery area.
RMAN-06563: controlfile or SPFILE must be restored using FROM AUTOBACKUP
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, connect to the recovery catalog and retry the restore. If the recovery catalog in not available, following is the procedure to restore controlfile or SPFILE:

1. Specify the DBID of the database with the SET DBID command.

2. If the autobackup was created with non-default autobackup format, then specify the autobackup format using the SET CONTROLFILE AUTOBACKUP FORMAT command.

3. If the backup was created with SBT device, then allocate an SBT channel using the ALLOCATE CHANNEL command.

4. Restore controlfile or SPFILE by starting the RESTORE ... FROM AUTOBACKUP command.

RMAN-06564: must use the TO clause when the instance is started with 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.
RMAN-06565: WARNING: string: sqlcode number was caught, automatic retry #number
Cause: The RMAN client caught a transient error and will automatically retry several times.
Action: No action required, this is an informational message.
RMAN-06566: target database incarnation not found in control file
Cause: resetlogs change# and/or time of the target database doesn't match any database incarnation in the control file.
Action: One of the following actions can be taken to resolve this error -- Restore the controlfile from the incarnation. -- To populate the new incarnation, inspect or restore an archived log/datafile/datafilecopy/backup set from the target incarnation
RMAN-06570: datafile number switched to datafile copy "string"
Cause: This message was issued in response to a SWITCH command.
Action: No action is required; this is an informational message.
RMAN-06571: datafile number does not have recoverable copy
Cause: The SWITCH command with the option TO COPY was specified but the datafile has no valid copy to switch to.
Action: Verify whether the datafile has a valid datafile copy.
RMAN-06572: database is open and datafile number is not offline
Cause: The SWITCH command with the option TO COPY was specified, but datafile is not offline and database is open.
Action: Either make sure the datafile is offline or the database must be mounted but not opened.
RMAN-06575: platform id number found in datafile string header is not a valid platform id
Cause: The platform id found in the datafile header was not recognized.
Action: Verify that this is a valid datafile.
RMAN-06576: platform 'string' (number) found in header of datafile string does not mmatch specified platform name 'string' (number)
Cause: The platform specified in the command did not match the platform found in the datafile header.
Action: Specify the correct platform name and retry the command.
RMAN-06577: FROM TAG option may only be used with datafilecopies
Cause: The FROM TAG option was specified for datafiles.
Action: Remove the option and resubmit the command.
RMAN-06578: INCREMENTAL LEVEL > 0 must be specified with FOR RECOVER OF
Cause: The FOR RECOVER OF option was specified without specifying INCREMENTAL LEVEL > 0.
Action: Specify INCREMENTAL LEVEL > 0 and resubmit the command.
RMAN-06580: the string option cannot be used with AS COPY
Cause: The specified option was specified for a backup as copy command.
Action: Remove the option and resubmit the command.
RMAN-06581: option string not supported
Cause: This option was specified and it is not supported.
Action: Remove the specified option.
RMAN-06582: AS COPY option cannot be used when backing up backupsets
Cause: The backupset was specified with AS COPY.
Action: Remove the AS COPY option or remove the backupsets.
RMAN-06583: at least 1 channel of TYPE DISK must be allocated to use AS COPY option
Cause: No channel of TYPE DISK was allocated.
Action: Allocate a channel of TYPE DISK and re-issue the command or remove AS COPY.
RMAN-06584: WARNING: AS BACKUPSET option added due to allocation of multiple channel types
Cause: DISK and non DISK channels were allocated for a backup command. Configuration indicates to produce image copies to DISK, however due to the mixed channel types BACKUPSETs will be created on DISK.
Action: Do not allocate non DISK channels to produce image copies to DISK or allocate only non DISK channels to produce BACKUPSETs only.
RMAN-06585: no copy of datafile number found
Cause: An available datafilecopy for the specified datafile could not be found.
Action: make sure that all specified datafiles have a copy available.
RMAN-06586: no copy of datafile number with tag string found
Cause: An available datafilecopy for the specified datafile could not be found.
Action: make sure that all specified datafiles have a copy available.
RMAN-06587: one or more datafilecopies were not found
Cause: This error message was accompanied by an additional error message or messages indicating the cause of the error.
Action: Follow the recommended actions of the additional error message or messages.
RMAN-06588: number of patterns (number) to DB_FILE_NAME_CONVERT should be even
Cause: An uneven number of patterns was specified.
Action: Specify one more or one less pattern.
RMAN-06589: cannot specify DB_FILE_NAME_CONVERT option without AS COPY
Cause: The DB_FILE_NAME_CONVERT option was specified without AS COPY. This is not permitted for backupset backups where multiple files are combined into a set.
Action: Remove the DB_FILE_NAME_CONVERT option and re-run the BACKUP command.
RMAN-06590: tablespace string cannot be converted
Cause: The system tablespaces could not be transported to other platforms.
Action: Remove the specified tablespace from the CONVERT command and retry the operation.
RMAN-06591: must specify TO PLATFORM
Cause: There was a missing parameter to the command.
Action: Specify the TO PLATFORM parameter with the command.
RMAN-06592: must specify FROM PLATFORM
Cause: There was a missing parameter to the command.
Action: Specify the FROM PLATFORM parameter with the command.
RMAN-06593: platform name 'string' specified in FROM PLATFORM is not valid
Cause: The platform name was not recognized.
Action: Specify a valid platform name.
RMAN-06594: platform name 'string' specified in TO PLATFORM is not valid
Cause: The platform name was not recognized.
Action: Specify a valid platform name.
RMAN-06595: platform name 'string' does not match database platform name 'string'
Cause: The platform name specified did not match the name of the database performing the conversion.
Action: Specify the correct platform name.
RMAN-06596: to use CONVERT compatibility must be set to 10.0.0 or greater, currently set to string
Cause: A command was attempted that requires a higher database compatibility.
Action: Raise the compatibility of the database before attempting the command again.
RMAN-06597: conversion between platforms 'string' and 'string' is not implemented
Cause: Conversion of Oracle data files between the specified platforms was not supported.
Action: Do not do the conversion.
RMAN-06598: conversion between platforms 'string' and 'string' is not needed
Cause: Conversion of Oracle data files between the specified platforms was not necessary because the Oracle data file format is already the same on both platforms.
Action: Do not do the conversion.
RMAN-06599: tablespace string is not read-only
Cause: A conversion was attempted on a tablespace which is not read-only.
Action: Change the tablespace to read-only and retry the operation.
RMAN-06600: old RMAN configuration parameters:
Cause: This message is issued in response to a CONFIGURE command.
Action: None - informational message.
RMAN-06601: new RMAN configuration parameters:
Cause: This message is issued in response to a CONFIGURE command.
Action: None - informational message.
RMAN-06604: new RMAN configuration parameters are successfully stored
Cause: This message is issued in response to a CONFIGURE command.
Action: None - informational message.
RMAN-06605: old RMAN configuration parameters are successfully deleted
Cause: This message is issued in response to a CONFIGURE command.
Action: None - informational message.
RMAN-06606: RMAN configuration parameters are successfully reset to default value
Cause: This message is issued in response to a CONFIGURE command.
Action: None - informational message.
RMAN-06607: RMAN configuration parameters are:
Cause: This message is issued in response to a SHOW command.
Action: None - informational message.
RMAN-06608: RMAN configuration has no stored or default parameters
Cause: This message is issued in response to a SHOW command.
Action: None - informational message.
RMAN-06609: AS COPY can be configured only for disk device
Cause: The AS COPY option was specified for non disk device.
Action: Remove the AS COPY option and resubmit the command.
RMAN-06700: error parsing text script in file string
Cause: Incorrect syntax or invalid commands were found.
Action: Fix text script and retry the command.
RMAN-06701: could not construct path for file: "string"
Cause: An error was encountered when trying to construct the full pathname for the specified file.
Action: Ensure that the path is correct.
RMAN-06702: could not initialize for input file: "string"
Cause: An error was encountered when trying to initialize the specified file for input.
Action: Ensure that the file exists.
RMAN-06703: could not open file: "string" (reason=string)
Cause: An error was encountered when trying to open the specified file.
Action: Ensure that the file has correct permissions.
RMAN-06705: text script line is too long (>1024)
Cause: A text script contained a line longer than the permitted maximum length.
Action: Split the line in smaller lines an retry the operation.
RMAN-06706: could not close file: "string" (reason=string)
Cause: An error was encountered when trying to close the specified file.
Action: Ensure that the file has correct permissions and still exists.
RMAN-06707: could not initialize for output file: "string"
Cause: An error was encountered when trying to initialize the specified file for output.
Action: Ensure that the file exists.
RMAN-06708: short write while writing file "string". Wrote string bytes instead of string bytes
Cause: An attempt was made to write to a file system that was full.
Action: Ensure that the file system has room for the file. Check system logs.
RMAN-06709: No scripts in recovery catalog
Cause: An attempt was made to list the scripts in the catalog, but no scripts could be found in the specified recovery catalog.
Action: None. This is an informational message.
RMAN-06710: script string not found in catalog
Cause: An attempt was made to call a script that could not be found in the target database or as a global script in the specified catalog.
Action: Verify the script name and retry the command.
RMAN-06711: global scripts require a target connection
Cause: Connection to a target database was not specified.
Action: Provide a target connection and retry the command.
RMAN-06716: skipping datafile number; already restored to file string
Cause: Recovery Manager determined that this file is already restored. Use FORCE option to override this optimization.
Action: informational message
RMAN-06717: number of source files (string) and destination files (string) does not match
Cause: The number of files to retrieve from the catalog does not match the number of destinations specified.
Action: Ensure that the number of files to be retrieved matches the number of destinations specified.
RMAN-06718: could not find file "string" in catalog
Cause: The filename provided was not found in the catalog.
Action: The specified file is not stored in the catalog, or it is stored with a different path than the one provided. Specify the filename as stored in the catalog.
RMAN-06719: file "string" (string bytes) restrieved from catalog
Cause: informational message
Action: no action required
RMAN-06720: file "string" removed from catalog
Cause: informational message
Action: no action required
RMAN-06721: could not normalize path for file: "string"
Cause: An error was encountered when trying to normalize the pathname for the specified file.
Action: Ensure that the path is correct.
RMAN-06722: unable to remove file "string" from catalog
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Follow actions for other messages.
RMAN-06723: file "string" (string bytes) updated in catalog
Cause: informational message
Action: no action required
RMAN-06724: backup not done; all files already backed up
Cause: A BACKUP command does not need to backup any files, because all of the files to backup are already backed up.
Action: None, informational message only
RMAN-06725: database not open: sort area size too small
Cause: sort area size too small to execute RMAN commands.
Action: open the database or increase sort_area_size.
RMAN-06726: could not locate archivelog string
Cause: The specified archivelog could not be found on any allocated channel.
Action: Allocate additional channels on other nodes of the cluster, or, if the archived logs have been deleted, use the CROSSCHECK ARCHIVELOG command to correct the recovery catalog entries.
RMAN-06727: could not locate datafilecopy string
Cause: The specified datafilecopy could not be found on any allocated channel.
Action: Allocate additional channels on other nodes of the cluster, or if the datafilecopy have been deleted, use the CROSSCHECK DATAFILECOPY command to correct the recovery catalog entries.
RMAN-06728: could not locate controlfilecopy string
Cause: The specified controlfilecopy could not be found on any allocated channel.
Action: Allocate additional channels on other nodes of the cluster, or if the controlfilecopy have been deleted, use the CROSSCHECK CONTROLFILECOPY command to correct the recovery catalog entries.
RMAN-06729: no backup of the SPFILE found to restore
Cause: A SPFILE restore could not proceed because no backup of the SPFILE was found. It may be the case that a backup of this file exists but does not satisfy the criteria specified in the user's restore operands.
Action: Modify options for the SPFILE restore.
RMAN-06730: no channel to restore a backup of the SPFILE
Cause: A SPFILE restore could not proceed because the backup on a device type that was not allocated for restore.
Action: None - this is an informational message. See message 6026 for further details.
RMAN-06731: command string:string%% complete, time left number:number:number
Cause: informational message
Action: no action required
RMAN-06732: database dropped
Cause: informational message
Action: no action required
RMAN-06733: database unregistered from the recovery catalog
Cause: informational message
Action: no action required
RMAN-06734: Do you really want to drop all backups and the database (enter YES or NO)?
Cause: This is a user prompt.
Action: Answer the question to proceed.
RMAN-06735: Do you really want to drop the database (enter YES or NO)?
Cause: This is a user prompt.
Action: Answer the question to proceed.
RMAN-06736: Do you really want to unregister the database (enter YES or NO)?
Cause: This is a user prompt.
Action: Answer the question to proceed.
RMAN-06737: database name "string" does not match target database name "string"
Cause: The UNREGISTER DATABASE command was used with a database name that does not match the name of the database to which RMAN is connected.
Action: Specify the correct database name or avoid specifying the database name when connected to the target database.
RMAN-06738: database name "string" is not unique in the recovery catalog
Cause: The UNREGISTER DATABASE command was used with a database name that is ambiguous.
Action: Use the SET DBID command to specify the database id and resolve the ambiguity.
RMAN-06739: database "string" is not found in the recovery catalog
Cause: The UNREGISTER DATABASE command was used with a database name that was not found in the recovery catalog.
Action: Make sure the database name specified in the DROP DATABASE command syntax is correct.
RMAN-06740: database name is not specified
Cause: The UNREGISTER DATABASE command failed because of the following:

o RMAN is not connected to the target database

o The database name is not specified in the command

o DBID is not set with the SET DBID command

Action: Any one of the following actions will fix the problem: o Connect to the target database o Specify database name o Set DBID with SET DBID command
RMAN-06741: database name is "string" and DBID is string
Cause: informational message
Action: no action required
RMAN-06742: platform name 'string' longer than number
Cause: The specified platform name exceeds the maximum allowable platform name.
Action: Correct the platform name.
RMAN-06743: specification does not match any backupset in the repository
Cause: The specified backupsets are not found in the repository.
Action: Verify backupset existence and retry the command.
RMAN-06744: specification does not match any datafilecopy in the repository
Cause: The specified datafilecopies are not found in the repository.
Action: Verify datafilecopy existence and retry the command.
RMAN-06745: skipping datafilecopy string; already backed up string time(s)
Cause: The indicated datafilecopy was not included in the backup set because it was already backed up on the device requested.
Action: Use FORCE option to override backup optimization.
RMAN-06746: backup cancelled because all files were skipped
Cause: All files for this backup set were skipped, therefore no backup no backup set was created.
Action: This message is informational only.
RMAN-06747: at least 1 channel of tertiary storage must be allocated to execute this command
Cause: The executed command requires a SBT channel, but no channels of type SBT were configured or allocated.
Action: ALLOCATE or CONFIGURE a SBT channel.
RMAN-06748: no or more than one tertiary storage channel found
Cause: RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST option was specified in BACKUP command, but no or more than one tertiary channel was found. One of the following could have caused this error: 1) All of the allocated channels are of type DISK. 2) No tertiary storage (SBT) channel configured. 3) CHANNEL or DEVICE TYPE option specified is of DISK type. 4) More than one tertiary storage channel allocated or configured and no DEVICE TYPE or CHANNEL option specified.
Action: One of the following: 1) Allocate a channel of TYPE SBT. 2) Configure a SBT channel. 3) Specify CHANNEL, DEVICE TYPE option of TYPE SBT.
RMAN-06750: SPFILE cannot be backed up by proxy.
Cause: The PROXY option was specified, but proxy copy of SPFILE is not supported. This file will be placed into a non-proxy backup set.
Action: No action required. This is an informational message.
RMAN-06751: ASM file string cannot be proxy backed up.
Cause: The PROXY option was specified, but proxy copy of ASM file is not supported. This file will be placed into a non-proxy backup set.
Action: No action required. This is an informational message.
RMAN-06899: updating recovery catalog with new database incarnation
Cause: The target database has a new incarnation that has not already been seen by the recovery catalog. This usually happens because a point-in-time recovery was done. RMAN has made the necessary updates to the recovery catalog.
Action: informational message
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
Cause: The routine createRmanStatusRow() or createRmanOutputRow() could add new row into V$RMAN_STATUS or V$RMAN_OUTPUT.
Action: Check the associated error messages. If the associated error message indicates a condition that can be corrected, do so, otherwise contact Oracle.
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
Cause: Informational message only.
Action: No action required.
RMAN-06902: AS COMPRESSED BACKUPSET option cannot be used when backing up backupsets
Cause: The backupset was specified with AS COMPRESSED BACKUPSET.
Action: Remove the AS COMPRESSED BACKUPSET option.
RMAN-06903: backup of datafile string was cancelled
Cause: This is informational message displayed when PARTIAL option of DURATION option was specified on the backup command and backup could not be completed with in the given duration time.
Action: Run backup command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in current job will be given preference to other files for next the backup command with DURATION option.
RMAN-06904: backup of log thread number seq number lowscn string was cancelled
Cause: This is informational message displayed when PARTIAL option of DURATION option was specified on the backup command and backup could not be completed with in the given duration time.
Action: Run backup command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in current job will be given preference to other files for next the backup command with DURATION option.
RMAN-06905: backup of backupset key number was cancelled
Cause: This is informational message displayed when PARTIAL option of DURATION option was specified on the backup command and backup could not be completed with in the given duration time.
Action: Run backup command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in current job will be given preference to other files for next the backup command with DURATION option.
RMAN-06906: backup of controlfile was cancelled
Cause: This is informational message displayed when PARTIAL option of DURATION option was specified on the backup command and backup could not be completed with in the given duration time.
Action: Run backup command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in current job will be given preference to other files for next the backup command with DURATION option.
RMAN-06907: MINIMIZE LOAD option not allowed for the specified input files
Cause: This option was specified in a backup command specification for BACKUP BACKUPSET or BACKUP CURRENT CONTROLFILE command.
Action: Remove the MINIMIZE LOAD option and retry the command.
RMAN-06908: WARNING: operation will not run in parallel on the allocated channels
Cause: RMAN allocated more than one channel for a job, but the job will not run in parallel on these channels because parallelism require Enterprise Edition.
Action: None
RMAN-06909: WARNING: parallelism require Enterprise Edition
Cause: RMAN allocated more than one channel for a job, but the job will not run in parallel on these channels because parallelism require Enterprise Edition.
Action: None
RMAN-06910: can not invoke parallel recovery for test recovery
Cause: Recover database was called with TEST and PARALLEL option
Action: Call recover database with either just the TEST or PARALLEL option
RMAN-06911: only one PARALLEL or NOPARALLEL clause may be specified
Cause: Recover database was called with PARALLEL and NOPARALLEL option
Action: Call recover database with either just the PARALLEL or NOPARALLEL option.
RMAN-07000: List of SPFILE Backups
Cause: This message is issued in response to a LIST BACKUP OF SPFILE command.
Action: no action required
RMAN-07500: searching for all files that match the pattern string
Cause: informational message
Action: no action required
RMAN-07501: searching for all files in the recovery area
Cause: informational message
Action: no action required
RMAN-07502: List of Files Unknown to the Database
Cause: This message is issued in response to a CATALOG command.
Action: no action required
RMAN-07506: Do you really want to catalog the above files (enter YES or NO)?
Cause: This is a user prompt.
Action: Answer the question to proceed.
RMAN-07507: cataloging files...
Cause: informational message
Action: no action required
RMAN-07508: cataloging done
Cause: informational message
Action: no action required
RMAN-07509: List of Cataloged Files
Cause: This message is issued in response to a CATALOG command.
Action: no action required
RMAN-07513: List of Files Which Where Not Cataloged
Cause: This message is issued in response to a CATALOG command.
Action: no action required
RMAN-07517: Reason: The file header is corrupted
Cause: Either the file is not an Oracle file or the file header is corrupted.
Action: Delete the file using OS utility.
RMAN-07521: cannot create recovery catalog in database version string; version string required
Cause: An attempt was made to use a version of the recovery catalog schema that was incompatible with the version of the database.
Action: Upgrade the catalog database to at least the required version or install the catalog schema in a different database which is of at least the required version.
RMAN-07522: CREATE TYPE privilege must be granted to user string
Cause: The CREATE CATALOG or UPGRADE CATALOG command was used, but the userid that was supplied in the CATALOG connect string does not have the CREATE TYPE privilege granted.
Action: Grant CREATE TYPE privilege to the recovery catalog owner.
RMAN-08000: channel string: copied datafile string
Cause: informational message
Action: no action required
RMAN-08001: restore not complete
Cause: All of the backup pieces have been successfully applied, but x$dbms_backup_restore indicates that the restore conversation is not complete. This usually means that the backup set contained corrupt data.
Action: Restore the files from a different backup set, if possible. The Recovery Manager CHANGE BACKUPPIECE UNAVAILABLE can be used to prevent Recovery Manager from attempting to restore from the corrupt backup piece(s).
RMAN-08002: starting full resync of recovery catalog
Cause: informational message
Action: no action required
RMAN-08004: full resync complete
Cause: informational message
Action: no action required
RMAN-08005: new incarnation of database registered in recovery catalog
Cause: informational message
Action: no action required
RMAN-08006: database registered in recovery catalog
Cause: informational message
Action: no action required
RMAN-08007: channel string: copied datafilecopy of datafile string
Cause: informational message
Action: no action required
RMAN-08008: channel string: starting full datafile backupset
Cause: informational message
Action: no action required
RMAN-08009: channel string: starting archive log backupset
Cause: informational message
Action: no action required
RMAN-08010: channel string: specifying datafile(s) in backupset
Cause: informational message
Action: no action required
RMAN-08011: including current controlfile in backupset
Cause: informational message
Action: no action required
RMAN-08012: including controlfile copy in backup set
Cause: informational message
Action: no action required
RMAN-08014: channel string: specifying archive log(s) in backup set
Cause: informational message
Action: no action required
RMAN-08015: datafile string switched to datafile copy
Cause: informational message
Action: no action required
RMAN-08016: channel string: starting datafile backupset restore
Cause: informational message
Action: no action required
RMAN-08017: channel string: starting archive log restore to default destination
Cause: informational message
Action: no action required
RMAN-08018: channel string: starting archive log restore to user-specified destination
Cause: informational message
Action: no action required
RMAN-08019: channel string: restoring datafile string
Cause: informational message
Action: no action required
RMAN-08020: including standby controlfile in backupset
Cause: informational message
Action: no action required
RMAN-08021: channel string: restoring controlfile
Cause: informational message
Action: no action required
RMAN-08022: channel string: restoring archive log
Cause: informational message
Action: no action required
RMAN-08023: channel string: restored backup piece string
Cause: informational message
Action: no action required
RMAN-08024: channel string: restore complete
Cause: informational message
Action: no action required
RMAN-08025: channel string: copied controlfile copy
Cause: informational message
Action: no action required
RMAN-08026: channel string: copied archive log
Cause: informational message
Action: no action required
RMAN-08027: channel string: copied current controlfile
Cause: informational message
Action: no action required
RMAN-08028: channel string: copy current controlfile failed
Cause: informational message
Action: no action required
RMAN-08029: snapshot controlfile name set to default value: string
Cause: informational message
Action: no action required
RMAN-08030: allocated channel: string
Cause: informational message
Action: no action required
RMAN-08031: released channel: string
Cause: informational message
Action: no action required
RMAN-08032: channel string: recid string stamp string does not match recovery catalog
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.
RMAN-08033: channel string: including datafilecopy of datafile string in backupset
Cause: informational message
Action: no action required
RMAN-08034: full resync skipped, target database not mounted
Cause: informational message
Action: no action required
RMAN-08035: partial resync skipped, target database not mounted
Cause: informational message
Action: no action required
RMAN-08036: channel string: could not create controlfile record for string string
Cause: The record identifying the named file was no longer present in the target database controlfile, and repeated attempts to inspect the file were unsuccessful in creating the record. This could be because the circular-reuse section of the controlfile 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 controlfile 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.
RMAN-08037: channel string: unexpected validation return code string
Cause: This is an internal error that should never be issued.
Action: Contact Oracle Support.
RMAN-08038: channel string: starting piece string at string
Cause: informational message
Action: no action required
RMAN-08039: channel string: starting incremental datafile backupset restore
Cause: informational message
Action: no action required
RMAN-08040: full resync skipped, controlfile is not current or backup
Cause: informational message
Action: no action required
RMAN-08041: partial resync skipped, controlfile is not current or backup
Cause: informational message
Action: no action required
RMAN-08042: channel string: copied standby controlfile
Cause: informational message
Action: no action required
RMAN-08043: channel string: copy standby controlfile failed
Cause: informational message
Action: no action required
RMAN-08044: channel string: finished piece string at string
Cause: informational message
Action: no action required
RMAN-08045: channel string: finished piece string at string with string copies
Cause: informational message
Action: no action required
RMAN-08046: channel string: starting compressed full datafile backupset
Cause: informational message
Action: no action required
RMAN-08047: channel string: starting compressed incremental level string datafile backupset
Cause: informational message
Action: no action required
RMAN-08048: channel string: starting incremental level string datafile backupset
Cause: informational message
Action: no action required
RMAN-08049: channel string: starting compressed archive log backupset
Cause: informational message
Action: no action required
RMAN-08050: cataloged datafile copy
Cause: informational message
Action: no action required
RMAN-08051: cataloged archive log
Cause: informational message
Action: no action required
RMAN-08052: cataloged controlfile copy
Cause: informational message
Action: no action required
RMAN-08054: starting media recovery
Cause: informational message
Action: no action required
RMAN-08055: media recovery complete
Cause: informational message
Action: no action required
RMAN-08056: skipping datafile string because it has not changed
Cause: The specified datafile has not had its checkpoint advanced since the previous backup, therefore it does not need a new incremental backup.
Action: informational message
RMAN-08057: channel string: backup cancelled because all files were skipped
Cause: All datafiles for this incremental backup set were skipped, therefore no backup set is created.
Action: informational message
RMAN-08058: replicating controlfile
Cause: informational message
Action: no action required
RMAN-08059: media recovery failed
Cause: informational message
Action: no action required
RMAN-08060: unable to find archive log
Cause: informational message
Action: no action required
RMAN-08066: database reset to incarnation string
Cause: informational message
Action: no action required
RMAN-08070: deleted datafile copy
Cause: informational message
Action: no action required
RMAN-08071: channel string: deleting archive log(s)
Cause: informational message
Action: no action required
RMAN-08072: deleted controlfile copy
Cause: informational message
Action: no action required
RMAN-08073: deleted backup piece
Cause: informational message
Action: no action required
RMAN-08074: crosschecked backup piece: found to be 'string'
Cause: informational message
Action: no action required
RMAN-08085: created script string
Cause: informational message
Action: no action required
RMAN-08086: replaced script string
Cause: informational message
Action: no action required
RMAN-08087: channel string: started backup set validation
Cause: informational message
Action: no action required
RMAN-08088: applied offline range to datafile string
Cause: informational message
Action: no action required
RMAN-08089: channel string: specifying datafile(s) to restore from backup set
Cause: informational message
Action: no action required
RMAN-08090: channel string: starting proxy restore
Cause: informational message
Action: no action required
RMAN-08091: channel string: specifying datafile(s) for proxy backup
Cause: informational message
Action: no action required
RMAN-08092: channel string: specifying datafilecopy of datafile string for proxy backup
Cause: informational message
Action: no action required
RMAN-08093: specifying current controlfile for proxy backup
Cause: informational message
Action: no action required
RMAN-08094: channel string: specifying datafile(s) for proxy restore
Cause: informational message
Action: no action required
RMAN-08096: channel string: starting validation of datafile backupset
Cause: informational message
Action: no action required
RMAN-08097: channel string: starting validation of archive log backupset
Cause: informational message
Action: no action required
RMAN-08098: channel string: validation complete
Cause: informational message
Action: no action required
RMAN-08099: specifying standby controlfile for proxy backup
Cause: informational message
Action: no action required
RMAN-08100: channel string: starting proxy validation
Cause: informational message
Action: no action required
RMAN-08101: channel string: proxy validation complete
Cause: informational message
Action: no action required
RMAN-08102: channel string: located backup piece: string
Cause: informational message
Action: no action required
RMAN-08103: channel string: could not locate backup piece: string
Cause: informational message
Action: no action required
RMAN-08104: input backupset count=string stamp=string creation_time=string
Cause: informational message
Action: no action required
RMAN-08105: channel string: backup cancelled because no pieces were found
Cause: All backupsets specified has no pieces. Therefore, no backup set is created.
Action: informational message
RMAN-08106: channel string: restoring block(s)
Cause: informational message
Action: no action required
RMAN-08107: channel string: block restore complete
Cause: informational message
Action: no action required
RMAN-08108: channel string: specifying block(s) to restore from backup set
Cause: informational message
Action: no action required
RMAN-08109: channel string: restored block(s) from backup piece string
Cause: informational message
Action: no action required
RMAN-08110: failover to next copy of backuppiece
Cause: informational message
Action: no action required
RMAN-08111: some blocks not recovered: See trace file for details
Cause: Some blocks not recovered due to errors.
Action: See trace file for details of the problem.
RMAN-08112: archivelog failover was done on string, check alert log for more info
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, nothing needs to be done. Otherwise delete the archivelog that has corrupted block(s) as recovery on applying this log would fail. alert log contains name of the log that has corrupted block(s).
RMAN-08113: including current SPFILE in backupset
Cause: informational message
Action: no action required
RMAN-08114: channel string: restoring SPFILE to PFILE
Cause: informational message
Action: no action required
RMAN-08115: channel string: restoring SPFILE
Cause: informational message
Action: no action required
RMAN-08116: output filename is original SPFILE location
Cause: informational message
Action: no action required
RMAN-08117: channel string: the autobackup does not contain an SPFILE
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.
RMAN-08118: WARNING: could not delete the following archived redo log
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.
RMAN-08119: skipping backup piece handle string; already exists
Cause: A BACKUP command does not need to backup controlfile autobackup pieces, because they already exists.
Action: This is an informational message, no action required.
RMAN-08120: WARNING: archive log not deleted, not yet applied by standby
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.
RMAN-08121: keep attributes for the backup are deleted
Cause: informational message
Action: no action required
RMAN-08122: keep attributes for the backup are changed
Cause: informational message
Action: no action required
RMAN-08123: keep attributes for the datafile/controlfile copy are deleted
Cause: informational message
Action: no action required
RMAN-08124: keep attributes for the datafile/controlfile copy are changed
Cause: informational message
Action: no action required
RMAN-08125: keep attributes for the proxy copy are deleted
Cause: informational message
Action: no action required
RMAN-08126: keep attributes for the proxy copy are changed
Cause: informational message
Action: no action required
RMAN-08127: cataloged backuppiece
Cause: informational message
Action: no action required
RMAN-08128: uncataloged backuppiece
Cause: informational message
Action: no action required
RMAN-08129: failover to piece handle=string tag=string
Cause: This is an informational message to indicate the server found a corrupted block in a piece and had to switch to another copy of piece to get corresponding un-corrupted block.
Action: See alert log for information on corruption block(s) and the name of the piece that has the corrupted block(s).
RMAN-08130: failover to copy on device type string
Cause: This is an informational message to indicate the RMAN could not successfully restore the database using the specified backups. An attempt was made to restore the datafiles/archivelogs/ controlfile/SPFILE using the same backupset on a different device type.
Action: See accompanying additional error messages indicating the cause of the failover.
RMAN-08131: channel string: specifying datafile copies to recover
Cause: informational message
Action: no action required
RMAN-08132: WARNING: cannot refresh aged file list
Cause: Cannot update deletable recovery area file list.
Action: Check the accompanying error.
RMAN-08133: channel string: the autobackup does not contain a standby controlfile.
Cause: The requested autobackup did not contain a standby controlfile.
Action: No action is required, RMAN will try three older autobackups before signaling ORA-19687.
RMAN-08135: some corrupt blocks found during conversion of file string
Cause: While converting the specified file from one platform to another, some corrupt blocks were discovered in the specified file. Details about the corruption have been written to a server trace file.
Action: If these corrupt blocks are unexpected, you may be able to use Block Media Recovery at the source database to fix the problem, then re-convert the files.
RMAN-08136: channel string: deleting incremental backup(s)
Cause: This is an informational message.
Action: No Action Required.
RMAN-08150: created global script string
Cause: informational message
Action: no action required
RMAN-08151: replaced global script string
Cause: informational message
Action: no action required
RMAN-08152: global script string written to file string
Cause: informational message
Action: no action required
RMAN-08153: deleted global script: string
Cause: informational message
Action: no action required
RMAN-08154: deleted script: string
Cause: informational message
Action: no action required
RMAN-08155: printing stored global script: string
Cause: informational message.
Action: no action required
RMAN-08156: printing stored script: string
Cause: informational message.
Action: no action required
RMAN-08157: script string written to file string
Cause: informational message
Action: no action required
RMAN-08158: executing script: string
Cause: informational message
Action: no action required
RMAN-08159: executing global script: string
Cause: informational message
Action: no action required
RMAN-08160: script commands will be loaded from file string
Cause: informational message
Action: no action required
RMAN-08161: contents of Memory Script:
Cause: informational message
Action: no action required
RMAN-08162: executing Memory Script
Cause: informational message
Action: no action required
RMAN-08180: channel string: restore complete, elapsed time: string
Cause: informational message
Action: no action required
RMAN-08181: media recovery complete, elapsed time: string
Cause: informational message
Action: no action required
RMAN-08182: channel string: validation complete, elapsed time: string
Cause: informational message
Action: no action required
RMAN-08183: channel string: block restore complete, elapsed time: string
Cause: informational message
Action: no action required
RMAN-08500: channel string: sid=string devtype=string
Cause: informational message
Action: no action required
RMAN-08501: output filename=string recid=string stamp=string
Cause: informational message
Action: no action required
RMAN-08503: piece handle=string comment=string
Cause: informational message
Action: no action required
RMAN-08504: input archive log thread=string sequence=string recid=string stamp=string
Cause: informational message
Action: no action required
RMAN-08505: output filename=string
Cause: informational message
Action: no action required
RMAN-08506: input filename=string
Cause: informational message
Action: no action required
RMAN-08507: input datafilecopy recid=string stamp=string filename=string
Cause: informational message
Action: no action required
RMAN-08508: archive log destination=string
Cause: informational message
Action: no action required
RMAN-08509: destination for restore of datafile string: string
Cause: informational message
Action: no action required
RMAN-08510: archive log thread=string sequence=string
Cause: informational message
Action: no action required
RMAN-08511: piece handle=string tag=string
Cause: informational message
Action: no action required
RMAN-08512: waiting for snapshot controlfile enqueue
Cause: informational message
Action: no action required
RMAN-08513: datafile copy filename=string recid=string stamp=string
Cause: informational message
Action: no action required
RMAN-08514: archive log filename=string recid=string stamp=string
Cause: informational message
Action: no action required
RMAN-08515: archive log filename=string thread=string sequence=string
Cause: informational message
Action: no action required
RMAN-08516: controlfile copy filename=string recid=string stamp=string
Cause: informational message
Action: no action required
RMAN-08517: backup piece handle=string recid=string stamp=string
Cause: informational message
Action: no action required
RMAN-08518: channel string: scanning controlfile copy string
Cause: informational message
Action: no action required
RMAN-08519: channel string: scanning datafilecopy string
Cause: informational message
Action: no action required
RMAN-08520: channel string: scanning archive log string
Cause: informational message
Action: no action required
RMAN-08521: offline range recid=string stamp=string
Cause: informational message
Action: no action required
RMAN-08522: input datafile fno=string name=string
Cause: informational message
Action: no action required
RMAN-08523: restoring datafile string to string
Cause: informational message
Action: no action required
RMAN-08524: input controlfilecopy name=string
Cause: informational message
Action: no action required
RMAN-08526: channel string: string
Cause: informational message
Action: no action required
RMAN-08527: channel string: starting string proxy datafile backup at string
Cause: informational message
Action: no action required
RMAN-08528: channel string: proxy copy complete, elapsed time: string
Cause: informational message
Action: no action required
RMAN-08529: proxy file handle=string
Cause: informational message
Action: no action required
RMAN-08531: channel string: proxy copy string is string in media management catalog
Cause: informational message
Action: no action required
RMAN-08532: channel string: restoring block(s) from datafilecopy string
Cause: informational message
Action: no action required
RMAN-08533: restoring blocks of datafile string
Cause: informational message
Action: no action required
RMAN-08534: channel string: controlfile restore from autobackup complete
Cause: informational message
Action: no action required
RMAN-08535: channel string: looking for autobackup on day: string
Cause: informational message
Action: no action required
RMAN-08536: channel string: autobackup found: string
Cause: informational message
Action: no action required
RMAN-08537: channel string: skipped, autobackup already found
Cause: informational message
Action: no action required
RMAN-08538: channel string: no autobackup in string days found
Cause: informational message
Action: no action required
RMAN-08539: backup set key=string recid=string stamp=string
Cause: informational message
Action: no action required
RMAN-08540: channel string: backup set complete, elapsed time: string
Cause: informational message
Action: no action required
RMAN-08541: channel string: SPFILE restore from autobackup complete
Cause: informational message
Action: no action required
RMAN-08542: channel string: starting proxy archivelog backup at string
Cause: informational message
Action: no action required
RMAN-08543: channel string: specifying archivelog(s) for proxy backup
Cause: informational message
Action: no action required
RMAN-08544: channel string: specifying archivelog(s) for proxy restore
Cause: informational message
Action: no action required
RMAN-08545: flashback command failed: See trace file for details
Cause: An attempt was made to issue a flashback command which failed due to errors. See trace file for details.
Action: See trace file for details of the problem.
RMAN-08546: channel string: autobackup found in the recovery area
Cause: informational message
Action: no action required
RMAN-08547: channel string: no autobackups found in the recovery area
Cause: The recovery area does not have desired autobackup.
Action: Check the option UNTIL TIME in case an existing autobackup does satisfy the criteria specified in the restore command. Otherwise, verify the init.ora parameters DB_RECOVERY_FILE_DEST and LOCK_NAME_SPACE to verify whether the recovery area location is set correctly. Note that the parameters can be specified as options to the restore command.
RMAN-08548: recovery area destination: string
Cause: informational message
Action: no action required
RMAN-08549: database name (or lock name space) used for search: string
Cause: informational message
Action: no action required
RMAN-08550: autobackup search outside recovery area not attempted because DBID was not set
Cause: Restore of a controlfile autobackup was attempted without DBID being set.
Action: If you want to search for autobackup outside recovery area, then specify the DBID of the database using SET DBID.
RMAN-08551: recovering datafilecopy fno=string name=string
Cause: informational message
Action: no action required
RMAN-08580: channel string: starting datafile copy
Cause: informational message
Action: no action required
RMAN-08581: channel string: datafile copy complete, elapsed time: string
Cause: informational message
Action: no action required
RMAN-08582: channel string: starting archive copy
Cause: informational message
Action: no action required
RMAN-08583: channel string: archivelog copy complete, elapsed time: string
Cause: informational message
Action: no action required
RMAN-08584: copying current controlfile
Cause: informational message
Action: no action required
RMAN-08585: copying standby controlfile
Cause: informational message
Action: no action required
RMAN-08586: output filename=string tag=string recid=string stamp=string
Cause: informational message
Action: no action required
RMAN-08587: input is copy of datafile string: string
Cause: informational message
Action: no action required
RMAN-08588: converted datafile=string
Cause: informational message
Action: no action required
RMAN-08589: channel string: starting datafile conversion
Cause: informational message
Action: no action required
RMAN-08590: channel string: datafile conversion complete, elapsed time: string
Cause: informational message
Action: no action required
RMAN-08591: WARNING: invalid archivelog deletion policy
Cause: An invalid ARCHIVELOG DELETION POLICY was supplied. The archivelog deletion policy was APPLIED but there was no mandatory archivelog destinations.
Action: One of the following: 1) Change archivelog deletion policy using CONFIGURE command 2) Make one or more of standby destination as MANDATORY.
RMAN-08599: channel string: throttle time: string
Cause: informational message
Action: no action required
RMAN-10000: error parsing target database connect string "string"
Cause: An invalid target connect string was supplied.
Action: Specify a valid connect string and re-run the job.
RMAN-10001: error parsing recovery catalog connect string "string"
Cause: An invalid recovery catalog connect string was supplied.
Action: Specify a valid connect string and re-run the job.
RMAN-10002: ORACLE error: string
Cause: The specified Oracle error was received. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-10003: unable to connect to target database
Cause: Recovery manager was unable to connect to the target database. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Ensure that that the target database is started, and that the connect string is valid.
RMAN-10004: unable to connect to recovery catalog
Cause: Recovery manager was unable to connect to the recovery catalog
Action: Ensure that that the recovery catalog is started, and that the connect string is valid. This message should be accompanied by other error message(s) indicating the cause of the error.
RMAN-10005: error opening cursor
Cause: An error was received while trying to open a cursor. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: If the associated Oracle error message indicates a condition that can be corrected, do so, otherwise contact Oracle.
RMAN-10006: error running SQL statement: string
Cause: An error message was received while running the SQL statement shown.
Action: If the associated Oracle error message indicates a condition that can be corrected, do so, otherwise contact Oracle.
RMAN-10007: error closing cursor
Cause: An error was received while trying to close a cursor. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: If the associated Oracle error message indicates a condition that can be corrected, do so, otherwise contact Oracle.
RMAN-10008: could not create channel context
Cause: An error was received while trying create a channel context. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: If the associated Oracle error message indicates a condition that can be corrected, do so, otherwise contact Oracle.
RMAN-10009: error logging off of Oracle
Cause: An error was received while disconnecting from Oracle. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: informational message
RMAN-10010: error while checking for RPC completion
Cause: Recovery Manager's channel context had an error while checking to see if a remote procedure call had completed. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: If other error messages indicate a condition that can be corrected, do so, otherwise contact Oracle.
RMAN-10011: synchronization error while polling for rpc number, action=string
Cause: Recovery Manager could not synchronize properly with a remote procedure call.
Action: This is an internal error that should not be issued. Contact Oracle Support.
RMAN-10012: KGU error: string
Cause: An error occurred while initializing the KGU subsystem
Action: This is an internal error that should not be issued. Contact Oracle Support.
RMAN-10013: error initializing PL/SQL
Cause: An error occurred while initializing the PL/SQL subsystem.
Action: This is an internal error that should not be issued. Contact Oracle Support.
RMAN-10014: PL/SQL error number on line number column number: string
Cause: PL/SQL error
Action: The text of this message will be issued by the PL/SQL subsystem. See the PL/SQL error message manual.
RMAN-10015: error compiling PL/SQL program
Cause: An error occurred while compiling a PL/SQL program.
Action: This is an internal error that should not be issued. Contact Oracle Support.
RMAN-10018: error cleaning up channel context
Cause: An error was received during inter-step cleanup of a channel context.
Action: This is an internal error that should not be issued. Contact Oracle Support.
RMAN-10020: error initializing Recovery Manager execution layer
Cause: An error was received while initializing the Recovery Manager execution layer in preparation for running a job. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: If other error messages indicate a condition that can be corrected, do so, otherwise contact Oracle.
RMAN-10022: error in system-dependant sleep routine
Cause: An error was received while waiting for a remote RPC to complete. The error occurred in the system-dependant sleep routine.
Action: This is an internal error that should not be issued. Contact Oracle Support.
RMAN-10023: RPC attempted to unrecognized package
Cause: The Recovery Manager internal RPC router received a package name that it could not understand.
Action: This is an internal error that should not be issued. Contact Oracle Support.
RMAN-10024: error setting up for rpc polling
Cause: The Recovery Manager could not create the RPC polling context which is required to test for RPC completion. This message should be accompanied by other error message(s) indicating the cause of the error.
Action: If other error messages indicate a condition that can be corrected, do so, otherwise contact Oracle.
RMAN-10025: connection is already registered for events
Cause: The Recovery Manager could not enable the target database connection to test for RPC completion.
Action: This is an internal error that should not be issued. Contact Oracle Support.
RMAN-10026: network error number-number occurred registering connection
Cause: An network error occurred while attempting to register the target database connection to test for RPC completion.
Action: This is an internal error that should not be issued. The message numbers are issued by the Sql*Net layer. Contact Oracle Support.
RMAN-10027: could not locate network layer context
Cause: Recovery Manager could not locate a necessary context area while attempting to register the target database connection to test for RPC completion.
Action: This is an internal error that should not be issued. Contact Oracle Support.
RMAN-10028: network error number-number occurred during remote RPC
Cause: An network error occurred while waiting for a remote RPC to complete.
Action: This is an internal error that should not be issued. The message numbers are issued by the Sql*Net layer. Contact Oracle Support.
RMAN-10029: unexpected return code number from PL/SQL execution
Cause: PL/SQL returned an unexpected return code while executing one channel program.
Action: This is an internal error that should not be issued. Contact Oracle Support.
RMAN-10030: RPC call appears to have failed to start on channel string
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.
RMAN-10031: RPC Error: ORA-number occurred during call to string.string
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.
RMAN-10032: unhandled exception during execution of job step number: string
Cause: An unhandled PL/SQL execption occurred during a job step.
Action: This error is accompanied by the error messages describing the exception.
RMAN-10033: error during compilation of job step number: string
Cause: PL/SQL detected a problem during the compilation of a job step
Action: This error message is accompanied by the error messages describing
RMAN-10034: unhandled exception during execution of job step number, error unknown
Cause: PL/SQL detected an unhandled exception during execution of a job step, but no further information available
Action: none
RMAN-10035: exception raised in RPC: string
Cause: A call to a remote package resulted in an exception.
Action: The exception should indicate what went wrong.
RMAN-10036: RPC call ok on channel string
Cause: This is just an informational message. It should be preceeded by message 10030.
Action: no action required
RMAN-10037: RPC anomaly detected on channel string, upinblt=number
Cause: This is an debugging message and can be ignored.
Action: no action required.
RMAN-10038: database session for channel string terminated unexpectedly
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.
RMAN-10039: error encountered while polling for RPC completion on channel string
Cause: This error should be accompanied by other errors giving the cause of the polling error.
Action: Check the accompanying errors.
RMAN-10040: asynchronous support not detected, RMAN will run synchronously
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.
RMAN-11000: message number number not found in recovery manager message file
Cause: Recovery manager message file is out of date.
Action: Make sure that the recovery manager error message file is current and installed in the correct location.
RMAN-11001: Oracle Error: string
Cause: informational message
Action: no action required
RMAN-11002: could not open a cursor to the target database
Cause: informational message
Action: no action required
RMAN-11003: failure during parse/execution of SQL statement: string
Cause: informational message
Action: no action required
RMAN-11004: format requires %%c when duplexing
Cause: SET_DUPLEX=ON was specified, but %c was not part of the format.
Action: Include %c in format, or use %U.
RMAN-11005: conflicting media information for piece "string"
Cause: While restoring the specified backup piece, RMAN received conflicting information about the physical location of the piece from the Media Management software. This can cause poor restore performance.
Action: If RMAN does not parallelize the restore from all of the available channels, then you should contact the Media Management vendor.
RMAN-11006: WARNING: test recovery results: string
Cause: User called recover database with the test option
Action: None required
RMAN-12000: execution layer initialization failed
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-12001: could not open channel string
Cause: An ALLOCATE CHANNEL command could not be processed.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
RMAN-12005: error during channel cleanup
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-12007: cannot allocate more than number channels
Cause: The maximum number of RMAN channels has been exceeded. Note that one channel is reserved for RMAN.
Action: Allocate fewer channels. Contact Oracle if you have a need for more channels in a single job.
RMAN-12008: could not locate backup piece string
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
RMAN-12009: command aborted because some backup pieces could not be located
Cause: Same as 7008.
Action: Refer to 7008.
RMAN-12010: automatic channel allocation initialization failed
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-12011: multiple records for default device type found in catalog
Cause: configuration for default device type not consistent.
Action: re-run CONFIGURE DEFAULT DEVICE TYPE command to set device type.
RMAN-12012: multiple records for string parallelism found in catalog
Cause: configuration for device parallelism is not consistent.
Action: re-run CONFIGURE PARALLELISM command for device to set parallelism.
RMAN-12013: multiple records for string channel number found in catalog
Cause: configuration for the channel is not consistent.
Action: re-run CONFIGURE CHANNEL command to configure this channel.
RMAN-12014: multiple records for default channel configuration for string found in catalog
Cause: configuration for the channel is not consistent.
Action: re-run CONFIGURE CHANNEL command to configure the channel.
RMAN-12015: configuration for string channel number is ignored
Cause: this is an informational message. parallelism for the device is less than associated channel number.
Action: to use this configuration increase parallelism for this device. to clear this configuration use CONFIGURE CHANNEL... CLEAR command.
RMAN-12016: using channel string
Cause: informational message
Action: no action required
RMAN-12017: could not locate pieces of backupset key string
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, use the CROSSCHECK BACKUP command to correct the recovery catalog entries.
RMAN-12018: channel string disabled, job failed on it will be run on another channel
Cause: This is an informational message displayed whenever a retriable error occurs for the job and there are channels available to run this step.
Action: no action required.
RMAN-12019: continuing other job steps, job failed will not be re-run
Cause: This is an informational message displayed whenever there is a non-retriable error occured for the job.
Action: no action required.
RMAN-12020: error on step filtered for normal output string
Cause: This message is added when stacking errors for failed jobs after channel failover was performed. It will be filtered from normal output.
Action: no action required.
RMAN-20000: abnormal termination of job step
Cause: A job step encountered an error and could not recover. This error should be followed by other errors indicating the cause of the problem.
Action: Check the accompanying error.
RMAN-20001: target database not found in recovery catalog
Cause: target database is not found in the recovery catalog
Action: make sure that the target database is registered in the recovery recovery catalog
RMAN-20002: target database already registered in recovery catalog
Cause: target database is already registered in the recovery catalog
Action: if the target database is really registered, there is no need to register it again. Note that the recovery catalog enforces that all databases have a unique DBID. If the new database was created by copying files from an existing database, it will have the same DBID as the original database and cannot be registered in the same recovery catalog.
RMAN-20003: target database incarnation not found in recovery catalog
Cause: resetlogs change# and/or time of the target database doesn't match any database incarnation in the recovery catalog.
Action: if target database was opened with resetlogs option then use 'reset database' to register the new incarnation.
RMAN-20004: target database name does not match name in recovery catalog
Cause: name of the target database doesn't match the one stored in the recovery catalog
Action: This is an internal error, call support.
RMAN-20005: target database name is ambiguous
Cause: two or more databases in the recovery catalog match this name
Action: none
RMAN-20006: target database name is missing
Cause: target database instance is not started or db_name initialization parameter is not set
Action: startup the instance and make sure that db_name parameter is set
RMAN-20009: database incarnation already registered
Cause: this incarnation is already registered in the recovery catalog
Action: no action required
RMAN-20010: database incarnation not found
Cause: database incarnation does not match any database incarnation in the recovery catalog
Action: specify a valid database incarnation key
RMAN-20011: target database incarnation is not current in recovery catalog
Cause: the database incarnation that matches the resetlogs change# and time of the mounted target database controlfile 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 controlfile using RMAN. Otherwise use 'reset database to incarnation <key>' make the intended incarnation current in the recovery catalog.
RMAN-20029: cannot make a snapshot controlfile
Cause: another operation that needs the snapshot controlfile is in progress
Action: try again later if necessary
RMAN-20030: resync in progress
Cause: this procedure can not be called while a resync is in progress
Action: This is an internal error
RMAN-20031: resync not started
Cause: this procedure can only be called in a resync
Action: This is an internal error
RMAN-20032: checkpoint change# too low
Cause: the checkpoint change# is less than the one of the previous resync or the checkpoint change# is null
Action: make sure that the right controlfile is used
RMAN-20033: controlfile sequence# too low
Cause: the controlfile sequence is less than the one of the previous resync
Action: make sure that the right controlfile is used
RMAN-20034: resync not needed
Cause: the control file has not changed since the previous resync
Action: nothing since the recovery catalog is in sync
RMAN-20039: format requires character when duplexing
Cause: SET_DUPLEX=ON was specified, but %c was not part of the format.
Action: Include %c in format, or use %U.
RMAN-20201: datafile not found in the recovery catalog
Cause: The specified datafile is not found in the recovery catalog
Action: make sure that the datafile name is correct and that the recovery catalog is up-to-date
RMAN-20202: tablespace not found in the recovery catalog
Cause: the specified tablespace is not found in the recovery catalog
Action: make sure that the tablespace name is correct and that the recovery catalog is up-to-date
RMAN-20203: translation in progress
Cause: this procedure can not be called when name translation is in progress
Action: this is an internal error
RMAN-20204: translation not started
Cause: getDatafile procedure was called before translateTablespace
Action: this is an internal error
RMAN-20205: incomplete UNTIL clause
Cause: The sequence# was NULL
Action: this is an internal error
RMAN-20206: log sequence not found in the repository
Cause: The specified log sequence does not exists in log history of the current database incarnation
Action: check the thread# and sequence#
RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time
Cause: UNTIL TIME and RECOVERY WINDOW cannot be less than the database creation time or RESETLOGS time.
Action: Check the UNTIL TIME or RECOVERY WINDOW. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command.
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
Cause: UNTIL CHANGE cannot be less than the database RESETLOGS change.
Action: Check the UNTIL CHANGE. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command.
RMAN-20209: duplicate datafile name
Cause: Two datafiles have the same name
Action: this is an internal error
RMAN-20211: FROM TIME is before RESETLOGS time
Cause: FROM TIME cannot be less than the database creation time or RESETLOGS time.
Action: Check the FROM TIME. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command.
RMAN-20215: backup set not found
Cause: The specified backup set key was not found in the recovery catalog
Action: Specify a different backup set key.
RMAN-20217: datafile not part of the database
Cause: the datafile does not exists or did not exist at until time/scn
Action: check the datafile name or number. This is an internal error for restore database or tablespace.
RMAN-20218: datafile not found in recovery catalog
Cause: This is an internal error
Action: Contact Oracle Customer Support.
RMAN-20220: controlfile copy not found in the recovery catalog
Cause: the specified controlfile is not in the recovery catalog or it has been marked deleted
Action: check the filename
RMAN-20221: ambiguous controlfile copy name
Cause: more than one controlfile copy in the recovery catalog match the specified name.
Action: none
RMAN-20222: datafilename not found in recovery catalog or is ambiguous
Cause: The specified datafilename is not the name of a datafile that is currently part of the target database, or an UNTIL clause has been specified and the filename was for a different datafile at the time specified by the UNTIL clause than it is now.
Action: Use a datafile number to specify the datafile you want to RESTORE or RECOVER.
RMAN-20230: datafile copy not found in the recovery catalog
Cause: the specified datafile is not in the recovery catalog or it has been marked deleted
Action: check the datafile copy name or key
RMAN-20231: ambiguous datafilecopy name
Cause: more than one controlfile copy in the recovery catalog match the specified name.
Action: use the datafile copy key to uniquely specify the datafile copy
RMAN-20240: archived log not found in the recovery catalog
Cause: the specified archived log was not found in the recovery catalog or it has been marked deleted
Action: check the archived log name or key
RMAN-20241: ambiguous archived log name
Cause: more than one archived log in the recovery catalog match the specified name
Action: use the archived log key to uniquely specify the archived log
RMAN-20250: offline range not found in the recovery catalog
Cause: the specified offline was not found in the recovery catalog
Action: check that recovery catalog is current
RMAN-20260: backup piece not found in the recovery catalog
Cause: the specified backup piece is not in the recovery catalog or it has been marked deleted
Action: check the backup piece handle or key
RMAN-20261: ambiguous backup piece handle
Cause: more than one backup piece in the recovery catalog match the specified handle
Action: use the backup piece key to uniquely specify the backup piece
RMAN-20272: no parent backup found for the incremental backup
Cause: no available backup or copy that could be used as the parent of the incremental backup was found in the recovery catalog.
Action: take a level 0 backup or copy of the datafile first
RMAN-20280: too many device types
Cause: more than 8 device types were allocated
Action: make sure that the job allocates at most 8 different device types
RMAN-20298: DBMS_RCVCAT package not compatible with the recovery catalog
Cause: The version of the recovery catalog tables does not work with this version of the DBMS_RCVCAT package.
Action: Check that the recovery catalog packages and schema are installed correctly. The UPGRADE CATALOG command can be used to upgrade the recovery catalog tables and packages to the most current version.
RMAN-20299: DBMS_RCVMAN package not compatible with the recovery catalog
Cause: The version of the recovery catalog tables does not work with this version of the DBMS_RCVMAN package.
Action: Check that the recovery catalog packages and schema are installed correctly. The UPGRADE CATALOG command can be used to upgrade the recovery catalog tables and packages to the most current version.
RMAN-20310: proxy copy not found in the recovery catalog
Cause: the specified proxy copy is not in the recovery catalog or it has been marked deleted
Action: check the proxy copy handle or key
RMAN-20311: ambiguous proxy copy handle
Cause: more than one proxy copy in the recovery catalog matches the specified handle
Action: use the proxy copy key to uniquely specify the proxy copy
RMAN-20401: script already exists
Cause: a CREATE SCRIPT was issued, but a script with the specified name already exists.
Action: use a different name or use REPLACE SCRIPT.
RMAN-20501: redo logs from parent database incarnation cannot be applied
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, ensure that it is marked AVAILABLE, and that a channel of the correct device type is allocated. It may also be necessary to remove the FROM BACKUPSET or FROM DATAFILECOPY or FROM TAG operands if these have been specified.
RMAN-20502: DELETE EXPIRED cannot delete objects that exist - run CROSSCHECK
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 with reality.
Action: Run CROSSCHECK.
RMAN-20503: DELETE cannot delete expired objects - run CROSSCHECK or DELETE EXPIRED
Cause: A DELETE command was run without EXPIRED option, but the object doesn't exist. This means the recovery catalog or controlfile is out of sync with reality.
Action: Run CROSSCHECK.
RMAN-20504: corruption list not found in recovery catalog
Cause: corruption list is empty
Action: make sure that one or more blocks are marked corrupted in v$copy_corruption and v$backup_corruption and recovery catalog is up-to-date.
RMAN-20505: create datafile during recovery
Cause: applying of archived log caused a create datafile redo-entry to to terminate recovery.
Action: none. This message is never displayed. RMAN automatically detects this case and creates the datafile.
RMAN-20506: no backup of archivelog found
Cause: during the recover process, no backup was found from which the archivelogs could be restored.
Action: this message should be followed by a list of missing archivelogs. Please make the necessary archivelog backups available and try again.
Go to previous page
Previous		 Go to next page
Next
Oracle
Copyright © 2004, Oracle. All rights reserved.
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Master Index
Master Index		 Go to Feedback page
Feedback