Monitoring the Oracle Database
With the Oracle
database
alert
monitor you can keep track of the following database functions for your
SAP System:
· Space management to monitor tablespaces and segments.
· Performance to monitor optimizer statistics, buffers, logs, and checkpoints
· Backup/restore to monitor database and redo log backup
· Consistency to check the consistency between the indexes, database objects, and database tables included in the ABAP Dictionary and those in the Oracle data dictionary.
· Health to monitor BRCONNECT database system checks
By configuring data collection tools, or methods, to run periodically, alerts are automatically updated and fed into the monitoring architecture. Analysis tools provide additional information about the alert conditions, and auto-react tools can be configured to automatically respond when an alert occurs.
For more information, see Information on Oracle Database Alerts.
Many alerts,
especially those under Health, are
based on
Database System Check
with BRCONNECT, which delivers much of the data required for database
monitoring to the SDBAD table. This avoids
time-consuming access to the Oracle data dictionary view DBA_SEGMENTS.

Therefore, we recommend you to schedule at least daily BRCONNECT database checks in the DBA Planning Calendar, so that the alerts in the database monitor are up-to-date.
For more information, see Database System Check and SAP Note 483659.

Database system check in the SAP System uses BRCONNECT by default from SAP Web Application Server 6.10 onwards. If you have an older release that still uses SAPDBA and you want to change to BRCONNECT, see SAP Note 403704.
...
1. To start the Oracle database monitor, choose Administration ® CCMS ® Control/Monitoring ® Alert Monitor ® SAP CCMS Monitor Templates ®Database. Alternatively, call transaction RZ20.
2. Open the monitors and check the results.
3. If any alerts have been raised, take the necessary action to correct the problem.

Some data collection tools, or methods, provide data for more than one node. Thresholds for these methods and how frequently they are scheduled to run can be configured through the node to which the method is attached. Unless otherwise noted, a node's collection and analysis methods are available from the node itself.
