For optimal performance in most systems, the entire SGA should fit in real memory. I was looking but could not find it.
This reduction in turn limits the ability of the system to adapt to workload changes. If the specified lower limit for the size of a given SGA component is less than its current size, there is no immediate change in the size of that component.
ASMM December 10, 2009 - 11: Oracle Version: It includes the following topics: Because certain SGA components either cannot easily shrink or must remain at a minimum size, the instance also prevents you from setting the target memory size too low. AMM January 11, 2013 - 9: See Also: How does this work. The new setting only limits the reduction of the large pool size to 200 M in the future.
When you decrease the size of a manually sized component, the memory that is released is given to the automatically sized components. Post as a guest Name.
On platforms that do not support this much physical memory, this parameter is ignored. A 32K block size is valid only on 64-bit platforms. When you disable automatic memory management, Oracle reverts to automatic shared memory management and automatic PGA memory management.
See Also: PGA pools. Brilliant article November 16, 2012 - 5: Suraj Sharma from India. Tony from Reading, UK.
Hot Network Questions.