GAUSS-01981 -- GAUSS-01990

GAUSS-01981: "could not seek in log file %u, segment %u to offset %u: %m"

SQLSTATE: XX000

Description: Files fail to be accessed. The reason may be that the file descriptor is invalid.

Solution: Check whether exceptions including disk faults or file damages exist by analyzing the %m information. Recovery method: 1. If the standby instance is faulty, wait until the cluster management software automatically recovers the instance. If the problem persists after the automatic recovery, the standby instance needs to be manually fixed. technical support 2. If the primary instance is faulty, the CM restarts it. If the problem persists, change the storage media. "

GAUSS-01982: "could not write to log file %u, segment %u at offset %u, length %lu: %m"

SQLSTATE: XX000

Description: Writing to the log file fails. Determine the specific failure cause based on the error message.

Solution: Check whether exceptions including disk faults or file damages exist by analyzing the %m information. Recovery method: 1. If the standby instance is faulty, wait until the cluster management software automatically recovers the instance. If the problem persists after the automatic recovery, the standby instance needs to be manually fixed. technical support 2. If the primary instance is faulty, the CM restarts it. If the problem persists, change the storage media. "

GAUSS-01983: "cannot continue WAL streaming, recovery has already ended"

SQLSTATE: XX000

Description: The walreceiver does not need to be enabled on the primary server. If it is enabled, an error message is reported.

Solution: The error message reporting is normal and does not need to be handled.

GAUSS-01984: "invalid standby handshake message type %d"

SQLSTATE: 08P01

Description: The primary server receives an invalid handshake type from the standby server.

Solution: Check whether the primary and standby server environment is normal and whether packet loss occurs. If no such issues exist, an internal error occurs. Contact technical support.

GAUSS-01985: "invalid standby query string: %s"

SQLSTATE: 08P01

Description: The primary server receives invalid query fields from the standby server.

Solution: Check whether the primary and standby server environment is normal and whether packet loss occurs. If no such issues exist, an internal error occurs. Contact technical support.

GAUSS-01986: "invalid standby message type '%c'"

SQLSTATE: 08P01

Description: The primary server receives an invalid message type from the standby server.

Solution: Check whether the primary and standby server environment is normal and whether packet loss occurs. If no such issues exist, an internal error occurs. Contact technical support.

GAUSS-01987: "number of requested standby connections exceeds max_wal_senders (currently %d)"

SQLSTATE: 53300

Description: The number of connection requests from the standby server to the primary server exceeds the upper limit. The reason may be that the standby server attempts to connect to the primary server for many times but all fail.

Solution: Check whether the former connections are ended. If not, manually close them.

GAUSS-01988: "could not read to data file %s length %u: %m"

SQLSTATE: XX000

Description: Reading the data file fails.

Solution: Determine the reason by analyzing the %m error message in logs. Recovery method: 1. If the problem is caused by some recoverable factors, perform restoration operation and restart the system. 2. If the problem is caused by unrecoverable faults, such as file damages and disk faults, restore the cluster from its backup data. "

GAUSS-01989: "fseek data file num %u error"

SQLSTATE: XX000

Description: Files fail to be accessed. The reason may be that the file descriptor is invalid.

Solution: R&D engineers need to check whether the file descriptors accessed are valid.

GAUSS-01990: "datareceiver still running according to shared memory state"

SQLSTATE: XX000

Description: Internal system error.

Solution: Contact technical support.