Standby cluster disconnection errors

When you execute the DISCONNECT statement to verify that a standby cluster meets the conditions of disconnection, errors may occur. This topic describes errors related to standby cluster disconnection, causes of the errors, and suggested solutions.

Error 1: cluster id mismatch, disconnect cluster is not allowed

Possible causes

The cluster ID of the standby cluster specified in the statement is incorrect.

Solutions

Query the V$OB_CLUSTER view to obtain the correct cluster_id of the standby cluster.

Example:

obclient> SELECT cluster_id FROM oceanbase.V$OB_CLUSTER;
+------------+
| CLUSTER_ID |
+------------+
|          2 |
+------------+
1 row in set

Error 2: have inactive server, disconnect cluster is not allowed

Possible causes

Some OBServer nodes in the standby cluster are inactive. A standby cluster with such nodes cannot be disconnected.

Solutions

Ensure that all OBServer nodes in the standby cluster are online before you execute the DISCONNECT statement.

Error 3: cluster name mismatch, disconnect cluster is not allowed

Possible causes

The name of the standby cluster specified in the statement is incorrect.

Solutions

Query the V$OB_CLUSTER view to obtain the correct cluster name.

Example:

obclient> SELECT cluster_name FROM oceanbase.V$OB_CLUSTER;
+-----------------+
| CLUSTER_NAME    |
+-----------------+
| cluster_name    |
+-----------------+
1 row in set

Error 4: cluster name conflict

Possible causes

The cluster name specified in the statement conflicts with the original cluster name.

Solutions

Change the cluster name to a new one and check whether the conflict is cleared.

Error 5: cluster role is not STANDBY, disconnect cluster is not allowed

Possible causes

The cluster you attempt to disconnect is the primary cluster. The primary cluster cannot be disconnected.

Solutions

Switch the primary cluster to the standby role and retry disconnecting it.

Error 6: switchover_status is incorrect, disconnect cluster is not allowed

Possible causes

The standby cluster in the switchover or failover state cannot be disconnected.

Solutions

Wait for the switchover or failover procedure to complete.

Error 7: cluster is in upgrade mode, disconnect cluster is not allowed

Possible causes

The standby cluster in the upgrade state cannot be disconnected.

Solutions

Wait for the upgrade procedure to complete.

Error 8: protection level is not MAXIMUM PERFORMANCE, disconnect cluster is not allowed

Possible causes

The standby cluster not at the protection level of MAXIMUM PERFORMANCE cannot be disconnected.

Solutions

To disconnect a standby cluster at another protection level, perform the following operation before you execute the DISCONNECT statement:

• If the primary cluster is available and the protection level of the standby cluster is not MAXIMUM PERFORMANCE, the standby cluster is synchronizing logs with the primary cluster. To avoid the stop of data writes on the existing primary cluster after the disconnection, change the protection level of the standby cluster to MAXIMUM PERFORMANCE.

• If the primary cluster is unavailable, specify the FORCE option in the DISCONNECT statement to force disconnect the standby cluster from the primary cluster.

Error 9: primary cluster is still alive and in protection, disconnect cluster is not allowed

Possible causes

If the primary cluster is available but the protection level of the standby cluster is not MAXIMUM PERFORMANCE, to avoid the stop of data writes on the existing primary cluster after the disconnection, you cannot execute the DISCONNECT statement even after you specify the FORCE option in the statement.

Solutions

Change the protection level of the standby cluster to MAXIMUM PERFORMANCE. For more information about the operation, see Switch the protection mode.