GAUSS-07611 -- GAUSS-07620

GAUSS-07611: “Length of CBM file home path exceeds MAXPGPATH!”

SQLSTATE:

Description:Internal system error.

Solution:Contact technical support.

GAUSS-07612: “Length of absolute CBM file path would exceed MAXPGPATH!”

SQLSTATE:

Description:Internal system error.

Solution:Contact technical support.

GAUSS-07613: “memory is temporarily unavailable while allocate page read buffer during validate CBM file”

SQLSTATE: 53000

Description:Internal system error.

Solution:Contact technical support.

GAUSS-07614: “Failed to truncate CBM file '%s' to length %ld”

SQLSTATE:

Description:Internal system error.

Solution:Contact technical support.

GAUSS-07615: “could not create new CBM file '%s': %m”

SQLSTATE:

Description:Internal system error.

Solution:Contact technical support.

GAUSS-07616: “could not open CBM file '%s': %m”

SQLSTATE:

Description:Internal system error.

Solution:Contact technical support.

GAUSS-07617: “failed to stat current cbm file %s :%m”

SQLSTATE:

Description:Internal system error.

Solution:Contact technical support.

GAUSS-07618: “The xlog LSN to be parsed %08X/%08X is smaller than already tracked xlog LSN %08X/%08X. This may be caused by xlog truncation (pg_rewind), xlog corruption or PITR (at present CBM does not support multiple timelines). Under these scenarios, inconsistent CBM files may be created. To be safe, we zap all existing CBM files and restart CBM tracking”

SQLSTATE: 22023

Description:Internal system error.

Solution:Contact technical support.

GAUSS-07619: “memory is temporarily unavailable while allocate xlog reader”

SQLSTATE: 53000

Description:Internal system error.

Solution:Contact technical support.

GAUSS-07620: “could not read WAL record at %08X/%08X: %s”

SQLSTATE: 22000

Description:Internal system error.

Solution:Contact technical support.