Statuses are defined for every database instance. Their occurrence triggers an event.
Certain events are always triggered and cannot be disabled. The time proposed by the system as to when the event should be triggered cannot be changed.
Other events
can be disabled or the time proposed by the system as to when the event should
be triggered can be changed. More than one value can be defined for certain
statuses, and an event should be output for each value.
You can use these events, for example, to display warnings of potential
performance problems when a certain usage level is reached, or to issue a note
when the optimizer statistics need to be updated.
The following events can be triggered:
Name |
Can it be disabled? |
Description |
ALIVE |
No |
Database instance is running |
AUTO_SAVE |
No |
Automatic log backup has started |
BACKUP_PAGES |
Yes |
Number of pages written in the backup |
DB_ABOVE_LIMIT |
Yes |
Defined database usage level (in percent) is exceeded |
DB_BELOW_LIMIT |
Yes |
Defined database usage level (in percent) is not reached |
EVENT |
No |
Event configuration has been changed |
LOG_ABOVE_LIMIT |
Yes |
Defined log usage level (in percent) is exceeded |
RESTART_SHUTDOWN |
No |
Database instance has been transferred to another operation status |
UPDATE_STATISTICS |
No |
SQL optimizer statistics need to be updated |
WARNING |
No |
A warning has been entered in the knldiag log file |
ERROR |
No |
An error has been entered in the knldiag log file |
You can use the following DBM commands to access events of the database instance:
event_set |
|
event_release |
|
event_delete |
|
event_wait |
You have the server authorization DBInfoRead.