Document Type | Technical Information
Category | Monitoring/Inspection
Applicable Product Version | 7FS02PS
Document Number | TMOTI007
Overview
Tibero Standby Cluster (hereinafter referred to as TSC) is a core feature of Tibero provided for database high availability, data protection, and disaster recovery. This document provides guidance on the items related to executing the cmrctl show command on the TSC observer.
Notecmrctl is a set of commands used in New CM to manage and control resources, and the cmrctl show command is used to check the information of resources registered in the CM.
Method
Example Execution
$ cmrctl show
Resource List of Observer obs
===================================================================
TSC_ID CLS_ID CM_NAME NID CM_STAT INST_STAT PRI/TAR
-------- -------- ----------- ----- --------- ----------- ---------
123 4 cms 1 UP UP(RECO) TARGET
5 cmp 1 UP UP(NRML) PRIMARY
===================================================================
Description of Items
Item | Description |
|---|---|
TSC_ID | TSCs are grouped using the tscid, which is the same tscid value used when adding a service in the CM. |
CLS_ID | Cluster ID issued by the Observer to the CM (Clusters in the same group have the same CLS_ID) |
CM_NAME | The CM_NAME of the connected CM |
NID | ID that the connected CM holds within its own Cluster |
CM_STAT | Current status of the connected CM (three possible states: DOWN / UNKNOWN / UP) |
INST_STAT | Instance status of the connected CM equipment (three possible states: DOWN / UNKNOWN / UP(MODE)) |
PRI/TAR | Indicates whether PRIMARY / TARGET / STANDBY / N * PRIMARY: Cluster with TIBERO booted in NORMAL mode. Two PRIMARY Clusters cannot exist in one TSC. * TARGET: The candidate to become the next PRIMARY when there is an issue with the PRIMARY or when the user performs a SwitchOver. * STANDBY: STANDBY Cluster not selected as TARGET. * N: Cluster that is none of the above. |