The revised version provides a great deal of new alert nodes and information that can displayed depending on the database version and instance type.
Furthermore, the concept of the data collection has been changed. In addition to focusing on a small number of data collectors, this includes an internal monitoring of the processing ability and the dependent automatic activation and deactivation of the collectors.
After you import these Support Packages, the liveCache alert monitor must also be set up again as described below, because the old alert monitor no longer works correctly and the analysis methods can generate runtime errors.
I. Creating the revised SAP DB/liveCache monitor
After you import the Support Package mentioned above, you receive the revised SAP DB and liveCache monitor
- automatically when you start the SAP System, or
- by calling the report RSLVCALMON once without specifying a
database connection (without starting the SAP system).
In each case, the old liveCache alert monitor is deleted automatically.
II. Structure of the revised SAP DB/liveCache alert monitoring
The revised SAP DB/liveCache alert monitor is available:
- in transaction RZ20 under "SAP CCMS Monitors for Optional
Components" -> "SAP DB Monitoring", or
- in transaction LC10 by choosing the button "Alert Monitor".
Here, the subtrees for the individual database connections for which the alert monitoring is activated are sorted according to database instance category (liveCache/Content Server/OLTP).
In RZ20, another subtree is generated with internal administrative information for each database connection, in addition to the subtree of the monitor. Both subtrees are found together under the database connection name under RZ20 -> "SAP CCMS Technical Expert Monitors" -> "All Monitoring Contexts".
III. Data collector
Unlike the old alert monitor, a data collector is no longer assigned to every individual leaf. Instead, there are exra nodes in the internal subtree with data collectors of different runtime intervals. Each of these data collectors reports information into several nodes of the monitoring tree.
If errors occur during data collection of a type where the server of the monitored instance is not accessible or where the instance cannot be accessed by SQL, the alert monitoring for the corresponding database connection is deactivated. The system automatically checks every hour whether the data collection can be activated again. If required, this check can also be started using the analysis methods (double-click on one of the collector nodes). To ensure that this check takes place hourly, you must schedule the CCMS standard job SAP_CCMS_MONI_BATCH_DP.
IV. Information about the alert monitor leaves
A long text is defined in the F1 Help for all the SAP DB/liveCache monitor leaves. In addition to the name of the data collector delivering this node, this usually contains further information on the reported values or alert colors.
V. Deleting a database connection from the SAP DB/liveCache Alert Monitor
1. Remove the alert monitoring indicator in transaction LC10 -> "Integration" -> "Alert Monitoring".
2. Call report RSLVCALMDEL with the name of the affected database connection.
Note:Do NOT delete this database connection (by choosing the connection name in the SAP DB/liveCache monitor under "SAP DB Monitoring" and "Edit" -> "Node" -> "Delete"). If you do, all other database connections are then also deleted from the monitor.