>Either there is a bug in your operating system (you didn't tell
>us what operating system you are using, by the way) or else there
>is still a process holding a transaction open that you are unaware
>of.


It turns out to be the latter.

It would be useful in such circumstances to identify the
process holding the lock in some way.

If you're on unix/linux the command  'lsof' will do that.
google will give you the specs and a link to the source if you want to
give it a go

-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to