Skip to main content

Search

Welcome to Tibero GTS!

TAC Installation Guide (TAS)

Document Type | Technical Information

Category | Installation

Applicable Product Version | Tibero 7.2.4

Document Number | TINTI038

 

Overview

1. What is TAC?

TAC (Tibero Active Cluster) is an Active-Active type cluster that links multiple Tiberos for a single DB workload.
TAC automatically fails over to a functioning node in case of failures in the DB engine, OS, system, or Public Network, maintaining a zero-downtime system and enabling rapid recovery.
Depending on the workload, it can be configured as a large-scale triple-redundant node beyond dual redundancy to deliver optimal performance when processing large volumes of data.
TAC allows flexible capacity adjustment through horizontal scaling of Active nodes and enhances system performance by minimizing Disk I/O using Global Cache.
 

2. TAC Installation Architecture

 

Method

TAC Installation (using TAS)

1. Installation Environment

1-1) Installation Sequence

Step

Item

Description

1

Basic SettingsEnvironment variables, CM, Tibero tip settings

2

Cluster Membership Layer ConfigurationProcess of connecting each node into the cluster

3

Cluster Resource Layer ConfigurationRegistering resources used by the nodes

4

DB ConfigurationDatabase setup
 

1-2) Node Environment

Item

Node 1

Node 2

Description

OS

tibero0tibero1Hostname of each server
UsertiberotiberoOS user where Tibero will be installed
Shared VolumeConfigured per server environment
Typically, filesystems are created by the OS itself, but shared filesystems are created and managed through cluster solutions.
For example, vxfs is created via Veritas solution, gpfs via hcmp, and gfs2 via pacemaker.

TAC

tibero0tibero1Tibero Instance Name
DB_NAMEtiberoTibero Database Name
LISTENER_PORT86298629Tibero Listener Port
Public IP

192.168.50.121

NIC: enp0s3

192.168.50.122

NIC: enp0s3

Public IP
LOCAL_CLUSTER_ADDR10.10.10.12110.10.10.122Inter-Connect IP
LOCAL_CLUSTER_PORT1862918629Communication port between Tibero nodes
CM_PORT2862928629Communication port for cmrctl command and Tibero↔CM communication

TAS

tas0tas1TAS Tibero Instance Name
TAS Tibero port76297629TAS Tibero Port
LOCAL_CLUSTER_PORT1762917629TAS Tibero Cluster Port

CM

cm0cm1TBCM SID
CM Inter-Connect PORT2900029000

Communication port between TBCM nodes

(defined during cmrctl add command)

CM_UI_PORT2862928629Port used to connect to TBCM for status check when executing cmrctl commands

 

1-3) Environment Variables

Since TAS requires starting an additional dedicated instance, a separate environment variable file (.bash_profile_tas) is created.

Item

Node 1

Node 2

TAC

(tibero)$ cat .bash_profile

### Tibero ENV ###
export TB_HOME=/home/tibero/tibero7
export TB_SID=tibero0
export PATH=$TB_HOME/bin:$TB_HOME/client/bin:$PATH
export LD_LIBRARY_PATH=$TB_HOME/lib:$TB_HOME/client/lib:$LD_LIBRARY_PATH

### Tibero Cluster Manager ENV ###
export CM_SID=cm0
export CM_HOME=$TB_HOME

(tibero)$ cat .bash_profile

### Tibero ENV ###
export TB_HOME=/home/tibero/tibero7
export TB_SID=tibero1
export PATH=$TB_HOME/bin:$TB_HOME/client/bin:$PATH
export LD_LIBRARY_PATH=$TB_HOME/lib:$TB_HOME/client/lib:$LD_LIBRARY_PATH

### Tibero Cluster Manager ENV ###
export CM_SID=cm1
export CM_HOME=$TB_HOME

TAS

(tibero)$ cat .bash_profile_tas

### TAS ENV ###
export PS1="[tas@\h \W]\$ "
export TB_HOME=/home/tibero/tibero7
PATH=$PATH:$HOME/.local/bin:$HOME/bin
export PATH=$PATH:$TB_HOME/bin:$TB_HOME/client/bin
export CM_HOME=$TB_HOME
export CM_SID=cm0
export TB_SID=tas0

(tibero)$ cat .bash_profile_tas

### TAS ENV ###
export PS1="[tas@\h \W]\$ "
export TB_HOME=/home/tibero/tibero7
PATH=$PATH:$HOME/.local/bin:$HOME/bin
export PATH=$PATH:$TB_HOME/bin:$TB_HOME/client/bin
export CM_HOME=$TB_HOME
export CM_SID=cm1
export TB_SID=tas1

 

 

