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 IC81333 Status: Closed

A RESTORE DATABASE WILL TRAP IF DB2PFCHR CAN NOT ALLOCATE MEMORY IN
SQBPREFETCHEREDU::RUNEDUINIT

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
During a database restore, db2pfchr will trap if db2pfchr can 
not allocate memory. 
 
A sample of db2diag.log: 
2011-12-14-19.43.58.422992+540 I65492709A439      LEVEL: Severe 
PID     : 8847514              TID  : 54743       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 54743                EDUNAME: db2pfchr (SAMPLE) 0 
FUNCTION: DB2 UDB, buffer pool services, 
sqbPrefetcherEdu::RunEDUInit, probe:7625 
MESSAGE : ZRC=0x8B0F0000=-1961951232=SQLO_NOMEM "No Memory 
Available" 
          DIA8300C A memory heap error has occurred. 
 
... FODC will occur ... 
 
2011-12-14-19.44.35.254612+540 E66395480A1142     LEVEL: 
Critical 
PID     : 8847514              TID  : 54743       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 54743                EDUNAME: db2pfchr (SAMPLE) 0 
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, 
probe:90 
MESSAGE : ADM14011C  A critical failure has caused the following 
type of error: 
          "Trap". The DB2 database manager cannot recover from 
the failure. 
          First Occurrence Data Capture (FODC) was invoked in 
the following 
          mode: "Automatic". FODC diagnostic information is 
located in the 
          following directory: 
 
"/home/db2inst1/sqllib/db2dump/FODC_Trap_2011-12-14-19.43.58.424 
833_0000/" 
 
A snippet of the stack trace: 
term + 0x14 
sqloTermEDUWaitPost + 0xC 
sqlpTermAgent + 0x15C 
sqbPrefetcherEdu::RunEDUTerm + 0x40 
EDUDriver + 0x308 
sqloEDUEntry + 0x264 
sqlzRunEDU + 0x24
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* During a database restore, db2pfchr will trap if db2pfchr    * 
* can not allocate memory.                                     * 
*                                                              * 
* A sample of db2diag.log:                                     * 
* 2011-12-14-19.43.58.422992+540 I65492709A439      LEVEL:     * 
* Severe                                                       * 
* PID    : 8847514              TID  : 54743      PROC :       * 
* db2sysc 0                                                    * 
* INSTANCE: db2inst1            NODE : 000                     * 
* EDUID  : 54743                EDUNAME: db2pfchr (SAMPLE) 0   * 
* FUNCTION: DB2 UDB, buffer pool                               * 
* services,sqbPrefetcherEdu::RunEDUInit, probe:7625            * 
* MESSAGE : ZRC=0x8B0F0000=-1961951232=SQLO_NOMEM "No Memory   * 
* Available"                                                   * 
*           DIA8300C A memory heap error has occurred.         * 
*                                                              * 
* ... FODC will occur ...                                      * 
*                                                              * 
* 2011-12-14-19.44.35.254612+540 E66395480A1142    LEVEL:      * 
* Critical                                                     * 
* PID    : 8847514              TID  : 54743      PROC :       * 
* db2sysc 0                                                    * 
* INSTANCE: db2inst1            NODE : 000                     * 
* EDUID  : 54743                EDUNAME: db2pfchr (SAMPLE) 0   * 
* FUNCTION: DB2 UDB, oper system services,                     * 
* sqloEDUCodeTrapHandler, probe:90                             * 
* MESSAGE : ADM14011C  A critical failure has caused the       * 
* following type of error:                                     * 
*           "Trap". The DB2 database manager cannot recover    * 
* from the failure.                                            * 
*           First Occurrence Data Capture (FODC) was invoked   * 
* in the following                                             * 
*           mode: "Automatic". FODC diagnostic information is  * 
* located in the                                               * 
*           following directory:                               * 
*                                                              * 
* "/home/db2inst1/sqllib/db2dump/FODC_Trap_2011-12-14-19.43.58 * 
* .424833_0000/"                                               * 
*                                                              * 
* A snippet of the stack trace:                                * 
* term + 0x14                                                  * 
* sqloTermEDUWaitPost + 0xC                                    * 
* sqlpTermAgent + 0x15C                                        * 
* sqbPrefetcherEdu::RunEDUTerm + 0x40                          * 
* EDUDriver + 0x308                                            * 
* sqloEDUEntry + 0x264                                         * 
* sqlzRunEDU + 0x24                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.7 fixpack 6.                    * 
****************************************************************
Local Fix:
Before the restore, pre-create the database using the same 
database name as during the restore, then restore into this 
existing database.
available fix packs:
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 9.7 FixPack 6.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.02.2012
05.06.2012
05.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList