GAUSS-03301 -- GAUSS-03310
GAUSS-03301: "cannot lock cluster for backup in presence of %d uncommitted prepared transactions"
SQLSTATE: 55P03
Description: The cluster cannot be locked for backup in presence of uncommitted prepared transactions.
Solution: Lock the cluster for backup after prepared transactions are committed.
GAUSS-03302: "cannot lock cluster for backup, lock is already held"
SQLSTATE: 55P03
Description: The cluster cannot be locked for backup because the lock is not obtained.
Solution: Lock the cluster for backup after the relevant locked resources are released.
GAUSS-03303: "cannot execute %s in a locked cluster"
SQLSTATE: 25006
Description: The cluster is locked by another database user. The command cannot be run.
Solution: Lock the cluster for backup after the relevant locked resources are released.
GAUSS-03304: "word is too long (%ld bytes, max %ld bytes)"
SQLSTATE: 54000
Description: The word is too long that exceeds the allowed maximum value.
Solution: Use word within the allowed range.
GAUSS-03305: "string is too long for tsvector (%ld bytes, max %ld bytes)"
SQLSTATE: 54000
Description: The string is too long that exceeds the allowed maximum length.
Solution: Use strings within the allowed range.
GAUSS-03306: "positions array too long"
SQLSTATE: XX000
Description: The length of the entered string exceeds the maximum length allowed by the tsvector type (1<<20) - 1.
Solution: Shorten the string.
GAUSS-03307: "invalid size of tsvector"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-03308: "invalid tsvector: lexeme too long"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-03309: "invalid tsvector: maximum total lexeme length exceeded"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-03310: "unexpected number of tsvector positions"
SQLSTATE: XX000
Description: Internal system error.
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