Tirumala

Health Check
Task KPI Actions
Server Status 1. Check and ensure that the status of all application server Remediate.
instances are active.
2. Perform a connection test of each one by double clicking on Remediate.
each entry
If connection test to one server has failed or is slow, perform OS-level
check on that particular application server.

SAP Buffers Execute ST02 on each server: Report with analysis and corrective
action to be performed by BASIS
1. Check SAP buffers if swapping is too high or hit ratio is too low Team.
especially for the following:
a. Buffer quality (Hit Ratio) > 98%.

Global Work 1. Observe general performance by refreshing the display

Process Overview
2. Sort on Time and take note of long running processes (this is
similar to KPI defined in SM50)
DIA more than 4 hrs (14,400s)
BTC more than 48 hrs (172,800s)

3. Observe non waiting or running status

Normally the workprocesses are in “running” or “waiting” status. Ensure
that there are no workprocesses in "Stopped" or in PRIV status, and if
there are, perform further analysis

Average Response Check if average dialog response time > 2000 ms

Time
User List 1. Look at the distribution across the servers. Report with analysis and corrective
action to be performed by BASIS
Team.
System Log Check and investigate system log for errors Report with analysis and corrective
a. Choose System log->Choose->All remote system logs action to be performed by BASIS
b. Display problems only Team.
c. Observe error messages.

ABAP Dumps Check and investigate ABAP Dumps Report with analysis and corrective
a. Select today and focus on last 2 hours action to be performed by BASIS
b. Observe the type and number of dumps: Team. Verify from Issue List.
- look for excessive number of dumps
- look for out of the ordinary or unusual dumps

Update 1. Ensure that "Update is active" status is shown from SM13 Remediate.

2. Investigate if there are more than 10 Update Records in “INIT”

status for more than 4 hours.
3. Investigate if there are more than 10 update records in status
“ERROR”.
ABAP Lock Entries 1. Ensure that there are no lock entries older than 6 hours. If yes, Remediate if possible and report
please investigate. exceptions to IM Team

2. Observe if current lock entries exceed [enqueue/table_size]: Remediate if possible and report
600 for Normal ABAP System exceptions to IM Team

Note: high lock count is not usually a sign of a problem without

additional analysis supporting a problem.
Database Locks Check and observe database locks in HELD and WAIT status (this Perform analysis and, if required,
can be related to previous SM66 check). report locks in long WAIT situations to
IM team

SAP Jobs 1. Report long running and delayed jobs Remediate for delayed jobs.
1.a. Set date selection from last week until today and user to all. List Report long running jobs to IM.
all jobs in Active and Ready status
1.b. Observe long running jobs active for more than 12 hours.
Perform a job "check status" from yesterday

2. Report delayed jobs Remediate.

2.a. Set date selection from last week until today and user to all. List
all jobs in Released status and sort via Delay
2.b. Observe jobs with long delay times.

3. Ensure that all housekeeping jobs are successful and are Remediate.
running as expected (no delayed or long running jobs).

Tablespaces Free From DB02 / brtools: Remediate.

Space
- Ensure tablespace usage does not exceed 95% and is not less than
100GB free
- Ensure that filesystems have sufficient space for growth

Database Alert Log From DB02, go to Performance->Additional Functions->Alert Log. Remediate.

Check Check errors from last check.

Database Archive Ensure that previous archive log backup runs are successful Remediate.
Log Backup

