Ann,

Thanks for the response.
I have attempted to get the info using ./gds_lock_print -o
but it always returns the follow error.

Unable to access lock table.
/usr/lib/firebird/run/isc_lock1.BIGHORN

any thoughts?

Thanks again
Kevin


--- In firebird-support@yahoogroups.com, "Ann W. Harrison"
<aharrison@...> wrote:

>
> kshenes wrote:
> >
> > Is there anyway to determine which clients are consuming the

locks?

>
> Yes for classic, no for superserver
>
> > Is there anyway to determine which transactions are causing the

locks?

> >
>
> Yes. The answer in both cases is to get a lock print. I think that
> just -o will give you enough information since it includes the owner
> blocks and the number of lock requests each owner has.
>
> The primary use of lock table space is "latches" - transient locks

on

> pages in the cache. The larger the cache, the more pages can be

locked.

> The more active transactions, the more owners, thus the more locks

on

> pages.
>
> Regards,
>
>
> Ann
>