Set lower memory limits for SGA components
Folks,
I am having a spirited discussion with my team concerning the setting of lower limits only for SGA components like SHARED_POOL, JAVA_POOL, LARGE_POOL, etc. while using ASMM. The SGA TARGET is obviously sized large enough to manage the SHRINK/GROW but I never want the possibility to SHRINK any of my pools to "0". Is the possibility remote - maybe - is setting the lower limits an insurance policy - yes - and a good practice as taught in all my Oracle Performance Tuning classes.
I am interested in others opinions.