Database Backup and Recovery (MOSC)

MOSC Banner

Block change tracking

edited Jun 29, 2012 2:36AM in Database Backup and Recovery (MOSC) 4 comments

We are using block change tracking for fast incremental perfromance.  One of our database's cumulative incremental is not using the change tracking feature for many of the datafiles in the database.  The v$backup_datafile view shows 65 datafiles are not using the feature and 22 are.  Because of this, the incremental takes 4.5 - 5 hours to complete.

Here is some background:

Block change tracking is enabled.

We run level 0 incrementals every Saturday and level 1 cumulative incrementals Sun-Fri.

There should be an adequate number of bitmap versions in the change tracking file (8 being the default) to support this schedule.

This database was upgraded from 10.2.0.5 to 11.2.0.2 using DBUA.  Block change tracking remained enabled after the upgrade.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center