Overview of Database Event
Categories 
Use
The following event categories exist:
● Event categories whose events are always active and cannot be changed
●
Event categories
for which you can activate/deactivate and change events. For each of these
event categories you can set one or more events to be triggered by the
database system when the corresponding defined value is reached (See:
Database
Manager CLI, 
event_set).
See also:
Automating Administration Tasks
Database Manager CLI, Using Events of the
Database Instance
Event Dispatcher
documentation
Event categories for which events are always active
(These events can be neither changed nor deactivated)
Event Category |
Description |
ADMIN |
The system triggers an event of this category when the database instance has been transferred to the ADMIN operational state. This event has the priority LOW. |
AUTOSAVE |
The system triggers an event of this category when the status of the automatic log backup changes. This event has the priority LOW. |
BACKUPRESULT |
Not yet implemented |
CHECKDATA |
The system triggers an event of this category when it has completed the database structure check (CHECK DATA or CHECK DATA WITH UPDATE). This event has the priority LOW. |
DATABASEFULL |
The systems triggers an event of this category at regular intervals when the data area of the database instance is 100% full. Note that the system only triggers this event in the ONLINE operational state and during a restart of the database instance. This event has the priority HIGH. To continue operation, add a data volume. |
ERROR |
The system triggers this event when it has entered an error in the kernel log knldiag. This event has the priority HIGH. |
EVENT |
The system triggers an event of this category when the event configuration has been changed. This event has the priority LOW. |
LOGFULL |
The system triggers an event of this category when the log area of the database instance is 100% full. This event has the priority HIGH. To continue operation, execute a log backup. |
LOGSEGMENTFULL |
The system triggers an event of this category when a log segment of the log area is full. This event has the priority LOW. |
ONLINE |
The system triggers an event of this category when the database instance has been transferred to the ONLINE operational state. This event has the priority LOW. |
OUTOFSESSIONS |
The system triggers an event of this category when all available user tasks are in use (no further users can log on to the database instance). This event has the priority HIGH. |
SYSTEMERROR |
The system triggers an event of this category when a serious system error has occurred (error messages -9000 through -9999). This event has the priority HIGH. |
STANDBY |
The system triggers an event of this category when the database instance has been transferred to the STANDBY operational state. This event has the priority LOW. |
UPDSTATWANTED |
The system triggers an event of this category when the SQL Optimizer statistics for at least one table need to be updated. This event has the priority LOW. |
Event categories for which you can activate/deactivate and change events
Event Category |
Description |
DBFILLINGABOVELIMIT |
The system triggers an event of this category when the fill level of the data area exceeds the predefined value. Events of this category are active with the following default values: HIGH (at fill level 90%, 95%, 96%, 97%, 98%, 99%) | MEDIUM | (at fill level 80%, 85%) LOW (at fill level 70%) In addition, for each time the fill level is exceeded by between 0% and 99%, you can define an event with its own priority. You can also override the priorities of the predefined events. |
DBFILLINGBELOWLIMIT |
The system triggers an event of this category when the fill level of the data area goes below the predefined value. Events of this category are active with the following default values: LOW (default value; at fill level 70%, 80%, 85%, 90%, 95%) | MEDIUM | HIGH In addition, for each time the fill level falls below the threshold by between 1% and 100%, you can define an event with its own priority. You can also override the priorities of the predefined events. |
LOGABOVELIMIT |
The system triggers an event of this category when the fill level of the log area exceeds the predefined value. Events of this category are active with the following default values: HIGH (at fill level 96%,97%,98%,99%) | MEDIUM (at fill level 90%, 95%) | LOW (at fill level 50%, 75%) In addition, for each time the fill level is exceeded, you can define an event with its own priority. You can also override the priorities of the predefined events. |