GAUSS-02051 -- GAUSS-02060

Updated on 2024-03-15 GMT+08:00

View PDF

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: Re-build the standby server. In the cluster environment, the CM server automatically recovers the standby server.

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

SQLSTATE: XX000

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

Solution:"1. Ensure that the programs enabled on the primary and standby server use the same version. 2. Re-build the standby server. In the cluster environment, the CM server automatically recovers 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:"1. Ensure that the pg_xlog directory is normal. 2. Re-build the standby server. In the cluster environment, the CM server automatically recovers the standby server. "

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

SQLSTATE: XX000

Description: Consistency of logs of the primary and standby servers fails to be verified. Resolve the problem based on the "%s" error message.

Solution:"1. In the preceding execution, role switching of the primary and standby server is inconsistent, resulting in log in-consistence. 2. Re-build the standby server. In the cluster environment, the CM server automatically recovers the standby server. "

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

SQLSTATE: XX000

Description: During primary-standby server logs consistence verification, the primary server returns an invalid CRC log value.

Solution:"1. The location of logs requested for verification by the standby server is invalid on the primary server. 2. Re-build the standby server. In the cluster environment, the CM server automatically recovers 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: Verifying consistency of logs of the primary and standby server fails.

Solution:"1. The logs of the primary server and those of the standby server are inconsistent. 2. Re-build the standby server. In the cluster environment, the CM server automatically recovers the standby server. "

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

SQLSTATE: XX000

Description: The standby/secondary standby 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 standby server fails to connect to the primary server to enable log replication. Resolve the problem based on the "%s" error message.

Solution:"1. If the network connection times out, adjust the current network environment. If the primary server is overloaded, adjust services. 2. 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.

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.

Parent topic: GAUSS-02001 -- GAUSS-02100

Previous topic: GAUSS-02041 -- GAUSS-02050

Next topic: GAUSS-02061 -- GAUSS-02070