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

DB2 Windows MESSAGE : ZRC=0X870F0002=-2029060094=SQLO_BPSE "DEBUG
LOGIC ERROR DETECTED" with NO File system cache

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
During some database read/write operations where NO FILE SYSTEM 
CACHING is specified, it is recommended that the data buffers 
used for these operations be sector-aligned. Otherwise, on some 
hardware subsystems, it can result in SQLO_BPSE errors logged in 
the db2diag.log. The DB2 code that handles this situation has a 
problem. Under some timing condition, an unaligned data buffer 
is used for the NO FILE SYSTEM CACHING read/write operation. 
 
db2diag.log: 
 
2013-01-09-17.09.17.160000+060 I1314961F13879       LEVEL: 
Severe 
PID     : 2508                 TID : 3392           PROC : 
db2syscs.exe 
INSTANCE: DB2ADMIN             NODE : 000           DB   : D19 
APPHDL  : 0-69                 APPID: 
fe80::6ca7:e825:7a69:21f2%12.52983.130109160910 
AUTHID  : SAPD19               HOSTNAME: HOST1 
EDUID   : 3392                 EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlbDMSMapAndRead, 
probe:30 
MESSAGE : ZRC=0x870F0002=-2029060094=SQLO_BPSE "Debug logic 
error detected" 
          DIA8501C A buffer pool logic error has occurred. 
DATA #1 : Object descriptor, PD_TYPE_SQLB_OBJECT_DESC, 96 bytes 
    Obj: {pool:2;obj:24;type:3} Parent={2;24}
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows Platforms Only                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 Fixpack 3 or Higher                     * 
****************************************************************
Local Fix:
Enable FILE SYSTEM CACHING may avoid this condition.
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First Fixed in DB2 v10.1 Fixpack 3
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC93357 IC95363 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.02.2013
27.09.2013
27.09.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList