A fix is available
APAR status
Closed as program error.
Error description
DB2 Administration Tool for z/OS during CM RUN does CHECK DATA before REBUILD INDEX/REORG TS when CREATING an INDEX and adding CONSTRAINT(s) at the same time. . Additional info in the RUN job output: msgDSNU204I : . DSNU204I ssid timestamp DSNUGDTC - PAGESET REBUILD PENDING ON INDEX schema.index_name PROHIBITS PROCESSING
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the DB2 Administration Tool for * * z/OS who use Compare to run a POST utility * * sequence when an index is in REBUILD * * PENDING state and the table space is in * * CHECK PENDING state. * **************************************************************** * PROBLEM DESCRIPTION: The Change Management (CM) RUN * * function performs a CHECK DATA * * before executing the REBUILD INDEX / * * REORG TS utilities when creating * * an INDEX and adding CONSTRAINT(s) * * at the same time. An informational * * message DSNU204I / msgDSNU204I * * is observed in the RUN job output: * * * * DSNU204I ssid timestamp * * DSNUGDTC - PAGESET REBUILD * * PENDING ON INDEX schema.index_name * * PROHIBITS PROCESSING * **************************************************************** * RECOMMENDATION: * **************************************************************** After the compare, the changed DDL in the APPLY job or in the Work Statement List (WSL) may cause the DB2 object to be in a different pending state and the post utility sequence will group together/execute the following sequence: 1 - CHECK DATA 2 - REBUILD INDEX 3 - REORG TABLESPACE to remove the pending status. However, when the TABLE SPACE and INDEX are both in REORG PENDING, REBUILD PENDING and CHECK PENDING states, we need to run REORG to first remove the REORG PENDING state, then other post utility statements can be executed successfully. When the TABLE SPACE and INDEX is not in REORG PENDING state (for example, ADVISORY REORG PENDING,m REBUILD PENDING and CHECK PENDING), a REBUILD INDEX, CHECK DATA and REORG TS is needed to remove the pending state. Considering this situation and the post utility statements are grouped together after all changed DDL for all the DB2 objects, the correct post utility sequence should be: 1 - REORG to remove the REORG PENDING state (phase 1 REORG) 2 - REBUILD INDEX 3 - CHECK DATA 4 - REORG for non-REORG (like ADVISORY REORG PENDING) PENDING state (phase 2 REORG)
Problem conclusion
The program has been changed to generate the following POST utility sequence : 1 - REORG to remove the REORG PENDING state(phase 1 reorg) 2 - REBUILD INDEX 3 - CHECK DATA 4 - REORG for non-REORG(like ADVISORY REORG PENDING) PENDING state ( phase 2 reorg )
Temporary fix
Comments
APAR Information
APAR number
PI15389
Reported component name
DB2 ADMIN TOOL
Reported component ID
568851500
Reported release
A20
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-04-07
Closed date
2014-08-27
Last modified date
2014-09-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
ADBGAJOB ADB2ALTJ ADB2CMF ADB2CMP ADB2CMR ADB2CMS ADB2CMT ADB2W1
Fix information
Fixed component name
DB2 ADMIN TOOL
Fixed component ID
568851500
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":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
03 September 2014