Explanation of the error

As it is explained in AMI REORG documentation, this is the description of error message NGTR597E:

NGTR597E - PAGE NUMBER (hexstring-1) EXCEEDS SPACEMAP (hexstring-2) PAGES COVERED

Explanation: This message indicates a problem with the table space being updated. An attempt was made to add a page (X'hexstring-1') to a spacemap page (X'hexstring-1'). However, the page being added exceeded the spacemap page's capacity. This message always precedes NGTR599.

User response: This will occur if the data set capacity is exceeded. In which case, reduce the PCTFREE value, and/or increase the FREEPAGE value, so the rows fit within DB2 limits.

After PTF BQU3368 (SPE2104) is applied, the use of +PBGPARTS(PROCESS) parameter allows AMI REORG to treat the PBG tablespace not as a single object but process each partition individually.

However, in this case, no FREESPACE can be added to a partition and this can result in the issuing of error message NGTR597E, if the object is defined with PCTFREE greater than 0, and the associated VSAM dataset has reached its maximum capacity:

NGTR597E PAGE NUMBER (hexstring-1) EXCEEDS SPACEMAP (hexstring-2) PAGES COVERED

Solution

The solution to this problem varies depending on two scenarios:

a) RTS keyword is specified in REORG TABLESPACE statement, +PBGPARTS(PROCESS) is in effect and ALL partitions qualify for REORG.

In this scenario, you can solve the error by applying PTF BQU3517. When all the partitions of a PBG Tablespace are selected to be REORG'd by RTS processing, the functionality of PTF BQU3517 will process ALL the Partitions of the Tablespace as a single object and this will allow the addition of FREESPACE to a full part.

b) RTS keyword is specified in REORG TABLESPACE statement, +PBGPARTS(PROCESS) is in effect but NOT ALL partitions qualify for REORG.

In this scenario, even if you APPLY BQU3517 error message NGTR597E is issued when processing a PBG tablespace, because RTS processing selects only SOME partitions of the Tablespace.

The following message appears to confirm that +PBGPARTS(PROCESS) will handle partitions individually:

NGTR764I INDIVIDUAL PARTS WILL BE REORGANIZED FOR PBG TABLESPACE DatabaseName.tableSpaceName.

When partitions are processed individually, FREESPACE can't be added to a full part.

In this case the solution to this problem is to specify +PBGPARTS(IGNORE) parameter to process the PBG Tablespace as a single object, which allows the adding of FREESPACE to a full partition.