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 first published in March 2006

Dig deeper on Oracle database design and architecture

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

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.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide

SearchDataCenter

SearchContentManagement

SearchFinancialApplications

Close