Monitoring Rman Backups

For RMAN jobs, you can query the following columns in the V$SESSION_LONGOPS dynamic view:

SID - The session ID for the RMAN channel

SERIAL# - The serial number of the server session

OPNAME - A description of what the row includes, such as RMAN: datafile copy, RMAN: full datafile backup, RMAN full datafile restore,

RMAN: aggregate input, or RMAN: aggregate output

CONTEXT - The context associated with the row, which is 2 for rows pertaining to backup output and 1 for other types of rows, except rows associated with proxy

copies

SOFAR - The work completed at the time the query is issued, which is the number of blocks read for image copies, the number of blocks read for files being

backed up, the number of blocks written to the backup piece for backups, the number of blocks processed by a single job step for restores, and the number of

files copied for proxy copies

TOTALWORK - The work to be performed at the time the query was issued, which is the total number of blocks in the file for image copies, the total number of

blocks to be read for files backed up by a single job step for backups, the number of blocks in all files to be restored in a single job step for restores, or the

number of files to be copied in a single job step for proxy copies

For example, you could issue the following query to monitor the progress of the BACKUP command at a detail level, and it would provide information

about the progress as each backup set was created:

SELECT sid, opname, context, sofar, totalwork, ROUND(sofar/totalwork, 2) "%Complete"

FROM V$SESSION_LONGOPS

WHERE opname LIKE 'RMAN%'

AND opname NOT LIKE '%aggregate%'

AND totalwork != 0

AND sofar <> totalwork;

You could issue the following query to monitor the progress of the entire BACKUP command you issued:

SELECT sid, opname, context, sofar, totalwork, ROUND(sofar/totalwork, 2) "%Complete"

FROM V$SESSION_LONGOPS

WHERE opname LIKE 'RMAN%'

AND opname LIKE '%aggregate%'

AND totalwork != 0

AND sofar <> totalwork;