Re: strang table locking

[Quoted] Kinda strange logic, guys. The trace file says that this is a table [Quoted] [Quoted] exclusive lock. INITTRANS says how many transactions may be kept in a block. If you have more transactions than that, you'll get a block [Quoted] latch, not a table lock. Try to index all foreign keys in the detail [Quoted] table, it should help.

In article <980799872.2896.0.nnrp-14.9e984b29_at_news.demon.co.uk>,   "Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote:
>
> Good point.
> You can (at least on 8.1.7, which is what my HP is at present):
> alter table xxx initrans 4;
> alter table move;
> or
> alter table xxx move initrans 4;
> and the ini_trans column of the resulting table
> is indeed 4 - and it should be true, although I
> haven't actually tried packing a sample table
> and dumping the resulting blocks after the move.
>
> --
> Jonathan Lewis
> Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk
>
> Practical Oracle 8i: Building Efficient Databases
>
> Publishers: Addison-Wesley
> More reviews at: http://www.jlcomp.demon.co.uk/book_rev.html
>
> Howard J. Rogers wrote in message <3a755c8a_at_news.iprimus.com.au>...
> >Jonathan: If inittrans is changed (it's only part of the sotrage
 clause
> >after all), will a move tablespace command result in the entire
 segment
> >picking up the new value?
> >
> >Regards
> >HJR
> >
>
>

Sent via Deja.com
http://www.deja.com/ Received on Wed Jan 31 2001 - 18:02:15 CET