Re: thow to resolve table locks

Locks are released by issuing a commit or rollback by the session. Deadlocks are resolved automatically by Oracle. Obviously there is no command to release locks for a different session than your own, as that will affect the complete transaction. The only other way to 'resolve locks' is to kill the session (and of course review your application, as you might be escalating locks)

From the garbled output below it looks like you are using explicit table level locks as opposed to row level locks. You shouldn't do that.

Regards,

Sybrand Bakker, Oracle DBA

<susana73_at_hotmail.com> wrote in message news:901p45$tbb$1_at_nnrp1.deja.com...
> My application basically connects to the database 24 hours a day. It
> hangs several times a week due to table locks. The application is a
> mixture of many small queries/updates to individual rows. I have been
> reading the documentation but I can't find anything that can release the
> default locks. Anyone know how?
>
> Thanks.
>
> USERNAME SID TYPE OWNER OBJECT HELD REQUEST
> --------------- ----- ---- ---------- ------------ ----------- -----------
> DBUSER 11 TX DBUSER EMP Exclusive None
> DBUSER 11 TX DB_OWNER EMP Exclusive None
> DBUSER 9 TX DBUSER EMP None Share
> DBUSER 9 TX DB_OWNER EMP None Share
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Wed Nov 29 2000 - 00:41:18 CST