RMAN-04006: error from auxiliary database: string

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-04005: error from target database: string

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-04004: error from recovery catalog database: string

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-04003: ociinit failed

RMAN-04003: ociinit failed

Cause: The call to OCIEnvInit failed.

Action: This error should not normally happen. Contact Oracle Customer Support.

RMAN-04002: ocipi failed, ORA-string

RMAN-04002: ocipi failed, ORA-string

Cause: OCI process level initialization failed.

Action: This error should not normally occur.

RMAN-04001: heap initialization failure

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-04000: memory allocation failure

RMAN-04000: memory allocation failure

Cause: A memory allocation request could not be satisified.

Action: Increase the amount of memory available to RMAN.

RMAN-03999: Oracle error occurred while while converting a date: ORA-number: string

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-03099: job cancelled at user request

RMAN-03099: job cancelled at user request

Cause: The user interrupted the current job.

Action: None.

RMAN-03098: %-*sRMAN-number: stringstring

RMAN-03098: %-*sRMAN-number: stringstring

Cause: This is the message prefix with a possible indentation.

Action: No action is required.

RMAN-03091: Finished string at string

RMAN-03091: Finished string at string

Cause: This is an informational message only.

Action: No action is required.

RMAN-03090: Starting string at string

RMAN-03090: Starting string at string

Cause: This is an informational message only.

Action: No action is required.

RMAN-03040: Spooling for trace turned off

RMAN-03040: Spooling for trace turned off

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

Action: No action is required.

RMAN-03039: Spooling for log turned off

RMAN-03039: Spooling for log turned off

Cause: a SPOOL LOG OFF comand was issued

Action: No action is required.

RMAN-03038: Spooling started in trace file: string

RMAN-03038: Spooling started in trace file: string

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

Action: No action is required.

RMAN-03037: Spooling started in log file: string

RMAN-03037: Spooling started in log file: string

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

Action: No action is required.

RMAN-03036: Debugging set to level=number, types=string

RMAN-03036: Debugging set to level=number, types=string

Cause: a DEBUG comand was issued

Action: No action is required.

RMAN-03035: Debugging turned off

RMAN-03035: Debugging turned off

Cause: a DEBUG OFF comand was issued

Action: No action is required.

RMAN-03034: LEVEL number is invalid. LEVEL must be between string and string

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-03033: current log archived

RMAN-03033: current log archived

Cause: A ALTER SYSTEM ARCHIVE LOG CURRENT command completed successfully.

Action: None, this is an informational message.

RMAN-03032: this option of set command needs to be used outside of 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-03031: this option of set command needs to be used inside a run block

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-03030: echo set off

RMAN-03030: echo set off

Cause: a SET ECHO OFF command was issued

Action: No action is required.

RMAN-03029: echo set on

RMAN-03029: echo set on

Cause: a SET ECHO ON command was issued

Action: No action is required.

RMAN-03028: fatal error code for command string : number

RMAN-03028: fatal error code for command string : number

Cause: Informational message. This preceeds error 3012.

Action: No action is required.

RMAN-03023: executing command: string

RMAN-03023: executing command: string

Cause: This is an informational message only.

Action: No action is required.

RMAN-03020: asynhronous RPC test will take 1 minute

RMAN-03020: asynhronous RPC test will take 1 minute

Cause: This is an informational message only.

Action: No action is required.

RMAN-03019: asynchronous RPCs are NOT working

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-03018: asynchronous RPCs are working correctly

RMAN-03018: asynchronous RPCs are working correctly

Cause: This is an informational message only.

Action: No action is required.

RMAN-03017: recursion detected in stored script string

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-03015: error occurred in stored script string

RMAN-03015: error occurred in stored script string

Cause: This is an informational message only.

Action: No action is required.

RMAN-03014: implicit resync of recovery catalog failed

RMAN-03014: implicit resync of recovery catalog failed

Cause: of the failure.

Action: No action is required.

RMAN-03013: Copyright (c) 1995, 2003, Oracle Corporation. All rights reserved.

RMAN-03013: Copyright (c) 1995, 2003, Oracle Corporation. All rights reserved.

Cause: This is the copyright banner

Action: No action is required.

RMAN-03012: fatal error during compilation of command

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-03011: Recovery Managerstring

RMAN-03011: Recovery Managerstring

Cause: This is the RMAN banner

Action: No action is required.

RMAN-03010: fatal error during library cache pre-loading

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-03009: failure of string command on string channel at string

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-03008: error while performing automatic resync of recovery catalog

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-03004: fatal error during execution of 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-03003: command not implemented yet: string

RMAN-03003: command not implemented yet: string

Cause: The command is not implemented in the current release.

Action: Avoid using the command.

RMAN-03002: failure of string command at string

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-03001: recovery manager command sequencer component initialization failed

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-03000: recovery manager compiler component initialization failed

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-02007: Integer value overflow

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-02006: script line too long

RMAN-02006: script line too long

Cause: a line longer than 500 bytes was encountered

Action: break the line up into shorter lines

RMAN-02005: token too big

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-02004: quoted string too big

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-02003: unrecognized character: string

RMAN-02003: unrecognized character: string

Cause: An input character that is neither an alpha, digit, or punctuation was encountered.

Action: Remove the character.

RMAN-02002: unexpected end of input file reached

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-02001: unrecognized punctuation symbol string

RMAN-02001: unrecognized punctuation symbol string

Cause: An illegal punctuation character was encountered.

Action: Remove the illegal character.

RMAN-02000: wrong message file version (msg number not found)

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 or S) and the rmanxx.msb file must be from the same version, release, and patch level.

RMAN-06081: error reading datafile header for datafile string, code string

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-06080: SWITCH required for datafile string

RMAN-06080: SWITCH required for datafile string

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

Action: Issue SWITCH command then retry RECOVER.

RMAN-06079: database must be mounted to perform recovery

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-06078: the control file is older than datafile string

RMAN-06078: the control file is older than datafile string

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

Action: RESTORE a control file and perform RECOVER DATABASE.

RMAN-06077: datafile string is a different version than contained in the control file

RMAN-06077: datafile string is a different version than contained in the control file

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

Action: If the datafile is correct, the fix the control file by using the SWITCH command. Otherwise, RESTORE the correct version of this datafile and retry the RECOVER command.

RMAN-06076: datafile string contains wrong datafile

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-06075: datafile string does not belong to this database

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-06074: file string is not an ORACLE datafile

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-06073: file header is corrupt for datafile string

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.