Re: INITRANS and MAXTRANS are confusing me?

Following up on Richard Foote, 13 Mar 2003:

>
> I think what Richard is getting at is that there is no free space left
> in the block for additional transaction entires to be created. If the
> block is absolutely chokers and you set INITTRANS too low, you could run
> out of space and locking/deadlocking issues could result.

Yeah, I got that. But it sounded like "once a process has a lock on header, no other row can be updated in block". Which is not what Oracle does. ;)

>
> I would suggest a possible solution to many of Richard's problems would
> be to increase the freelist/freelist groups or look at using ASSM
> (Howard's not around is he ?) if it's the loading of the data that's
> causing the problems.

Narh. Just sort the ETL transactions by PK of table then split the file into bits, one for each parallel process. Bingo, no more problems.

> Yes there could be issues with inappropriate block locking but it's
> generally a result of a preventable design flaw.
>

Agreed. But he's got a problem he needs solving now and he doesn't exactly like the prospects of re-building. Neither would I if I was in his skin... :(

-- 
Cheers
Nuno Souto
wizofoz2k_at_yahoo.com.au.nospam