>Instance runs 20 parallel load processes You might be encountering enqueue waits. Typically INITRANS=3D1 for tables & 2 for indexes (YMMV). Unless & until the session holding the Interested Transaction Lock releases it, other sessions will quietly get into line waiting for it to be released. This is NOT a deadlock & won't be reported as one. HTH & HAND! On 4/17/05, ryan_gaffuri@xxxxxxxxxxx <ryan_gaffuri@xxxxxxxxxxx> wrote: > Please provide your definition of 'hang'? To see if your processes are st= ill running look in v$sess_io, if the values there are incrementing, then p= rocessing is still going on. > you need to find out what the processes are doing at the point that they = are freezing? Best way is to get a 10046 trace of one of the processes dump= ed to a file. Another alternative is to use statspack of before the 'hang' = and then another snapshot afterward and look at what sql is processing. >=20 > you mentioned that the times that you have problems are when you have loc= k waits. you could have 1 process doing something for a long time and aquir= ing a lock on a row. the rest of the processes require that row and have to= wait for a commit or rollback. >=20 > the v$ tables(other than a quick look at v$sess_io) probably won't be hel= pful here. you need to know exactly what is going on when this occurs. >=20 > -- > //www.freelists.org/webpage/oracle-l > -- //www.freelists.org/webpage/oracle-l