|
Problem IC65076
|
Status: Closed |
HITTING INSTANCE MEMORY LIMIT SHOULD NOT BRING DOWN THE DATABASE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Instance Memory limits are not intended to be enforced where
enforcing the limit would result in bringing down the database
i.e. "database marked bad". However, currently, Instance Memory
allocation failures in the deadlock detector and global deadlock
detector will have this effect.
Connections will be forced off, and the database will be
recycled requiring crash recovery.
This APAR will allow allocations from these EDUs to exceed the
Instance Memory limit. Note that memory allocation failures due
to other reasons (eg. Operating System limits) will still cause
the database to be recycled.
db2diag.log entries include:
2009-11-30-10.40.52.636927-360 I5534792E511 LEVEL: Error
PID : 16939 TID : 183307856224 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
EDUID : 30 EDUNAME: db2dlock (SAMPLE) 0
FUNCTION: DB2 UDB, lock manager, sqlpldl, probe:815
MESSAGE : Not able to allocate memory for ldd matrix from db
shared heap. total
matrix size:
DATA #1 : Hexdump, 8 bytes
0x0000002AADFFDD20 : 00B0 4000 0000 0000
..@.....
2009-11-30-10.40.52.637028-360 I5535304E444 LEVEL: Error
PID : 16939 TID : 183307856224 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
EDUID : 30 EDUNAME: db2dlock (SAMPLE) 0
FUNCTION: DB2 UDB, lock manager, sqlpldl, probe:815
MESSAGE : Dead Lock Detector error:
DATA #1 : Hexdump, 8 bytes
0x0000002AADFFDDE8 : 7700 1080 0200 0F8B
w....... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Systems with an enforced Instance Memory limit *
****************************************************************
* PROBLEM DESCRIPTION: *
* See error description *
****************************************************************
* RECOMMENDATION: *
* Increase Instance Memory limit or reduce DB2's *
* memoryrequirements *
**************************************************************** |
| Local Fix: |
Consider using the AUTOMATIC setting for Instance Memory or
increasing the Instance Memory limit |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in DB2 Version 9.7 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.12.2009
14.06.2010
14.06.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
