The 1092 error should have produced a trace file in your bdump dir. Tha may
give you some clues. Are your tablespaces locally managed? Did any of your
objects with a small extent size grow dramatically recently? You may want to
set event 10046 to level 12 and run some of you slow queries. This should give
you a better understanding of where the problem is. you can also look at
v$session_wait,v$system_event, and v$latch (if latch free is high on the list
of wait events). To use the 10046 trace do the following: SQL> alter session
set events '10046 trace name context forever, level 12'; run your query and
look at the trace file that will be located id your udump directory. You can
also tkprof this file to see what exactly your query is doing. Hope this
helps.
--
Posted via Mailgate.ORG Server - http://www.Mailgate.ORG
Received on Thu Jan 10 2002 - 12:18:25 CST
