Re: how to determine cause of deadlock

The critical point is:
> or the block has no more free space.

You may simply have very full blocks, so there is no room for dynamic addition of extra transaction slots.

Can you rebuild the table and indexes
with a higher initrans - how many concurrent processes are you likely to have hitting a single block at any one moment ? Try
that as the INITRANS.

--

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

gdas wrote in message <07b58444.00c49df7_at_usw-ex0102-015.remarq.com>...


>the initrans value on the feature table is set to 1 and the

>inittrans value on the indexes in that table are set to 2.  Both

>are the oracle defaults and both have a maxtrans value of 255.

>

>I was reading up on initrans in the oracle documentation and it

>says this:

>

>If the number of concurrent transactions updating a block

>exceeds the INITRANS value, Oracle dynamically allocates

>transaction entries in the block until either the MAXTRANS value

>is exceeded or the block has no more free space.

>

>Is this statement correct?  Since oracle should automatically be

>increasing the number of concurrent transactions up to 255.  The

>documentation also says that the range for maxtrans is 1 to 255,

>which implies that I can't increase it anymore.  Am I screwed

>here?

>

>Thanks for the assistance,

>Gavin

>

>

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

>

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

>Up to 100 minutes free!

>http://www.keen.com

>