GAUSS-01991 -- GAUSS-02000

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

View PDF

GAUSS-01991: "terminating datareceiver due to Secondary Standby has no data"

SQLSTATE: XX000

Description: When no data on the secondary server is to be synchronized to the standby server, datareceiver on the standby server exits.

Solution: The error does not need to be handled.

GAUSS-01992: "cannot continue DATA streaming, recovery has already ended"

SQLSTATE: XX000

Description: Restoration of the current instance has been terminated. Data replication does not need to be continued.

Solution: The error does not need to be handled.

GAUSS-01993: "terminating datareceiver process due to the death of datarcvwriter"

SQLSTATE: XX000

Description: Internal system error.

Solution: Contact technical support.

GAUSS-01994: "terminating datareceiver due to timeout"

SQLSTATE: XX000

Description: The heartbeat between the primary and standby servers times out. The standby server disconnects from the primary server upon failing to detect the heartbeat.

Solution: 1. Determine the reason by checking the service load and network environment of the primary server. 2. Use the gs_guc tool to increase wal_sender_timeout or wal_receiver_timeout, or reduce the service load as required. "

GAUSS-01995: "terminating datareceiver process due to administrator command"

SQLSTATE: 57P01

Description: The datareceiver thread of the standby server receives the SIGTERM message. The error message is printed before the process exits.

Solution: Check the exception logs before the error message is sent by searching for pg_log to determine whether the operations are correct.

GAUSS-01996: "no replication connection config information."

SQLSTATE: XX000

Description: The configuration of replconninfo1 or replconninfo2 is empty in the postgresql.conf file.

Solution: Modify corresponding configuration options in the postgresql.conf file using the gs_guc tool.

GAUSS-01997: "rm data comand is not from primary,peer_role=%d"

SQLSTATE: XX000

Description: The data deletion command received by the standby DN is not from the primary DN.

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

GAUSS-01998: "could not create data file '%s': %m"

SQLSTATE: XX000

Description: The file fails to be created. This is probably caused by incorrect permission or damaged directory.

Solution: Analyze the cause based on the error message. If the permission is incorrect, change the permission. If the directory is damaged, recover the file system or disk.

GAUSS-01999: "could not write to data file %s buffer len %u, length %u: %m"

SQLSTATE: XX000

Description: A file may fail to be opened due to insufficient space, incorrect permission, or damaged file.

Solution: Analyze the cause based on the error message. If the space is insufficient, clear some space. If the permission is incorrect, change the permission. If the file is damaged, recover the file system or disk.

GAUSS-02000: "could not write to data file %s at offset %u, length %u: %m"

SQLSTATE: XX000

Description: A file may fail to be opened due to insufficient space, incorrect permission, or damaged file.

Parent topic: GAUSS-01901 -- GAUSS-02000

Previous topic: GAUSS-01981 -- GAUSS-01990

Next topic: GAUSS-02001 -- GAUSS-02100