Re: how to determine cause of deadlock

Good point.

If you use serializable transactions, you should increase INITRANS. Given that most people leave INITRANS at the default of 1 for tables and 2 for indexes, the manuals (I think) advise increasing initrans to 2 and 3 respectively. If you have already increased INITRANS for highly concurrent tables, you may have done enough anyway to cater for serializability.

--

Jonathan Lewis
Yet another Oracle-related web site:  http://www.jlcomp.demon.co.uk

Atta ur-Rehman wrote in message <8l3d3q$vmc$1_at_nnrp1.deja.com>...


>nice discussion folks.

>

>i was just wondering if we've missed to consider the transaction

>isolation level set in the application and how a serializeable

>isolation level gonna affect this whole scenario. i think, i read it

>somewhere, that if the transaction isolation level is set to

>serializeable then the INITRANS parameter should be set to at least 3.

>

>any commnets from gurus?

>

>regards,

>

>:) ATTA

>

>In article <15d5d80c.b9c2a2e6_at_usw-ex0102-015.remarq.com>,

>  gdas <gdas1NOgdSPAM_at_yahoo.com.invalid> wrote:

>> Jonathan,

>>

>> I rebuilt the table and the indexes with a higher initrans value

>> (I put both at 100...no scientific method here...just randomly

>> picked it).

>>

>> The application has now been running for 3 consecutive days and

>> not a single deadlock has occurred.  Now that we've proven the

>> solution, I'll go back and try to set a lower initrans value to

>> minimize the wasted space.

>>

>> Who would've thought?  Learning something new everyday...

>>

>> Thanks for your help,

>> Gavin

>>

>> -----------------------------------------------------------

>>

>> Got questions?  Get answers over the phone at Keen.com.

>> Up to 100 minutes free!

>> http://www.keen.com

>>

>>

>

>--

>

>getting the meanin' of data...

>

>

>Sent via Deja.com http://www.deja.com/

>Before you buy.