A fix is available
APAR status
Closed as program error.
Error description
When some rows of a range partitioned table space reside in the wrong partition, it is possible that a reorg may issue multiple MSGDSNU393I messages for the same partition during the SORTBLD PHASE: DSNU393I DSNURBXA - SORTBLD PHASE STATISTICS - NUMBER OF KEYS=nnnn FOR INDEX db1.ix1 PART 1 DSNU393I DSNURBXA - SORTBLD PHASE STATISTICS - NUMBER OF KEYS=nnnn FOR INDEX db1.ix1 PART 2 DSNU393I DSNURBXA - SORTBLD PHASE STATISTICS - NUMBER OF KEYS=mmmm FOR INDEX db1.ix1 PART 1 Normally REORG does not move the rows to the appropriate partition unless a rebalance of some kind has been requested, and the reorg would end with rc 0. This apar will allow REORG to issue a warning message and end with RC 4 when out of order keys are detected.
Local fix
run REORG REBALANCE, including the impacted partitions
Problem summary
**************************************************************** * USERS AFFECTED: All Db2 11 for z/OS and Db2 12 for z/OS * * users of REORG utility. * **************************************************************** * PROBLEM DESCRIPTION: Multiple MSGDSNU393I messages were * * issued for the same partition of a * * partitioned index during SORTBLD * * phase of the REORG utility. * **************************************************************** * RECOMMENDATION: Apply PTF when available. * **************************************************************** User ran a REORG TABLESPACE utility against a partitioned table space with one or more partitioned indexes defined. The utility completed successfully, but it was noticed that more than one DSNU393I - SORTBLD PHASE STATISTICS - NUMBER OF KEYS=n messages were issued for the same partition of a partitioned index, interleaving with other DSNU393I messages for different partitions of the same index. The reported problem is caused by broken data where one or more data records are placed in the wrong partition before the start of the REORG execution. Although REORG is able to rebuild the partitioned index consistent with the broken data layout and completes successfully despite the multiple MSGDSNU393I messages, user is unaware of the existing data integrity issue due to REORG completion with an overall return code of 0.
Problem conclusion
Code has been modified for REORG to issue a new warning message MSGDSNU2930I to indicate out of partition sequence keys are detected when building a partitioned index. This new message is issued in addition to the existing DSNU393I messages which are not changed by this APAR. The Message guide will be updated with the following: DSNU2930I csect-name - OUT OF PARTITION SEQUENCE KEYS DETECTED FOR INDEX creator-name.index-name Explanation The utility detected out of order keys were being processed for the specified index. This condition can be caused by internal program logic error, or due to pre-existing data- corruption on the objects before the utility execution. You are being alerted because having out of order keys that are not in partition order can result in sub-optimal utility performance, and possibly data corruption that cannot be resolved by utility execution. csect-name The name of the control section that issued the message. creator-name.index-name The name of the index, identified by the name of its creator. System action: Utility processing continues. User response: Run the CHECK INDEX utility to validate the integrity of the rebuilt index. If you suspect an internal Db2 sort issue, contact IBM support with utility job output. Severity 4 (warning)
Temporary fix
Comments
APAR Information
APAR number
PI88906
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-10-16
Closed date
2019-04-02
Last modified date
2019-05-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI62291 UI62292
Modules/Macros
DSNFUDIR DSNFUDRE DSNUMSGE DSNURBXA
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 May 2019