Statuses are defined for each database instance. If one of these statuses occurs, an event can be triggered.
The system default for the status of all events is active. The following table shows which events can be deactivated and activated again and the events for which the system default for triggering the event can be changed:
Name of the Event |
Can Be Deactivated |
Description |
ADMIN |
No |
The database instance has been set to ADMIN mode. |
AUTO_SAVE |
No |
The automatic log backup has started. |
DBFILLINGABOVELIMIT |
Yes |
The
defined database fill level (in percent) has been exceeded. |
DBFILLINGBELOWLIMIT |
Yes |
The
defined database fill level (in percent) has been undershot. |
EVENT |
No |
The event configuration has been changed. |
LOGABOVELIMIT |
Yes |
The
defined log fill level (in percent) has been exceeded. |
UPDSTATWANTED |
No |
The SQL optimizer statistics must be updated. |
ERROR |
No |
An error has been written to knldiag log file. |
BACKUPRESULT |
No |
The return values of the backup operation (including 0) are output as events. |
CHECKDATA |
No |
The result of the command is output as an event. |
DATABASEFULL |
No |
The data area of the database instance is completely full. A data volume must be added to continue operation. |
LOGFULL |
No |
The log area of the database instance is completely full. A log volume must be added to continue operation. |
ONLINE |
No |
The database instance has been set to ONLINE mode. |
OUTOFSESSIONS |
No |
All existing user tasks are busy. |
STANDBY |
No |
The database instance has been set to STANDBY mode. |
SYSTEMERROR |
No |
A fatal system error has occurred (message numbers -9000 to -9999). |
LOGSEGMENTFULL |
No |
A log segment is full and cannot be backed up. |
Overview of the DBM Commands for Accessing Database Events
Action |
Syntax |
event_set |
|
event_release |
|
event_delete |
|
event_list |
|
event_wait |
You have the DBInfoRead server authorization.