Updated on 2025-03-26 GMT+08:00

GAUSS-01111 -- GAUSS-01120

GAUSS-01111: "cannot cluster on invalid index '%s'"

SQLSTATE: 0A000

Description: The specified index is an invalid index left after CREATE INDEX CONCURRENTLY fails to be executed.

Solution: Do not cluster invalid indexes.

GAUSS-01112: "cannot cluster on invalid index %u"

SQLSTATE: XX000

Description: The index is invalid. Clustering cannot be performed.

Solution: The system catalog is abnormal and you should contact technical support.

GAUSS-01113: "CLUSTER does not support lossy index conditions"

SQLSTATE: XX000

Description: Lossy index conditions cannot be used for the CLUSTER table.

Solution: Check the index created in the CLUTER table. Hash and gist indexes are not supported.

GAUSS-01114: "unexpected HeapTupleSatisfiesVacuum result"

SQLSTATE: XX000

Description: Internal system error.

Solution:contact technical support

GAUSS-01115: "can not cluster partition %s using %s because of unusable local index"

SQLSTATE: XX000

Description: The clustered partitioned table cannot use local indexes because they are unavailable.

Solution: Rebuild the partitioned table.

GAUSS-01116: "clustering failed, internal error"

SQLSTATE: XX000

Description: The partitioned index table is invalid.

Solution: Rebuild the partitioned table to generate a correct partitioned index table.

GAUSS-01117: "cannot swap mapped relation '%s' with non-mapped relation"

SQLSTATE: XX000

Description: During scale-out, the physical files of two tables fail to be exchanged using the gs_switch_relfilenode function, because the physical file in a table is invalid.

Solution: Check whether the physical file in the table specified in the gs_switch_relfilenode function is valid. If it is invalid, delete the table and rebuild the table using CREATE TABLE. Then, rebuild its physical file.

GAUSS-01118: "cannot change tablespace of mapped relation '%s'"

SQLSTATE: XX000

Description: During scale-out, the tablespaces of two tables are inconsistent and fail to be exchanged using the gs_switch_relfilenode function.

Solution: Delete the current table, rebuild tablespace using CREATE TABLESPACE, and rebuild the table using CREATE TABLE.

GAUSS-01119: "cannot swap toast by links for mapped relation '%s'"

SQLSTATE: XX000

Description: During scale-out, the physical files of two tables fail to be exchanged using the gs_switch_relfilenode function, because the toast table in one of the tables is empty.

Solution: Delete the current table, rebuild it using CREATE TABLE, and rebuild its physical file.

GAUSS-01120: "could not find relation mapping for relation '%s', OID %u"

SQLSTATE: XX000

Description: During scale-out, the physical files of two tables fail to be exchanged using the gs_switch_relfilenode function, because the physical file in a table is invalid.

Solution: Check whether the physical file in the table specified in the gs_switch_relfilenode function is valid. If it is invalid, delete the table and rebuild the table using CREATE TABLE. Then, rebuild its physical file.