Subject | Re: [ib-support] Interpreting the iblockpr output.. |
---|---|
Author | Ann W. Harrison |
Post date | 2002-10-27T22:27:16Z |
At 11:54 PM 10/26/2002 +0200, Ignacio J. Ortega wrote:
I can't put my hand on it, but it should reappear soon.
a process has waited for more than 10 seconds (I think), finds and
reports deadlocks. However, the lock table printout will tell you
if some process has a resource locked and other processes are
waiting for it.
Basically LOCK blocks describe a resource than can be locked -
tables, buffers, indexes ... there are about a dozen. PROC
blocks describe processes (connections) that request locks on
resources. REQ blocks describe a request, possibly granted,
for a lock on a resource.
I'll try to dig up the paper, but in the mean time, the lock
manager header file (subsystem LOCK) should help.
Regards,
Ann
www.ibphoenix.com
We have answers.
>Where i can fin some docs about the interpretation of iblockpr output?I wrote a paper on that a long long time ago. At the moment,
I can't put my hand on it, but it should reappear soon.
>i'm trying to understand a deadlock condition.. is this possible withIt shouldn't be. The lock manager code searches the table anytime
>iblockpr?..
a process has waited for more than 10 seconds (I think), finds and
reports deadlocks. However, the lock table printout will tell you
if some process has a resource locked and other processes are
waiting for it.
Basically LOCK blocks describe a resource than can be locked -
tables, buffers, indexes ... there are about a dozen. PROC
blocks describe processes (connections) that request locks on
resources. REQ blocks describe a request, possibly granted,
for a lock on a resource.
I'll try to dig up the paper, but in the mean time, the lock
manager header file (subsystem LOCK) should help.
Regards,
Ann
www.ibphoenix.com
We have answers.