GAUSS-02001 -- GAUSS-02010

Updated on 2023-12-22 GMT+08:00

View PDF

GAUSS-02001: "could not fdatasync data file num %d, fd %d: %m"

SQLSTATE: XX000

Description: Files cannot be synchronized to the disk. Determine the reason by analyzing the %m error message.

Solution: Determine whether the problem is caused by read-only disk or full disk space by analyzing the error message. Restore the disk space as needed.

GAUSS-02002: "received incorrect data page checksum at: rnode[%u,%u,%u], blocknum[%u], segno[%u], pageoffset[%u], size[%u], queueoffset[%u/%u]"

SQLSTATE: XX000

Description: A data page CRC received by the standby server from the primary server fails to be verified.

Solution: Check whether the network environment is normal or whether a packet is lost.

GAUSS-02004: "could not receive the ongoing mode infomation from the primary server: %s"

SQLSTATE: XX000

Description: The standby server fails to receive operation mode information from the primary server.

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-02005: "invalid response from primary server"

SQLSTATE: XX000

Description: The length of the system identifier message received by the standby server from the primary server is incorrect.

Solution: Check whether the network environment is normal or whether a packet is lost.

GAUSS-02006: "the mode of the remote server must be primary, current is %d"

SQLSTATE: XX000

Description: The status of the primary server is not primary.

Solution: Run the gs_om -t status --detail command to query information about the connection between the primary and standby server. Ensure that the configuration of the replconninfo1 and replconninfo2 fields in the postgresql.conf file are matching.

GAUSS-02007: "could not receive database system identifier and timeline ID from the primary server: %s"

SQLSTATE: XX000

Description: The standby server sends a system verification message to the primary server. The primary server returns a failure message. Resolve the problem based on the "%s" error message.

GAUSS-02008: "database system identifier differs between the primary and standby"

SQLSTATE: XX000

Description: The standby server sends a system verification message to the primary server. The system ID of the primary server is different from that of the standby server. It is preliminarily suspected that the primary and standby servers establish connection for the first time.

Solution: Re-build the standby server. In the cluster environment, the CM server automatically rebuilds the standby server.

GAUSS-02009: "timeline %u of the primary does not match recovery target timeline %u"

SQLSTATE: XX000

Description: The standby server sends the system verification message to the primary server. The timeline of the primary server is inconsistent with that of the standby server. It is preliminarily suspected that the primary server performed backup and restoration operations, and the timeline was changed.

Solution: Re-build the standby server. In the cluster environment, the CM server automatically rebuilds the standby server.

GAUSS-02010: "could not start DATA streaming: %s"

SQLSTATE: XX000

Description: The standby server fails to request the primary server to enable data 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. If the primary server is shut down unexpectedly, identify the cause. "

Parent topic: GAUSS-02001 -- GAUSS-02100

Previous topic: GAUSS-02001 -- GAUSS-02100

Next topic: GAUSS-02011 -- GAUSS-02020