A fix is available
APAR status
Closed as program error.
Error description
After a DB2 Data Sharing crash, many inflights were seen with RETAINED locks. A subsequent RESTART LIGHT crashed, as IRLM was modified down and then after finally RESTART completed - data inconsistency errors in abends 04E RC0C90206 in DSNIIDIS ERQUAL5002 were seen, as we now have regressed data.
Local fix
Allow RESTART LIGHT to complete. Additional symptoms: MSGDSNI014I DSNKINSL RC00C90101 ERQUAL500E ABEND04E ABND=04E-00C90101,U=CCEPTM ,M=(N),C=810.DMC DSNILREP,M=DSNTFRCV,LOC=DSNK2DM .DSNKINSL:500E
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 data sharing users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90206 in DSNIIDIS * * ERQUAL5002 after a failed restart * * with INFLIGHT or INABORT units of * * recovery (URs). * **************************************************************** * RECOMMENDATION: * **************************************************************** If DB2 is restarted after an abnormal subsystem termination that left INFLIGHT or INABORT URs and then the restart is cancelled or otherwise abnormally terminated during the backward recovery phase (or AUB phase), data loss may occur in group buffer pool dependent (GBPD) objects that were being updated by the affected units of recovery. If the unit of recovery goes in to postponed abort status, it is NOT subject to this problem. This problem applies to both normal restart and restart with the LIGHT(YES) parameter. This problem does not apply to DB2 subsystems that are not data sharing. Possible symptoms include: ABEND04E RC00C90206 in DSNIIDIS ERQUAL5002 ABEND04E RC00C90101 in DSNKINSL ERQUAL500E MSGDSNI014I
Problem conclusion
DB2 restart processing for INFLIGHT and INABORT URs is changed to recognize the situation where there have been previous restart failures during backward recovery and will do additional processing to ensure all necessary log records are applied until restart is successful.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PK75714
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2008-11-14
Closed date
2008-12-29
Last modified date
2009-02-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK42798 UK42799
Modules/Macros
DSNDRSCA DSNDRURE DSNDRVPL DSNILHIS DSNRPLCS DSNRRAUB DSNRRHSL
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":"8.1","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":"8.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 February 2009