Scribd
Upload
51 views2 pages

Quick Review: No Task Transaction Procedure / Remark 1

This document provides a daily monitoring checklist for critical tasks, the SAP system, and the database. For the SAP system, the checklist includes checking that application servers and work processes are running, reviewing logs for errors or warnings, and ensuring jobs and processes have not been canceled or are experiencing issues. For the database, the checklist includes reviewing error logs, monitoring tablespace usage, and checking database statistics. The goal is to identify any problems, bottlenecks, or security risks on a daily basis.

Uploaded by

Ranjeet Salunkhe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
51 views2 pages

Quick Review: No Task Transaction Procedure / Remark 1

This document provides a daily monitoring checklist for critical tasks, the SAP system, and the database. For the SAP system, the checklist includes checking that application servers and work processes are running, reviewing logs for errors or warnings, and ensuring jobs and processes have not been canceled or are experiencing issues. For the database, the checklist includes reviewing error logs, monitoring tablespace usage, and checking database statistics. The goal is to identify any problems, bottlenecks, or security risks on a daily basis.

Uploaded by

Ranjeet Salunkhe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Quick Review

Daily Monitoring Tasks

1. Critical tasks
2. SAP System
3. Database

Critical tasks

No Task Transaction Procedure / Remark


1 Check that the R/3System is up. Log onto the R/3
System
2 Check that daily backup executed without DB12 Check database
errors backup.

SAP System

No Task Transaction Procedure / Remark


1 Check that all SM51 Check that all servers are up.
application servers are
up.
2 Check work processes SM50 All work processes with a “running” or a
(started from SM51). “waiting” status
3 Global Work Process SM66 Check no work process is running more than
overview 1800 second
3 Look for any failed SM13  Set date to one day ago
updates (update  Enter * in the user ID
terminates).  Set to “all” updates Check for lines with
“Err.”

4 Check system log. SM21 Set date and time to before the last log
review. Check for:

 Errors
 Warnings
 Security messages
 Database problems

5 Review for canceled SM37 Enter an asterisk (*) in User ID.Verify that all
jobs. critical jobs were successful.
6 Check for “old” locks. SM12 Enter an asterisk (*) for the user ID.
7 Check for users on the SM04AL08 Review for an unknown or different user ID
system. and terminal.This task should be done several
times a day.
8 Check for spool SP01 Enter an asterisk (*) for Created ByLook for
problems. spool jobs that have been “In process” for
over an hour.
9 Check job log SM37 Check for:

 New jobs
 Incorrect jobs

10 Review and resolve ST22 Look for an excessive number of dumps.


dumps. Look for dumps of an unusual nature.
11 Review buffer ST02 Look for swaps.
statistics.

Database

No Task Transaction Procedure / Remark


1 Review error log for ST04
problems.
2 Database DB02 If tablespace is used more than 90 % add
GrowthMissing new data file to itRebuild the Missing
Indexes Indexes
3 Database Statistics DB13
log

You might also like