1-4) Check Shared Disks for TAS

The following shared disk devices are used for TAS.

[root@tibero ~]# lsblk
NAME                 MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sdb      8:16   0   10G  0 disk 
sdc      8:32   0   10G  0 disk 

[root@tibero ~]# udevadm info --query=all --name=/dev/sdb | grep -E 'ID_SERIAL' | grep -v "SHORT" | sed 's/E: ID_SERIAL=//g'
cf9d02b4-4d402877
[root@tibero ~]# udevadm info --query=all --name=/dev/sdc | grep -E 'ID_SERIAL' | grep -v "SHORT" | sed 's/E: ID_SERIAL=//g'
5b02310d-1158d586


[root@tibero ~]# vi /etc/udev/rules.d/tas.rules
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
ACTION=="add|change", KERNEL=="sd?", ENV{ID_SERIAL}=="cf9d02b4-4d402877", SYMLINK+="tasdisk/data001", OWNER=="tibero", GROUP=="dba", MODE=="0660"
ACTION=="add|change", KERNEL=="sd?", ENV{ID_SERIAL}=="5b02310d-1158d586", SYMLINK+="tasdisk/data002", OWNER=="tibero", GROUP=="dba", MODE=="0660"
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――

 

2. Installation

2-1) $CM.tip Configuration

Node 1

Node 2

(tibero)$ vi $TB_HOME/config/$CM_SID.tip

CM_NAME=cm0
CM_UI_PORT=28629
CM_RESOURCE_FILE=/home/tibero/tibero7/config/cm0_res_file  ## Local area for each node

(tibero)$ vi $TB_HOME/config/$CM_SID.tip

CM_NAME=cm1
CM_UI_PORT=28629
CM_RESOURCE_FILE=/home/tibero/tibero7/config/cm1_res_file  ## Local area for each node

 

2-2) $TB.tip Configuration

Item

Node 1

Node 2

TAC

(tibero)$ vi $TB_HOME/config/$TB_SID.tip

DB_NAME=tibero
LISTENER_PORT=8629
CONTROL_FILES="+DS0/control1/c1.ctl","+DS0/control2/c2.ctl"
DB_CREATE_FILE_DEST="+DS0/tbdata"
LOG_ARCHIVE_DEST="+DS0/tbarch"
LOG_ARCHIVE_FORMAT="log-t%t-r%r-s%s.arc"

############Memory & Session###################
TOTAL_SHM_SIZE=2G
MEMORY_TARGET=4G
MAX_SESSION_COUNT=20
LOG_BUFFER=10M

########cluster################
THREAD=0
UNDO_TABLESPACE=UNDO0
CLUSTER_DATABASE=Y
LOCAL_CLUSTER_ADDR=10.10.10.121
LOCAL_CLUSTER_PORT=18629
CM_PORT=28629

########TAS################
USE_ACTIVE_STORAGE=Y
AS_PORT=7629

(tibero)$ vi $TB_HOME/config/$TB_SID.tip

DB_NAME=tibero
LISTENER_PORT=8629
CONTROL_FILES="+DS0/control1/c1.ctl","+DS0/control2/c2.ctl"
DB_CREATE_FILE_DEST="+DS0/tbdata"
LOG_ARCHIVE_DEST="+DS0/tbarch"
LOG_ARCHIVE_FORMAT="log-t%t-r%r-s%s.arc"

############Memory & Session###################
TOTAL_SHM_SIZE=2G
MEMORY_TARGET=4G
MAX_SESSION_COUNT=20
LOG_BUFFER=10M

########cluster################
THREAD=1
UNDO_TABLESPACE=UNDO1
CLUSTER_DATABASE=Y
LOCAL_CLUSTER_ADDR=10.10.10.122
LOCAL_CLUSTER_PORT=18629
CM_PORT=28629

########TAS################
USE_ACTIVE_STORAGE=Y
AS_PORT=7629

TAS

(tibero)$ . ~/.bash_profile_tas
(tibero)$ vi $TB_HOME/config/$TB_SID.tip

DB_NAME=tas
LISTENER_PORT=7629
TOTAL_SHM_SIZE=600M
MEMORY_TARGET=1G

INSTANCE_TYPE=AS
AS_DISKSTRING="/dev/tasdisk/*"

CLUSTER_DATABASE=Y
THREAD=0

