RE: Truncate table "REUSE STORAGE"

But the disadvantage of reusing storage is if the table data will fit into a smaller allocation then on reload this unnecessary space will still be allocated to the table and its indexes. If freeing space was not the point of the reorganization then what was?

If the table will expand again to fill the same space then maybe you do want to reuse. Just keep in mind why you are unloading, truncating, and reloading.

HTH -- Mark D Powell --

-----Original Message-----

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Allen, Brandon Sent: Friday, March 24, 2006 11:29 AM
To: cemail_219_at_hotmail.com; oracle-l_at_freelists.org Subject: RE: Truncate table "REUSE STORAGE"

Yes, at least I think it would save some time since it avoids deallocating and then reallocating the storage (extents) for the segment. I haven't actually tested to confirm or see how much of a difference it makes though. I'd expect it to make more difference in a dictionary managed tablespace than in an LMT.

Regards,
Brandon

Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.

--

http://www.freelists.org/webpage/oracle-l

--

http://www.freelists.org/webpage/oracle-l Received on Fri Mar 24 2006 - 12:46:28 CST