GAUSS-01761 -- GAUSS-01770
GAUSS-01761: "column name must be qualified"
SQLSTATE: 42601
Description: The attribute name in the object must be specified and described.
Solution:contact technical support
GAUSS-01762: "must be owner of large object %u"
SQLSTATE: 42501
Description: The execution user is not the owner of the large object.
Solution: Check whether the user is the owner of the large object.
GAUSS-01763: "must be system admin"
SQLSTATE: 42501
Description: The current user is not an initial user.
Solution: Ensure that the user permissions are correctly inherited when the object is defined.
GAUSS-01764: "must have CREATEROLE privilege"
SQLSTATE: 42501
Description: The current user needs to obtain the permission to create objects.
Solution: Check the permissions of the user who owns the object data and verify the validity of the object.
GAUSS-01765: "unrecognized object type: %d"
SQLSTATE: XX000
Description: Internal system error.
Solution:contact technical support
GAUSS-01766: "cache lookup failed for cache %d oid %u"
SQLSTATE: XX000
Description: Internal system error.
Solution:contact technical support
GAUSS-01767: "unrecognized class id: %u"
SQLSTATE: XX000
Description: Internal system error.
Solution:contact technical support
GAUSS-01768: "temporary tables cannot specify a schema name"
SQLSTATE: 42P16
Description: The current temporary table is not in the original temporary tablespace.
Solution: Ensure that the temporary tablespace is correctly created and that the tablespace OID is correct.
GAUSS-01769: "could not obtain lock on relation '%s.%s'"
SQLSTATE: 55P03
Description: The error occurs because the lock cannot be requested.
Solution: Check whether there are conflicting locks on the table or whether all locks are allocated.
GAUSS-01770: "no schema has been selected to create in"
SQLSTATE: 3F000
Description: The corresponding space is not specified when the table is created.
Solution: Create a schema or enter a created schema and create the table again.
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