This is a permanent blocking situation and would not be resolve by waiting. SQL server is capable to detect deadlocks and can declare one of the process as deadlock victim and kills that process. The following steps outline this process:. After you have identified the blocking spid , which is typically a Tivoli Business Systems Manager process, save all of the above detail for IBM Software Support and restart the process or service.
One method for determining the context of an spid is to look at its input buffer. The following example shows partial output from listing the spid input buffer and the spid :.
If the blocking spid is a Tivoli Business Systems Manager service, and you know the service name, use the Services management tool or the sc Windows R command to stop and start it. This can cause very unpredictable results. One of them must be killed to allow either of them to finish. Like Liked by 1 person. Like Like. You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account.
Notify me of new comments via email. Place the code for session 1 in one query window and the code for session 2 in the other query window. Then execute each of the two sessions step by step, going back and forth between the two query windows as required.
This is an example of blocking. Don't cancel the query from step five. Let it continue running.
0コメント