I do not avoid fragmentation in my tablespaces. Quite the opposite is true. I embrace fragmentation in my tablespaces and I expect my database segments to become fragmented. When I create my tablespaces, I create them as a Locally Managed Tablespace (LMT). The LMT manages my extents for me. With Oracle managing my extents, I will almost always see a segment comprised of multiple extents, which is fragmentation of that segment.
There is nothing wrong with fragmentation in the tablespace. It used to be that the DBA would occasionally defragment the tablespace to improve performance. Such defragmentation operations should not be done as it has been shown that fragmentation of database segments does not cause performance problems in the Oracle database. Defragmenting the tablespace is only wasting time.
Dig Deeper on Oracle database design and architecture
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.