Note in-line
--
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/seminar.html
Optimising Oracle Seminar - schedule updated Sept 19th
"Howard J. Rogers" <hjr_at_dizwell.com> wrote in message
news:41a62c19$0$17539$afc38c87_at_news.optusnet.com.au...
>
>> But what happen when there isn't enough space in the block ??? an
>> exception occur ??
>
> A buffer busy wait. You queue up for access to a freed transaction slot.
> That's measured as a wait on the system.
An ITL wait, not a buffer busy wait, which shows
up as a TX lock wait in mode 4 in v$lock (one of
several reasons for TX/4).
>
>> may the low initrans cause a deadlock (2 session locking 2 blocks....) ??
>
> No. Deadlocks are caused by two transactions trying to lock each others
> rows. Nothing to do with this at all.
>
It would be unusual, but since an ITL wait is a TX wait,
then two transactions could deadlock because they were
waiting for each other to commit and release an ITL slot.
This may in part justify Oracle's decision to set the number
of ITL entries in tables to 2 (even when you set initrans and
maxtrans to 1).
> Regards
> HJR
>
>
Received on Thu Nov 25 2004 - 14:23:04 CST
