2.4.2 NDB Error Codes: by Type

2.4.2.1 No error

2.4.2.2 Application error

2.4.2.3 Configuration or application error

2.4.2.4 No data found

2.4.2.5 Constraint violation

2.4.2.6 Schema error

2.4.2.7 Schema object already exists

2.4.2.8 User defined error

2.4.2.9 Insufficient space

2.4.2.10 Temporary Resource error

2.4.2.11 Node Recovery error

2.4.2.12 Overload error

2.4.2.13 Timeout expired

2.4.2.14 Node shutdown

2.4.2.15 Internal temporary

2.4.2.16 Unknown result error

2.4.2.17 Internal error

2.4.2.18 Function not implemented

This section contains a number of error code lists, one for each type of NDB API error. The error types include the following:

• No error

• Application error

• Scan application error

• Configuration or application error (currently unused)

• No data found

• Constraint violation

• Schema error

• User defined error

• Insufficient space

• Temporary Resource error

• Node Recovery error

• Overload error

• Timeout expired

• Node shutdown

• Internal temporary

• Unknown result error

• Unknown error code (currently unused)

• Internal error

• Function not implemented

The information in each list includes, for each error:

• The NDB error code

• The corresponding MySQL error code

• The NDB classification code

  See Section 2.4.4, “NDB Error Classifications”, for the meanings of these classification codes.

• The text of the error message

Similar errors have been grouped together in each list. Each list is ordered alphabetically.

You can always obtain the latest error codes and information from the file storage/ndb/src/ndbapi/ndberror.cpp. (In previous releases of NDB Cluster, this file was named ndberror.c.)

These types are also shown in the error_status column of the ndbinfo.error_messages table.