GAUSS-04091 -- GAUSS-04100
GAUSS-04091: "proclock table corrupted"
SQLSTATE: XX000
Description: The proclock hash table is damaged.
Solution: Contact technical support.
GAUSS-04092: "LockAcquire failed"
SQLSTATE: XX000
Description: Failed to obtain a common lock.
Solution: Check the concurrent execution status.
GAUSS-04093: "lock table corrupted"
SQLSTATE: XX000
Description: The lock hash table is damaged.
Solution: Contact technical support.
GAUSS-04094: "lock %s on object %u/%u/%u is already held"
SQLSTATE: XX000
Description: The object has been locked.
Solution: Check the lock status of the object.
GAUSS-04095: "locallock table corrupted"
SQLSTATE: XX000
Description: The locallock hash table is damaged.
Solution: Contact technical support.
GAUSS-04096: "failed to re-find shared lock object"
SQLSTATE: XX000
Description: Failed to find the shared lock again.
Solution: Contact technical support.
GAUSS-04097: "failed to re-find shared proclock object"
SQLSTATE: XX000
Description: Failed to find the shared proclock again.
Solution: Contact technical support.
GAUSS-04098: "too many conflicting locks found"
SQLSTATE: XX000
Description: The number of common lock conflicts is greater than MaxBackends.
Solution: Reduce the number of concurrent SQL statements.
GAUSS-04099: "cannot PREPARE while holding both session-level and transaction-level locks on the same object"
SQLSTATE: 0A000
Description: You cannot hold session-level and transaction-level locks for the same object at the same time.
Solution: Check the lock status of the object.
GAUSS-04100: "we seem to have dropped a bit somewhere"
SQLSTATE: XX000
Description: The masks of holding and releasing the lock do not match.
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.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot