Failover-related errors

This topic describes possible errors that may occur after you execute a failover command, and their causes and solutions.

Error 1: Failover is not allowed when protection level not in MAXIMUM PROTECTION or AVAILABILITY

Possible cause

OceanBase Database supports lossless failovers only for standby clusters whose protection levels are MAXIMUM PROTECTION or MAXIMUM`` AVAILABILITY. For more information about the prerequisites for executing a lossless failover, see Preparations for a failover.

Solution

We recommend that you use the following lossy failover command instead:

obclient> ALTER SYSTEM ACTIVATE PHYSICAL STANDBY CLUSTER;

Error 2: Failover is not allowed when primary cluster [cluster_id=id] is still alive

Possible cause

The primary cluster is still active. To avoid two primary clusters, OceanBase Database requires that the primary cluster must be inactive during a failover.

Solution

Make sure that all the servers in the primary cluster are down before you run the failover command.

Error 3: Failover is not allowed when cluster have inactive servers

Possible cause

Not all the servers in the standby cluster are active.

Solution

Make sure that all the servers in the standby cluster are active before you run the failover command.