Overview

This document describes how to shut down a remote Tibero using tbsql.

This method can be used when there are security issues or when direct terminal access to the target server is not possible.

This document was written based on a case in which direct terminal access was not possible because the root password for the target server had been lost while providing support to the National Intelligence Service, so the Tibero instance on the target server was accessed remotely and shut down through tbsql from another server.

Test Environment

• OS: Linux node1 5.14.0-706.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Fri May 15 22:16:01 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
• Tibero: Tibero 7 (DB 7.2.5) Build 313465
• Configuration: Single 

Method

Configuring tbdsn.tbr

You must configure the connection information for the remote Tibero to connect through tbsql.

Configure the connection information for the remote Tibero in $TB_HOME/client/confing/tbds.tbr.

-- Existing server connection information

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



-- Remote Tibero connection information
remote=(
   (INSTANCE=(HOST=10.23.212.86)
             (PORT=8629)
             (DB_NAME=tibero)
   )
)

After completing the configuration, connect to verify that the connection works properly.

In addition, DBA privileges are required to shut down Tibero through tbsql, so you must verify the information for a user with DBA privileges in advance.

node1@tibero:/home/tibero/tibero7/client/config # tbsql sys/tibero@remote

tbSQL 7

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

Connected to Tibero using remote.

SQL> ls user

USERNAME
--------------------------------------------------------------------------------------------------------------------------------
SYS

Shutdown Methods

There are three options for shutting down a remote Tibero through tbsql:

• tbdown
• tbdown immediate
• tbdown abort

The tbdown command is not recommended because if other sessions are connected, it waits indefinitely until those sessions are terminated.

Shutting down with tbdown

node1@tibero:/home/tibero # tbsql sys/tibero@remote

tbSQL 7

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

Connected to Tibero using remote.

SQL> tbdown
DB instance was terminated.
 

--Engine log
[2026-08-04T13:31:15.053] [FRM-157] [I-B7A] get shutdown request msg.[command] mode[1]:NORMAL from terminal:N
[2026-08-04T13:31:15.054] [FRM-157] [I-L41] shutdown: started (mode=1)
[2026-08-04T13:31:15.055] [FRM-157] [I-WYK] shutdown: check hotbackup

Shutting down with tbdown immediate

node1@tibero:/home/tibero # tbsql sys/tibero@remote

tbSQL 7

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

Connected to Tibero using remote.

SQL> tbdown immediate
DB instance was terminated.



--Engine log
[2026-08-04T13:32:09.711] [FRM-157] [I-B7A] get shutdown request msg.[command] mode[3]:IMMEDIATE from terminal:N
[2026-08-04T13:32:09.712] [FRM-157] [I-L41] shutdown: started (mode=3)
[2026-08-04T13:32:09.713] [FRM-157] [I-WYK] shutdown: check hotbackup
[2026-08-04T13:32:09.714] [FRM-157] [I-UP0] shutdown: send session kill to all the WTHRs
[2026-08-04T13:32:09.714] [FRM-157] [I-D8G] shutdown: send session kill to TPR/JOB/RSRC

Shutting down with tbdown abort

node1@tibero:/home/tibero # tbsql sys/tibero@remote

tbSQL 7

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

Connected to Tibero using remote.

SQL> tbdown abort
DB instance was terminated.
 

--Engine log

[2026-08-04T13:33:38.259] [FRM-157] [I-B7A] get shutdown request msg.[command] mode[4]:ABORT from terminal:N
[2026-08-04T13:33:38.259] [FRM-157] [I-L41] shutdown: started (mode=4)
[2026-08-04T13:33:38.259] [FRM-157] [I-QZQ] shutdown: send SHUTDOWN ABORT to MTHR
[2026-08-04T13:33:38.260] [FRM-000] [I-AFS] MTHR received SHUTDOWN message! SHUTTING DOWN...(issuer:157, mode[4]:ABORT)
[2026-08-04T13:33:38.260] [MT -000] [I-U0Z] MTHR starts to shutdown mode=4, CUR_SVRMODE=8
[2026-08-04T13:33:38.260] [MT -000] [I-DZU] MTHR terminiates all childs

tbdown abnormal (unsupported)

node1@tibero:/home/tibero # tbsql sys/tibero@remote

tbSQL 7

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

Connected to Tibero using remote.

SQL> tbdown abnormal
TBS-70003: Invalid command. Enter HELP or HELP <command>.
at line 1, column 8:
tbdown abnormal
      ^^^^^^^^

Notes

An error occurs when attempting to shut down Tibero through tbsql in the following cases.

Insufficient privileges

node1@tibero:/home/tibero # tbsql sys/tibero

tbSQL 7

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

Connected to Tibero.

SQL> create user test identified by test;

User 'TEST' created.

SQL> grant resource, connect to test;

Granted.

SQL> q
Disconnected.
node1@tibero:/home/tibero # tbsql test/test@remote

tbSQL 7

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

Connected to Tibero using remote.

SQL> tbdown
TBR-2119: Shutdown failed.

TBR-17004: Permission denied.
 

--Succeeds normally when DBA privileges are available

SQL> conn sys/tibero
Connected to Tibero.

SQL> grant dba to test;

Granted.

SQL> q
Disconnected.
node1@tibero:/home/tibero # tbsql test/test@remote

tbSQL 7

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

Connected to Tibero using remote.

SQL> tbdown
DB instance was terminated.

When attempting to shut down with the tbdown command while a session is connected to the target server (waits indefinitely until the session is disconnected)

-Attempting shutdown while another session exists

node1@tibero:/home/tibero # tbsql sys/tibero@remote

tbSQL 7

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

Connected to Tibero using remote.

SQL> select count(*) from v$session;

 COUNT(*)
----------
        2

1 row selected.

SQL> tbdown
DB instance was terminated.
 

--SID of the other session

SQL> select * from _vt_mytid;

      TID
----------
      157

1 row selected.
 

--Engine log when attempting tbdown while a session exists

[2026-07-31T15:48:01.804] [FRM-158] [I-N13] shutdown: acquire SESS lock (sessid=150)
[2026-07-31T15:48:01.805] [FRM-158] [I-N13] shutdown: acquire SESS lock (sessid=151)
[2026-07-31T15:48:01.805] [FRM-158] [I-N13] shutdown: acquire SESS lock (sessid=152)
[2026-07-31T15:48:01.806] [FRM-158] [I-N13] shutdown: acquire SESS lock (sessid=153)
[2026-07-31T15:48:01.806] [FRM-158] [I-N13] shutdown: acquire SESS lock (sessid=154)
[2026-07-31T15:48:01.807] [FRM-158] [I-N13] shutdown: acquire SESS lock (sessid=155)
[2026-07-31T15:48:01.808] [FRM-158] [I-N13] shutdown: acquire SESS lock (sessid=156)
[2026-07-31T15:48:01.809] [FRM-158] [I-N13] shutdown: acquire SESS lock (sessid=157)

....Waits until the session is terminated, then proceeds to the next step

[2026-07-31T15:49:27.041] [FRM-158] [I-N13] shutdown: acquire SESS lock (sessid=159)
[2026-07-31T15:49:27.044] [FRM-158] [I-N13] shutdown: acquire SESS lock (sessid=160)
[2026-07-31T15:49:27.045] [FRM-158] [I-N13] shutdown: acquire SESS lock (sessid=161)
[2026-07-31T15:49:27.045] [FRM-158] [I-N13] shutdown: acquire SESS lock (sessid=162)
[2026-07-31T15:49:27.045] [FRM-158] [I-N13] shutdown: acquire SESS lock (sessid=163)