Monitoring the R/3 Log Disk 

Use

The size of the transaction log must be checked regularly to work out how much free space is available on the log disk. There should always be enough free space to allow the next file extension. When the R/3 System has been installed the autogrow increment is set. At least the size of this increment should be available on the log disk to permit the next file extension. If less space is available and the transaction log file fills up, the R/3 System will come to a standstill.

Ideally, the transaction log should never be filled to more than 60-70%. If the transaction log regularly exceeds this level between 2 transaction log backups, the transaction log must be saved at more frequent time intervals.

The size of the log can be assessed on the basis of information given for completed backups in the R/3 Backup Monitor.

Procedure

  1. To access the Backup Monitor choose Administration ® CCMS ® DB Administration ® Backup logs.
    Alternatively, enter the transaction code DB12.

    2. The initial screen of the Backup Monitor appears.

  2. Choose Backup history and then Logs Backup.
  3. A result list appears. Find the largest transaction log backup of the past week. Select a column and then History info to find out the number of pages that were processed during the backup. To work out the amount of space used in the transaction log, multiply the number of dumped pages by 8 KB. You can then work out how much free space is left on the transaction log disk.

If you use a RAID1 disk system exclusively for the R/3 transaction log and create hourly log backups, you will rarely encounter space problems. The R/3 log file is initially created with a size of 1.5 GB. The smallest RAID disk normally has 4 GB space and the log file can therefore grow to 4 GB.