A fix is available
APAR status
Closed as program error.
Error description
After a power outage, and DB2 abend, there were a vast number of table spaces with exception states. A subsequent DB2 start failed with rc00c90303 and abend04e rc00e20004 in dsnsvbk +718 , with caller of dsnsvbk as dsnidbae ( DBET ). It appeared that a storage pool used by DBET had reached its maximum expansion size . The pool was ACOMPH12 . . Example of messages in syslog: DSNV086E +PR11 DB2 ABNORMAL TERMINATION REASON=00C90303 ... IEA794I SVC DUMP HAS CAPTURED: DUMPID=027 REQUESTED BY JOB (DSNMSTR) DUMP TITLE=DSN ,ABND=04E-00E20004,U=SYSOPR ,M=N ,C=101.DMC - DSNIDBAB,M=DSNTFRCV,LOC=DSNIDBAE.DSNSVBK +0718
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * **************************************************************** * PROBLEM DESCRIPTION: DB2 encountered RC00C90303 then * * followed by RC00E20004 in DSNSVBK+0718 * * with caller DSNIDBAE during DB2 restart * * when a very large number of objects * * were in an exception state. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 was not able to come up because it was encountering a storage shortage due to numerous DBET blocks being allocated. Investigation showed that there was fragmentation in the storage such that storage manager was not able to compact the free storage when it detected that there was shortage in storage. Allocated DBET blocks were around 22K but the pool expansion size was only 44K. In this case, only one DBET block could fit in an expansion segment, wasting over 21K per allocated block. This can result in fragmentation in storage since during DB2 restart DBET is one of the few components using this pool.
Problem conclusion
DB2 was modified to increase the expansion size of the the pool where DBET blocks are located.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PM74421
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-10-05
Closed date
2012-11-16
Last modified date
2013-01-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK83620 UK83621
Modules/Macros
DSNTSTRT
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":"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:
02 January 2013