Start of Content Area

Background documentation Monitoring ABAP Error Messages  Locate the document in its SAP Library structure

Use the ABAP Critical Messages monitor to obtain information about the most important error messages of your ABAP system or of your monitored ABAP systems. You can see areas that you particularly need to monitor in your daily administration at a glance in the subtrees of this monitor.

Execution

Check the ABAP Critical Messages monitor for alerts. To open the monitor, proceed as described in Tasks. Depending on the affected nodes, you can react to the alert as follows:

Affected MTE

Meaning

ABAP Shortdumps

Errors during the execution of ABAP programs are displayed here in the status attribute <instance>\Shortdumps. The system has created a dump and reported this to the monitoring architecture. Transaction ST22 (ABAP Runtime Errors) is set as the analysis method (see also Program Checks).

Aborted Batch Jobs

Errors during the execution of jobs are displayed here in the <instance>\Aborted Jobs status attributes. A separate red alert is generated for each of these jobs. Transaction SM37 (Job Selection) is set as the analysis method with the selection condition Job Status Canceled (see also Job was canceled).

Update
    Update Errors

Incorrect update requests are displayed here in the <instance>ErrorInUpdate status attributes. Transaction SM13 (Update Requests) is set as the analysis method (see also Analyzing and Correcting Update Errors).

Update
    Update Service

This status attribute specifies whether the update process in the corresponding system is active.

Syslog Messages

Messages from the system log are displayed here, grouped by instances and topic areas. This allows you to identify and correct errors in the monitored systems and their environments. Transaction SM21 (System Log: Analysis) is set as the analysis method.

Note

By default, each system log message generates an alert of the appropriate color. Syslog Monitor describes how you can restrict alert generation only to the message IDs that you define. In this case, alerts are only generated for selected syslog messages.

Database
    Database Health

This monitoring object monitors different parameters and frequent errors for each database type. You can use this information to assess whether your database is working correctly. For more information, see the appropriate point below for your database:

·        MaxDB: Health

·        Oracle: Database Health Alerts

·        DB2 UDB for iSeries: Monitoring the Database with the Alert Monitor (iSeries)

·        Microsoft SQL Server Alerts for SQL Server

 

Database
    Database Backup

This monitoring object monitors the date and the status of the current database backup. For more information, see the appropriate point below for your database:

·        MaxDB: Last Backup

·        Oracle: Database Backup and Restore Alerts

·        Microsoft SQL Server Alerts for SQL Server

This graphic is explained in the accompanying text Monitoring start page

 

 

End of Content Area