You probably read something wrong. You can find a some of answers in standard Oracle documentations and others you might infer from what you know about your application and what you read from docs. Consider those: http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14220/memory.htm#sthref1304 http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14211/memory.htm#sthref540
Now, from practical point of view Oracle is really good managing it's cache and usually it's effective enough keeping hot blocks in memory without configuring keep and recycle pools.
Hello
I would like to ask you about KEEP_POOL and RECYCLE_POOL. I read about this subjects, but maybe you have experience with that. What is better to put into KEEP or RECYCLE - big tables or small tables with index or without index. How can I find the best candidates to keep pool or recycle_pool? How does keep behaves when client inserts or updates data. Any suggestion are very welcome.
Rgds.
Wojtek -- //www.freelists.org/webpage/oracle-l
-- Best regards, Alex Gorbachev
The Pythian Group Sr. Oracle DBA
http://www.pythian.com/blogs/author/alex/ http://blog.oracloid.com -- //www.freelists.org/webpage/oracle-l
