![]() ![]() Solving a semaphore lock and wait situation There are situation where the semaphore locker cannot be identified, for these cases you can use the semd tool as explained in the note 2027885. Using the snapshot feature created by dispatcher ( see further):.Using the SAPCONTROL client connecting to sapstartsrv service:.Using the standalone tool DPMON ( see further):.SM50 transaction (not always possible to use during the standstill situation).The first step is to identify the locker. There are few ways to identify the semaphore locker: However, if the locker hold the semaphore and release after a while, changing the work process locker, we have the second situation. ![]() If the locker does not release the semaphore the system stuck and we have the first situation (usually caused by a deadlock). The work process locker (semaphore locker) is the responsible to stuck the system, it may lock the semaphore forever or during a specific time span.
0 Comments
Leave a Reply. |