Restarting database
If the database is in a multi-cluster configuration, the users can restart it on a per-node basis. The users can check the restart progress by clicking the [🔔] icon in the top right corner of the console screen. If the database operational status is not Running, or the instance status is Recovery, Disconnect, the users cannot restart it.
Caution
When restarting the database, all currently connected sessions will be terminated.
It might take a few minutes before they are reactivated.
If the instance status is disconnect after the restart, please contact AWS][email protected] or [Azure][email protected] depending on the usersr CSP.
Navigate to the OwlDB console screen > Dashboards menu.
Pull down the radio button for the database the users want to restart, and click the Restart button.
If the database is in a multi-cluster configuration, pull down the nodes the users want to restart.
Pull down the database shutdown mode.
NORMAL
(coming soon) Wait until all sessions are disconnected before shutting down
POST_TX
(coming soon) Wait until all transactions are finished before shutting down
IMMEDIATE
Forcibly abort all operations currently in progress, rolling back all transactions in progress before shutting down
ABORT
Forcibly terminate Tibero's processes
ABNORMAL
Forcibly terminate server processes unconditionally without connecting to the Tibero server (recommended for emergency use only)
Caution
When shutting down in ABORT mode, some system resources (shared memory, semaphores, etc.) may not be released, resulting in possible breakage recovery. We recommend using it only in the following situations
Normal shutdown is not possible due to an internal Tibero error.
If there is a problem with the H/W and Tibero needs to be shut down immediately.
When an emergency condition such as hacking occurs and Tibero needs to be shut down immediately.
Caution
ABNORMAL mode shuts down the server immediately with an OS forced shutdown signal, and system resources (shared memory, semaphores, etc.) are not freed, requiring a restart followed by a breakage repair process. It is recommended to be used only in the following situations
Tibero internal errors prevent a normal shutdown.
When there is a delay after issuing a shutdown command with a shutdown mode other than ABNORMAL, and the users are forced to shut down immediately.
When a problem occurs due to external factors such as H/W or OS, and running a termination mode other than ABNORMAL fails.
When Tibero needs to be shut down immediately due to an emergency condition such as hacking.
Click the restart button.
Last updated