A fix is available
APAR status
Closed as program error.
Error description
1. Object was DSN1COPY+RESET 2. Dictionary from DSN1COPY was created before BSDS's converted to 10 bytes. so it still used the old 6 bytes field to hold the dictionary's version(LRSN) 3. This dictionary from DSN1COPY was populated to CDDS by REORG INITCDDS or REORG KEEPDICTIONARY 4. On current system, BSDS's been converted to 10 bytes. so all new dictionary generated would use the new 10 bytes field to hold the dictionary's version(LRSN). When above conditions are satisfied, As long as the old dictionary from DSN1COPY was populated to CDDS, DB2 would fail to insert any new dictionary generated by LOAD/REORG.
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All Db2 11 for z/OS users who use the GDPS * * Continuous Availability (Active Active) * * solution * **************************************************************** * PROBLEM DESCRIPTION: REORG failed to insert dictionary of a * * DSN1COPY'ed page set into the CDDS * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** User had a Db2 subsystem setup with the GDPS Continuous Availability Active Active 2.0 function. A compressed table space with CDC table was DSN1COPYed, converted to extended page format, and then restored with the DSN1COPY created prior to the extended page format conversion. A REORG TABLESPACE was then run against this object, which completed successfully, but it was noticed that the compression dictionary of the DSN1COPY-restored page set was never inserted into the Compression Dictionary Data Set (CDDS). This problem was caused by incorrect program logic where REORG erroneously determined that the dictionary already exists in the CDDS due to the zeroed dictionary timestamp after DSN1COPY usage.
Problem conclusion
Code has been modified to correctly compare the dictionary timestamp of a DSN1COPY restored page set during LOAD and REORG CDDS handling.
Temporary fix
Comments
APAR Information
APAR number
PI93693
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
2018-02-12
Closed date
2018-04-19
Last modified date
2018-06-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI55727
Modules/Macros
DSNIDCSF DSNPDLT1 DSNURPDC DSNUZLCR
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RB10 PSY UI55727
UP18/05/29 P F805
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:
04 June 2018