DFS3286W REORG# NOT FOUND FOR PARTITION yyyyyyy

Explanation

The reorganization number for a HALDB partition cannot be determined during reload when new records have been moved into the partition. The reorganization number from the primary data set and the RECON cannot be determined or are null.

When IMS is unable to determine the correct reorganization number during reload, it is possible that the reorganization number has been set incorrectly for this partition. An incorrect reorganization number can cause failures during resolution of the indirect pointers for segments involved in a logical relationship or the target of a secondary index or both. This failure can cause IMS to follow a bad pointer and cause a data integrity failure.

System action

The reorganization number was set in the data set using the reorganization number of the first record loaded into the partition.

System programmer response

If the database does not have any logical relationships or secondary index databases, then no action is required.

If the database has logical relationships or a secondary index target, then determine if the reorganization number was regressed. Follow these steps to determine if the number was regressed:
  1. Determine the key of the first record in the partition after reload.
  2. Determine the reorganization number for the partition of the first record before reload.
  3. Determine the reorganization number for the partition of the first record after reload.
If the reorganization number after reload is less than or equal to the reorganization number before reload, a data integrity failure might occur. To prevent a data integrity failure take the following steps:
  1. Reverse the changes in the partition boundaries, restoring the partitions to their original partitions.
  2. Enable the reorganization number verification function. You can do this using the DBRC CHANGE.RECON REORGV command.
  3. Set the reorganization number in the RECON, by making updates to the partition or by executing the HD Unload utility.
  4. Redo the changes to the partition boundaries.
Attention: If you cannot enable reorganization number verification, then IMS can prevent the regression of the reorganization number during reload as long as the primary database data set is not scratched and reallocated, or the partition is not reinitialized to empty.

Module

DFSPSEL0