The first thing that comes to my mind is that with massive deletes you will have an artificially high high water mark with could very well have a significant impact on queries the perform full table scans. You would need to review sql that hits that table and check to see if full scans are performed if so, create a second table and alter the sql to hit that to tell if it would make a significant different. Then there's the potential disk savings...which are often not that big of a deal. There's probably more to it and i believe you could find the info in the archives. -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of ryan_gaffuri@xxxxxxxxxxx Sent: Wednesday, September 08, 2004 3:51 PM To: thump@xxxxxxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx Cc: David Subject: Re: segment fragmentation if you use LMTs you have no fragmentation problems.=20 -------------- Original message --------------=20 > I have been asked to determine segment/object fragmentation levels after a=20 > mass delete has been performed.=20 >=20 > Do LMT only negate fragmentation occuring at a tablespace level as an=20 -- To unsubscribe - mailto:oracle-l-request@xxxxxxxxxxxxx&subject=3Dunsubscribe=20 To search the archives - //www.freelists.org/archives/oracle-l/ -- To unsubscribe - mailto:oracle-l-request@xxxxxxxxxxxxx&subject=unsubscribe To search the archives - //www.freelists.org/archives/oracle-l/