!--a11y-->
Monitoring the Database with the Alert Monitor
(Informix) 
Using the
alert monitor, you
can monitor the following database alerts:
· Space management – reorganization and space monitoring
· DB system check – consistency and profile
· Backup/restore
The alerts described in this section are all triggered automatically from DB System Checks in CCMS (Informix).
· Changing the default thresholds
Although SAP recommends that you do not normally change the default thresholds, you can set thresholds yourself for most of the database alerts.
· Deactivating an alert
You can deactivate an alert, but only do this for a particular reason and for a short time.
For more information, see Configuring DB System Checks in CCMS (Informix).
...
1. Start the alert monitor.
2. Choose SAP CCMS Monitor Templates.
3. Choose Entire System.
4. Open the Database monitoring tree element (MTE).
For each instance, the alerts are displayed with color coding to indicate severity. The following alerts are possible in the Database MTE:
MTE |
Meaning |
For more information, see |
SpaceManagement |
Monitors the space situation in your database |
|
Reorganization |
Checks if reorganization or application data archive required, due to tables running out of extents or running out of allocated pages |
|
SpaceMonitoring |
Checks if dbspace fill level OK and if tables can be extended correctly |
See also next step. |
DBSystemCheck |
Checks key aspects of your database system |
|
DB Consistency |
Checks if chunk sizes are within limit, if raw devices are overlapping, and if logging mode OK |
|
DB Profile |
Checks value of settings in the ONCONFIG file |
|
Backup |
Checks aspects affecting database backup and archive |
|
Restore |
Checks number of |

To get up-to-date and detailed information about what the alerts mean and how you should react, use the online help.
5. If you have the SpaceMonitoring alert for a dbspace, choose Start analysis tool to extend the dbspace. Refer to Extending a Dbspace with CCMS.
By using the database alert monitor continually during productive database operation, you can find out quickly and easily whether your database has problems. The result is a more highly tuned database and reduced system downtime.
