Checking Freespace

During each reorganization, SAPDBA checks whether all reorganized objects can be restored with their data in the appropriate tablespaces. Besides the size of INITIAL and NEXT, the number of extents expected is also taken into account (according to MINEXTENTS and the amount of data to be imported). This corresponds to the default of the option Check space: for ALL extents

In certain exceptional cases (particularly when the option Compress Extents: no and/or Reduce object size: no is set), the memory space check may be too restrictive. This means that SAPDBA states that there is too little freespace although there would be enough space.

In such cases, the option Check space: ONLY first MINEXTENTS extents can be set. This means that only the INITIAL extent or the extents according to MINEXTENTS are included in the storage space check. Other NEXT extents are not taken into consideration in the space check.

If additional NEXT extents are generated during the import/load and the import/load terminates due to lack of space, the import/load can be repeated with restart after the tablespace has been increased.