RMAN incremental level 1 backups are not using block change tracking file
(Doc ID 1192652.1)
Last updated on FEBRUARY 03, 2025
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 to 12.1.0.2 [Release 10.2 to 12.1]Information in this document applies to any platform.
*** ***
Symptoms
With block change tracking enabled, during an rman level 1 incremental backup it can be observed that block change tracking is not used for datafiles. Using this query to determine if block change tracking is being used for the backup. Change the RMAN owner, date and time, and db_id to match your environment:
Replace the completion_time accordingly in the below query
select
file# fno,
used_change_tracking BCT,
incremental_level INCR,
datafile_blocks BLKS,
block_size blksz,
blocks_read READ,
round((blocks_read/datafile_blocks) * 100,2) "%READ",
blocks WRTN, round((blocks/datafile_blocks)*100,2) "%WRTN"
from rman102.rc_backup_datafile
where completion_time between
to_date('08-10-2010 09:00:00', 'MM-DD-YYYY HH24:MI:SS') and
to_date('08-10-2010 13:00:00', 'MM-DD-YYYY HH24:MI:SS')
and db_key=458227
order by file#;
file# fno,
used_change_tracking BCT,
incremental_level INCR,
datafile_blocks BLKS,
block_size blksz,
blocks_read READ,
round((blocks_read/datafile_blocks) * 100,2) "%READ",
blocks WRTN, round((blocks/datafile_blocks)*100,2) "%WRTN"
from rman102.rc_backup_datafile
where completion_time between
to_date('08-10-2010 09:00:00', 'MM-DD-YYYY HH24:MI:SS') and
to_date('08-10-2010 13:00:00', 'MM-DD-YYYY HH24:MI:SS')
and db_key=458227
order by file#;
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 |