A fix is available
APAR status
Closed as program error.
Error description
Dump Title: DMP3,ABND=04E-00C90101,U=SYSOPR ,M=N ,C=101.DMC -DSNIB ,M=DSNTFRCV,LOC=DSNIDM .DSNISMCP:5069 Auto GRECP recovery issued ABEND04E RC00C90101 DSNISMCP:5069 because a page was overlaid. _9A64000 00C9C1BC 2C6C1800 0CB21480 00DE0EF4 _9A64010 00007600 04002100 0001C2A0 160B5D5F _9A64020 0A20260A DE6D99BF 70006022 01703200 | _9A641E0 000032C2 2100000F C2A0160B 5D5F0A20 ******** should be 70480400 This overlay was done by a redo of a UTS member cluster space map page's segment allocation log. 0126663FB9DA TYPE( REDO ) URID(0126663E411E) LRSN(C9C1BC2C8FA4) DBID(0E0D) OBID(0002) PAGE(000CB494) SUBTYPE(SEGMENT ALLOCATION/DEALLOCATION) CLR(NO) PROCNAME(DSNISGNS) *LG** 080E0D00 02000CB4 940130C1 BC2C8FA2 4500 0000 000E0007 00914000 00000000 0380000B 000451E0 00000032 C2 **** The offset to the changed data was incorrect and caused the overlay. . UTS member cluster doesn't maintain the segment chain. But mistakenly generated the redo log to update the segment chain although the segment chain hadn't been updated in the segment allocation process. The incorrect redo log may cause a problem during forward recovery.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: DB2 10 for z/OS users of UTS MEMBER CLUSTER * * table spaces. * **************************************************************** * PROBLEM DESCRIPTION: ABND04E RC00C90101 DSNISMCP ERQUAL5069. * * Other symptoms related to storage * * overlays are possible. * **************************************************************** * RECOMMENDATION: * **************************************************************** For table spaces defined as MEMBER CLUSTER, an invalid log record was created for segment chain allocation. For any forward recovery process, this invalid log record can cause overlays in other areas of DB2 storage. For member cluster objects the segment chain is not maintained and so this log record should not have been created in the first place.
Problem conclusion
DB2 code has been corrected to avoid creating the incorrect segment chaining log record for UTS MEMBER CLUSTER objects.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PM71009
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2012-08-16
Closed date
2012-10-02
Last modified date
2012-11-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK82303
Modules/Macros
DSNISGNS
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RA10 PSY UK82303
UP12/10/17 P F210
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":"10.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":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 November 2012