Monitoring
Use
We recommend that you monitor your database instance during production operation. This way, you can recognize problems early and avoid disruptions or failures.
Activities
To monitor your
database instance, use operating system functions, the Database Manager, the
Event Dispatcher, the Database Analyzer and in SAP systems the CCMS (in
particular the
Database Alert
Monitor or
liveCache Alert
Monitor).
You can use events
to ensure that you are notified of critical database states. See Utilities,
Event
Dispatcher
Monitoring Free Memory in the Data Area
If the memory in the data area is full, the database system stops all current transactions and the database is unavailable for users. To avoid this, regularly check whether there is sufficient free memory in the data area. See
●
Database Manager GUI,
Displaying Data Area
Information
●
Database Manager CLI,
info
●
Database Administration in CCMS:
MaxDB,
Monitoring the Data
Area
●
Database Administration in CCMS: SAP liveCache
Technology,
Monitoring the Data
Area
Monitoring Free Memory in the Log Area
If the memory in the log area is full, the database system cannot write any further redo log entries and therefore stops all transactions. The database is unavailable for users. To avoid this, regularly check whether there is sufficient free memory in the log area. See
●
Database Manager GUI,
Displaying Log Area
Information
●
Database Manager CLI,
info
●
Database Administration in CCMS:
MaxDB,
Monitoring the Log
Area
●
Database Administration in CCMS: SAP liveCache
Technology,
Monitoring the Log
Area
Monitoring the Hit Rate for Access to the Caches
The lower the hit rate for database system access to the caches, the less efficiently the database system works. See
●
Database Manager GUI,
Displaying Cache
Information
●
Database Manager CLI,
info
●
Database Administration in CCMS:
MaxDB,
Caches
●
Database Administration in CCMS: SAP liveCache
Technology,
Caches
Monitoring CPU Usage by the Database Instance
If the database instance has to share the computer’s processor(s) with too many other programs, performance can be poor. To avoid this, use operating system resources to monitor CPU usage by the processes of the database instance. See
Monitoring Backups
Backups can fail for various reasons, for example if you have entered as the backup template a file in a directory that no longer exists at the time of the backup. The backup history displays which backups have been performed and if they were successful. For this reason, check the backup history regularly, in particular if you use automatic log backup or have automated the backup process using scripts. See
●
Database Manager GUI,
Displaying the Backup
History
●
Database Manager CLI,
backup_history_list
●
Database Management in CCMS,
DBA
History
Regularly check whether your backups are intact. See
●
Database Manager GUI,
Checking
Backups
●
Database Manager CLI,
recover_check
Monitoring Database Structures
Hardware defects can cause errors in the database structures. For this reason, check the database structures regularly. See Checking Database Structures
Monitoring Database Activities
Monitor the following database activities:
● I/O activity
● Lock activity
● Logging activity
See
●
Database Manager GUI,
Displaying Database
Activities
●
Database Manager CLI,
info
●
Database
Management in CCMS,
Activities
Overview
Monitoring the Number of Database Sessions
If the maximum number of possible database sessions has been reached, no further users can log on to the database instance. For this reason, monitor the number of database sessions.
See
●
Database Manager GUI,
Displaying Database
Sessions
●
Database Manager CLI,
info
●
Database Administration in CCMS:
MaxDB,
User
Tasks
●
Database Administration in CCMS: SAP liveCache
Technology,
User
Tasks
Monitoring Security-Relevant Activities
See
●
MaxDB Security Guide,
Checking Log Files for
Failed Logon Attempts
See also:
Event Dispatcher
documentation
Database Analyzer
documentation