Why fragmented SYSTEM tablespace ?

I have just created a new database with a system tablespace sized at 130 MB.  Even though it is only 25% full and does not contain any auditing records it is still fragmented.  Why ?   Do I dare try to defragment it ?

                                            Fragmented segments with more than 2 extents

OWNER                SEGMENT_NAME                      SEGMENT_TYPE         EXTENTS
-------------------- --------------------------------- ----------------- ----------
SYS                  SOURCE$                           TABLE                     11
SYS                  SYSTEM                            ROLLBACK                  10
SYS                  IDL_UB2$                          TABLE                     10
SYS                  C_OBJ#                            CLUSTER                    9
SYS                  I_SOURCE1                         INDEX                      9
SYS                  IDL_UB1$                          TABLE                      9
SYS                  VIEW$                             TABLE                      7
SYS                  I_COL1                            INDEX                      6
SYS                  I_OBJ2                            INDEX                      6
SYS                  I_OBJAUTH1                        INDEX                      6
SYS                  IDL_SB4$                          TABLE                      6
SYS                  OBJ$                              TABLE                      6
SYS                  C_FILE#_BLOCK#                    CLUSTER                    5
SYS                  C_USER#                           CLUSTER                    5
SYS                  I_ARGUMENT1                       INDEX                      5
SYS                  I_OBJAUTH2                        INDEX                      5
SYS                  ARGUMENT$                         TABLE                      5
SYS                  COM$                              TABLE                      5
SYS                  OBJAUTH$                          TABLE                      5
SYS                  C_TS#                             CLUSTER                    4
SYS                  I_COL2                            INDEX                      4
SYS                  I_COM1                            INDEX                      4
SYS                  I_DEPENDENCY2                     INDEX                      4
SYS                  ACCESS$                           TABLE                      4
SYS                  DEPENDENCY$                       TABLE                      4
SYS                  IDL_CHAR$                         TABLE                      4
SYS                  TRIGGER$                          TABLE                      4
SYS                  I_CON1                            INDEX                      3
SYS                  I_DEPENDENCY1                     INDEX                      3
SYS                  I_OBJ1                            INDEX                      3
SYS                  I_SYSAUTH1                        INDEX                      3
SYS                  SEQ$                              TABLE                      3
SYS                  SYN$                              TABLE                      3
Who is Participating?
myerpzConnect With a Mentor Commented:
My advice would be to leave it alone and not worry about it. Read the white paper : "How to stop defragmenting and start living" in the Internet DBA section of Oracle Technet and you will see what I mean.


I think it is looking good. One of my db is in state like that

segment          bytes          extents

I_SOURCE1     418914304     26
SOURCE$          953606144     23
IDL_UB1$     1333714944     23
IDL_UB2$     302833664     22
ARGUMENT$     107454464     17

and we can see no negative impact on performance.

 Talking about fragmentation is typical topic of big flamewars.

When create new Oracle DB, both users system or sys temporary tablespace are system. Also, the default tablespace for 1st rollback segment is system. Both will cause the system tablespace becomes fragmented
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Hi, Eugene,

Fragmentation per se of the SYSTEM tablespace does not seem to be an issue, unless you have encountered a specific problem because of it.  Compared with the sizes of data tablespaces, the SYSTEM tablespace is usually very small, and the amount of I/O involved is also comparatively small.
The fragmentation is in objects, not in free space.
This fragmentation is result of starage clause - INITIAL EXTENT and NEXT EXTENT.
When the initial extent is full, then the next data will storaged in next extent - this next storage portion.
You can "defragment" object with re-creating it with new storage clause. For objects in tablespace SYSTEM this is not recomendet!
The another way is to make full export with compress extents and then make full import.

EugeneGardnerAuthor Commented:
Thanks for the replies.  I will be reading through the article Myerpz mentioned.  I eventually found it at:

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.