This topic describes how to check the status of an OceanBase cluster after it is upgraded.
Procedure
Log in to OceanBase Database.
For example, log in to the sys tenant of OceanBase Database as the
rootuser.obclient -h10.10.10.1 -P2881 -uroot@sys -p******Query the corresponding view for information about events related to cluster upgrades.
Here is an example:
SELECT * FROM oceanbase.DBA_OB_CLUSTER_EVENT_HISTORY WHERE MODULE='UPGRADE'\GThe result is as follows:
*************************** 1. row *************************** TIMESTAMP: 2024-05-22 14:42:37.876473 MODULE: UPGRADE EVENT: BEGIN_UPGRADE NAME1: cluster_version VALUE1: 4.3.0.1 NAME2: build_version VALUE2: 4.3.0.1_200000082024022210-d597f573c0f7fcdeefc74e78f6e66e9c0435a2bb(Feb 22 2024 11:01:15) NAME3: VALUE3: NAME4: VALUE4: NAME5: VALUE5: NAME6: VALUE6: EXTRA_INFO: *************************** 2. row *************************** TIMESTAMP: 2024-05-22 14:42:37.895952 MODULE: UPGRADE EVENT: BEGIN_ROLLING_UPGRADE NAME1: cluster_version VALUE1: 4.3.0.1 NAME2: build_version VALUE2: 4.3.0.1_200000082024022210-d597f573c0f7fcdeefc74e78f6e66e9c0435a2bb(Feb 22 2024 11:01:15) NAME3: VALUE3: NAME4: VALUE4: NAME5: VALUE5: NAME6: VALUE6: EXTRA_INFO: *************************** 3. row *************************** TIMESTAMP: 2024-05-22 14:52:47.609906 MODULE: UPGRADE EVENT: END_ROLLING_UPGRADE NAME1: cluster_version VALUE1: 4.3.1.0 NAME2: ori_cluster_version VALUE2: 4.3.0.1 NAME3: build_version VALUE3: 4.3.1.0_100000172024050810-fa1385d2910f990a8bb646c53ac03e2529d1bab8(May 8 2024 10:41:26) NAME4: VALUE4: NAME5: VALUE5: NAME6: VALUE6: EXTRA_INFO: 3 rows in set
References
For more information about how to connect to OceanBase Database, see Overview of connection methods.
For more information about cluster-level events, see oceanbase.DBA_OB_CLUSTER_EVENT_HISTORY.