As well as events that serve to automate administration tasks (see Concepts of the Database System, Overview of Database Events), there are also special events of the event dispatcher. These events provide information about the status of the event dispatcher.
The special events of the event dispatcher are always active so you do not need to activate them with the Database Manager CLI.
Special Events of the Event Dispatcher
Name |
When does the database instance trigger this event? |
DISPINFO:DISPSTART |
When a user starts the event dispatcher. |
DISPINFO:DISPSTOP |
When a user stops the event dispatcher. |
DISPWARN:SHUTDOWN |
When the database instance has been set to the OFFLINE operational state. |
DISPERR:DBCRASH |
When the database instance kernel crashes (system breakdown). |
DISPERR:CONNLOST |
When the event dispatcher loses the connection to the DBM server. If you have started the event dispatcher on the same computer as the database application, this event can also be used to inform you of a breakdown in the network connection between the database application and the database instance. |
DISPWARN:MISSEDEVT |
When the database instance kernel has sent an event and the event dispatcher does not react to this. |
DISPERR:NOEVENTTASK |
When it was not possible to start the event dispatcher because there were no more event tasks free. To configure the number of event tasks, use the database parameter _MAXEVENTTASKS, see Concepts of the Database System, Support Database Parameters. |
See also:
Overview of Event Dispatcher Commands