Reseved shared pool memory is physically a part of normal shared pool memory. Oracle spreads the reserved pool evenly across all shared pool memory extents, that way the reserved pool can grow-shrink easier along with rest of shared pool. When you do a shared pool heapdump, you'd see there are tiny chunks of memory called "reserved stoppers". When kgh heap manager is searching for free space within an extent and hits the reserved stopper chunk, it will know that memory from this stopper up to end of extent is reserved, thus doesn't allow small allocations there. Tanel. _____ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Roby Sherman Sent: Sunday, June 24, 2007 23:50 To: oracle-l Subject: Re: V$SGASTAT in 10.2 and the Reserved Pool Hi. I got the principles, thanks, I was more curious of where it was tallied... It looks like reserved pool free memory is summed with general shared pool memory in V$SGASTAT... Slightly misleading, but I can deal with that. Thanks.