Considerations when loading partition-by-growth table spaces

How LOADPLUS handles new partitions

The following considerations apply when LOADPLUS adds new partitions:

• If you are making copies, LOADPLUS copies all partitions, including those that it adds to the table space. Therefore, you must consider possible expansion when allocating your copy data sets. We recommend that you enable dynamic allocation for your copy data sets when loading partition-by-growth table spaces. For more information, see Copy-data-sets-in-LOADPLUS.
• How LOADPLUS handles compression dictionaries for new partitions depends on the type of job that you are running:
  • For LOAD REPLACE, LOADPLUS uses the dictionary from the first partition.
  • For LOAD RESUME YES, LOADPLUS uses the dictionary from the partition in which the load started adding rows.

Row format considerations for partition-by-growth table spaces

For partition-by-growth table spaces, LOADPLUS uses the existing row format of the table space.

The following requirements apply:

• All partitions in the table space must be in the same row format.
• The partitions must be in the following format, based on the Db2 subsystem parameter RRF:
  • When RRF=ENABLE, the format must be reordered row format (RRF).
  • When RRF=DISABLE, the format must be basic row format (BRF).

SHRLEVEL considerations for partition-by-growth table spaces

The following considerations apply to the SHRLEVEL option that you specify:

• For load jobs that use staging data sets, do not preallocate your staging data sets when loading partition-by-growth table spaces. Allow LOADPLUS to handle the allocation.
• For LOAD REPLACE SHRLEVEL CHANGE, LOADPLUS does not support partitions that are added during your load other than those that LOADPLUS adds. If LOADPLUS detects that a new partition is added after the load has started, LOADPLUS issues messages BMC50225E and BMC50010U and terminates with return code 16.
• For a SQLAPPLY load, message BMC51579I does not indicate how many rows were loaded into each partition. Use the information in this message only to ensure that the total number of rows loaded into the table space is correct.

Other option considerations when loading partition-by-growth table spaces

The following considerations apply to specific options when you are loading partition-by-growth table spaces:

• You cannot specify the INTO PART option (with or without REPLACE) when loading a partition-by-growth table space.
• If you are making partition-level copies and sending them to tape, ensure that the value for the MAXTAPE option takes potential expansion into account.

Restart limitations when loading partition-by-growth table spaces

The following limitations apply to restarting your load job when you are loading a partition-by-growth table space:

• If the value for MAXPARTITIONS changes between the time the job fails and the time you restart it, LOADPLUS issues message BMC50221U and terminates.
• If Db2 adds partitions before you restart a job, LOADPLUS issues message BMC50221U and terminate.
• If a SHRLEVEL NONE load job fails because insufficient space is available, we recommend that you perform an ALTER to decrease the PCTFREE or FREEPAGE value before restarting the job. However, LOADPLUS only honors these changes only in the following situations:
  • For a single-phase load, LOADPLUS honors these changes for partitions that it has not started loading.
  • For a two-phase load, LOADPLUS honors these changes only if the failure occurs during the PRELOAD phase.

BMCSYNC table considerations when loading partition-by-growth table spaces

When you are loading a partition-by-growth table space, you might need to increase the size of the BMCSYNC table space from the standard size that was allocated during installation.

Estimate this allocation based on all of the following factors:

• The number of utilities that you are running concurrently
• The value of MAXPARTITIONS
• The number of files that you are dynamically allocating