Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
Cause: lpmloadpkg() return an error indication.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
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.
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.
Cause: lpmloadpkg() return an error indication.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
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.
Cause: The TARGET parameter was not specified.
Action: Supply the necessary parameter.
Cause: An error occurred when trying to open the file.
Action: Check that the filename was specified correctly and that the file exists and that the user running RMAN has read permission for the file.
Cause: An error occurred when trying to open the file.
Action: Check that the filename was specified correctly and that the file exists and that the user running RMAN has write permission for the file.
Cause: The parser detected a syntax error.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
Cause: The specified user name exceeds the maximum allowable username length.
Action: Correct the username.
Cause: The specified password exceeds the maximum allowable password length.
Action: Correct the password.
Cause: The Net8 host connect string exceeds the max allowable length.
Action: Correct the host string.
Cause: An error occurred while trying to read from STDIN or from the CMDFILE.
Action: Ensure that the CMDFILE is readable. The CMDFILE must be a text file with 1 line per record.
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.
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.
Cause: Control C (^C) or ATTN was entered.
Action: No action required.
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.
Cause: The end of an inline commandfile was reached. This is an informational message.
Action: No action required.
Cause: An internal error in recovery manager occurred.
Action: Contact ORACLE support.
Cause: A fatal error has occurred.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
Cause: An error was signalled during parsing.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
Cause: This is an informational message indicating the line and column where a syntax error was detected.
Action: No action required.
Cause: This is an informational message indicating the identifier token that caused a syntax error.
Action: No Action required.
Cause: The RMANXX.MSB file is not the correct version.
Action: Check that the installation was done correctly. The RMAN binary (executable, load module, whatever it is called on your O/S) and the RMANXX.MSB file must be from the same version, release, and patch level.
Cause: An illegal punctuation character was encountered.
Action: Remove the illegal character.
Cause: This is probably caused by failure to supply the closing quote for a quoted string.
Action: Correct the input.
Cause: An input character that is neither an alpha, digit, or punctuation was encountered.
Action: Remove the character.
Cause: A quoted string longer than 2000 bytes was encountered.
Action: This may be caused by a missing close quote. If so, add the missing quote, otherwise shorten the string.
Cause: A token longer than 1000 bytes was encountered.
Action: Tokens must be separated by whitespace or punctuation. Either add the missing whitespace or punctuation, or shorten the token.
Cause: A line longer than 500 bytes was encountered.
Action: Break the line into shorter lines, then retry the operation.
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
Cause: The command is not implemented in the current release.
Action: Avoid using the command.
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
Cause: This is an informational message.
Action: No action required.
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
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.
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
Cause: A fatal error occurred during compilation of a command.
Action: This message should be accompanied by other errors explaining the cause of the failure.
Cause: Informational message to accompany RMAN-03012.: Follow the instructions in the message.
Cause: This message is accompanied by other errors explaining the cause of the failure.
Action: Follow the instructions in the messages which follow.
Cause: This is an information message only.
Action: No action required.
Cause: A stored script is calling itself or another script which calls itself.
Action: Remove the recusion.
Cause: This is an informational message.
Action: No action required.
Cause: The RPCTEST command has determined that RPCs are not executing asynchronously. Instead, they are blocking. This is caused by using a Net8 driver that does not support non-blocking UPI.
Action: Try using a different Net8 driver.
Cause: This is an informational message.
Action: No action required.
Cause: This is an information message only.
Action: No action required.
Cause: This is an information message only.
Action: No action required.
Cause: This is an information message only.
Action: No action required.
Cause: This is an information message only.
Action: No action required.
Cause: This is an information message only.
Action: No action required.
Cause: An error was caught, and RMAN is cleaning up the channels.
Action: No action required. This is an informational message only.
Cause: This is an informational message.
Action: No action required.
Cause: The user interrupted the current job.
Action: None.
Cause: A memory allocation request could not be satisfied.
Action: Increase the amount of memory available to RMAN.
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
Cause: OCI process level initialization failed.
Action: This error should not normally occur.
