Oracle does not try to preserve a certain amount of free memory in the shared
pool (as operating systems do). In fact Oracle tries to cache as much as
possible. There will always be a small amount of free memory because of the way
that the LRU algorithms works, but if that is at all generous (other than after
instance start-up) then the shared pool is too big.


-----Original Message-----
Sent: Thursday, 31 August 2000 1:06


According to Gurry & Corrigan's "Oracle Performance Tuning", Oracle always
preserves some (how much - I don't know) free memory in shared pool. That's
the reason for my previous question. So if my understanding of your answer is
correct the free memory in shared pool can't be considered as a key during
fine tuning (except of the case when too much memory was allocated for
shared pool). Did I understand this issue correctly?