My Oracle Support Banner

RMAN BACKUP OF PHYSICAL STANDBY VERY SLOW AFTER UPGRADE TO 11GR2. (Doc ID 972885.1)

Last updated on FEBRUARY 03, 2022

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Generic (Platform Independent)

Symptoms

RMAN incremental backup at standby site with Block Change Tracking enabled waits 10 mins before each backuppiece commences. With many backuppieces being created, this greatly increases the overall backup runtime.
RMAN debug trace shows the following calls before each backup commences:

DBGMISC: ENTERED krmzbjob [11:26:13.222]
DBGMISC: duration(stepid=1) starttime=704028373 [11:26:13.222] (krmzbjob)
DBGMISC: EXITED krmzbjob with status 1 (TRUE) [11:26:13.222] elapsed time [00:00:00:00.000]
DBGRPC: krmxrpc - channel ORA_DISK_1 kpurpc2 err=0 db=target proc=SYS.DBMS_BACKUP_RESTORE.SETLIMIT excl: 0
DBGRPC: krmxrpc - channel ORA_DISK_1 kpurpc2 err=0 db=target proc=SYS.DBMS_BACKUP_RESTORE.SETLIMIT excl: 0
DBGRPC: krmxrpc - channel ORA_DISK_1 kpurpc2 err=0 db=target proc=SYS.DBMS_BACKUP_RESTORE.SETLIMIT excl: 0
DBGRPC: krmxrpc - channel ORA_DISK_1 kpurpc2 err=0 db=target proc=SYS.DBMS_BACKUP_RESTORE.BACKUPSTATUS excl: 0
DBGRPC: krmxrpc - channel ORA_DISK_1 kpurpc2 err=0 db=target proc=SYS.DBMS_BACKUP_RESTORE.SETRMANSTATUSROWID excl: 0
DBGRPC: krmxrpc - channel ORA_DISK_1 kpurpc2 err=0 db=target proc=SYS.DBMS_BACKUP_RESTORE.BACKUPSETDATAFILE excl: 0
DBGMISC: ENTERED krmzlog [11:36:13.399]

The time spent on each series of calls is exactly 10 minutes.
A systemstate dump will show that the backup channel is waiting for 'Backup Restore Switch Bitmap sleep' (search for the channel eg "client info: rman channel=ORA_DISK_1")


Cause

To view full details, sign in with your My Oracle Support account.

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

In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.