solidDB Help : solidDB reference : SQL: System events : Conditions or warnings that cause SYS_EVENT_MESSAGES
  
Conditions or warnings that cause SYS_EVENT_MESSAGES
This topic lists the warning messages that cause the server to post the event SYS_EVENT_MESSAGES
The numbers in the Error code column match the solidDB error code numbers, as listed in Error codes. These values get passed in the NUMDATAINFO event parameter.
 
Error code
Error description
30010
User username failed to connect, version mismatch. Client version version, server version version.
30011
User username failed to connect, collation version mismatch.
30012
User username failed to connect, there are too many connected clients.
30020
Server is in fatal state, no new connections are allowed
30020
User username failed to connect, database character set is utf8, unsupported by client.
30282
Checkpoint creation not started because shutdown is in progress.
30283
Checkpoint creation not started because it is disabled.
30300
Backup completed successfully.
The server also posts a second event (SYS_EVENT_BACKUP) when it starts or completes a backup.
30301
Backup started to directory_path.
The server also posts a second event (SYS_EVENT_BACKUP) when it starts or completes a backup.
30359
Server noticed time inconsistency during at-command execution. If the system time has been changed, restart the server.
30361
Illegal at command command ignored.
30362
Illegal immediate at command command ignored.
30405
Unable to open message log file file_name
30800
Unable to reserve requested number memory blocks for external sorter.
Only number memory blocks were available. SQL: SQL_statement
30801
Unable to reserve requested <number> memory blocks for external sorter.
Only number memory blocks were available.
Go up to
SQL: System events