Post originally written at April 2, 2017 updated at October 19, 2019.
One of the possible ways of configuring to reduce costs while performing any incremental backup of a database is to enable the Block Change Tracking feature. Thus, when there is the execution of this type of backup the RMAN uses the file that was created when this feature is enabled only to save the blocks that have been changing in the database and then increasing the performance saving costs during the execution. Therefore, in this post, I will show how to enable this option (All commands below were executed inside of SQLPLUS utility):
1- Check if the option is enabled or not:
set pages 2000 set lines 200 SELECT status, filename FROM V$BLOCK_CHANGE_TRACKING 2 ; STATUS FILENAME DISABLED
2- Configure the DB_CREATE_FILE_DEST parameter:
ALTER SYSTEM SET DB_CREATE_FILE_DEST = '/u01/app/oracle/oradata';
3- Enable block change tracking for the database:
ALTER DATABASE ENABLE BLOCK CHANGE TRACKING;
4- See the option enabled:
SELECT status, filename FROM V$BLOCK_CHANGE_TRACKING; STATUS FILENAME ENABLED /u01/app/oracle/oradata/TECHDB/changetracking/o1_mf_gtptrbp4_.chg
Hi! I am Bruno, a Brazilian born and bred. Former Oracle ACE, Computer Scientist, MSc in Data Science, over ten years of experience in companies such as IBM, Epico Tech, and Playtech based in three different countries (Brazil, Hungary, and Sweden) and joined projects remotely in many others. I am super excited to show you my interest in Databases, Cloud, Data Science, Data Engineering, Bigdata, AI, Programming, Software Engineering, and data in general.
(Continue reading)