Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Health Check steps

 Check in sm66 and sm50:
–If long running processes are available (see column Time)
–If processes in PRIV mode are available.
–If long running processes in stopped debug mode are available
–If you see the report sapmssy1 hanging around with no action than something is wrong with the rfccpic interface. This is not a normal behavior. This processes should be analysed.
–Are there enough Work Process’s of all types available
–If there a work process running for too long…check with user
–20% of process’s are performing same action
–20% Priv : Check which users using large amounts of memory. Use dpmon if all process go into priv mode.
–20 % reading from same table :Look for Lock issue or  expensive sql statements
–40% seq read,db commit: Possible DB issue

Check the overall performance with

– Which kind of workload exists mainly?  RFC, Dialog, Background…
–SMLG (F5)
Check the System logs : SM21
Check the SAP locks : SM12
Check the update process
–SM13  - Ensure update process is active
Check for dumps in sap system : ST22

Check the transport environment

–Check for Support Packs Installation Running.
–Check if large number of Transports being imported.
–For tp issue. Run tp check in STMS.
–Check for client copies : SCC3
Check ST02 for swaps
–See Memory allocation of the sap system section for more details.
Check ST06 for CPU usage
–See CPU allocation and consumption for more detail.
Check DB Alerts
–DB16 : Not available for all DB versions
Check DB Jobs

Batch environment:

--Check Status of Jobs:
         T/C sm37 with a ‘*’ in User name und Job name. Mark active box. Set start time in the past.
         Execute the job check (Job =>Check status)
        If jobs remain in active status and have a long run time. Check if job should be running. Do not cancel customers jobs without authorization.
--Standard Jobs.
        Ensure duplicate standard jobs are not running.
        Refer to Note 16083 for more info on standard jobs and also for any issues with Standard jobs.

FileSystem Checks: All Levels

--Run df –h of df –g to check space on file system
--To check which folders contain large files you can run du –sk * | sort –rn (This may take a long time depending how deep the hierarchy of folders is)
--Check for core dumps in the file system
--To find core dumps in the file system use following steps:
      ‘cd /usr/sap/<SID>’  and execute  ‘find . -name 'core' -exec ls {} \;’
--Check the Work directory and remove the following files for e.g.  *.old, core dumps etc
--Check for old versions of Kernel in the system
--Usefull Reports to delete files from abap side(please take a approval before running)
            WF Jobs - RSWTTR02
            Global Directory - RSBTCDEL  RSPO0041