Using Compress extents yes causes a logical compression of the extents into one extent. Each table and each index is merged in a single extent during the later import.

The size of the combined extent is calculated, on the SAPDBA side, from the sum of the extents allocated in total by the object.

If this sum exceeds the maximum amount of free space available (for reorganization of a table or an index) or the maximum data file size (for a tablespace reorganization), the extent is divided up into single extents so that the free space or data file size is not exceeded. In this case, the values for INITIAL and NEXT are equal; MINEXTENTS is set to the number of extents required. SAPDBA will issue a recommendation that you reduce the value for NEXT after the reorganization.