GAUSS-03761 -- GAUSS-03770
GAUSS-03761: "openning partition %u, but relation %s %u is neither table nor index"
SQLSTATE: XX000
Description: The operation partition is neither a table nor an index.
Solution: Check whether the object of the SQL operation is a table or index.
GAUSS-03762: "closing partition %u, but relation %u is neither table nor index"
SQLSTATE: 2200X
Description: The closed partition is neither a table nor an index.
Solution: Check whether the object of the SQL operation is a table or index.
GAUSS-03763: "failed to add tuple to page"
SQLSTATE: XX000
Description: Failed to add a tuple to the page.
Solution: Contact technical support.
GAUSS-03764: "page %u of relation '%s' should be empty but is not"
SQLSTATE: XX000
Description: The page should not be empty.
Solution: Contact technical support.
GAUSS-03765: "tuple is too big: size %lu"
SQLSTATE: XX000
Description: The tuple length is greater than the free space on the page.
Solution: Contact technical support.
GAUSS-03766: "Unsupported data type in CStore"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-03767: "This query is not supported by optimizer in CStore"
SQLSTATE: XX000
Description: The column-store query is run on the CN.
Solution: Check whether the column-store table is queried on the CN.
GAUSS-03768: "number of local indexes found: %d for partition %s not equal with number of indexes on table: %d"
SQLSTATE: 42809
Description: Internal system error.
Solution: Contact technical support.
GAUSS-03769: "Invalid partition value cache record"
SQLSTATE: XX000
Description: The value read from the cache is incorrect while you insert data to a column-store partitioned table.
Solution: Contact technical support.
GAUSS-03770: "read incomplete record from partition value cache."
SQLSTATE: XX000
Description: The value read from the cache is incorrect while you insert data to a column-store partitioned table.
Solution: Contact technical support.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.