Databases Reference
In-Depth Information
You can also join V$RMAN_OUTPUT to V$RMAN_STATUS to get additional information. This useful query
shows the type of command RMAN is running, its current status, and its associated output messages:
select
a.sid
,a.recid
,b.operation
,b.status
,a.output
from v$rman_output a
,v$rman_status b
where a.rman_status_recid = b.recid
and a.rman_status_stamp = b.stamp
order by a.recid;
How It Works
The V$RMAN_OUTPUT view contains messages recently reported by RMAN. It is an in-memory view that can hold up to
a maximum of 32,768 rows. Information in this view is cleared out when you stop and restart your database. The OUTPUT
column of V$RMAN_OUTPUT contains the messages that RMAN logs to your terminal when running commands.
Another handy use of this view is to query the output in the event that you are using a log file. If you are writing
RMAN output to a log file, then RMAN will not display messages to your terminal. In this situation, you can query
V$RMAN_OUTPUT to check on the status of currently running RMAN operations:
select
a.sid
,a.recid
,b.operation
,b.status
,a.output
from v$rman_output a
,v$rman_status b
where a.rman_status_recid = b.recid
and a.rman_status_stamp = b.stamp
and b.status = 'RUNNING'
order by a.recid;
Enabling RMAN's Debug Output
Problem
You're working with Oracle Support and they have requested that you enable RMAN debugging and send them the output.
Solution
You can turn on debugging in several different ways:
•
From the OS prompt or RMAN command line
•
When allocating a channel
•
When configuring a channel
