Skip to main content
๐Ÿ““ Tibero Online Manual Click here ๐Ÿ““

Search

Welcome to Tibero GTS!

BCT (Block Change Tracking) Setup and Disable Method (TAC Environment)

Document Type | Technical Information

Category | Backup/Recovery

Applicable Product Version | 7FS02PS

Document Number | TBATI003

 

Overview

This document explains the setup and disable methods for Block Change Tracking (hereafter BCT) in a TAC environment. 

Note
  • BCT can be used during Incremental Backup.
  • BCT records changes in data files since the last backup point and is used during backup. Because it is easy to track which blocks need to be backed up, the execution speed of Incremental Backup can be improved. 

 

Method

Caution
In a TAC environment, the BCT file path must be configured on a shared volume. 
 

1. Add the following content to the bottom of the Tip file (Modification required on both NODE 1 and 2)

BLOCK_CHANGE_TRACKING="+DS0/BCT/emp_change.bct"  #-- Configure BCT file path on shared volume
LGWR_USE_AIO=N

 

2. Enable BCT feature (Perform on either NODE 1 or 2, only one node)

SQL> ALTER SYSTEM ENABLE BLOCK CHANGE TRACKING; 

System altered.

 

3. Connect to TAS and verify the BCT file

$ tbascmd 28629

ASCMD 7 


TmaxTibero Corporation Copyright (c) 2020-. All rights reserved.


[18:30]ASCMD +> ls
+DS0



Number of diskspaces found: 1


[18:30]ASCMD +> cd +DS0
[18:30]ASCMD +DS0> ls
tac/
BCT/

Number of files found: 2

[18:30]ASCMD +DS0> cd BCT 
[18:30]ASCMD +DS0/BCT> ls
emp_change.bct                #-- Confirm BCT file

Number of files found: 1

[18:30]ASCMD +DS0/BCT> q

 

4. Perform tbrmgr incremental backup

$ tbrmgr backup -i --with-archivelog -o /db/backup


==============================================================================
=   Recovery Manager(RMGR) starts                                            =
=                                                                            =
=   TmaxTibero Corporation Copyright (c) 2020-. All rights reserved.         =
==============================================================================
archive log check succeeded
RMGR '-o' option used
: backing up to /db/backup

==============================================================================
   RMGR - Backup (INCREMENTAL)
==============================================================================
Initializing the backup progress, it may take few minutes...

BACKUP  (set_id:  3, ts_id:  0, df_id:  0)
100.0% |===============================>|     677/677     blks    0.00s
Synchronizing...
BACKUP  (set_id:  3, ts_id:  1, df_id:  1)
100.0% |===============================>|     124/124     blks    1.01s
Synchronizing...
BACKUP  (set_id:  3, ts_id:  3, df_id:  2)
100.0% |===============================>|       8/8       blks    0.00s
Synchronizing...
BACKUP  (set_id:  3, ts_id:  4, df_id:  3)
100.0% |===============================>|     391/391     blks    0.00s
Synchronizing...
BACKUP  (set_id:  3, ts_id:  5, df_id:  4)
100.0% |===============================>|     247/247     blks    0.00s
Synchronizing...



Switching an online logfile...
Backing up archive logfiles...
Archivelog log-tac1-t0-r0-s12.arc (thread: 0, set_id: 3, low_tsn: 67942, next_tsn: 68406) backed up
Archivelog log-tac1-t1-r0-s10.arc (thread: 1, set_id: 3, low_tsn: 67983, next_tsn: 68406) backed up

Archive logfiles backup succeeded

Backing up the control file...
Control file backup succeeded

Database backup succeeded

RMGR backup ends

 

5. Disable BCT feature (Perform on either NODE 1 or 2, only one node)

SQL> ALTER SYSTEM DISABLE BLOCK CHANGE TRACKING;

System altered.

 

 

 

 

Related to