Re: Hitting the roof on shared pool

Have you patcher the 7.3.4 yet? For example-there is an issue with large views in 7.3.4 which is corrected in 7.3.4.3 or the latest 7.3.4 patchset-cant exactly remember which patch set corrected that issue... We found that to parse a cursor with the use of views required up to 6x the amount of memory. For example-a cursor was taking up to 120K , and with a patch-it was reduced to 20K...

HTH
Greg

ole c meldahl wrote:

> Hi
>
> We have a set of complex jobs which we need to run simuntaneously, there
> is a whole set of complex views depending on complex views involved, and
> the query plan seem to fill up shared pool.
>
> Is there any other way to avoid this than increasing shared pool? Can I
> for instance pin the top complex views and avoid a complete reparse of
> these each time(COMPLEX_VIEW_MERGE = false)? Will 8.0.5 be any better at
> this? What are the practical limits for shared pool? We have an instance
> on a busy server running many instances.
>
> BTW we're on Oracle 7.3.4 moving to 8.0.5
>
> Any input is greatly appreciated!!
>
> ole c
Received on Wed Nov 24 1999 - 06:58:59 CST