<quote>
LMODE   NUMBER  Lock mode in which the session holds the lock:
      0 - none
      1 - null (NULL)
      2 - row-S (SS)
      3 - row-X (SX)
      4 - share (S)
      5 - S/Row-X (SSX)
      6 - exclusive (X)
</quote>

and on Concept manual, on chapter 13
<quote>
*Row Exclusive Table Locks (RX)*

A row exclusive table lock !(also called a subexclusive table lock,
SX)!
 generally indicates that the transaction holding the lock has made
one or more
 updates to rows in the table. A row exclusive table lock is acquired
automatically
 for a table modified by the following types of statements:

INSERT INTO table ... ;

UPDATE table ... ;

DELETE FROM table ... ;

LOCK TABLE table IN ROW EXCLUSIVE MODE;

A row exclusive table lock is slightly more restrictive than a row
share table lock.

Permitted Operations: A row exclusive table lock held by a transaction
allows other transactions to
  query, insert, update, delete, or lock rows concurrently in the same
table. Therefore, row exclusive
  table locks allow multiple transactions to obtain simultaneous row
exclusive and row share table locks
  for the same table.

Prohibited Operations: A row exclusive table lock held by a
transaction prevents other transactions
 from manually locking the table for exclusive reading or writing.
Therefore, other transactions
 cannot concurrently lock the table using the following
statements:

</quote>

So, in my case it seems as more than one session has subexclusive
table lock, SX (lmode 3) on
the same record and one locking the others (a particular case of
deadlock).

Any ideas?

thanks

Bye
 Cristian Cudizio

http://oracledb.wordpress.com
http://cristiancudizio.wordpress.com

-----------------------------------------------Reply-----------------------------------------------