> From: Ann W. Harrison [mailto:aharrison@...]
> Sent: Sunday, October 27, 2002 11:27 PM
>

Ann,

>
> It shouldn't be. The lock manager code searches the table anytime
> 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.
>

To be clear, i have a problem restoring a gbk in fb 1.5. gbak dies with
a deadlock message, and i'm trying to understand this exact problem, and
in the way i've find and compiled iblockpr, How can i investigate this
kind of deadlock?

I was trying to see if the history should save the dangling lock that
caused the deadlock, i will catch where the real problem is.. dont you?

I've imagined that at least learning what the LOCK module does.. maybe
should help in the resolution of my restore problem ;)

Saludos,
Ignacio J. Ortega