CM_PORT=28629
LOCAL_CLUSTER_ADDR=192.168.50.121
LOCAL_CLUSTER_PORT=17629

(tibero)$ . ~/.bash_profile_tas
(tibero)$ vi $TB_HOME/config/$TB_SID.tip

DB_NAME=tas
LISTENER_PORT=7629
TOTAL_SHM_SIZE=600M
MEMORY_TARGET=1G

INSTANCE_TYPE=AS
AS_DISKSTRING="/dev/tasdisk/*"

CLUSTER_DATABASE=Y
THREAD=1

CM_PORT=28629
LOCAL_CLUSTER_ADDR=192.168.50.122
LOCAL_CLUSTER_PORT=17629

 

2-3) tbdsn.tbr Configuration

Node 1

Node 2

(tibero)$ vi $TB_HOME/client/config/tbdsn.tbr

tibero0=(
   (INSTANCE=(HOST=localhost)
             (PORT=8629)
             (DB_NAME=tibero)
   )
)

tas0=(
   (INSTANCE=(HOST=localhost)
             (PORT=7629)
             (DB_NAME=tas)
   )
)

(tibero)$ vi $TB_HOME/client/config/tbdsn.tbr

tibero1=(
   (INSTANCE=(HOST=localhost)
             (PORT=8629)
             (DB_NAME=tibero)
   )
)

tas1=(
   (INSTANCE=(HOST=localhost)
             (PORT=7629)
             (DB_NAME=tas)
   )
)

 

2-4) Register CM Membership Layer Resource

Node

Item

Command

Node 1

Start TBCM(tibero)$ tbcm -b      # Run as root if VIP environment is used
Register Network(tibero)$ cmrctl add network --name net0 --ipaddr 10.10.10.121 --portno 29000
(tibero)$ cmrctl add network --name pub0 --nettype public --ifname enp0s3
Register Cluster(tibero)$ cmrctl add cluster --name cls0 --incnet net0 --pubnet pub0 --cfile "+/dev/tasdisk/*"
Start Cluster(tibero)$ cmrctl start cluster --name cls0

Node 2

Start TBCM(tibero)$ tbcm -b      # Run as root if VIP environment is used
Register Network(tibero)$ cmrctl add network --name net1 --ipaddr 10.10.10.122 --portno 29000
(tibero)$ cmrctl add network --name pub1 --nettype public --ifname enp0s3
Register Cluster(tibero)$ cmrctl add cluster --name cls0 --incnet net1 --pubnet pub1 --cfile "+/dev/tasdisk/*"
Start Cluster(tibero)$ cmrctl start cluster --name cls0

 

2-5) Register CM Resource TAS Layer Resource

Register the TAS Resource.

Node

Item

Command

Node 1

Register TAS Service(tibero)$ cmrctl add service --name tas --cname cls0 --type as
Register TAS(tibero)$ cmrctl add as --name tas0 --svcname tas --dbhome $TB_HOME --envfile $HOME/.bash_profile_tas

Node 2

Register TAS(tibero)$ cmrctl add as --name tas1 --svcname tas --dbhome $TB_HOME --envfile $HOME/.bash_profile_tas

 

 

2-6) Create TAS

TAS is created on Node 1.

Node

Item

Command

Node 1

Apply TAS profile(tibero)$ . ~/.bash_profile_tas
Start TAS instance in nomount mode(tibero)$ tbboot nomount
Create Diskspace(tibero)$ tbsql sys/tibero
SQL> CREATE DISKSPACE DS0
EXTERNAL REDUNDANCY
FAILGROUP FG1
DISK '/dev/tasdisk/data001' NAME data001,
    '/dev/tasdisk/data002' NAME data002 ;
Start TAS and add thread(tibero)$ tbboot
SQL> alter diskspace DS0 add thread 1 ;

Node 2

Apply TAS profile(tibero)$ . ~/.bash_profile_tas
Start TAS instance(tibero)$ tbboot 

 

 

2-7) Register CM Resource DB Layer Resource

Since services are shared, registration on Node 2 is omitted.

Node

Item

Command

Node 1

Register DB Service(tibero)$ cmrctl add service --name tibero --cname cls0 --type db
Register DB(tibero)$ cmrctl add db --name tibero0 --svcname tibero --dbhome $TB_HOME --envfile /home/tibero/.bash_profile
Register VIP(tibero)$ cmrctl add vip --name vip0 --node cm0 --svcname tibero --ipaddr 192.168.50.126/255.255.255.0 --bcast 192.168.50.255

