GAUSS-04381 -- GAUSS-04390
GAUSS-04381: "detected write past chunk end in %s %p"
SQLSTATE: XX000
Description: While memory is freed up, the entered characters are verified. If the characters are incorrect, an error is reported.
Solution: A PANIC level error occurs when the system checks memory overwriting in debug mode. When the process is stopped, a core dump occurs.
GAUSS-04382: "Error happen when execute memcpy_s:%d"
SQLSTATE: XX000
Description: When the security function is invoked, an error occurs in memory replication.
Solution: Roll back the job that is being executed.
GAUSS-04383: "Bucketmap is NULL"
SQLSTATE: XX000
Description: Bucketmap is empty.
Solution: Do not perform this operation.
GAUSS-04384: "invalid thread id: 0"
SQLSTATE: 22023
Description: During function parameter check, the value 0 exists. Zero indicates that the thread ID is invalid.
Solution: Enter a valid thread ID.
GAUSS-04385: "invalid name of memory context: NULL or '' "
SQLSTATE: XX000
Description: The NULL or empty characters are regarded as invalid memory context names when the system checks the function parameters.
Solution: Ensure that the memory context is valid.
GAUSS-04386: "Failed to receive GTM commit transaction response for DN or other CN."
SQLSTATE: XX000
Description: The feedback information to notify the GTM of submitting a transaction fails to be obtained due to GTM disconnection.
Solution: Check whether the connection between the GTM and other instances is normal.
GAUSS-04387: "column '%s' needs too many memory"
SQLSTATE: 0A000
Description: The number of records imported using the column-store method is too large.
Solution: Import the records using the row-store method.
GAUSS-04389: "Failed to initialze multi-threads for LLVM."
SQLSTATE: XX000
Description: During the database start, the LLVM fails to initialize the multi-thread environment.
Solution: Restart the database.
GAUSS-04390: "Failed to initialze NativeTarget for LLVM."
SQLSTATE: XX000
Description: Failed to initialize the LLVM local object when starting the database.
Solution: Restart the database.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.