|
|
|
Re: how to free up the shared pool memory [message #57379 is a reply to message #57372] |
Tue, 10 June 2003 12:59 |
Trifon Anguelov
Messages: 514 Registered: June 2002
|
Senior Member |
|
|
The shared pool has cached SQL and PL/SQL code. Once the transaction starts, there is no more need for the shared code to be accessed, so flushing the shared pool will not affect your running transactions.
However will affect the transactions after the flush. All the SQL shared code will be gone, and you have to do hard parses to polulate it again, your library cache hit ration will decrease, etc...
Better tune your shared pool, that flushing it. It will happend again, so you will be flushing until you tune it. What good that can make ???
Hope that helps,
clio_usa
OCP - DBA
Visit our Web site
|
|
|