Re: Locked tables...

Sounds like an application problem to me... assume your "row" is a column? "Record already in use" could be because someone had queried for update and never committed... I'd take a look at the application, or at least check with users as to how they are using the form...

On Mon, 24 May 1999 16:04:08 +1000, cmilner <cmilner_at_connect.com.au> wrote:

>I have a recurring problem in that one table in the database has a row called
>RECORD_LOCK. Often, the users phone saying they can't access a record,
>'record already in use'. The procedure I go through is loggin off all users,
>updating all locks to 'N' in the table, and then allow them log back on.
>
>Is there a way to trace back from row level which Unix process is locking the
>table? Unfortunately, simple updating the table from 'Y' to 'N' is not sufficient,
>the process locking table is still there.
>
>Ta for any help
>
>chris
Received on Tue May 25 1999 - 14:54:29 CDT