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 log location received does not match with that can be written to the buffer.
Solution: Re-establish the primary-standby relationship. The standby server synchronizes the latest log segments.
GAUSS-02022: "rm xlog comand 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 tuple descriptor constructed is not a row result message.
Solution: Query again. Check whether this 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 rather than the primary-standby replication slot specifies a database.
Solution: Record error information. 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. Re-build the standby server or restart the secondary server. In the cluster environment, the CM server 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 file exists in the pg_xlog directory of the instances or 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 exists in the pg_xlog directory of the instances or 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 whether abnormal deletion occurs by analyzing logs and data files. Restart instances.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.