I've been using DBOptimizer and using Tanel Poders scripts. SID 0 is using a lot of CPU (in a particular test case). If the latch was named 'shared pool latch' I'd have an explanation, but LatchProfX is revealing that latch 'ksuosstats global area' is at the top and 'shared pool latch' is not listed. I went to MOS and searched, as well as Google, and ksuosstats normally shows up as part of a list of latches and the discussion is normally centered around another issue. Can anyone let me know what this might be all about? Is it part of the shared pool, and therefore part of the initialization process normally associated with SID 0? (thanks Tanel). Joel Patterson Database Administrator 904 727-2546