Q

Defragmenting schemas with LMT

We have Oracle 9i databases using bitmap tablespaces (LMT). Now it's time to defragment a few schemas, because few tables have more than 60 extents; how could we do that? I know the normal export (compress=y) and import will not work on LMT.

We have Oracle 9i databases using bitmap tablespaces (LMT). Now it's time to defragment a few schemas, because few tables have more than 60 extents; how could we do that? I know the normal export (compress=y) and import will not work on LMT.
I have to ask what you hope to accomplish by using fewer than 60 extents in your table. A table with many extents does not have performance problems compared to the same data in a table with fewer extents. I have many, many tables with many thousands of extents and I do not have performance problems with these tables. By its very nature, Locally Managed Tablespaces will cause fragmentation and require many extents for a segmeent. This is by design and is to be expected. I would just leave your tables as they are.
This was last published in March 2006

Dig Deeper on Oracle database design and architecture

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide

SearchDataCenter

SearchContentManagement

SearchFinancialApplications

Close