# eXtreme DB Disk Manager Error Codes

> The following error codes indicate non-fatal error conditions that might be returned by the eXtremeDB disk manager:

> Mnemonic Constant Name
> Value
> Meaning
> MCO_E_DISK
> 100
> General disk manager error
> MCO_E_DISK_OPEN
> 101
> Unable to open persistent storage device
> MCO_E_DISK_ALREADY_OPENED
> 102
> Persistent storage device already opened
> MCO_E_DISK_NOT_OPENED
> 103
> Persistent storage device not opened
> MCO_E_DISK_INVALID_PARAM
> 104
> Invalid disk parameters value
> MCO_E_DISK_PAGE_ACCESS
> 105
> Attempt to access invalid disk page
> MCO_E_DISK_OPERATION_NOT_ALLOWED
> 106
> Specified disk operation is not allowed
> MCO_E_DISK_ALREADY_CONNECTED
> 107
> Persistent storage device is already connected
> MCO_E_DISK_KEY_TOO_LONG
> 108
> Index key is too long
> MCO_E_DISK_TOO_MANY_INDICES
> 109
> Too many indexes in persistent classes
> MCO_E_DISK_TOO_MANY_CLASSES
> 110
> Too many persistent classes
> MCO_E_DISK_SPACE_EXHAUSTED
> 111
> Persistent storage is out of space
> MCO_E_DISK_INCOMPATIBLE_LOG_TYPE
> 112
> Incompatible database log type
> MCO_E_DISK_BAD_PAGE_SIZE
> 113
> Database page size is not acceptable
> MCO_E_DISK_SYNC
> 114
> Failed operation on sync primitive
> MCO_E_DISK_PAGE_POOL_EXHAUSTED
> 115
> Too many pinned disk pages
> MCO_E_DISK_CLOSE
> 116
> Error closing persistent storage device
> MCO_E_DISK_TRUNCATE
> 117
> Unable to truncate persistent storage device
> MCO_E_DISK_SEEK
> 118
> Unable to perform seek in persistent storage device
> MCO_E_DISK_WRITE
> 119
> Unable to write to persistent storage device
> MCO_E_DISK_READ
> 120
> Unable to read from persistent storage device
> MCO_E_DISK_FLUSH
> 121
> Unable to flush to persistent storage device
> MCO_E_DISK_TOO_HIGH_TREE
> 122
> Index too big
> MCO_E_DISK_VERSION_MISMATCH
> 123
> Version mismatch
> MCO_E_DISK_CONFLICT
> 124
> MVCC conflict
> MCO_E_DISK_SCHEMA_CHANGED
> 125
> Database schema was changed
> MCO_E_DISK_CRC_MISMATCH
> 126
> CRC is not matched for the loaded page
> MCO_E_DISK_TM_MISMATCH
> 127
> Different transaction manager is used (MVCC/MURSIW)
> MCO_E_DISK_DICT_LIMITS_MISMATCH
> 128
> Different max_classes/max_indexes
> MCO_E_DISK_BTREE_ALLOC
> 129
> Failed allocate new B-Ttree page: could run out of disk, or out of page pool
> Invalid return codes
> 130-199
> Values between 130 and 199 are not valid eXtremeDB return codes

> Related Topics