Protection mode switching errors

This topic describes possible errors that may occur after you run the protection mode switching command, and their causes and solutions.

Error 1: set protection mode in standby cluster not allowed

Possible cause

You cannot change the protection mode for a standby cluster.

Solution

Run the protection mode switching command on the primary cluster.

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

Possible cause

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

Solution

Wait until the upgrade is complete.

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

Possible cause

You cannot switch to the maximum protection mode when some servers are inactive.

Solution

Ensure that all the servers are active before you switch to the maximum protection mode.

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

Possible cause

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

Solution

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

   obclient> SELECT CLUSTER_ID, REDO_TRANSPORT_OPTIONS FROM 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 Configure log transfer parameters for a standby cluster.