home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC65891 Status: Closed

"Large dynamic increases in bufferpool memory can result in DB2
instance crash when the memory is release"

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
The problem occurs  starting with  V95FP5. 
 
Error seen in db2diag.log 
 
2010-01-07-14.39.12.015860-300 I249780A485        LEVEL: Severe 
PID     : 258224               TID  : 2068        PROC : db2sysc 
INSTANCE: inst1                NODE : 000         DB   : SAMPLE 
APPHDL  : 0-144                APPID: *LOCAL.inst1.100107193854 
AUTHID  : INST1 
 
EDUID   : 2068                 EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, SQO Memory Management, sqloFreeMemChunks, 
probe:40 
DATA #1 : <preformatted> 
Could not find ChunkGroup for address: 0000000000000000 
 
 
Stack Generated 
 
 
Signal #11 
 
sqloCrashOnCriticalMemoryValidationFailure 
sqloFreeMemChunks 
sqlbFreeAllPageAndBPDMem 
sqlbFreeAllPageAndBPDMem 
sqlbAllocPageAndBPDMemForNewBP 
sqlbInitBufferPool 
SQLB_BUFFERPOOL 
sqlbCreateUncommittedBPRuntime 
sqlbCreateBufferPool 
sqlrlcbp 
sqlnq_create_bufferpool_end 
sqlnq_create_bufferpool_stmt 
sqlnp_smactn 
sqlnp_parser 
sqlnp_main
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* First appears in v9.5 Fixpack 5                              * 
*                                                              * 
* Occurs when adding a large  bufferpool  during a  single     * 
* database activation                                          * 
*                                                              * 
* Error seen in db2diag.log                                    * 
*                                                              * 
* 2010-01-07-14.39.12.015860-300 I249780A485        LEVEL:     * 
* Severe                                                       * 
* PID     : 258224               TID  : 2068        PROC :     * 
* db2sysc 0                                                    * 
* INSTANCE: inst1                NODE : 000         DB   :     * 
* SAMPLE                                                       * 
* APPHDL  : 0-144                APPID:                        * 
* *LOCAL.inst1.100107193854                                    * 
* AUTHID  : INST1                                              * 
* EDUID   : 2068                 EDUNAME: db2agent (SAMPLE) 0  * 
* FUNCTION: DB2 UDB, SQO Memory Management, sqloFreeMemChunks, * 
* probe:40                                                     * 
* DATA #1 : <preformatted>                                     * 
* Could not find ChunkGroup for address: 0000000000000000      * 
*                                                              * 
* Stack will be generated like the following:                  * 
*                                                              * 
*                                                              * 
* DB2 build information: DB2 v9.5.0.5 s091123 SQL09055         * 
* timestamp: 2010-01-07-14.39.12.018855                        * 
* instance name: db2inst1                                      * 
* EDU name     : db2agent (SAMPLE) 0                           * 
* EDU ID       : 2068                                          * 
* Signal #11                                                   * 
* uname: S:AIX R:3 V:5 M:002B02ED4C00 N:efkxdb2121pc           * 
* ...                                                          * 
* ...                                                          * 
* ...                                                          * 
*                                                              * 
* -------Frame------ ------Function + Offset------             * 
*                                                              * 
* 0x0900000003E61E80                                           * 
* sqloCrashOnCriticalMemoryValidationFailure                   * 
* 0x0900000003E65A14                                           * 
* sqloCrashOnCriticalMemoryValidationFailure                   * 
* 0x09000000030D86C8 sqloFreeMemChunks                         * 
* 0x09000000032E8970 sqlbFreeAllPageAndBPDMem                  * 
* 0x090000000387A8B4 sqlbFreeAllPageAndBPDMem                  * 
* 0x09000000046687A8 sqlbAllocPageAndBPDMemForNewBP            * 
* 0x09000000031DB798 sqlbInitBufferPool                        * 
* 0x090000000636CC70 sqlbCreateUncommittedBPRuntime            * 
* 0x0900000004CF2EE4 sqlbCreateBufferPool                      * 
* 0x0900000004D4E450 sqlrlcbp                                  * 
* 0x0900000004D4DE20 sqlnq_create_bufferpool_end               * 
* 0x0900000004D4DC84 sqlnq_create_bufferpool_stmt              * 
* 0x0900000003276BDC sqlnp_smactn                              * 
* 0x090000000327729C sqlnp_parser                              * 
* 0x090000000321C088 sqlnp_main                                * 
*                                                              * 
*                                                              * 
*                                                              * 
* Workaround                                                   * 
* Create initial bufferpool with using a smaller size          * 
* Deactivate and then reactivate the database.                 * 
* Then alter bufferpool  to increase the size.                 * 
*                                                              * 
* example:                                                     * 
* db2 CREATE BUFFERPOOL "BP1"  SIZE 500000 PAGESIZE 8192       * 
* db2 connect reset                                            * 
*                                                              * 
* The database should be  deactivated and activated again.     * 
*                                                              * 
* Then we recalculate the db memory set requirements and the   * 
* bufferpool can  be increased.                                * 
* For example                                                  * 
* db2 connect to sample                                        * 
* db2 alter bufferpool "BP1" SIZE 1000000                      * 
* db2 connect reset                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.5 Fixpack 6                                    * 
****************************************************************
Local Fix:
Workaround: 
Avoid dynamic large increases in bufferpool memory during a 
single database activation 
If bufferpool memory needs to be added or increased,  fix 
database memory to a higher value before the database is 
activated.
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Fixed contained in V9.5 Fixpack 6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.01.2010
19.10.2010
24.03.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)