Filesystem Check Check if usage for following systems exceed 85%: Remediate and if required raise to IM.
- /usr/sap/*, /sapmnt & other SAP filesystems
Transaction / OS-level Command status
SM51
OK

OK
ST02

OK
SM66
OK

OK

OK
St03N
OK
AL08/SM04

OK
SM21

OK
ST22

OK
SM13
OK
OK
OK
SM12

OK
 DB01

OK
SM37

OK

OK

OK
DB02
thejaswi:
PSAPTEMP16=100
SYSTOOLTEMPSPACE-100

DB02

NA
DB12

OK
ST06/ST06N/OS07N

OK
 Tirumala
Health Check
Task KPI
Server Status 1. Check and ensure that the status of all application server
instances are active.
2. Perform a connection test of each one by double clicking on
each entry
If connection test to one server has failed or is slow, perform OS-level
check on that particular application server.

SAP Buffers Execute ST02 on each server:

1. Check SAP buffers if swapping is too high or hit ratio is too low
especially for the following:
a. Buffer quality (Hit Ratio) > 98%.

Global Work 1. Observe general performance by refreshing the display

Process Overview
2. Sort on Time and take note of long running processes (this is
similar to KPI defined in SM50)
DIA more than 4 hrs (14,400s)
BTC more than 48 hrs (172,800s)

3. Observe non waiting or running status

Normally the workprocesses are in “running” or “waiting” status. Ensure
that there are no workprocesses in "Stopped" or in PRIV status, and if
there are, perform further analysis

Average Response Check if average dialog response time > 2000 ms

Time
User List 1. Look at the distribution across the servers.

System Log Check and investigate system log for errors

a. Choose System log->Choose->All remote system logs
b. Display problems only
c. Observe error messages.

ABAP Dumps Check and investigate ABAP Dumps

a. Select today and focus on last 2 hours
b. Observe the type and number of dumps:
- look for excessive number of dumps
- look for out of the ordinary or unusual dumps

Update 1. Ensure that "Update is active" status is shown from SM13

2. Investigate if there are more than 10 Update Records in “INIT”

status for more than 4 hours.
3. Investigate if there are more than 10 update records in status
“ERROR”.
ABAP Lock Entries 1. Ensure that there are no lock entries older than 6 hours. If yes,
please investigate.

2. Observe if current lock entries exceed [enqueue/table_size]:

600 for Normal ABAP System

Note: high lock count is not usually a sign of a problem without

additional analysis supporting a problem.
Database Locks Check and observe database locks in HELD and WAIT status (this
can be related to previous SM66 check).

SAP Jobs 1. Report long running and delayed jobs

1.a. Set date selection from last week until today and user to all. List
all jobs in Active and Ready status
1.b. Observe long running jobs active for more than 12 hours.
Perform a job "check status" from yesterday

2. Report delayed jobs

2.a. Set date selection from last week until today and user to all. List
all jobs in Released status and sort via Delay
2.b. Observe jobs with long delay times.

3. Ensure that all housekeeping jobs are successful and are

running as expected (no delayed or long running jobs).

Tablespaces Free From DB02 / brtools:

Space
- Ensure tablespace usage does not exceed 95% and is not less than
100GB free
- Ensure that filesystems have sufficient space for growth

Database Alert Log From DB02, go to Performance->Additional Functions->Alert Log.

Check Check errors from last check.

Database Archive Ensure that previous archive log backup runs are successful
Log Backup

Filesystem Check Check if usage for following systems exceed 85%:

- /usr/sap/*, /sapmnt & other SAP filesystems
 Tirumala
Health Check
Actions Transaction / OS-level Command status
Remediate. SM51
OK
Remediate.

OK
Report with analysis and corrective ST02
action to be performed by BASIS
Team.

OK
SM66
OK

OK

OK
St03N
OK
Report with analysis and corrective AL08/SM04
action to be performed by BASIS
Team.
OK
Report with analysis and corrective SM21
action to be performed by BASIS
Team.

OK
Report with analysis and corrective ST22
action to be performed by BASIS
Team. Verify from Issue List.

OK
Remediate. SM13
OK

OK

OK
Remediate if possible and report SM12
exceptions to IM Team

OK
Remediate if possible and report
exceptions to IM Team

OK
Perform analysis and, if required, DB01
report locks in long WAIT situations to
IM team
OK
Remediate for delayed jobs. SM37
Report long running jobs to IM.

OK
Remediate.

OK
Remediate.

OK
Remediate. DB02

Remediate. DB02

NA
Remediate. DB12

OK
Remediate and if required raise to IM. ST06/ST06N/OS07N

OK
 Tirumala
Health Check
Task KPI Actions
Server Status 1. Check and ensure that the status of all application server Remediate.
instances are active.
2. Perform a connection test of each one by double clicking on Remediate.
each entry
If connection test to one server has failed or is slow, perform OS-level
check on that particular application server.

SAP Buffers Execute ST02 on each server: Report with analysis and corrective
action to be performed by BASIS
1. Check SAP buffers if swapping is too high or hit ratio is too low Team.
especially for the following:
a. Buffer quality (Hit Ratio) > 98%.

Global Work 1. Observe general performance by refreshing the display

Process Overview
2. Sort on Time and take note of long running processes (this is
similar to KPI defined in SM50)
DIA more than 4 hrs (14,400s)
BTC more than 48 hrs (172,800s)

3. Observe non waiting or running status

Normally the workprocesses are in “running” or “waiting” status. Ensure
that there are no workprocesses in "Stopped" or in PRIV status, and if
there are, perform further analysis

Average Response Check if average dialog response time > 2000 ms

Time
User List 1. Look at the distribution across the servers. Report with analysis and corrective
action to be performed by BASIS
Team.
System Log Check and investigate system log for errors Report with analysis and corrective
a. Choose System log->Choose->All remote system logs action to be performed by BASIS
b. Display problems only Team.
c. Observe error messages.

ABAP Dumps Check and investigate ABAP Dumps Report with analysis and corrective
a. Select today and focus on last 2 hours action to be performed by BASIS
b. Observe the type and number of dumps: Team. Verify from Issue List.
- look for excessive number of dumps
- look for out of the ordinary or unusual dumps

Update 1. Ensure that "Update is active" status is shown from SM13 Remediate.

2. Investigate if there are more than 10 Update Records in “INIT”

status for more than 4 hours.
3. Investigate if there are more than 10 update records in status
“ERROR”.
ABAP Lock Entries 1. Ensure that there are no lock entries older than 6 hours. If yes, Remediate if possible and report
please investigate. exceptions to IM Team

2. Observe if current lock entries exceed [enqueue/table_size]: Remediate if possible and report
600 for Normal ABAP System exceptions to IM Team

Note: high lock count is not usually a sign of a problem without

additional analysis supporting a problem.
Database Locks Check and observe database locks in HELD and WAIT status (this Perform analysis and, if required,
can be related to previous SM66 check). report locks in long WAIT situations to
IM team

SAP Jobs 1. Report long running and delayed jobs Remediate for delayed jobs.
1.a. Set date selection from last week until today and user to all. List Report long running jobs to IM.
all jobs in Active and Ready status
1.b. Observe long running jobs active for more than 12 hours.
Perform a job "check status" from yesterday

2. Report delayed jobs Remediate.

2.a. Set date selection from last week until today and user to all. List
all jobs in Released status and sort via Delay
2.b. Observe jobs with long delay times.

3. Ensure that all housekeeping jobs are successful and are Remediate.
running as expected (no delayed or long running jobs).

Tablespaces Free From DB02 / brtools: Remediate.

Space
- Ensure tablespace usage does not exceed 95% and is not less than
100GB free
- Ensure that filesystems have sufficient space for growth

Database Alert Log From DB02, go to Performance->Additional Functions->Alert Log. Remediate.

Check Check errors from last check.

Database Archive Ensure that previous archive log backup runs are successful Remediate.
Log Backup

Filesystem Check Check if usage for following systems exceed 85%: Remediate and if required raise to IM.
- /usr/sap/*, /sapmnt & other SAP filesystems
Transaction / OS-level Command status
SM51

ST02

SM66

St03N

AL08/SM04

SM21

ST22

SM13

SM12
 DB01

SM37

DB02

DB02

NA
DB12

ST06/ST06N/OS07N