Show TOC

Function documentationNative DB Monitors Locate this document in the navigation structure

 

The Native DB Monitors function is a collection of database-dependent monitors for monitoring underlying databases directly. The function supports all RDMBSs that are allowed as primary databases for the AS Java.

Caution Caution

You need appropriate authorization to use the Native DB Monitors. Without the appropriate authorization, the monitors do not work correctly.

End of the caution.

Prerequisites

You are in   Problem Management   Database   Open SQL Monitors   Native DB Monitors.  

Features

The Native DB Monitors function consists of the following monitors:

  • Database Activity

    Shows a database-dependent view of the current database activity. The displayed columns are different depending on the RDBMS.

    Caution Caution

    Refreshing the list may take longer on databases with a high number of parallel sessions.

    End of the caution.

  • Current Exclusive Lock Wait Situations

    Shows processes currently holding or waiting for locks.

    Note Note

    The Current Exclusive Lock Wait Situations on Database table is generally the same for all supported databases. However, the column content can have different meanings depending on the RDBMS.

    End of the note.

    Note Note

    You cannot sort or filter the Current Exclusive Lock Wait Situations on Database table.

    End of the note.

Activities

To view database activity for a DataSource on a underlying database, select a DataSource in the Native SQL and Open SQL Datasources screen area and choose Show DB Activity. The Current Database Activity area opens.

To view lock situations, select a DataSource in the Native SQL and Open SQL Datasources screen area and choose Show Current Exclusive Lock Wait Situations. The Current Exclusive Lock Wait Situations on Database area opens. Normally, exclusive lock situations do not last long and thus it is normal (and desired) for the table to be empty.

Note Note

You can use the Database Activity, Current Exclusive Lock Wait Situations, and the Connection Monitor together to investigate reasons for lock wait situations. We recommend that you open the three monitors in parallel in separate browser windows to facilitate such analyses.

End of the note.