I really can't answer definitively one way or another. If it was good for you under 8 and 9, then of course you know for versions 8 and 9. The thinking has always been in the past (oracle 8 and 9), when the subject came up, especially with tables, that the least recently used algorithm employed by oracle would purge essentially keep the hot tables anyway and so there wasn't any point in pinning them. Now I'm sure you have more detail than that, but thought I'd put that out there for consideration for whatever it might be worth. Joel Patterson Database Administrator 904 727-2546 -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Crisler, Jon Sent: Wednesday, March 10, 2010 11:37 AM To: karlarao@xxxxxxxxx; moovarkku.mudhalvan@xxxxxxxxxxxxxxxx Cc: Oracle-L@xxxxxxxxxxxxx Subject: RE: SGA Fragmentation - How to Monitor If this is an Oracle Applications / Ebiz / ERP system you can also look into "pinning packages". This was a good thing to do under 8i and 9i, so I assume that it is still valid with Oracle 10g. -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Karl Arao Sent: Wednesday, March 10, 2010 5:31 AM To: moovarkku.mudhalvan@xxxxxxxxxxxxxxxx Cc: Oracle-L@xxxxxxxxxxxxx Subject: Re: SGA Fragmentation - How to Monitor There's also a note that contains good explanations plus cool toolkits/scripts that you could use. ORA-4031 Common Analysis/Diagnostic Scripts Doc ID: 430473.1 - Karl Arao karlarao.wordpress.com karlarao.tiddlyspot.com -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l