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

Search

Welcome to Tibero GTS!

TTA BMT Function Verification Scenario (TAC Configuration) - Redundancy Function

Document Type | Technical Information

Category | Administration

Applicable Product Versions | Tibero5, Tibero6, Tibero7

Document Number | TADTI214

 

Overview

This document describes a BMT scenario to verify the proper operation of the redundancy function in a TAC environment.

 

 

Method

DBMS Failure Failover

This section explains the failover function for DBMS instance failures.

 

Procedure

Step

Scenario

1Client connection setup (tbdsn.tbr)
2Confirm instance connection
3Prepare data for query execution
4Execute query
5Instance failure (process kill)
6Verify failover

 

Results

Step

Scenario

1Client connection setup (tbdsn.tbr)
tta1=(
(INSTANCE=(HOST=192.168.51.161)
(PORT=8639)
(DB_NAME=tta)
)
(INSTANCE=(HOST=192.168.51.162)
(PORT=8639)
(DB_NAME=tta)
)
(USE_FAILOVER=(TYPE=CURSOR)
(RETRY=3)
)
)
2Confirm instance connection
tbsql sys/tibero@tta1
select instance_name from v$instance;
INSTANCE_NAME                           
----------------------------------------
tta1
3Prepare data for query execution
drop table tibero.test;
drop table tibero.test1;
create table tibero.test as
select level as col1, level || '_test' as col2,
trunc(level/100) as col3
from dual connect by level < 10000001;
create table tibero.test1 as
select level as col1, level || '_test' as col2,
trunc(level/100) as col3
from dual connect by level < 10000001;
4Execute query

SERVER

CLIENT

 select max(a.col1), max(b.col1) from tibero.test a , tibero.test1 b where a.col1= b.col1
5Instance failure (process kill)

-- Node1 

tbdown abnormal

6Verify failover

-- Node2

select max(a.col1), max(b.col1) from tibero.test a , tibero.test1 b where a.col1= b.col1;

MAX(A.COL1) MAX(B.COL1)

 ----------- -----------
10000000    10000000
1 row selected.
Total elapsed time 00:00:48.513198

 

DBMS Failure Failback

This section explains the failback function for DBMS instance failures.

 

Procedure

StepScenario
1Check service
2Start instance
3Connect with tbsql and verify connected instance

 

Results

StepScenario
1Check service
[root@tech-tac0 cumulative]$ cmrctl show all
Resource List of Node cm0
=====================================================================
 CLUSTER     TYPE        NAME       STATUS           DETAIL
----------- -------- -------------- -------- ------------------------
    COMMON  network           net0       UP (private) 10.10.10.231/29000
    COMMON  cluster           cls0       UP inc: net0, pub: N/A
      cls0     file         cls0:0       UP /share/tac/CMFILE/CMFILE
      cls0  service         testdb       UP Database, Active Cluster (auto-restart: OFF)
      cls0       db        testdb0     DOWN testdb, /root/tibero_engine, failed retry cnt: 0
=====================================================================
Resource List of Node cm1
=====================================================================
 CLUSTER     TYPE        NAME       STATUS           DETAIL
----------- -------- -------------- -------- ------------------------
    COMMON  network           net1       UP (private) 10.10.10.232/29000
    COMMON  cluster           cls0       UP inc: net1, pub: N/A
      cls0     file         cls0:0       UP /share/tac/CMFILE/CMFILE
      cls0  service         testdb       UP Database, Active Cluster (auto-restart: OFF)
      cls0       db        testdb1 UP(NRML) testdb, /root/tibero_engine, failed retry cnt: 0
=====================================================================
2Start instance

[root@tech-tac0 cumulative]$ tbboot
Change core dump dir to /root/tibero_engine/bin/prof.
Listener port = 8629

Tibero 7

TmaxTibero Corporation Copyright (c) 2020-. All rights reserved.
Tibero instance started up (NORMAL mode).
 

3Connect with tbsql and verify connected instance

SQL> select instance_name from v$instance;

INSTANCE_NAME
----------------------------------------
testdb0

1 row selected.

SQL> exit
Disconnected.


cmrctl show all
Resource List of Node cm0
=====================================================================
 CLUSTER     TYPE        NAME       STATUS           DETAIL
