Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 00550-20501: RMAN Errors

##### 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 name

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 name

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 Net8 host connect string exceeds the max 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 name

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: Control C (^C) or ATTN was entered.

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. To interpret them correctly, read from the bottom to the top.

##### RMAN-00570: **end-of-file**

Cause: The end of an inline commandfile was reached. This is an informational message.

Action: No action required.

##### RMAN-00600: internal error, arguments arg arg arg arg arg

Cause: An internal error in recovery manager occurred.

Action: Contact ORACLE 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-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 num column num file: name

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: name

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

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 symbol

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: char

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 into shorter lines, then retry the operation.

##### 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 during compilation 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: name

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-03005: %05.5d: name

Cause: This is an informational message.

Action: No action required.

##### RMAN-03006: non-retryable error occurred during execution of command: name

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

##### RMAN-03007: retryable error occurred during execution of command: name

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors. If the error can be fixed, the RETRY command can be used to retry the failed operation.

##### 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-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-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: command type: name

Cause: Informational message to accompany RMAN-03012.: Follow the instructions in the message.

##### RMAN-03014: implicit resync of recovery catalog failed

Cause: This message is accompanied by other errors explaining the cause of the failure.

Action: Follow the instructions in the messages which follow.

##### RMAN-03015: error occurred in stored script name

Cause: This is an information message only.

Action: No action required.

##### RMAN-03017: recursion detected in stored script name

Cause: A stored script is calling itself or another script which calls itself.

Action: Remove the recusion.

##### RMAN-03018: async RPCs are working correctly

Cause: This is an informational message.

Action: No action required.

##### RMAN-03019: async 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 Net8 driver that does not support non-blocking UPI.

Action: Try using a different Net8 driver.

##### RMAN-03020: async RPC test will take 1 minute

Cause: This is an informational message.

Action: No action required.

##### RMAN-03021: executing script: name

Cause: This is an information message only.

Action: No action required.

##### RMAN-03022: compiling command: name

Cause: This is an information message only.

Action: No action required.

##### RMAN-03023: executing command: name

Cause: This is an information message only.

Action: No action required.

##### RMAN-03024: performing implicit full resync of recovery catalog

Cause: This is an information message only.

Action: No action required.

##### RMAN-03025: performing implicit partial resync of recovery catalog

Cause: This is an information message only.

Action: No action required.

##### RMAN-03026: error recovery releasing channel resources

Cause: An error was caught, and RMAN is cleaning up the channels.

Action: No action required. This is an informational message only.

##### RMAN-03027: printing stored script: name

Cause: This is an informational message.

Action: No action required.

##### RMAN-03099: job cancelled at user request

Cause: The user interrupted the current job.

Action: None.

##### RMAN-04000: memory allocation failure

Cause: A memory allocation request could not be satisfied.

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-num

Cause: OCI process level initialization failed.

Action: This error should not normally occur.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index