Monitoring Databases 
To recognize problems in time and avoid disruptions, we recommend that you monitor your database when it is being used in a production system.
Procedure
Use one of the following database tools:
Database Studio, Database Manager CLI, or CCMS (in SAP systems only)
Automatic Problem Notification
To receive automatic notifications of critical database states, you can use database events.
More information: Glossary, Event
Monitoring Free Memory in the Data Area
If the data area is full, the database system stops all running transactions and the database is unavailable for users. To avoid this, regularly check whether there is sufficient free space in the data area.
More information:
Database Studio, Displaying the Data Area
Database Manager CLI, info
Database Administration in CCMS, Monitoring the Data Area
Monitoring Free Memory in the Log Area
If the log area is full, the database system cannot write any further redo log entries and therefore stops all transactions, and is unavailable for users. To avoid this, regularly check whether there is sufficient free space in the log area.
More information:
Database Studio, Displaying the Log Area
Database Manager CLI, info
Database Administration in CCMS, Monitoring the Log Area
Monitoring the Hit Rate for Access to the Caches
The hit rate is calculated as the following ratio: the number of times that the database system has accessed a cache and found the information it was looking for there, divided by the proportion of the total number of times that the database system has accessed the cache. The performance of the database system is best if the database system can retrieve as much information as possible from the caches (high hit rate), since access to hard discs is considerably slower.
More information:
Database Studio, Displaying Caches (Working Memory Areas)
Database Manager CLI, Info
Database Administration in CCMS, Caches
Monitoring Backups
Backups can fail for various reasons. Example: When creating the backup template, you specified a file in a directory that no longer exists at the time of the backup. Regularly check whether your backups are intact.
The backup history displays which backups have been performed and whether they were successful. Check the backup history regularly, in particular if you use the automatic log backup function or have automated the backup process using scripts.
More information:
Database Studio,
Database Manager CLI,
Database Administration in CCMS, DBA History
Monitoring Database Activities
Monitor the following database activities:
I/O activity
Lock activity
Logging activity
More information:
Database Studio, Displaying Database Properties
Database Manager CLI, info
Database Administration in CCMS, Activities Overview
Monitoring the Number of Database Sessions
If the maximum number of database sessions has been reached, no further users can log on to the database. For this reason, monitor the number of database sessions.
More information:
Database Studio, Editor: Administration
Database Manager CLI, info
Database Administration in CCMS, User Tasks
Monitoring Security-Relevant Activities
More information:
SAP MaxDB Security Guide, Checking Log Files for Failed Logon Attempts