Originally posted by ganjisb
Found that the following event has been set.

event = "10235 trace name context forever, level 1"


Is this causing the problem ?
This event will check the memory manager internal structures. and generates trace in the UDUMP.

This can be a possible cause as this degrades the performance.

According to metalink

-------------------------------------------------------
This event may be used to try to catch HEAP corruption problems closer to when they occur. Typically level 12 is required to get close to the corruption but this can impact performance too much to be useful.
-------------------------------------------------------

Try removing this parameter and then startup the database and run the querry again.

Regards
Amar