Re: rman Ora-4031 - how to flush large pool?

Doug,

you forgot to mention your database version and platform.

I'm pretty sure flush shared pool does not flush the large pool. It's used for completely different purposes. I believe RMAN only uses the large pool for IO buffers and that's not what's running full with a 4031. I've seen many times flushing the shared pool only very temporarily or not at all alleviates 40431's. Best bet in my experience is to bounce the instance and bump the shared pool up. It could also be some sort of bug since it's RMAN that's causing it and never anything else (assuming here).

Finn

On Mon, Jul 14, 2008 at 7:36 PM, Douglas Cowles <dcowles_at_us.ibm.com> wrote:
> We have a system that is throwing ORA-4031's in rman archive log backups
> after the system has been up a few days. To my understanding, RMAN tries to
> use the large pool for it's activities. When we alter system flush shared
> pool - the errors do not stop - the database has to be bounced or the
> large_pool has to be increased 3M or so. Does alter system flush shared_pool
> flush the large pool? If it does, then why would that not defragment the
> pool? If it does not, is there a way to do it? In general, will flushing the
> shared_pool defragment it - large pool or otherwise?
>
> Thanks,
> Doug C.
>

--
http://www.freelists.org/webpage/oracle-l