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

Search

Welcome to Tibero GTS!

How to Configure TSC-Standby Redo Log Group

Document Type | Technical Information 

Field | Installation

Applicable Product Version | 7FS02PS

Document Number | TINTI002

 

Overview

In the existing TSC (Tibero Standby Cluster) environment, there is a possibility of a bottleneck where the LNR process does not receive Redo Log from LNW during synchronization.
The Standby Redo Log Group feature improves performance by allowing the Standby DB to refer to the Standby Redo Log Group instead of directly viewing the Online Redo Log, enabling Redo reception during synchronization.
 

Constraints

  1. The number and size of Online Redo Log Files in the Primary DB and Standby Redo Log Files in the Standby DB must be configured identically.
  2. The number of Redo Log Groups and Standby Redo Log Groups must be the same.
  3. Multiplexing of Standby Redo Logfiles is not supported.
  4. The disable public standby redo thread feature is not supported.
 

Parameter(Standby DB)

USE_STANDBY_REDO_LOG=Y

 

Method

1. Configure TSC

The TSC between Primary and Standby must be fully configured.
 

2. Add settings to Primary DB and Standby DB $TB_SID.tip 

-- Primary DB
LOG_REPLICATION_MODE=PERFORMANCE
LOG_REPLICATION_DEST_1="192.168.179.66:8862 LGWR ASYNC"

-- Standby DB
_STANDBY_CONN_PORT=8862
_STANDBY_NETWORK_TIMEOUT=60
USE_STANDBY_REDO_LOG=Y
 

3. Standby DB: Add Standby Redo Log Group

Check the Redo Log Groups and sizes, then add Standby Redo Log Groups with the same group numbers and count as the Redo Log Files.
SQL> alter database add standby logfile thread 0 group 0 '/home/tibero7/database/tibero1/srl01.redo' size 50M;
SQL> alter database add standby logfile thread 0 group 1 '/home/tibero7/database/tibero1/srl02.redo' size 50M;
SQL> alter database add standby logfile thread 0 group 2 '/home/tibero7/database/tibero1/srl03.redo' size 50M;
 
Caution
You must configure the same number and group numbers as the Online Redo Logs of the Primary DB.
 

4. Standby DB: Enable Redo Log Thread

SQL> alter database enable public standby redo thread 0;
 

5. Standby DB: Perform MR (Media Recovery)

 SQL> alter database recover automatic for standby;
 

6. Standby DB: Shut down and start in Recovery mode

$ tbdown immediate
$ tbboot recovery

-- Change to read only mode
SQL> alter database open read only continue recovery;
 

7. Primary DB: Start in Normal mode 

 $ tbboot
 

8. Check synchronization status

The connection status from Primary DB to Standby DB is properly set and currently in CONNECTED state.

$ tbsql tibero/tmax
SQL> select * from v$standby_dest;
 
 
 

Related to