Analysis of hanging situations

A hanging situation can be caused by problems in the database, in the operating system or in the R/3 System. Afterwards an analysis is almost impossible. Therefore it only makes sense to open a OSS message on this, if all information described below was gathered during the hanging situation.

A hanging situation exists if many R/3 work processes run "endlessly". If only one individual work process is affected, this is not an hanging situation but a report that is running very long. The examination of such a report is described in Note 155413.

Symptoms of hanging situations:
- Archiver stuck
- Update process is deactivated (SM13/SM50)

Information to be gathered for analysis:
1. Process Overview
- SM50/SM66/dpmon
If you can get in to SAP transaction, then you need to execute dpmon on unix level (sidadm)

Example
- dpmon pf=d:\usr\sap\PRD\sys\profile\PRD_DVEBMGS00_sapserver
- Enter m (for menu)
- Enter l

2. Check on CPU/Memory/Disk utilization
- ST06 -> "Detail analysis menu" -> "Top CPU Process"
- topas-AIX
- top-hp
- nmon
- Caplan monitoring

3. DB Process Overview
- ST04 -> "Detail analysis menu" -> "Exclusive lockwaits"
- Check oracle trace file /oracle/SID/saptrace/background/alertSID.log

4. SAP Developer Trace/SQL Error Log
Before restarting the SAP system, backup all Developer Traces.


Reference:
Note 155402 - Analysis of hanging situations