RMAN "SWITCH" COMMAND TAKING A LONG TIME (Doc ID 1391847.1)

Last updated on AUGUST 19, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.3 [Release 10.2 to 11.2]
Oracle Database - Enterprise Edition - Version 11.2.0.4 to 11.2.0.4 [Release 11.2]
Information in this document applies to any platform.

Symptoms

The RMAN SWITCH command ws taking a long time.

After enabling RMAN client debug tracing, it was seen that the majority of the time was being spent in the call to sys.dbms_backup_restore.switchToCopy().
Server-side tracing of the RMAN default process showed that the time was being spent doing many controlfile reads:



begin sys.dbms_backup_restore.switchToCopy( copy_recid => :recid, copy_stamp => :stamp); end;

call    count  cpu    elapsed disk query current rows
------- ------ ------ ------- ---- ----- ------- ----
Parse        1   0.00    0.00    0     0       0    0
Execute      1   0.24   22.26    0     0       0    1
Fetch        0   0.00    0.00    0     0       0    0
------- ------ ------ ------- ---- ----- ------- ----
total        2   0.24   22.26    0     0       0    1
...
Elapsed times include waiting on following events:
Event waited on              Times  Max. Wait  Total Waited
---------------------------- Waited ---------- ------------
control file sequential read   4910       0.02        22.02

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms