1. How do you troubleshoot a critical Dialog Work Process bottleneck in SM50?
Panelist Expectation: Rather than reciting theory, demonstrate a live troubleshooting sequence:
1. Check SM50/SM66 to identify work process states (Running, On Hold, Waiting).
2. Note the action column: Sequential Read, Direct Read, or Database Lock.
3. Inspect SM12 for persistent lock entries and DB01 for exclusive DB lock waits.
4. Check ST04 for expensive SQL queries causing prolonged CPU consumption, and review dev_w* trace logs if core dumps are produced.
1. Check SM50/SM66 to identify work process states (Running, On Hold, Waiting).
2. Note the action column: Sequential Read, Direct Read, or Database Lock.
3. Inspect SM12 for persistent lock entries and DB01 for exclusive DB lock waits.
4. Check ST04 for expensive SQL queries causing prolonged CPU consumption, and review dev_w* trace logs if core dumps are produced.