----------- -------- -------------- -------- ------------------------
    COMMON  network           net0       UP (private) 10.10.10.231/29000
    COMMON  cluster           cls0       UP inc: net0, pub: N/A
      cls0     file         cls0:0       UP /share/tac/CMFILE/CMFILE
      cls0  service         testdb       UP Database, Active Cluster (auto-restart: OFF)
      cls0       db        testdb0 UP(NRML) testdb, /root/tibero_engine, failed retry cnt: 0
=====================================================================
Resource List of Node cm1
=====================================================================
 CLUSTER     TYPE        NAME       STATUS           DETAIL
----------- -------- -------------- -------- ------------------------
    COMMON  network           net1       UP (private) 10.10.10.232/29000
    COMMON  cluster           cls0       UP inc: net1, pub: N/A
      cls0     file         cls0:0       UP /share/tac/CMFILE/CMFILE
      cls0  service         testdb       UP Database, Active Cluster (auto-restart: OFF)
      cls0       db        testdb1 UP(NRML) testdb, /root/tibero_engine, failed retry cnt: 0
=====================================================================

 

Network (public) Failure Failover

This section explains the failover function for public network failures.

 

Procedure

StepScenario
1Client connection setup (tbdsn.tbr)
2Confirm instance connection
3Prepare data for query execution
4Execute query
5Network (public) failure
6Verify failover

 

Results

StepScenario
1Client connection setup (tbdsn.tbr)

tta1=(
(INSTANCE=(HOST=192.168.51.161)
(PORT=8639)
(DB_NAME=tta)
(SELF_KEEPALIVE=
(SELF_KEEPIDLE=20)
(SELF_KEEPCNT=3)
(SELF_KEEPINTVL=4)
)
)

(INSTANCE=(HOST=192.168.51.162)
(PORT=8639)
(DB_NAME=tta)
(SELF_KEEPALIVE=
(SELF_KEEPIDLE=20)
(SELF_KEEPCNT=3)

(SELF_KEEPINTVL=4)
)
)
(USE_FAILOVER=(TYPE=CURSOR)
(RETRY=3)
)
)

2Confirm instance connection
tbsql sys/tibero@tta1
select instance_name from v$instance;
INSTANCE_NAME                           
----------------------------------------
tta1
3Prepare data for query execution
drop table tibero.test;
drop table tibero.test1;
create table tibero.test as
select level as col1, level || '_test' as col2,
trunc(level/100) as col3
from dual connect by level < 10000001;
create table tibero.test1 as
select level as col1, level || '_test' as col2,
trunc(level/100) as col3
from dual connect by level < 10000001;
4Execute query
SERVERCLIENT
 set timing on
select max(a.col1), max(b.col1) from tibero.test a , tibero.test1 b where a.col1= b.col1;
5Network (public) failure

-- Node1 

ifconfig en1 down

6Verify failover

-- Node2

select max(a.col1), max(b.col1) from tibero.test a , tibero.test1 b where a.col1= b.col1;

MAX(A.COL1) MAX(B.COL1)

 ----------- -----------
10000000    10000000
1 row selected.
Total elapsed time 00:00:48.513198

 

 

Network (Public) Failure Failback Function

This section explains the failback function for public network failures.

 

Procedure

StepScenario
1Restore network (Public)
2Check service
3Connect with tbsql and verify connected instance

 

Results

StepScenario
1Restore network (Public)
ifconfig en1 up
2Check service
cmrctl show all
Resource List of Node cm0
=====================================================================
 CLUSTER     TYPE        NAME       STATUS           DETAIL
----------- -------- -------------- -------- ------------------------
    COMMON  network           net0       UP (private) 10.10.10.231/29000
    COMMON  cluster           cls0       UP inc: net0, pub: N/A
      cls0     file         cls0:0       UP /share/tac/CMFILE/CMFILE
      cls0  service         testdb       UP Database, Active Cluster (auto-restart: OFF)
      cls0       db        testdb0 UP(NRML) testdb, /root/tibero_engine, failed retry cnt: 0
=====================================================================
Resource List of Node cm1
=====================================================================
 CLUSTER     TYPE        NAME       STATUS           DETAIL
