# eXtremeDB Transaction Logging Error Codes

> The following error codes indicate non-fatal error conditions that might be returned by the eXtremeDB Transaction Logging runtime while processing Transaction Logging (TL) operations:

> Mnemonic Constant Name
> Value
> Meaning
> MCO_E_TL
> 600
> TL Error Code base
> MCO_E_TL_INVAL
> 601
> Invalid argument value
> MCO_E_TL_ALREADY_STARTED
> 602
> TL already started
> MCO_E_TL_NOT_STARTED
> 603
> TL is not started
> MCO_E_TL_LOG_NOT_OPENED
> 604
> Log file is not opened
> MCO_E_TL_INVFORMAT
> 605
> Completely corrupted LOG file
> MCO_E_TL_NOT_INITIALIZED
> 606
> TL API function called when it is not initialized
> MCO_E_TL_IO_ERROR
> 607
> Input / output error
> MCO_E_TL_NOT_ITERABLE
> 608
> Log file created without flag `MCO_TRANSLOG_ITERABLE` or unsupported transaction manager is applied
> MCO_E_TL_TRANS_STARTED
> 609
> Function invoked inside transaction
> MCO_E_TL_PIPE_USED
> 610
> Pipe still opened by previous instance of reader
> MCO_E_TL_PIPE_LOST
> 611
> Pipes were closed in all of writers connections. Keep at least one opened between log start and stop
> MCO_E_TL_PIPE_TERM
> 612
> Reader abnormally terminated its job
> MCO_E_TL_NO_AUTO_OID
> 613
> No `auto_oid` index declared in the database schema
> MCO_E_TL_NOT_APPLICABLE
> 614
> The only objects related to events mask were written into the Log file. So it can't be useful to restore database
> MCO_E_TL_NO_DYNAMIC_PIPE
> 615
> Attempt to attach / detach pipe device for non-dynamic configuration
> MCO_E_TL_SYNC
> 616
> Failed operation on TL sync primitive
> MCO_E_TL_PLAY_STOPPED
> 617
> Function mco_translog_play (iterate) has been terminated by calling of function `mco_translog_play_stop()`
> MCO_E_TL_PLAY_NOT_STARTED
> 618
> Function mco_translog_play (iterate) has not been started using current connection
> Invalid return codes
> 619-699
> Values between 619 and 699 are not valid eXtremeDB return codes

> Related Topics