# eXtremeDB Status Codes

> The following table lists status codes that can be returned by the eXtremeDB runtime. These return codes do not indicate error conditions but rather runtime states that can and will occur during normal database operations.

> Mnemonic Constant Name
> Value
> Meaning
> MCO_S_OK
> 0
> Success
> MCO_S_BUSY
> 1
> The instance is busy
> MCO_S_OVERFLOW
> 2
> Tree overflow (Indicates an internal error with B-Tree indexes which should not be returned to the user)
> MCO_S_UNDERFLOW
> 3
> Tree underflow (Indicates an internal error with B-Tree indexes which should not be returned to the user)
> MCO_S_NOTFOUND
> 10
> Search operation failed
> MCO_S_CURSOR_END
> 11
> Cursor cannot be moved
> MCO_S_CURSOR_EMPTY
> 12
> No objects in index
> MCO_S_DUPLICATE
> 13
> Index restriction violated (duplicate)
> MCO_S_EVENT_RELEASED
> 14
> Waiting thread was released
> MCO_S_DEAD_CONNECTION
> 15
> Database connection is invalid
> MCO_S_NULL_VALUE
> 16
> Field has NULL value
> MCO_S_TL_INVDATA
> 17
> Broken record during recovering
> MCO_S_TL_NOT_INITIALIZED
> 18
> TL is not initialized in current process
> MCO_S_DEFERRED_DELETE
> 19
> Memory segment is busy, will be deleted later
> Invalid return codes
> 20-48
> Values between 20 and 48 are not valid eXtremeDB return codes

> Related Topics