0550-0999 |
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.
|
