Monitoring the Database Fill Level and Content Server

Use

Operation Monitoring the Fill Level of Database Instances

You need to monitor the data area and the log area in order to prevent a possible database crash.

Once the data or the log area is 100% full, the database instance can no longer accept any more transactions. Although this is a valid operating status, the content server cannot process any more requests and it therefore appears "frozen".

Therefore, to enable the database instance to continue to accept transactions, either the data area has to be increased, or the log area has to be backed up.

In particular, regularly backing up the log area is an absolute requirement for smooth database operation. We recommend that you activate automatic log backup.

Procedure

Use the following functions in the database manager GUI:

  • Displaying data area information

  • Displaying log area information

  • Activating and deactivating automatic log backup

  • Creating, displaying, and deleting volumes

Monitoring the File System Fill Level

The fill level of the file system where the repositories are has to be monitored from the operating system.

Automatic Repository Fill Level Indicator in the UNIX Content Server

If the fill level of the storage medium (database or file system) reaches 70%, the fill level percentage is displayed instead of the operation status running in transaction CSADMIN.

Monitoring the Operation of the Content Server: CCMS

Purpose

You can use the Computing Center Management System (CCMS) to monitor, control, and configure your SAP System. The CCMS tools allow you to analyze and distribute the load on the clients in your system, and can display the resource usage of the system components. The transactions in question are SCMSMO and CSMONITOR (both open the same view).

Features

The CCMS provides a range of monitors and administration functions for