GAUSS-01221 -- GAUSS-01230
GAUSS-01221: "Column Store unsupport CHECK constraint"
SQLSTATE: XX000
Description: Currently, column storage does not support the CHECK constraint.
Solution: Delete the CHECK constraint.
GAUSS-01222: "cannot copy to view '%s'"
SQLSTATE: 42809
Description: Failed to use COPY to copy data to a view.
Solution: Do not use COPY to copy data to a view.
GAUSS-01223: "cannot copy to foreign table '%s'"
SQLSTATE: 42809
Description: Failed to use COPY to copy data to a foreign table.
Solution: Do not use COPY to copy data to a foreign table.
GAUSS-01224: "cannot copy to sequence '%s'"
SQLSTATE: 42809
Description: Failed to use COPY to copy data to a sequence.
Solution: Do not use COPY to copy data to a sequence.
GAUSS-01225: "cannot copy to non-table relation '%s'"
SQLSTATE: 42809
Description: Failed to use COPY to copy data to a non-table.
Solution: Do not use COPY to copy data to a non-table.
GAUSS-01226: "invalid COPY file header (COPY SEND)"
SQLSTATE: 22P04
Description: The file header specified by COPY is invalid.
Solution: The data file specified by COPY is damaged. Check the file.
GAUSS-01227: "Copy failed on a Datanode"
SQLSTATE: 08000
Description: Failed to import data.
Solution: Check logs on DNs to identify the error type and take required measures.
GAUSS-01228: "Missing data when batch insert compressed data !"
SQLSTATE: XX000
Description: Data is lost while compressed data is imported to a row-store table.
Solution: Run alter table to disable the compression feature of the row-store table and import the data again.
GAUSS-01229: "Non-shippable ROW triggers not supported with COPY"
SQLSTATE: 0A000
Description: COPY does not support row triggers.
Solution: Do not use row triggers in COPY.
GAUSS-01230: "could not open file '%s' for reading: %m"
SQLSTATE: XX000
Description: The file failed to be opened.
Solution: Based on the error codes, identify the causes of the open failure (The file does not exist, the user does not have the permission, or the disk space is full.) and resolve the problem.
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