Deleting an Active aka Runaway Job
Opinions on this topic vary so these are good guidelines to use. These are
pretty much in the order they should be tried:
1. Kill the session via SM37 or SM04.
2. Try End session through SM50 or cancel program from SM66.
3. If the Work Process in SM50 is in stopped state then killing it will not help much or quickly, you need to identify why it is stopped (running a program on another server, runing in parallel etc.) Try and end those.
4. Kill Work Process in SM50 without core.
5. Kill process or PID via program RSBDCOS0.
6. If all else fails, restart the SAP instance server.
The most important things to remember when killing a WP are:
1. Change to restart = no as otherwise the session can jump back in sometimes as most of its memory is not actually living in the WP.
2. Allow it a long time to stop, there is no need to do it twice or 50 times as I have seen some people do, the poor old thing is just trying to recover rollback and reinitialize itself.
2. Try End session through SM50 or cancel program from SM66.
3. If the Work Process in SM50 is in stopped state then killing it will not help much or quickly, you need to identify why it is stopped (running a program on another server, runing in parallel etc.) Try and end those.
4. Kill Work Process in SM50 without core.
5. Kill process or PID via program RSBDCOS0.
6. If all else fails, restart the SAP instance server.
The most important things to remember when killing a WP are:
1. Change to restart = no as otherwise the session can jump back in sometimes as most of its memory is not actually living in the WP.
2. Allow it a long time to stop, there is no need to do it twice or 50 times as I have seen some people do, the poor old thing is just trying to recover rollback and reinitialize itself.
No comments:
Post a Comment