Node 2

Register DB(tibero)$ cmrctl add db --name tibero1 --svcname tibero --dbhome $TB_HOME --envfile /home/tibero/.bash_profile
Register VIP(tibero)$ cmrctl add vip --name vip1 --node cm1 --svcname tibero --ipaddr 192.168.50.127/255.255.255.0 --bcast 192.168.50.255

Note

VIP registration is not mandatory, but if registered, TBCM must be started with root privileges.

 

VIP Registration Command

cmrctl add vip --name <vip_name> --node <cm_sid> --svcname <database_name> --ipaddr <virtual_IP>/<Netmask> --bcase <broadcast>

 

 

2-8) Create Database

Node

Item

Command

Node 1

Start DB in nomount mode(tibero)$ . ~/.bash_profile
(tibero)$ tbboot nomount (or cmrctl start db --name tibero0 --option "-t nomount")
Create Database

(tibero)$ tbsql sys/tibero

SQL> create database
user sys identified by tibero
character set UTF8  -- UTF8, EUCKR, ASCII, MSWIN949
logfile group 0 ('redo001.redo','redo002.redo') size 300M,
       group 1 ('redo011.redo','redo012.redo') size 300M,
       group 2 ('redo021.redo','redo022.redo') size 300M
maxdatafiles 1024
maxlogfiles 100
maxlogmembers 8
archivelog
   datafile 'system001.dtf' size 100m autoextend on
   default temporary tablespace TEMP tempfile 'temp001.dtf' size 100m autoextend on next 32M
   default tablespace USR datafile 'usr001.dtf' size 100m autoextend on
   undo tablespace UNDO0 datafile 'undo001.dtf' size 100m autoextend on next 32M
   syssub datafile 'syssub.dtf' size 10m reuse autoextend on ;

Start DB(tibero)$ tbboot
Run system_install.sh(tibero)$ sh $TB_HOME/scripts/system_install.sh -p1 tibero -p2 syscat
Add Undo and Redo on Node 2

(tibero)$ tbsql sys/tibero

SQL> create undo tablespace UNDO1 datafile '+DS0/tbdata/undo011.dtf' size 100m autoextend on next 32M;
SQL> alter database add logfile thread 1 group 3 ('+DS0/tbdata/redo101.redo', '+DS0/tbdata/redo102.redo') size 300M;
SQL> alter database add logfile thread 1 group 4 ('+DS0/tbdata/redo111.redo', '+DS0/tbdata/redo112.redo') size 300M;
SQL> alter database add logfile thread 1 group 5 ('+DS0/tbdata/redo121.redo', '+DS0/tbdata/redo122.redo') size 300M;

Activate Node 2SQL> alter database enable public thread 1 ;

Node 2

Start DB(tibero)$ . ~/.bash_profile
(tibero)$ tbboot 

 

2-9) Verification

Item

Details

Cluster

DB

 

Reference

1. $CM_SID.tip Configuration

Item

Required
or Not

Description

CM_NAMERequiredName used as node identifier when creating the cluster. 
Different nodes’ CMs must have different values.
CM_UI_PORTRequiredNetwork port number used to connect to CM when executing cmrctl commands.
CM_RESOURCE_FILERequiredPath to the CM resource file.
LOG_LVL_CMOptionalSpecifies the logging level of CM. 
Higher values cause CM to log more; accepts integer values from 1 to 6. (Default: 2)
CM_LOG_DESTOptionalSpecifies the directory where CM logs are stored.
Must be an absolute path. 
(Default: $CM_HOME/instance/$CM_SID/)
CM_HEARTBEAT_EXPIREOptionalDefines the standard time for CM to detect issues with other nodes’ CM.
After this time, the cluster member is considered out. (Unit: seconds, Default: 300)
CM_WATCHDOG_EXPIREOptionalSpecifies the expiration period if the watchdog function between Tibero and CM is enabled.
If CM does not operate within this time, Tibero automatically shuts down.
Should be set lower than CM_HEARTBEAT_EXPIRE (Unit: seconds, Default: 290)
CM_FENCEOptional

Determines whether to run the CM fence daemon.

If CM performs I/O longer than the time specified by CM_WATCHDOG_EXPIRE, other CMs exclude this CM’s node from the cluster, requiring a reboot of this node’s OS.
The CM Guard daemon prevents this node from performing I/O and requires root privileges to run; to set this to Y, CM must run as root. Default: N

 
 
 

Related to