This topic describes possible errors that may occur after you execute a failover statement and their causes and solutions.
Error 1: Failover is not allowed when protection level not in MAXIMUM PROTECTION or AVAILABILITY
Possible causes
The protection level of the standby cluster is not MAXIMUM PROTECTION or MAXIMUM AVAILABILITY. For more information about the prerequisites for executing a lossless failover, see Preparations for a failover.
Solutions
We recommend that you perform a lossy failover by executing the following statement. For more information about lossy failover, see Perform a lossy failover.
obclient> ALTER SYSTEM ACTIVATE PHYSICAL STANDBY CLUSTER;
Error 2: Failover is not allowed when primary cluster [cluster_id=id] is still alive
Possible causes
The primary cluster is still active. To avoid the coexistence of two primary clusters, you cannot perform a failover on a standby cluster whose primary cluster is still active.
Solutions
Make sure that all the OBServer nodes in the primary cluster are inactive before you execute the failover statement.
Error 3: Failover is not allowed when cluster have inactive servers
Possible causes
Not all OBServer nodes in the standby cluster are active.
Solutions
Make sure that all OBServer nodes in the standby cluster are active before you execute the failover statement.
Error 4: Failover is not allowed when cluster has permanent offline server. Make sure all inactive servers are permanent offline, and use FORCE option to skip this check
Possible causes
Not all the OBServer nodes in the standby cluster are active.
Solutions
Verify that the inactive OBServer nodes in the standby cluster are permanently offline and specify the FORCE option in the failover statement to force a lossy failover. For more information about the operation, see Perform a lossy failover.