Hitting the roof on shared pool

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 - 03:53:07 CST