The system has started or completed a backup operation. The NUMDATAINFO parameter indicates the state of the backup, which can have one of the following values:

Note that the server also posts a second event (SYS_EVENT_MESSAGES) when it starts or completes a backup.

A backup operation has been requested (but has not yet started).

If the user application callback function returns non-zero, backup is not performed.

This event can be caught by the user only if the user is using Shared Memory Access (SMA) or Linked Library Access (LLA).

None of the parameters are used.

The system has started or completed a checkpoint operation.

If the system started a checkpoint, then the "state" parameter (NUMDATAINFO) is 1, and the message (TEXTDATA) parameter is "started".

If the system completed a checkpoint, then the "state" parameter (NUMDATAINFO) is 0, and the message (TEXTDATA) parameter is "completed".

A checkpoint operation has been requested (but has not yet started). Checkpoints are typically executed each time a certain number of log writes has completed.

If the user application callback function returns non-zero, then the merge is not performed.

This event can be caught by the user only if the user is using SMA or LLA.

None of the parameters are used.

Some type of server error has occurred. The message parameter (TEXTDATA) contains the error text. See Conditions or warnings that cause SYS_EVENT_ERROR for a list of server errors that can cause this event to be posted.

The system is idle.

Some tasks have a priority of "idle" and are only run when the system is not running any other tasks. Because very low priority tasks can be running in an "idle" system, the system is not necessarily truly idle in the sense of not doing anything.

This event can be caught by the user only if the user is using SMA or LLA.

None of the parameters are used.

The system has encountered an event related to in-memory database memory limits.

The NUMDATAINFO parameter indicates the current memory allocation in kilobytes.

The TEXTDATA parameter can have one of the following values:

There has been an illegal login attempt. The user name (TEXTDATA) and userid (NUMDATAINFO) indicate the user who tried to log in.

When the sync mode changes from NORMAL to MAINTENANCE, the server will send this system event. The value of the NODE_NAME parameter is the name of the node in which maintenance mode started.

A single solidDB server can have multiple "nodes" (catalogs).) For more details about sync mode, see SET SYNC MODE.

Parameters: NODE_NAME WVARCHAR.

When the sync mode changes from MAINTENANCE to NORMAL, the server will send this system event. The value of the NODE_NAME parameter is the name of the node in which maintenance mode started.

A single solidDB server can have multiple "nodes" (catalogs).) For more details about sync mode, see SET SYNC MODE.

Parameters: NODE_NAME WVARCHAR

An event associated with the "merge" operation (merging data from the Bonsai tree to the main storage tree) has occurred. The parameter STATE (NUMDATAINFO) gives more details:

A merge operation has been requested (but has not yet started).

If the user application callback function returns non-zero, the merge is not performed.

This event can be caught by the user only if the user is using SMA or LLA.

None of the parameters are used.

This event is posted when the server has a message (error message or warning message) to log to solerror.out or solmsg.out. In this case, the TEXTDATA contains the message text and NUMDATAINFO the code. If the message to be written is an error, both SYS_EVENT_ERROR and SYS_EVENT_MESSAGES will be posted. If the message is only a warning, only SYS_EVENT_MESSAGES is posted. For a list of the warnings that can cause SYS_EVENT_MESSAGES, see Conditions or warnings that cause SYS_EVENT_MESSAGES.

Event sent with ADMIN COMMAND 'notify'.

This event is posted if a configuration parameter is changed with the following command:

The parameter MESSAGE (TEXTDATA) contains the section name and the parameter name.

The system has encountered an event related to process size memory limits.

The NUMDATAINFO parameter indicates the current memory allocation in kilobytes.

The TEXTDATA parameter can have one of the following values:

This event indicates that there is a change in the CREP replicator status.

The NUMDATAINFO parameter details the replicator status and contains one of the following integer values:

This event indicates that there are rows that need to be merged from the Bonsai tree to the main storage tree. The rows parameter (NUMDATAINFO) indicates the number of non-merged rows in the Bonsai tree.

This event is posted when a START AFTER COMMIT (SAC) fails. The application can wait for this event and use the job ID (which is in the NUMDATAINFO field) to retrieve the error message from the system table SYS_BACKGROUNDJOB_INFO. (The job ID in NUMDATAINFO matches the job ID that is returned when the START AFTER COMMIT statement is executed.)

A shutdown request has been received. If the user application callback function returns non-zero, then shutdown is not performed.

This event can be caught by the user only if the user is using SMA or LLA.

None of the parameters are used.

This event is posted when monitoring settings are changed.

State (NUMDATAINFO) has one of the following values:

0: monitoring off.

1: monitoring on.

UID is the user ID of the user for whom monitoring was turned on or off.

This event is posted when the "state" of the database is changed. The parameter STATE (NUMDATAINFO) indicates the new state:

This event is posted when a server shutdown is started. The NUMDATAINFO and TEXTDATA parameters provide no information.

Server trace is turned on or off with the ADMIN COMMAND 'trace' command.

The parameter STATE (NUMDATAINFO) indicates the new trace state:

This event is posted when an "AT" command (that is, a timed command) is executed. The message parameter (TEXTDATA) contains the command.

This event is not used.

The parameter REASON (NUMDATAINFO) contains the reason for the event: