If you are reorganizing a tablespace that grows quickly (e.g. tablespace with transaction data), we recommend using the SAPDBA command option sapdba -next <tablespace/s> . This option instructs SAPDBA to adjust the value of NEXT in accordance with the rapid growth of the tablespace. Adjusting NEXT prevents the tablespace from reaching the MAXEXTENTS limit too quickly.

The -next option involves adjusting the NEXT parameter according to the tables DD09L and TGORA/IGORA.

The new value for NEXT is calculated as the maximum of the following 2 values:

1. An SAP object is assigned a size category via table DD09L. The NEXT value is determined from table TGORA/IGORA based on that category. (If no category is assigned in DD09L, this value is not generated.)
2. SAPDBA calculates the maximum of the following values:

SAPDBA compares this chosen value (maximum of 1. and 2.) with the values for the extent size in TGORA/IGORA. SAPDBA chooses the next smaller value found in TGORA/IGORA as the new NEXT value. If TGORA/IGORA do not exist, SAPDBA uses an internal default value. See also Default Value for NEXT.

This procedure prevents the number of extents from growing too quickly and - with repeated use - simulates an asynchronous, linear PCTINCREASE response. The changed tables are recorded along with their old and new values in the log <timestamp>.nxt .

See SAPDBA Command Mode.