 |
|
Oracle Tips by Burleson |
Oracle 10g RMAN - How big is the Block Change Tracking
File?
The size of the block change tracking file is
proportional to:
-
The database size in bytes: the block
change tracking file contains data representing every data file
block in the database. The data is approximately 1/250000 of
the total size of the database.
-
The number of enabled threads: In a Real
Application Cluster (RAC) environment, the instances update
different areas of the tracking file without any locking or
inter-node block swapping. You enable block change tracking for
the entire database and not for individual instances.
-
The number of old backups: The block change
tracking file keeps a record of all changes between previous
backups, in addition to the modification since the last backup.
It retains the change history for a maximum of eight backups.
The size of the file is calculated by the
following formula:
Size of the Block Change Tracking File =
( (Threads*2) + number of old backups ) * database size in bytes
-------------------------------------------------------------------------
250,000
The
minimum size for the block change tracking file is 10 MB. Using this
formula, a 2 TB database with only one thread and having five
backups in the RMAN repository will require a block change tracking
file of 59 MB.
Get the complete Oracle10g story:
To get the code instantly, click here:
Need an Oracle Mentor?
BEI is now offering personal mentors for Oracle DBAs where you can have an
Oracle expert right at your fingertips, anytime day or night. We work with
hundreds of Oracle databases every year, so we know exactly how to quickly
assist you with any Oracle question.
Why risk an unplanned outage? You can now get telephone access to Don
Burleson or any of his Oracle Certified DBAs with more than 20 years of
full-time IT experience. Click here for details:
http://www.dba-oracle.com/service_oracle_backup.htm

|