Protection mode switching errors

This topic describes possible errors that may occur after you execute the protection mode switching statement and the possible causes and solutions to these errors.

Error 1: set protection mode in standby cluster not allowed

Possible causes

You cannot change the protection mode for a standby cluster.

Solutions

Execute the protection mode switching statement on the primary cluster. For more information, see Switch the protection mode.

Error 2: set cluster protection mode when cluster is upgrading not allowed

Possible causes

OceanBase Database versions earlier than V2.2.72 do not support protection mode switching during an upgrade.

Solutions

Switch the projection mode after the upgrade is completed.

Error 3: one server is not alive, set maximum protection mode not allowed

Possible causes

You cannot switch a cluster to the MAXIMUM PROTECTION mode when some OBServer nodes in the cluster are inactive.

Solutions

Ensure that all the OBServer nodes in the cluster are active before you switch the cluster to the MAXIMUM PROTECTION mode.

Error 4: set maximum availabilty mode with zero or more than one cluster in sync mode not allowed

Possible causes

When you switch a cluster to the MAXIMUM AVAILABILITY mode from other modes, ensure that the log transfer mode of only one standby cluster is set to SYNC.

Solutions

1. Log on to the primary cluster and query the V$OB_STANDBY_STATUS view to check the log transfer mode of each standby cluster.

   obclient> SELECT CLUSTER_ID, REDO_TRANSPORT_OPTIONS FROM oceanbase.V$OB_STANDBY_STATUS;
   

2. Change the log transfer mode of standby clusters and ensure that the log transfer mode of only one standby cluster is set to SYNC.

   For more information about the log transfer mode of standby clusters, see Set the log transfer parameter for a standby cluster.