My Oracle Support Banner

Higher bitmap switches recorded than scheduled incremental backup causing no use of BCT by cumulative backups (Doc ID 2144267.1)

Last updated on FEBRUARY 14, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1.0 and later
Information in this document applies to any platform.

Symptoms

 Every incremental backups do BCT switches (recorded per datafile). By default Oracle keeps details of 8 incremental backups . If need to store more bitmaps (number of incremental backups higher than 8 in b/w 2 L0 backups)  then need to adjust by parameter "_bct_bitmaps_per_file" (default 8) accordingly so that BCT file having sufficient history to use BCT .

 We can keep track of these bitmaps and incremental backups via below query (query tweaked for one datafile you can remove the file number to get datails of all the files)

 

alter session set nls_date_format = 'DD-MON-YYYY HH24:MI:SS';
set linesize 400
set pagesize 100
set numwidth 16
Select RECID, FILE#, CREATION_CHANGE#, CREATION_TIME, INCREMENTAL_LEVEL,INCREMENTAL_CHANGE#, CHECKPOINT_CHANGE#, CHECKPOINT_TIME, MARKED_CORRUPT,USED_CHANGE_TRACKING FROM v$backup_datafile where file#=<file number>;
SELECT inst_id, csno, fno, vercnt, vertime, hist_first, hist_last, low, high FROM x$krcfbh where fno=<file number> ORDER BY csno, fno, vercnt;

 

Some times we see incremental backups not using BCT and same time we see more bitmap switches than expected ( switch count (bitmap version) should be equal to number of incremental backups)

 

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
References


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