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 required.
Category Archives: RMAN Database Error Messages
RMAN-01006: error signalled during parse
RMAN-01006: error signalled during parse
Cause: An error was signalled during parsing.
Action: This message should be accompanied by one or more other error messages indicating the cause of the error.
RMAN-00601: fatal error in recovery manager
RMAN-00601: fatal error in recovery manager
Cause: A fatal error has occurred.
Action: This message should be accompanied by one or more other error messages indicating the cause of the error.
RMAN-00600: internal error, arguments [string] [string] [string] [string] [string]
RMAN-00600: internal error, arguments [string] [string] [string] [string] [string]
Cause: An internal error in Recovery Manager occurred.
Action: Contact Oracle Support Services.
RMAN-00578: pipe string is not private and owned by SYS
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-00577: PIPE requires that TARGET be specified on the command line
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-00576: PIPE cannot be used with CMDFILE
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-00575: timeout while trying to write to dbms_pipe
RMAN-00575: timeout while trying to write to dbms_pipe
Cause: RMAN was running in DBMS_PIPE mode. A timeout occurred while calling DBMS_PIPE.SEND_MESSAGE. This occurs when the pipe is full and no process has dequeued any of the messages. This is usually caused by death of the process that was talking to RMAN.
Action: RMAN will abort.
RMAN-00574: rman aborting due to errors read/writing dbms_pipe
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 preceded by information describing the error.
Action: RMAN terminates. Refer to the cause/action for the preceding errors.
RMAN-00573: dbms_pipe.next_item_time returned unknown type code: number
RMAN-00573: dbms_pipe.next_item_time returned unknown type code: number
Cause: This is an internal error
Action: Contact Oracle Support Services.