Analyzing the Statistics 
Reorganization is not required as often as is commonly assumed. This can be briefly explained with the following considerations.
- Number of data files
: A reorganization with data files is not necessary until the total number of data files in the database approaches the limit MAXDATAFILES. In such cases, reorganize tablespaces that consist of many files using the SAPDBA option Reorganization
®
Reorganize tablespace and data files.
- Number of extents per table or index
:
SAP usually uses indexes to find entries. This means that full table scans are only rarely required. It is not necessary to limit the number of extents per table as long as ORACLE is capable of managing that number.
A reorganization should be considered when total system performance declines due to a large number of extents of a table or an index. If many of the objects consist of a large number of extents, reorganize the relevant table, index, or the entire tablespace.
- Number of freespace fragments in the tablespace
:
The system monitor of the ORACLE database system is capable of automatically merging the contiguous freespace areas. This significantly reduces the probability that a reorganization will become necessary due to freespace problems.
If, however, none of the remaining fragments is large enough to create a new extent, you should extend the tablespace and possibly schedule a tablespace reorganization at a later time that is suitable.
Also see
Limitations of the Database System.