Updated on 2025-03-26 GMT+08:00

GAUSS-02051 -- GAUSS-02060

GAUSS-02051: "database system version is different between the primary and standby"

SQLSTATE: XX000

Description: The system version of the primary server does not match that of the standby server.

Solution: The standby server needs to be rebuilt. In the cluster environment, the CM automatically rebuilds the standby server.

GAUSS-02052: "the primary protocol version %s is not the same as the standby protocol version %s."

SQLSTATE: XX000

Description: The HA protocol version of the primary server does not match that of the standby server.

Solution: Ensure that the programs started by the active and standby instances are of the same version. The standby server needs to be rebuilt. In the cluster environment, the CM automatically rebuilds the standby server.

GAUSS-02053: "Invalid xlog offset at %X/%X. Please check xlog files or rebuild the primary/standby relationship."

SQLSTATE: XX000

Description: The WAL logs of the standby server are invalid.

Solution: Ensure that the pg_xlog log directory of the instance is normal. The standby server needs to be rebuilt. In the cluster environment, the CM automatically rebuilds the standby server. "

GAUSS-02054: "failed to identify consistence at %X/%X: %s"

SQLSTATE: XX000

Description: Failed to check the consistency of the primary and standby server logs. Resolve the problem based on the "%s" error message.

Solution: In the preceding execution, role switching of the primary and standby server is inconsistent, resulting in log in-consistence. The standby server needs to be rebuilt. In the cluster environment, the CM automatically rebuilds the standby server. "

GAUSS-02055: "could not parse primary record's crc,primary_reccrc=%s reccrc=%u"

SQLSTATE: XX000

Description: The primary server returns an invalid CRC log during primary/standby server log consistency check.

Solution: The standby server requests a check for logs from an invalid location on the primary server. The standby server needs to be rebuilt. In the cluster environment, the CM automatically rebuilds the standby server.

GAUSS-02056: "standby_rec=%x/%xstandby latest record's crc %u and primary corresponding record's crc %u not matched"

SQLSTATE: XX000

Description: Failed to check the consistency of primary/standby server logs.

Solution: Ensure that there is no inconsistency among primary/standby server logs. The standby server needs to be rebuilt. In the cluster environment, the CM automatically rebuilds the standby server.

GAUSS-02057: "could not create replication slot %s : %s"

SQLSTATE: XX000

Description: The standby/secondary server fails to connect to the primary server to create slots.

Solution: Resolve the problem based on the "%s" error message.

GAUSS-02058: "could not start WAL streaming: %s"

SQLSTATE: XX000

Description: The standby/secondary server fails to connect to the primary server to enable log replication. Resolve the problem based on the "%s" error message.

Solution: If the network connection times out, adjust the current network environment. If the primary server is overloaded, adjust services. If the primary server is shut down unexpectedly, identify the cause.

GAUSS-02059: "could not receive data from WAL stream: %s"

SQLSTATE: XX000

Description: During data replication between the primary and standby servers, the standby server detects primary-standby server connection errors. Resolve the problem based on the "%s" error message.

Solution: If the network connection times out, adjust the current network environment. If the primary server is overloaded, adjust services. If the primary server is shut down unexpectedly, identify the cause.

GAUSS-02060: "replication terminated by primary server at %X/%X"

SQLSTATE: XX000

Description: The primary server terminates data replication to the standby server.

Solution: Check external causes.