27
To enable this functionality, issue the following command:
SQL> select status from v$block_change_tracking;
STATUS
----------
DISABLED
SQL> alter database enable block change tracking;
Database altered.
SQL> select status from v$block_change_tracking;
STATUS
----------
ENABLED;
SQL> select FILENAME,bytes from v$block_change_tracking;
FILENAME
BYTES
---------------------------------------------- ----------
+DG_DB/rac/changetracking/ctf.351.638031151 23166976
The incremental backup with enabled change block tracking took 11 minutes to complete.
Recovery recommendations
•
Favor using incremental backups for recovery instead of archived logs
•
Enable block change tracking for incremental backups
•
Increase the Oracle parameter PARALLEL_EXECUTION_MESSAGE_SIZE for parallel recovery. This
parameter determines the buffer size for the message exchanged among parallel processes.
•
Use the dynamic view V$RECOVERY_PROGRESS to monitor the recovery progress
Summary
As it has been shown throughout this paper, Data Protector offers several possibilities to perform the
configuration in an Oracle10g RAC environment. It is not necessarily a complex task, but limitations
and implications need to be understood.
In summary, if ease of configuration and availability are the key premises, using an Oracle Service to
configure the integration is the best approach.
If however, due to backup window constraints and backup devices availability, the backup time
needs to be minimized, the recommendation is to perform a manual allocation of channels on specific
instances.
Independent from the configuration option chosen, Data Protector’s Oracle Integration with Oracle
RMAN is the ideal choice for protecting your Oracle Database.
