Rman Performance Monitoring

Rman Performance Tuning related views

View Name	Description
V$rman_backup_job_details	Backup Job Information
V$backup_async_io	Rman asynchronous I/O performance information for the currently running, recently completed backup and restore operations
V$backup_sync_io	Rman synchronous I/O performance information for the currently running, recently completed backup and restore operations
V$process	Current active process
V$session	Current Active Session Information
V$session_longops	can display Rman backup, restore, and recovery progress
V$recovery_progress	Rman Operation Progress
V$session_wait	Displays events, resource information, for which the session is waiting

1. Find out the database session executing Rman

Sql> SELECT s.sid, s.serial#, P.spid, S.client_info  2from    v$process p, v$session s   3   WHERE p.addr = s.paddr  4     '%rman%';       SID    serial# SPID                     client_info------------------------------------------------------------------- -----------------------------------------                15313356                    Rman channel=Ora_disk_1sql

You can use SET command ID to identify the Rman session process when performing Rman operations

rman> run{2> Allocate channel d1 type disk; 3  set command ID ' my_session ' ; 4> backup database; 5>}

 sql> select B.sid, b.serial#, A.spid, b.client_info  2   from V$process A, v$session b  3   WHERE a.addr = b.paddr  4  and B.client_info Like   %rman%          ------------------------------------------------------------- -----------------------------------------------69  157  13434  id=my_s Ession , Rman channel=d1sql  > 

2. View Rman Job Details:

Sql>SelectSession_recid,2Input_bytes_per_sec_display,3Output_bytes_per_sec_display,4Time_taken_display,5End_time6     fromv$rman_backup_job_details7ORDER by End_time; Session_recid input_bytes_per_sec_ output_bytes_per_sec time_taken_display end_time------------- -------------------- -------------------- ------------------------------ ---------------------------- --1     3.09M                3.12M            xx:xx:Geneva                        --jun- the            3   178.12K122.60K to: -: at                        --jun- the            -   107.93M               75.97M            xx:xx: -                        at-jun- the            the    64.91M               50.01M            xx:xx:Panax Notoginseng                        --jun- the           Wuyi   109.27M               76.85M            xx:xx: -                        --jun- the            $   109.27M               76.85M            xx:xx: -                        --jun- the            -    43.96M               31.23M            xx: Geneva:Ten                        in-jun- the           98    19.74M               14.03M            xx:Geneva: -                        in-jun- the8rows selected. SQL>

3. View the progress of the Rman operation

SelectS.client_info, Sl.opname, Sl.message, Sl.sid, sl.serial#, P.spid, Sl.sofar, Sl.totalwork, round (Sl.sofar/sl.totalwork * -,2)"% Complete"   fromV$session_longops SL, v$session S, v$process pwhereP.ADDR =s.paddr and Sl.sid=S.sid and sl.serial#=s.serial# and Opname like'rman%'and Opname not like'%aggregate%'and totalwork!=0and Sofar<> totalwork;

If I/O is not turned on Slaves,rman just use share pool.

If I/O slaves is turned on for Rman backup (dbwr_io_slaves or backup_tape_io_slaves is set), the size of the large pool needs to be considered because Rman uses large pool.

Oracle's official recommendation: Large_pool_size = Num_of_allocated_channels * (MB + (4 * size_of_tape_buffer))

The media recovery for Rman turns on parallel recovery by default based on the value of the Cpu_count parameter.

Rman Performance Monitoring