Don, Can we see the following? select event, sum(time_waited) tw from dba_hist_active_sess_history where to_char(sample_time,'yyyy-mm-dd hh24:mi')='<first minute of problem>Please also provide this for the two or three minutes preceding the problem, and a minute with no problems from well before the issue. When finding the first minute, it is important you find the first minute when things were not looking normal in dba_hist_active_sess_history, not necessarily the first minute things were noticeably bad on the database.
Thanks, Jeremiah Wilton ORA-600 Consulting http://www.ora-600.net Don Seiler wrote:
Actually those Concurrency events regarding latches had 0 time_waited. The events that did have some time were "os thread startup" events from CJQ0. Sounds like Oracle trying to kick off scheduled jobs? I'll check the job history. On 9/14/07, Don Seiler <don@xxxxxxxxx> wrote:The two largest items are Concurrency and Other. The concurrency events deal with latches (shared pool and library cache). The Other events deal with "block change tracking buffer space" and "latch free". There is also a large number of "Configuration" class events, but those come at 11:28, after all the fun, so might just be another symptom.
-- //www.freelists.org/webpage/oracle-l