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

FAILED ONLINE BACKUP CAN LEAD TO MEMORY CORRUPTION AND TRAP
[SQLBPFCLOSEPARALLELIO()]

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
An online backup using parallelism can lead to memory corruption 
if it fails. 
The corruption can be detected much later as this will actually 
overwrite the 
memory free block header of a block that the archive the freed. 
 
A typical stack would be: 
 
  [0] 0x0900000010556A84 pdLog + 0xF4 
  [1] 0x0900000011F8CDC8 diagnoseMemoryCorruptionAndCrash + 
0x290 
  [2] 0x0900000011F8CA60 
diagnoseMemoryCorruptionAndCrash@glue7F8 + 0x7C 
  [3] 0x090000001036ED44 .MemTreePut.fdpr.clone.45 + 0x10 
  [4] 0x090000001036888C sqlofmblkEx + 0x268 
  [5] 0x0900000012C53454 sqlbpfCloseParallelIO + 0x74 
  [6] 0x0900000012C7471C sqluBMTerm + 0x164 
  [7] 0x09000000119A4708 sqlubbuf + 0x2F8 
  [8] 0x0900000011363F5C sqleSubCoordProcessRequest + 0x1F4 
  [9] 0x090000001082BCA8 RunEDU + 0x1A8 
 
Some possible online backup errors triggering this could be a 
read error 
 
A typical db2diag.log error would be: 
 
  2015-05-27-12.32.36.111563+000 I597141A1347       LEVEL: Error 
  PID     : 14221634             TID  : 74620       PROC : 
db2sysc 0 
  INSTANCE: db2inst              NODE : 000         DB   : 
TESTDB 
  APPHDL  : 0-55915              APPID: LOCAL 
  AUTHID  : PCHADM 
  EDUID   : 74620                EDUNAME: db2bm.72871.0 (PCH) 0 
  FUNCTION: DB2 UDB, oper system services, sqloReadVLow, 
probe:100 
  MESSAGE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does 
not exist" 
            DIA8506C Unexpected end of file was reached.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V9.7 FP 10 and below                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fixpack 11                               * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 V9.7 Fixpack 11
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.06.2015
12.10.2015
12.10.2015
Problem solved at the following versions (IBM BugInfos)
9.7.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.11 FixList