Re: TX mode 4 locks

I like the thorough description of the
things you've checked to pin down the
problem and eliminate possibilities.

One option that you haven't covered
is that sessions 105 and 203 may be
trying to insert rows with primary keys
that session 8 has inserted but not
committed.

In this circumstance, 105 and 203
have to wait for 8 to commit or rollback so that they can decide whether to
stop and raise "duplicate key" or carry on.

--
Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

  The educated person is not the person
  who can answer the questions, but the
  person who can question the answers -- T. Schick Jr


One-day tutorials:
http://www.jlcomp.demon.co.uk/tutorial.html

____Denmark__May 21-23rd
____Sweden___June
____Australia__June 28th (Canberra - CBO)
____Finland__September
____Norway___September


Three-day seminar:
see http://www.jlcomp.demon.co.uk/seminar.html
____UK_(Manchester)_May x 2
____Estonia___June 4th - 6th
____Australia_June 18th - 20th (Perth)
____Australia_June 23rd - 25th (Melbourne)
____USA_(CA, TX)_August
____UK___September

The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html


"srivenu" <srivenu_at_hotmail.com> wrote in message
news:1a68177.0305170038.3f19591e_at_posting.google.com...


> I'am facing some inexplicable TX mode locks in my instance.

> Can someone please explain me the reason.

>




>

> 1) I have only 3 sessions currently inserting into the NOTES table

> whereas the table and all its indexes have initrans set to 10.

> 2) All the foreign keys on NOTES table are indexed.

> 3) None of the indexes are BITMAP indexes.

> 4) There are no pending 2PC transactions.

>

> Can someone please tell me why the 2 sessions are waiting for a TX

> mode 4 lock on the NOTES table ?

> Are there any other cases where the TX mode 4 lock is acquired ?

>