Database Reference
In-Depth Information
RMAN sent a message with a single item (or line). This is indicated by the return value
RV=1
. The message from RMAN indicates that it connected to the target database. At this point,
RMAN is not ready to receive a command, which is indicated by
WAIT_FOR_INPUT=0
. Let's retrieve
the next message.
SQL> EXEC :rv:=site_sys.rman_pipe_if.receive(:pipe_arg, :msg, :wait_for_input, -
> :rman_error, :rman_msg, :ora_error, :ora_msg)
PL/SQL procedure successfully completed.
SQL> SELECT :rv rv, :msg msg, :wait_for_input wait_for_input FROM dual;
RV MSG Wait for input
--- --------------------------------------------------- --------------
1 RMAN-00572: waiting for dbms_pipe input 1
Now RMAN is ready to accept a command (
WAIT_FOR_INPUT=1
), so let's tell RMAN to
connect to the catalog database.
SQL> BEGIN
:cmd:='CONNECT CATALOG rman/
rman@ten_tcp.world;';
-- send a message
:rv:=site_sys.rman_pipe_if.send(:pipe_arg, :cmd);
END;
/
PL/SQL procedure successfully completed.
SQL> PRINT rv
RV
---
0
Let's find out whether the
CONNECT
CATALOG
command completed successfully (for the sake
of conciseness, the call to
site_sys.rman_pipe_if.receive
has been omitted).
SQL> SELECT :rv rv, :msg msg FROM dual;
RV MSG
--- --------------------------------------------------------------------------------
4 RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-04004: error from recovery catalog database: ORA-12170: TNS:Connect timeout
occurred
An error, which prevented RMAN from connecting to the catalog database, occurred. Yet,
RMAN is still running and ready to receive further commands as we will see shortly. But first,
let's look at the additional information, such as this RMAN error code, returned by
RMAN_PIPE_IF
:
