Documentation Home
MySQL NDB Cluster API Developer Guide
Download this Manual NdbError::Classification

Description.  This type describes the type of error, or the logical group to which it belongs.

Enumeration values.  Possible values are shown, along with descriptions, in the following table:

Table 2.32 NdbError Classification data type values and descriptions

Name Description
NoError Indicates success (no error occurred)
ApplicationError An error occurred in an application program
NoDataFound A read operation failed due to one or more missing records.
ConstraintViolation A constraint violation occurred, such as attempting to insert a tuple having a primary key value already in use in the target table.
SchemaError An error took place when trying to create or use a table.
InsufficientSpace There was insufficient memory for data or indexes.
TemporaryResourceError This type of error is typically encountered when there are too many active transactions.
NodeRecoveryError This is a temporary failure which was likely caused by a node recovery in progress, some examples being when information sent between an application and NDB is lost, or when there is a distribution change.
OverloadError This type of error is often caused when there is insufficient logfile space.
TimeoutExpired A timeout, often caused by a deadlock.
UnknownResultError It is not known whether a transaction was committed.
InternalError A serious error has occurred in NDB itself.
FunctionNotImplemented The application attempted to use a function which is not yet implemented.
UnknownErrorCode This is seen where the NDB error handler cannot determine the correct error code to report.
NodeShutdown This is caused by a node shutdown.
SchemaObjectExists The application attempted to create a schema object that already exists.
InternalTemporary A request was sent to a node other than the master.


Related information specific to certain error conditions may be found in Section 2.4.2, “NDB Error Codes: by Type”, and in Section 2.4.4, “NDB Error Classifications”.

User Comments
User comments in this section are, as the name implies, provided by MySQL users. The MySQL documentation team is not responsible for, nor do they endorse, any of the information provided here.
Sign Up Login You must be logged in to post a comment.