Skip Headers
Oracle® Database Error Messages
10g Release 2 (10.2)
Part Number B14219-01
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
Contact Us
Go to previous page
Previous		 Go to next page
Next
View PDF

33 RMAN-00550 to RMAN-20507

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 is 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 is 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-00702: The command has no syntax errors
Cause: This is an informational message only.
Action: No action is required.
RMAN-00703: The cmdfile has no syntax errors
Cause: This is an informational message only.
Action: No action is required.
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 is 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 is required.
RMAN-01009: syntax error: found "string": expecting one of: "string"
Cause: A syntax error was signalled during parsing.
Action: Correct the input.
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 Managerstring
Cause: This is the RMAN banner
Action: No action is 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 is required.
RMAN-03014: implicit resync of recovery catalog failed
Cause: of the failure.
Action: No action is required.
RMAN-03015: error occurred in stored script string
Cause: This is an informational message only.
Action: No action is 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: This is an informational message only.
Action: No action is 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: This is an informational message only.
Action: No action is required.
RMAN-03023: executing command: string
Cause: This is an informational message only.
Action: No action is required.
RMAN-03028: fatal error code for command string : number
Cause: Informational message. This preceeds error 3012.
Action: No action is required.
RMAN-03029: echo set on
Cause: a SET ECHO ON command was issued
Action: No action is required.
RMAN-03030: echo set off
Cause: a SET ECHO OFF command was issued
Action: No action is 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 is required.
RMAN-03036: Debugging set to level=number, types=string
Cause: a DEBUG comand was issued
Action: No action is required.
RMAN-03037: Spooling started in log file: string
Cause: a SPOOL LOG TO ... comand was issued
Action: No action is required.
RMAN-03038: Spooling started in trace file: string
Cause: a SPOOL TRACE TO ... comand was issued
Action: No action is required.
RMAN-03039: Spooling for log turned off
Cause: a SPOOL LOG OFF comand was issued
Action: No action is required.
RMAN-03040: Spooling for trace turned off
Cause: a SPOOL TRACE TO ... comand was issued
Action: No action is required.
RMAN-03090: Starting string at string
Cause: This is an informational message only.
Action: No action is required.
RMAN-03091: Finished string at string
Cause: This is an informational message only.
Action: No action is required.
RMAN-03098: %-*sRMAN-number: stringstring
Cause: This is the message prefix with a possible indentation.
Action: No action is 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-04017: startup error description: string
Cause: of failure.
Action: No action is required.
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: starting Oracle instance without parameter file for retrival of spfile
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: This is an informational message only.
Action: No action is 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 is 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 control file 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-05014: tablespaces with undo segments were not found in recovery catalog
Cause: The recovery catalog did not have information about tablespaces with undo segments.
Action: Manually specify the tablespaces with undo segments in the optional UNDO TABLESPACES clause of the RECOVER command.
RMAN-05015: WARNING: not enough information in recovery catalog for specified point in time recovery
Cause: The recovery catalog did not have information about the tablespaces with undo segements at the specified point-in-time. This happened because the current recovery catatog was not in use at the specified point-in-time. A list of tablespaces with undo segments was supplied.
Action: RMAN assumes that the current set of tablespaces with undo segments is the same set that was in use at the specified point-in-time. If the set of tablespaces with undo segments changes, the recovery fails. If recovery fails, use the optional UNDO TABLESPACES clause of the RECOVER command to specify the correct set of tablespaces.
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/ control file/SPFILE using a previous existing backup.
Action: See accompanying 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 DESTINATION option for normal recovery
Cause: The AUXILIARY DESTINATION option was specified for a normal recovery. It is only allowed for tablespace point in time recovery.
Action: Remove the AUXILIARY DESTINATION 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-05022: TRANSPORT TABLESPACE may not be used with user-managed auxiliary instance
Cause: A user-managed auxiliary instance was specified.
Action: Retry the operation with an RMAN-managed auxiliary instance.
RMAN-05023: TABLESPACE DESTINATION required
Cause: A required TABLESPACE DESTINATION was not specified.
Action: Specify a TABLESPACE DESTINATION and retry the operation.
RMAN-05024: List of tablespaces presumed to have UNDO segments
Cause: Accompanying message to 5015.
Action: See action of message 5015.
RMAN-05025: tablespace string
Cause: Accompanying message to 5015.
Action: See action of message 5015.
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point in time
Cause: RMAN assumes that the current set of tablespaces with undo segments is the same set that was in use at the specified point-in-time. If the set of tablespaces with undo segments changes, the recovery fails. If recovery fails, use the optional UNDO TABLESPACES clause of the RECOVER command to specify the correct set of tablespaces.
Action: RMAN assumes that the current set of tablespaces with undo segments is the same set that was in use at the specified point-in-time. If the set of tablespaces with undo segments changes, the recovery fails. If recovery fails, use the optional UNDO TABLESPACES clause of the RECOVER command to specify the correct set of tablespaces.
RMAN-05027: List of tablespaces expected to have UNDO segments
Cause: Accompanying message to 5026.
Action: See action of message 5026.
RMAN-05028: tablespace string
Cause: Accompanying message to 5026.
Action: See action of message 5026.
RMAN-05029: UNDO TABLESPACE clause is only valid for Tablespace Point-in-Time Recovery
Cause: The UNDO TABLESPACE clause was specified for non-Tablespace Point-in-Time Recovery (TSPITR).
Action: Remove the UNDO TABLESPACE clause.
RMAN-05030: CLONE clause cannot be used with Tablespace Point-in-Time Recovery
Cause: The CLONE clause was specified for a Tablespace Point-in-Time Recovery (TSPITR).
Action: Remove the CLONE clause.
RMAN-05031: cannot specify UNDO TABLESPACES clause for normal recovery
Cause: The UNDO TABLESPACES clause was specified for a normal recovery. It is only allowed for tablespace point in time recovery.
Action: Remove the UNDO TABLESPACES clause and re-run the RECOVER command.
RMAN-05032: data file string will be created automatically during restore operation
Cause: The specified data file did not have an available backup.
Action: None. This is an informational message displayed for VALIDATE or PREVIEW option of the RESTORE command.
RMAN-05033: Media recovery start SCN is string
Cause: The above SCN would be starting media recovery SCN, if the specified files are restored.
Action: None. This is an informational message displayed for PREVIEW option of the RESTORE command.
RMAN-05034: Recovery must be done beyond SCN string to clear data files fuzziness
Cause: The above SCN identifies the minimum SCN beyond which the media recovery must be performed on the specific data files to clear the media recovery fuzziness for all data files.
Action: None. This is an informational message displayed for PREVIEW option of the RESTORE command.
RMAN-05035: archive logs generated after SCN string not found in repository
Cause: The repository did not have a record of archived logs containing the redo generated after the specified SCN.
Action: None. To avoid this message, perform a log switch if the database is in open mode.
RMAN-05040: List of tablespaces that have been dropped from the target database:
Cause: One or more tablespaces in the recovery set were not found in the controlfile of the target database.
Action: None. Informational message.
RMAN-05041: Error during export of metadata
Cause: Export of metadata received an error from datapump.
Action: This message is accompanied by other error message(s) indicating the cause of the error.
RMAN-05042: Error during import of metadata
Cause: Import of metadata received an error from datapump.
Action: This message is accompanied by other error message(s) indicating the cause of the error.
RMAN-05043: tablespace string
Cause: Accompanying message to 5040.
Action: See Action of message 5040.
RMAN-05044: Performing export of metadata...
Cause: This is an informational message only.
Action: No action is required.
RMAN-05045: Performing import of metadata...
Cause: This is an informational message only.
Action: No action is required.
RMAN-05046: Export completed
Cause: This is an informational message only.
Action: No action is required.
RMAN-05047: Import completed
Cause: This is an informational message only.
Action: No action is required.
RMAN-05048: specified filename string conflicts with a file used by the target database
Cause: The specified filename was already in use by another datafile in the database.
Action: Use SET NEWNAME command to specify a different name for the datafile that does not conflict with a filename in use by the target database.
RMAN-05049: datafile string is an Oracle Managed File, DB_CREATE_FILE_DEST not set at target
Cause: A tablespace point-in-time recovery (tspitr) was attempted but the datafile is an Oracle Managed File and DB_FILE_CREATE_DEST is not currently set for the target database.
Action: Specify DB_FILE_CREATE_DEST for the target database or provide a NEWNAME for the specified datafile.
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 control file checkpoint (string) is more recent than duplication point in time (string)
Cause: A DUPLICATE FOR STANDBY command was issued, but the checkpoint of the control file 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 control file checkpoint; otherwise archive (and backup/copy) the current log.
RMAN-05510: Duplicate finished
Cause: This is an informational message only.
Action: No action is required.
RMAN-05511: Datafile string skipped by request
Cause: This is an informational message only.
Action: No action is 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, control file is not current or backup
Cause: DUPLICATE requires that the target database has a current control file.
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-05516: duplicate operand specified: string
Cause: The specified operand appears more than once in the same duplicate option list
Action: Delete the duplicated operand.
RMAN-05517: temporary file string conflicts with file used by target database
Cause: RMAN attempted to use the specified temporary file as a restore destination in the auxiliary database, but this name was already in use by the target database.
Action: Use the SET NEWNAME FOR TEMPFILE command to specify a name for the indicated temporary file, making sure that the new name does not conflict with a filename in use by target database. Alternatively, use DB_FILE_NAME_CONVERT and retry the command.
RMAN-05520: database name mismatch, auxiliary instance has string, command specified string
Cause: The database name specified in the initialization parameter was not the same as the database name provided in the DUPLICATE command.
Action: Correct the database name in the command or adjust the database name of the auxiliary instance.
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: This is an informational message only.
Action: No action is required.
RMAN-06006: connected to target database: string (not mounted)
Cause: This is an informational message only.
Action: No action is required.
RMAN-06007: target database not mounted and db_name not set in init.ora
Cause: The target database has not mounted the control file, and its "init.ora" file does not specify the DB_NAME parameter.
Action: MOUNT the target database, or add the DB_NAME parameter to its "init.ora" and restart the instance.
RMAN-06008: connected to recovery catalog database
Cause: This is an informational message only.
Action: No action is required.
RMAN-06009: using target database control file instead of recovery catalog
Cause: This is an informational message only.
Action: No action is 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 control file.
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 datafile copy name: string
Cause: An error occurred while looking up the specified datafile copy name in the recovery catalog or target database control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the 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 duplicated 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 control file.
Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the tablespace is entered correctly. If the tablespace was added recently, then a RESYNC CATALOG must be done to update the recovery catalog.
RMAN-06020: connected to auxiliary database (not started)
Cause: This is an informational message only.
Action: No action is required.
RM