A fix is available
APAR status
Closed as program error.
Error description
ABEND04E RC00C90101 in DSNIDBMF ERQUAL5016 was caused by orphaned UTxx state in DBET, and there was no utility running and no SYSUTILX record to match. (d144872)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 for z/OS users of data sharing who * * perform group restart to build SCA * **************************************************************** * PROBLEM DESCRIPTION: A restrictive state (e.g. RECP, RBDP, * * REORGP, UTUT, UTRO or other) coming * * back after group restart even though * * it should not be on (it has already * * been reset) * **************************************************************** * RECOMMENDATION: * **************************************************************** The following was the scenario encountered (in two-way data sharing in this example). The scenario involves the UTUT state but the problem could happen with any state. 1. Member B turned on the UTUT state. 2. Member A took a checkpoint that contained the UTUT state. 3. Member B turned off the UTUT state. 4. Member B took a checkpoint. 5. Group restart occurred with member A going back to the checkpoint from Step 2. Then member A did the restart for its peer member B with its log apply beginning with the checkpoint from Step 4. 6. When member A was performing its DBET rectify at the beginning of the forward log recovery, it reset the UTUT state because the UTUT's time stamp was earlier than the DBET RBA stored in the local DBET. However, the group DBET SCA was not updated to reflect the change. 7. DB2 came up for member A (correctly - without the UTUT state). 8. DB2 came up for member B - on this member, the UTUT state was now back on for the object by mistake (the state got picked up grom the group DBET SCA). 9. After a subsequent (regular) restart of member A, the UTUT state came back for member A as well (the state got picked up from the group DBET in SCA).
Problem conclusion
DB2 code has been modified such that when the DBET RBA time stamp of local DBET is later than the time stamp of a local DBET entry during DBET rectify, the exception state from the entry gets reset in group DBET in SCA as well, not just in local DBET.
Temporary fix
Comments
ž**** PE12/11/15 FIX IN ERROR. SEE APAR PM77066 FOR DESCRIPTION
APAR Information
APAR number
PM53155
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
2011-11-29
Closed date
2012-03-26
Last modified date
2013-01-31
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK77362 UK77363 UK77364
Modules/Macros
DSNIDBNI
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RA10 PSY UK77362
UP12/04/12 P F204
R810 PSY UK77363
UP12/04/12 P F204
R910 PSY UK77364
UP12/04/12 P F204
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:
31 January 2013