A fix is available
APAR status
Closed as program error.
Error description
The aforementioned abend happened because the -START DATABASE SPACENAM command does not build the recovery range correctly when the starting LRSN of members is older than the group- wise starting LRSN. The starting LRSN of members is older than the group-wise starting LRSN, and the page's PGLOGRBA is 0, with the member's begin RBA being 0. (d157888) There is no known data integrity issue, storage overlay or incorrout associated with this issue. After the abend, GRECP remains on and still protects the object.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 for z/OS 9 or 10 users of database * * GRECP or LPL recovery * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNKUNR2 ERQUAL5007 * * during -START DATABASE SPACENAM command * * GRECP recovery because the command does * * not build the recovery range correctly * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND04E RC00C90101 may occur during the GRECP/LPL recovery process if the member's beginning recovery LRSN (which comes from DB2 checkpoint and is based on the restart point for all objects being modified by that member, across all buffer pools) is older than the group-wide LRSN (which comes from GBP checkpoint) and the member's begin RBA is zero. When these conditions exist, there is a chance that the recovery process will build the recovery range incorrectly. There is no known data integrity issue, storage overlay or incorrout associated with this issue. After the abend, GRECP remains on and still protects the object.
Problem conclusion
The group-wide beginning recovery LRSN will be used as the member's beginning recovery LRSN if the member's begin RBA is zero.
Temporary fix
Comments
APAR Information
APAR number
PM62272
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-04-11
Closed date
2012-06-01
Last modified date
2012-07-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK79293 UK79294
Modules/Macros
DSNISREC
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":"9.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":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 July 2012