I ran into this problem recently also. There might be some sort of event
you can dump to view the size of these objects, not sure, we were pretty
sure we knew which array was causing the problem but not sure where in
the code the array was getting hit. I have a package that will rewrite
the PLSQL and add instrumentation, I added some info about UGA/PGA size
to the output then monitored, we narrowed it down to a particular
package/procedure, added more detailed instrumentation there and then
found the specific message being added to the array that was the
culprit. In your case it sounds like you need to determine which array
is the problem first and some sort of dump may be able to tell you that,
I am sure if that is the case someone will chime in.
--
http://www.freelists.org/webpage/oracle-l
Received on Thu May 12 2005 - 11:34:41 CDT
