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

Search

Welcome to Tibero GTS!

Building a Non-Stop Synchronization Environment Using ProSync Bidirectional CM FailOver (1/4)

Document Type | Technical Information

Category | Installation

Applicable Product Versions | Tibero7.2.3, ProSync 4.6.0

Document Number | PINTI003

 

Overview

This guide on Building a Non-Stop Synchronization Environment Using ProSync Bidirectional CM FailOver` is described over a total of 4 parts.

This document covers Part 1: ProSync Bidirectional Installation.

  • Part 1: ProSync Bidirectional Installation
  • Part 2: ProSync Bidirectional Synchronization Verification 
  • Part 3: CM Fail-Over Configuration
  • Part 4: CM FailOver Operation

 

Environment

OSRocky Linux 8.10
Tibero VersionTibero 7.2.4 (build seq 305455)
ProSync VersionProSync 4.6.0 (build seq 308985)

 

 

Method

Bidirectional CM FailOver Environment Setup

  • Proceed assuming that TAC to TAC installation is already completed.
  • The ProSync engine for CM FailOver configuration must also be located on a shared file system.
NodeDatabase NameInstance NameIP Address
node1db12db12010.10.10.65
node2db12110.10.10.66
node3db34db34010.10.10.67
node4db34110.10.10.68
TAC to TAC Database

 

A Set ProSync Synchronization Configuration

NodeAgent NameProSync Process
node1agent1_12_34ext1, llob
node2agent2_12_34ext2, llob(standby)
node3agent3_12_34apply
node4agent4_12_34apply(standby)
A Set ProSync: node1, node2 to node3, node4

β€» Caution

When using CM FailOver, the ProSync engine path must be located on a shared file system.

Otherwise, synchronization will fail after FailOver occurs.

tree $PRS_HOME/var/$INSTANCE_ID
β”œβ”€β”€ alloc
β”œβ”€β”€ lr1
β”‚   β”œβ”€β”€ redo_data_16_0.tlr
β”‚   β”œβ”€β”€ redo_data_17_0.tlr
β”‚   β”œβ”€β”€ redo_data_18_0.tlr
β”‚   └── tli1.log
└── lr2
    β”œβ”€β”€ redo_data_10_0.tlr
    β”œβ”€β”€ redo_data_11_0.tlr
    └── tli2.log

 

B Set ProSync Synchronization Configuration

NodeAgent NameProSync Process
node3agent1_34_12ext1, llob
node4agent2_34_12ext2, llob(standby)
node1agent3_34_12apply
node2agent4_34_12apply(standby)
B Set ProSync: node3, node4 to node1, node2

β€» Caution

When using CM FailOver, the ProSync engine path must be located on a shared file system.

Otherwise, synchronization will fail after FailOver occurs.

tree $PRS_HOME/var/$INSTANCE_ID
β”œβ”€β”€ alloc
β”œβ”€β”€ lr1
β”‚   β”œβ”€β”€ redo_data_16_0.tlr
β”‚   β”œβ”€β”€ redo_data_17_0.tlr
β”‚   β”œβ”€β”€ redo_data_18_0.tlr
β”‚   └── tli1.log
└── lr2
    β”œβ”€β”€ redo_data_10_0.tlr
    β”œβ”€β”€ redo_data_11_0.tlr
    └── tli2.log

 

 

Installation

Common Preparation for A and B Sets

User Profile

  • Apply the following profile information to all Nodes
  • For A Set operation, apply prs12 and then proceed
  • For B Set operation, apply prs34 and then proceed
#############################
# TIBERO ProSync environment variable
#############################
prs12(){
    export PRS_HOME=/share/prosync4_12_34
    export TOP_ID=prs_12_34
    export INSTANCE_ID=$TOP_ID
    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$PRS_HOME/lib:$PRS_HOME/client/lib
    export PATH=$PATH:$LD_LIBRARY_PATH:$PRS_HOME/bin
}

prs34(){
    export PRS_HOME=/share/prosync4_34_12
    export TOP_ID=prs_34_12
    export INSTANCE_ID=$TOP_ID
    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$PRS_HOME/lib:$PRS_HOME/client/lib
    export PATH=$PATH:$LD_LIBRARY_PATH:$PRS_HOME/bin
}

#### ProSync alias
alias phome='cd $PRS_HOME'
alias plog='cd $PRS_HOME/var/'
alias pcfg='cd $PRS_HOME/config'

 

User SQL

  • Execute TAC SQL on node1 and node2 (only on one node)
  • Execute TAC SQL on node3 and node4 (only on one node)
create user user_12_34 identified by 'tibero';
grant connect, resource to user_12_34;

create user user_34_12 identified by 'tibero';
grant connect, resource to user_34_12;

 

Database $TB_SID.tip

  • Since bidirectional synchronization settings are applied, apply these parameters to all Nodes.
  • Database restart is required to apply parameters.
############ ProSync
#### Must
_ENABLE_LOG_MINER=Y
_DDL_TRIGGER_ENABLE=Y
_SPAN_UNDO=N
_ENABLE_MRG_TDD_MU=N

 

Cluster $CM_SID.tip

  • CM_ID is a parameter used when enabling CM FailOver functionality.
    • CM restart is required
  • Apply in advance for the next chapter.
# node1 $CM_SID.tip
CM_ID=0

# node2 $CM_SID.tip
CM_ID=1

# node3 $CM_SID.tip
CM_ID=0

# node4 $CM_SID.tip
CM_ID=1

 

tbdsn.tbr

  • Set configuration values in advance to use database connection information during ProSync installation.
################################
# Database Name
################################
db12=(
  (INSTANCE=(HOST=10.10.10.65)
  (PORT=8629)
  (DB_NAME=db12)
  )
  (INSTANCE=(HOST=10.10.10.66)
  (PORT=8629)
  (DB_NAME=db12)
  )
)

db34=(
  (INSTANCE=(HOST=10.10.10.67)
  (PORT=8629)
  (DB_NAME=db34)
  )
  (INSTANCE=(HOST=10.10.10.68)
  (PORT=8629)
  (DB_NAME=db34)
  )
)
################################
# Instance Name
################################
db120=(
  (INSTANCE=(HOST=10.10.10.65)
  (PORT=8629)
  (DB_NAME=db12)
  )
  (INSTANCE=(HOST=10.10.10.66)
  (PORT=8629)
  (DB_NAME=db12)
  )
)

db121=(
  (INSTANCE=(HOST=10.10.10.66)
  (PORT=8629)
  (DB_NAME=db12)
  )
  (INSTANCE=(HOST=10.10.10.65)
  (PORT=8629)
  (DB_NAME=db12)
  )
)
################################
db340=(
  (INSTANCE=(HOST=10.10.10.67)
  (PORT=8629)
  (DB_NAME=db34)
  )
  (INSTANCE=(HOST=10.10.10.68)
  (PORT=8629)
  (DB_NAME=db34)
  )
)

db341=(
    (INSTANCE=(HOST=10.10.10.68)
	(PORT=8629)
	(DB_NAME=db34)
    )
    (INSTANCE=(HOST=10.10.10.67)
	(PORT=8629)
	(DB_NAME=db34)
    )
)
################################

 

ProSync Binary

  • Prepare binaries for each Node.
    • For CM FailOver usage, both A Set and B Set must be located on a shared file system.
su - tibero
cd /share/
tar -xvzf prosync4-bin-linux64_3.10-308985-20260120151605.tar.gz

# A Set ProSync Engine
/share/prosync4_12_34

# B Set ProSync Engine
/share/prosync4_34_12

 

  • For both A and B Sets, copy the configuration files located in templates/ to under install/.
cd $PRS_HOME/install
cp $PRS_HOME/install/templates/prs_install_agent.cfg.template prs_install_agent.cfg
cp $PRS_HOME/install/templates/prs_install.cfg.template prs_install.cfg
cp $PRS_HOME/install/templates/prs_obj_group1.list.template prs_obj_group1.list

ls -lt $PRS_HOME/install
... omitted ...

-rw-r--r-- 1 tibero dba    957 Mar 17 05:32 prs_install_agent.cfg
-rw-r--r-- 1 tibero dba   2186 Mar 17 05:29 prs_install.cfg
-rw-r--r-- 1 tibero dba    208 Mar 12 00:46 prs_obj_group1.list
... omitted ...

 

A Set ProSync Preparation

prs_install_agent.cfg

  • Prepare Agent information for each Node in advance.
  • Prepare Agent settings in the `prs_install_agent.cfg` file in advance.
AGENT_CNT=4

AGENT_ID_0=agent1_12_34
AGENT_HOST_0=10.10.10.65
AGENT_PORT_0=7600
AGENT_CM_GROUP_0=grp_src_12_34
AGENT_CM_ID_0=0

AGENT_ID_1=agent2_12_34
AGENT_HOST_1=10.10.10.66
AGENT_PORT_1=7601
AGENT_CM_GROUP_1=grp_src_12_34
AGENT_CM_ID_1=1

AGENT_ID_2=agent3_12_34
AGENT_HOST_2=10.10.10.67
AGENT_PORT_2=7602
AGENT_CM_GROUP_2=grp_tar_12_34
AGENT_CM_ID_2=0

AGENT_ID_3=agent4_12_34
AGENT_HOST_3=10.10.10.68
AGENT_PORT_3=7602
AGENT_CM_GROUP_3=grp_tar_12_34
AGENT_CM_ID_3=1

 

prs_install.cfg

  • Once ProSync Agent installation is successful, install the ProSync Instance.
  • Prepare ProSync Instance settings in the prs_install.cfg file in advance.
# ProSync INSTANCE settings
INSTANCE_ID=prs_12_34
PRS_USER=prosync_12_34
PRS_PWD=tmax

# ProSync Process settings
AGENT_LIST_DELIMITER=,
EXT_CNT=2
EXT_AGENT_ID_LIST_0=agent1_12_34,agent2_12_34
EXT_AGENT_ID_LIST_1=agent2_12_34,agent1_12_34
APPLY_PORT=7620
APPLY_AGENT_ID_LIST=agent3_12_34,agent4_12_34
LLOB_PORT=7630
LLOB_AGENT_ID_LIST=agent1_12_34,agent2_12_34

# Source information
SRC_DB_TYPE=TIBERO
SRC_DB_NAME=db12
SRC_INSTALL_USER=sys
SRC_INSTALL_PWD=tibero
SRC_DB_CNT=2
SRC_DB_ALIAS_0=db120
SRC_DB_ALIAS_1=db121

# Target information
TAR_DB_TYPE=TIBERO
TAR_DB_NAME=db34
TAR_INSTALL_USER=sys
TAR_INSTALL_PWD=tibero
TAR_DB_CNT=2

 

prs_obj_group1.list

  • Set the synchronization list in advance in the prs_obj_group1.list file.
  • If you want to set synchronization targets later, you can leave the value blank.
USER_12_34.%

 

A Set ProSync Installation

ProSync Agent Installation

  • Install the ProSync Agent first.
su - tibero
prs12
cd $PRS_HOME/install
sh prs_install_agent.sh
  • Detailed installation output messages omitted
    • Check the output messages to confirm successful installation.
********************************************************************************
* Agent Install Step (4/4)
* Creating files for CM
********************************************************************************
AGENT_CM_ID detected
generating prs_0.sh...
PRS_HOME=/share/prosync4_12_34
AGENT_ID=agent1_12_34
prs_0.sh has created in $PRS_HOME/bin/
AGENT_CM_ID detected
generating prs_1.sh...
PRS_HOME=/share/prosync4_12_34
AGENT_ID=agent2_12_34
prs_1.sh has created in $PRS_HOME/bin/
AGENT_CM_ID detected
generating prs_0.sh...
PRS_HOME=/share/prosync4_12_34
AGENT_ID=agent3_12_34
prs_0.sh has created in $PRS_HOME/bin/
AGENT_CM_ID detected
generating prs_1.sh...
PRS_HOME=/share/prosync4_12_34
AGENT_ID=agent4_12_34
prs_1.sh has created in $PRS_HOME/bin/
Agent installation Done.

 

ProSync Instance Installation

  • Install the ProSync Instance.
su - tibero
prs12
cd $PRS_HOME/install
sh prs_install.sh
  • Detailed installation output messages omitted
    • Check the output messages to confirm successful installation.
********************************************************************************
* ProSync is installed successfully on Tue, 17 Mar 2026 05:34:17 +0000.
*
*   PRS_HOME     = /share/prosync4_12_34
*   Binary Path  = /share/prosync4_12_34/bin
*   ProSync User = prosync_12_34
*
*   Archived Log Path     = /share/tac/tbarch0/
*   Archived Log Format   = log-t%t-r%r-s%s.arc
*   Initial log sequence# = 15
*
*   Archived Log Path     = /share/tac/tbarch1/
*   Archived Log Format   = log-t%t-r%r-s%s.arc
*   Initial log sequence# = 9
*
*   Initial change# (TSN) = 337479
*
********************************************************************************

 

β€» Caution

/share/prosync4_12_34/install/prs_common.sh: line 9: /share/prosync4_12_34/install/prs_util.sh: No such file or directory

Modify line 9 of $PRS_HOME/install/prs_common.sh file

# Before modification

  9 . prs_util.sh

# After modification

  9 . $PRS_HOME/install/prs_util.sh

 

B Set ProSync Preparation

prs_install_agent.cfg

  • Prepare Agent information for each Node in advance.
  • Prepare Agent settings in the `prs_install_agent.cfg` file in advance.
AGENT_CNT=4

AGENT_ID_0=agent1_34_12
AGENT_HOST_0=10.10.10.67
AGENT_PORT_0=8600
AGENT_CM_GROUP_0=grp_src_34_12
AGENT_CM_ID_0=0

AGENT_ID_1=agent2_34_12
AGENT_HOST_1=10.10.10.68
AGENT_PORT_1=8601
AGENT_CM_GROUP_1=grp_src_34_12
AGENT_CM_ID_1=1

AGENT_ID_2=agent3_34_12
AGENT_HOST_2=10.10.10.65
AGENT_PORT_2=8602
AGENT_CM_GROUP_2=grp_tar_34_12
AGENT_CM_ID_2=0

AGENT_ID_3=agent4_34_12
AGENT_HOST_3=10.10.10.66
AGENT_PORT_3=8602
AGENT_CM_GROUP_3=grp_tar_34_12
AGENT_CM_ID_3=1

 

prs_install.cfg

  • Once ProSync Agent installation is successful, install the ProSync Instance.
  • Prepare ProSync Instance settings in the prs_install.cfg file in advance.
# ProSync INSTANCE settings
INSTANCE_ID=prs_34_12
PRS_USER=prosync_34_12
PRS_PWD=tmax

# ProSync Process settings
AGENT_LIST_DELIMITER=,
EXT_CNT=2
EXT_AGENT_ID_LIST_0=agent1_34_12,agent2_34_12
EXT_AGENT_ID_LIST_1=agent2_34_12,agent1_34_12
APPLY_PORT=6620
APPLY_AGENT_ID_LIST=agent3_34_12,agent4_34_12
LLOB_PORT=6630
LLOB_AGENT_ID_LIST=agent1_34_12,agent2_34_12

# Source information
SRC_DB_TYPE=TIBERO
SRC_DB_NAME=db34
SRC_INSTALL_USER=sys
SRC_INSTALL_PWD=tibero
SRC_DB_CNT=2
SRC_DB_ALIAS_0=db340
SRC_DB_ALIAS_1=db341

# Target information
TAR_DB_TYPE=TIBERO
TAR_DB_NAME=db12
TAR_INSTALL_USER=sys
TAR_INSTALL_PWD=tibero
TAR_DB_CNT=2

 

prs_obj_group1.list

  • prs_obj_group1.list file contains the synchronization list set in advance.
  • If you want to set synchronization targets later, you can leave the value blank.
USER_34_12.%

 

B Set ProSync Installation

ProSync Agent Installation

  • Install the ProSync Agent first.
su - tibero
prs34
cd $PRS_HOME/install
sh prs_install_agent.sh
  • Detailed installation output messages omitted
    • Check the output messages to confirm successful installation.
********************************************************************************
* Agent Install Step (4/4)
* Creating files for CM
********************************************************************************
AGENT_CM_ID detected
generating prs_0.sh...
PRS_HOME=/share/prosync4_34_12
AGENT_ID=agent1_34_12
prs_0.sh has created in $PRS_HOME/bin/
AGENT_CM_ID detected
generating prs_1.sh...
PRS_HOME=/share/prosync4_34_12
AGENT_ID=agent2_34_12
prs_1.sh has created in $PRS_HOME/bin/
AGENT_CM_ID detected
generating prs_0.sh...
PRS_HOME=/share/prosync4_34_12
AGENT_ID=agent3_34_12
prs_0.sh has created in $PRS_HOME/bin/
AGENT_CM_ID detected
generating prs_1.sh...
PRS_HOME=/share/prosync4_34_12
AGENT_ID=agent4_34_12
prs_1.sh has created in $PRS_HOME/bin/
Agent installation Done.

 

ProSync Instance Installation

  • Install the ProSync Instance.
su - tibero
prs34
cd $PRS_HOME/install
sh prs_install.sh
  • Detailed installation output messages omitted
    • Check the output messages to confirm successful installation.
********************************************************************************
* ProSync is installed successfully on Tue, 17 Mar 2026 05:28:40 +0000.
*
*   PRS_HOME     = /share/prosync4_34_12
*   Binary Path  = /share/prosync4_34_12/bin
*   ProSync User = prosync_34_12
*
*   Archived Log Path     = /share/tac/tbarch0/
*   Archived Log Format   = log-t%t-r%r-s%s.arc
*   Initial log sequence# = 15
*
*   Archived Log Path     = /share/tac/tbarch1/
*   Archived Log Format   = log-t%t-r%r-s%s.arc
*   Initial log sequence# = 9
*
*   Initial change# (TSN) = 333768
*
********************************************************************************

 

β€» Caution

/share/prosync4_12_34/install/prs_common.sh: line 9: /share/prosync4_12_34/install/prs_util.sh: No such file or directory

Modify line 9 of $PRS_HOME/install/prs_common.sh file

# Before modification

  9 . prs_util.sh

# After modification

  9 . $PRS_HOME/install/prs_util.sh