>> YOU ONLY increase INITRANS when you have the specific waits assocuated with this type of contention. Read this carefully:http://www.dba-oracle.com/t_initrans.htm
Eliminating data block contention involves eliminating “hot” data blocks from the application, and super-high concurrent DML can cause block contention that will be relieved by increasing INITRANS for the effected tables and indexes.
As the database version is 8i, I dont have v$segment_statistics or as such to check the ITL waits. Actually, we are facing ORA-00060. Most of the times I found a particular table CUST_BILL_MAST in the trace files from udump directory. Some times other tables too.
Also, the application is getting freezed sometimes and we are forced to kill those sessions. I dont find ORA-00060 during that time. I dont know what to do as I cant capture as its not an event. There is no error in alertlog. This is happening at one of the client's place. The DBA operator is just killing the sessions. I told to capture the SQL and also take a system state dump when that freezing occurs. That has not happened since few days. Meanwhile we thought to incrase the INITRANS for all the TABLES. Aslo, As we are migrating to 10g and as we have AUTO SEGMENT SPACE MANAGEMENT, we dont want to worry about FREELISTS.
So, we want too increase INITRANS and check it.
Also, Is there a way to find out ITL Waits or is there something like V$SEGMENT_STATISTICS in Oracle 8i to check the actual contention? Ofcourse once we move to Oracle10g, there are rich features to find out the contention and which help to resolve the issue easily.