Information on Oracle Database Alerts

Some monitoring tree elements (MTEs) for alerts when you monitor the Oracle database, especially Database Health Alerts, are marked in this documentation as follows:


These MTEs are based on the most recent database system check with BRCONNECT, using the command brconnect -f check. The conditions for the corresponding checks are specified in the DBCHECKORA table. If required, you can configure the database system check.

For more information on the check conditions, see SAP Note 435290.

BRCONNECT stores the results of the checks in the DBMSGORA table. The MTE Last evaluation of check results evaluates the results of the most recent BRCONNECT checks and, if required, generates alerts in the corresponding MTE nodes.

You can also run a one-off database system check using the MTE Start of database check in the Health monitoring tree to immediately start a new database system check and update the database monitor.

You can also view the results of the database check directly, without using the database alert monitor. For more information, see Displaying Alert Messages from Database System Check.

The BRCONNECT MTEs are dynamically set up during the initialization of the monitoring infrastructure, based on the check conditions set up in the DBCHECKORA table. If one of these MTEs does not have a corresponding check condition in the DBCHECKORA table (because the check is inactive), then it does not appear in the Oracle database monitor.

Therefore, these MTEs can dynamically appear and disappear, depending on whether the corresponding check conditions exist. The MTE always appears at the relevant position in the monitoring tree, as specified in this documentation.

You can set up new check conditions in the following categories:

    • DBO: Concrete database operations (function ID)
    • ORA: Oracle messages (message code, message text)
    • PROF: Oracle profile parameters (parameter names)

You can only set up new check conditions for database administration when the corresponding BRCONNECT functionality is available. For conditions that do not use the OBJECT field in the DBCHECKORA table, you can set up your own name for the corresponding MTE. To do this, specify #RZ20 followed by the new name, as shown in the following example:

This is an example of how to specify a new dynamic MTE:

TYPE field: DBO

PARAM field: DBV

OBJECT field: #RZ20 Database verification

The result is that a new MTE called Database verification is set up in the Oracle database monitor under Health ® DBA operations.

For more information on the BRCONNECT check conditions, see :

Then do the following to reinitialize the Oracle context for database alert monitoring in the RZ20 transaction, so as to incorporate your new check conditions:

    1. Find out on which application servers the Oracle context exists by calling transaction RZ21 and then entering Topology ® Context Overview ® Segment Name, then Topology ® Segment Overview ® Destination.
    2. Log on to the application server where the Oracle context exists.
    3. Start the Oracle database monitor by choosing Administration ® CCMS ® Control/Monitoring ® Alert-Monitor ® SAP CCMS Monitor Templates ® Database, or call transaction RZ20.
    4. Choose Extras ® Activate Maintenance Function.
    5. Select Oracle and reset all alerts by choosing Edit ® Nodes (MTE) ® Reset.
    6. Select Oracle and delete the Oracle tree by choosing Edit ® Nodes (MTE) ® Delete.
    7. Recreate the Oracle context on this application server by calling transaction SE38 in and entering RSDBMON0 in Program then choosing Execute.

NON-STANDARD MTEs from the Health monitoring tree are not set up in the standard database monitor because identical or similar MTEs are already present at another point in the monitoring tree. However, if you want to set up the NON-STANDARD but not the OPTIONAL MTEs, use SQLPLUS to add the following row to the SORAMON table:

connect sapr3/<password> or connect sap<sid>/<password>

insert into soramon (category, timestamp, value)

values ('SYSCHECK ALL_COND', '20020101000000', 1)

Then reinitialize the Oracle context as described above.

The result is that all NON-STANDARD alerts are reported only in the Health part of the database monitoring tree.

You can also have the alerts reported at both points of the monitoring tree by using SQLPLUS to add the following row to the SORAMON table:

connect sapr3/<password> or connect sap<sid>/<password>

insert into soramon (category, timestamp, value)

values ('SYSCHECK ALL_COND', '20020101000000', 2)