Re: Oracle 8.1.7: shared pool fragmented - can I clear it on-the-fly?

How can you say you shared pool is fragmented ??

Be precise with error codes in your terms.... informatic is a cartesian science, not an art.

However, memory management issues can cause some areas of shared pool to have a bad use of memory... this was some times ago an issue, notably in the sql area for non binded statements.

In some case, doing an "alter system flush shared_pool" may help for application which are not using shared SQL, or obviously is doing strange statements.

This command will flush from SQL area un-pinned statements (not currently being executed), and PL/SQL blocks. This can result in unused chunks of memory to be said free, knowing these chunks are of the same size.

If your application is making a strong use of big PL/SQL blocks (stored or not), then ensure these are using bind variables (they can be shared), and maybe try to allocate a bigger dedicated space for large PL/SQL blocks (someting like "shared_pool_reserved_size").

"Holger Marzen" <holger_at_marzen.de> a écrit dans le message de news:bbban1$gos$1_at_bluebell.marzen.de...
> We run a customer's application on Oracle 8.1.7. From time to time it's
> not possible to log in anymore. The shared seems to be fragmented. A
> restart of the instance helps, but then the application has to be
> restarted as well.
>
> Is it possible to de-fragment the shared pool or at least clear it while
> the instance is up and the application stays connected?
Received on Sat May 31 2003 - 18:29:19 CDT