Skip navigation links
2.3.32 The OperationOptions Structure »
Section Navigation      [Toggle]

2.3.31.1. NdbError Types

[+/-]

2.3.31.1.1. The NdbError::Status Type
2.3.31.1.2. The NdbError::Classification Type

Abstract

This section discusses the Status and Classification datatypes defined by NdbError.

2.3.31.1.1. The NdbError::Status Type

Description.  This type is used to describe an error's status.

Enumeration values. 

Value Description
Success No error has occurred
TemporaryError A temporary and usually recoverable error; the application should retry the operation giving rise to the error
PermanentError Permanent error; not recoverable
UnknownResult The operation's result or status is unknown

Note

Related information specific to certain error conditions may be found in Section 5.2.3, “NDB Error Classifications”.

2.3.31.1.2. The NdbError::Classification Type

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

Enumeration values. 

Value 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 nonmaster node.

Note

Related information specific to certain error conditions may be found in Section 5.2.2, “NDB Error Codes and Messages”, and in Section 5.2.3, “NDB Error Classifications”.