Which four statements regarding the block change track file are correct? (Choose four)
A.
The minimum size of this file is 10 MB.
B.
The maintenance of this file is fully automatic.
C.
The changed blocks are tracked in this file as redo is generated.
D.
The location of this file must be different from that of the database files.
E.
The Oracle database records block change information in this file by default.
F.
The V$BLOCK_CHANGE_TRACKING view contains the name and location of this file.
Explanation:
A – True. Should say "start" not "minimum". The size of the change tracking file is proportional to the size of the database and the number of enabled threads of redo. The size is not related to the frequency of updates to the database. Typically, the space required for block change tracking is Overview of Reporting on Backups and the RMAN Repository approximately 1/30,000 the size of the data blocks to be tracked. B – False. Using change tracking in no way changes the commands used to perform incremental backups, and the change tracking files themselves generally require little maintenance after initial configuration.
C – True. Changed blocks are tracked by the CTWR background process as redo is generated. Database incremental backups, automatically use the change tracking file; D – False. You can also create the change tracking file in a location you choose yourself, using the following SQL statement:
SQL> ALTER DATABASE ENABLE BLOCK CHANGE TRACKING
USING FILE’/mydir/rman_change_track.f’ REUSE;
E – True. One change tracking file is created for the whole database. By default, the change tracking file is created as an Oracle managed file in DB_CREATE_FILE_DEST. F – True. From SQL*Plus, you can query V$BLOCK_CHANGE_TRACKING.STATUS to determine whether change tracking is enabled, and if it is, query V$BLOCK_CHANGE_TRACKING.FILENAME to display the filename. REF.: Oracle(r) Backup and Recovery Basics, 4-19, 4-20 and 4-21