> > It's not a 12 seconds it's a 1192 seconds, I think. > > And it doesn't look like 'collection error' since the max.wait is 2.8 > > seconds > > Probably the problem is on client's side, not on the server. Server > > spent 23 seconds of it's CPU time and waited 1192 seconds for client's > > commands. > > I checked the docs, according them that's centiseconds (100ths of a > second) 1192cs is 11.92s, close enought to 12 for government work. I beg your pardon but what kind of docs did you check? In 'Elapsed times include waiting on following events' section times are in seconds. In raw trace files for Oracle version less than 9 times are in centiseconds. Egor http://www.oracledba.ru/orasrp/ Free Oracle Session Resource Profiler -- //www.freelists.org/webpage/oracle-l