This content has been marked as final. Show 3 replies
It is not backed up according to section 4.4.4 of Backup and Recovery Basics:
Although RMAN does not support backup and recovery of the change-tracking file itself, if the whole database or a subset needs to be restored and recovered, then recovery has no user-visible effect on change tracking. After the restore and recovery, the change tracking file is cleared, and starts recording block changes again. The next incremental backup after any recovery is able to use change-tracking data.
According to Metalink note:
Subject: Ora-19755: Could Not Open Change Tracking File Ora--17503 on Database Open
Doc ID: Note:344885.1 Type: PROBLEM
Last Revision Date: 21-DEC-2005 Status: PUBLISHED
you could disable block change tracking before running recover statement and reenabled it after successfull recovery.
Message was edited by:
But how do I disable block change tracking without opening the database? I don't seem to be able to issue 'alter database disable....'
ALTER DATABASE DISABLE BLOCK CHANGE TRACKING;
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00558: error encountered while parsing input commands
RMAN-01005: syntax error: found "identifier": expecting one of: "mount, open"
RMAN-01008: the bad identifier was: DISABLE
RMAN-01007: at line 1 column 16 file: standard input
BCT can be disabled with the database in a MOUNT state.
ALTER DATABASE MOUNT
ALTER DATABASE DISABLE BLOCK CHANGE TRACKING