----------- -------- -------------- -------- ------------------------
    COMMON  network           net1       UP (private) 10.10.10.232/29000
    COMMON  cluster           cls0       UP inc: net1, pub: N/A
      cls0     file         cls0:0       UP /share/tac/CMFILE/CMFILE
      cls0  service         testdb       UP Database, Active Cluster (auto-restart: OFF)
      cls0       db        testdb1 UP(NRML) testdb, /root/tibero_engine, failed retry cnt: 0
=====================================================================
3Connect with tbsql and verify connected instance
select instance_name from v$instance;
INSTANCE_NAME                 
----------------------------------------
tta2
1 row selected.

 

Network (Interconnect) Failure Failover Function

This section explains the failover function for interconnect network failures.

 

Procedure

StepScenario
1Client connection setup (tbdsn.tbr)
2Confirm instance connection
3Prepare data for query execution
4Execute query
5Network (interconnect) failure
6Check query execution result
7Check service

 

Results

StepScenario
1Client connection setup (tbdsn.tbr)
tta1=(
(INSTANCE=(HOST=192.168.51.161)
(PORT=8639)
(DB_NAME=tta)
)
(INSTANCE=(HOST=192.168.51.162)
(PORT=8639)
(DB_NAME=tta)
)
(USE_FAILOVER=(TYPE=CURSOR)
(RETRY=3)
)
)
2Confirm instance connection

tbsql sys/tibero@tta1

select instance_name from v$instance;
INSTANCE_NAME                           
----------------------------------------
tta1

3Prepare data for query execution
drop table tibero.test;
drop table tibero.test1;
create table tibero.test as
select level as col1, level || '_test' as col2,
trunc(level/100) as col3
from dual connect by level < 10000001;
create table tibero.test1 as
select level as col1, level || '_test' as col2,
trunc(level/100) as col3
from dual connect by level < 10000001;
4Execute query
SERVERCLIENT
 set timing on
select max(a.col1), max(b.col1) from tibero.test a , tibero.test1 b where a.col1= b.col1;
5Network (interconnect) failure
ifconfig en4 down
6Check query execution result

MAX(A.COL1) MAX(B.COL1) 

----------- -----------
10000000    10000000
1 row selected.
Total elapsed time 00:01:19.900213 

7Check service
[root@tech-tac0 cumulative]$ cmrctl show all
Resource List of Node cm0
=====================================================================
 CLUSTER     TYPE        NAME       STATUS           DETAIL
----------- -------- -------------- -------- ------------------------
    COMMON  network           net0       DOWN (private) 10.10.10.231/29000
    COMMON  cluster           cls0       DOWN inc: net0, pub: N/A
      cls0     file         cls0:0       DOWN /share/tac/CMFILE/CMFILE
      cls0  service         testdb       UP Database, Active Cluster (auto-restart: OFF)
      cls0       db        testdb0     DOWN testdb, /root/tibero_engine, failed retry cnt: 0
=====================================================================
Resource List of Node cm1
=====================================================================
 CLUSTER     TYPE        NAME       STATUS           DETAIL
----------- -------- -------------- -------- ------------------------
    COMMON  network           net1       UP (private) 10.10.10.232/29000
    COMMON  cluster           cls0       UP inc: net1, pub: N/A
      cls0     file         cls0:0       UP /share/tac/CMFILE/CMFILE
      cls0  service         testdb       UP Database, Active Cluster (auto-restart: OFF)
      cls0       db        testdb1 UP(NRML) testdb, /root/tibero_engine, failed retry cnt: 0
=====================================================================
 

 

Network (Interconnect) Failure Failback Function

This section explains the failback function for interconnect network failures.

 

Procedure

StepScenario
1Restore network (interconnect)
2Start instance
3Connect with tbsql and verify connected instance

 

Results

StepScenario
1Restore network (interconnect)
ifconfig en4 up
2Start instance

tbcm -b
CM Guard daemon started up.
import resources from '/root/tibero_engine/config/cm0_res_file'...

TBCM 7.1.1 (Build 300983)

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

Tibero cluster manager started up.
Local node name is (cm0:28629).

 

tbboot
Change core dump dir to /root/tibero_engine/bin/prof.
Listener port = 8629

Tibero 7

TmaxTibero Corporation Copyright (c) 2020-. All rights reserved.
Tibero instance started up (NORMAL mode).

3Connect with tbsql and verify connected instance

SQL> select instance_name from v$instance;

INSTANCE_NAME
----------------------------------------
testdb0

1 row selected.

 

 

Related to