GAUSS-02021 -- GAUSS-02030
GAUSS-02021: "Unexpected seek in the walreceiver buffer. xlogrecptr is (%u:%u) but local xlogptr is (%u:%u)."
SQLSTATE: XX000
Description: The location of the received log does not match the location of the log that can be written into the buffer.
Solution: Re-establish the primary-standby relationship. The standby node performs synchronization again based on the last valid log.
GAUSS-02022: "rm xlog command is not from primary,peer_role=%d"
SQLSTATE: XX000
Description: Internal system error.
Solution:contact technical support
GAUSS-02023: "return type must be a row type"
SQLSTATE: XX000
Description: The constructed tuple descriptor is not a row result.
Solution: Query again. If the error persists, contact technical support.
GAUSS-02024: "cannot use a replication slot created for changeset extraction for streaming replication"
SQLSTATE: 55000
Description: The logic slot, not the primary-standby replication slot, specifies a database.
Solution: Record error information and contact technical support.
GAUSS-02025: "cannot handle changeset extraction yet"
SQLSTATE: XX000
Description: Internal system error.
Solution:contact technical support
GAUSS-02026: "requested WAL segment %s has already been removed"
SQLSTATE: XX000
Description: The logs requested by the standby/secondary server have been removed from the primary server.
Solution: Check whether there are discontinuous log names in the pg_xlog directory of the primary server instances. Rebuild the standby server or restart the standby server. In a cluster, the CM automatically rebuilds the standby server. "
GAUSS-02027: "could not open file '%s' (log file %u, segment %u): %m"
SQLSTATE: XX000
Description: A specific log segment file cannot be opened.
Solution: Check whether the opened file exists in the pg_xlog directory of the instance and whether the permission is correct. Resolve the problem based on specific log error codes. "
GAUSS-02028: "could not read from log file %u, segment %u, offset %u, length %lu: %m"
SQLSTATE: XX000
Description: A specific log segment file cannot be opened.
Solution: Check whether the file to be read exists in the pg_xlog directory of the instance and whether the permission is correct. Resolve the problem based on specific log error codes. "
GAUSS-02030: "%u/%u/%u invalid bcm buffer %u"
SQLSTATE: XX000
Description: The specified BCM buffer cannot be read.
Solution: Check logs and data files to determine whether abnormal deletion occurs. Restart instances. "
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot