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

DB2 server may stop abnormally with error DBMarkedBad after executing
select statement using distinct keyword.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
DB2 server may stop abnormally with error DBMarkedBad after 
executing select statement using distinct 
keyword. The problem only occurs when the database is created 
using collating sequence "UCA400_LTH". 
 
In db2diag.log we get error messages like below: 
2012-01-09-11.27.52.368733-300 E5358746E614        LEVEL: Severe 
PID     : 21720                TID  : 183333022048 PROC : 
db2sysc 
INSTANCE: xxxxxxxx             NODE : 000          DB   : SBKDB 
APPHDL  : 0-15                 APPID: 
*LOCAL.xxxxxxx.120109162752 
AUTHID  : xxxxxxxx 
EDUID   : 25                   EDUNAME: db2agent (ABCDB) 
FUNCTION: DB2 UDB, sort/list services, 
sqlsBinSortICUsortkeypart, probe:460 
MESSAGE : ZRC=0x870F0031=-2029060047=SQLO_BADS "Bad Address or 
length" 
DATA #1 : <preformatted> 
Error during retrieval of sort key. Input data: 
.......................................... 
UCAInfo: 140 -- 1 
 
2012-01-09-11.27.52.368909-300 I5359361E467        LEVEL: Severe 
PID     : 21720                TID  : 183333022048 PROC : 
db2sysc 
INSTANCE: xxxxxxxx      NODE : 000              DB   : ABCDB 
APPHDL  : 0-15                 APPID: 
*LOCAL.xxxxxxxx.120109162752 
AUTHID  : xxxxxxxx 
EDUID   : 25                   EDUNAME: db2agent (ABCDB) 
FUNCTION: DB2 UDB, sort/list services, sqlsopen, probe:45 
RETCODE : ZRC=0x870F0031=-2029060047=SQLO_BADS "Bad Address or 
length" 
 
 
2012-01-09-11.27.52.796863-300 I5479689E238       LEVEL: Severe 
PID:21720 TID:183333022048 NODE:000 Title: MASTER TIME INFO 
Dump 
File:/home/xxxxxxx/xxxxxxxx/sqllib/db2dump/FODC_DBMarkedBad_2012 
-01-09-11.27.52.787610/21720.25.000.dump.bin 
 
The stack trace back: 
  (/view/db2_v95fp5_linuxamd64_s091123/vbs/INST/lib/libdb2e.so.1 
) 
0x0000002A973725E6 _ZN16sqeLocalDatabase9MarkDBBadEi + 0x017e 
  (/view/db2_v95fp5_linuxamd64_s091123/vbs/INST/lib/libdb2e.so.1 
) 
0x0000002A98A9A822 _Z21sqlrr_rds_common_postP14db2UCinterfaceiil 
+ 0x1684 
  (/view/db2_v95fp5_linuxamd64_s091123/vbs/INST/lib/libdb2e.so.1 
) 
0x0000002A96CA3558 
_Z10sqlrr_openP14db2UCinterfaceP15db2UCCursorInfo + 0x098e 
  (/view/db2_v95fp5_linuxamd64_s091123/vbs/INST/lib/libdb2e.so.1 
) 
0x0000002A969E8118 
_Z16sqljs_ddm_opnqryP14db2UCinterfaceP13sqljDDMObject + 0x015c 
  (/view/db2_v95fp5_linuxamd64_s091123/vbs/INST/lib/libdb2e.so.1 
) 
0x0000002A969DF266 
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U 
Cinterface + 0x03b2 
  (/view/db2_v95fp5_linuxamd64_s091123/vbs/INST/lib/libdb2e.so.1 
) 
0x0000002A969DF5E1 
_Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterface + 0x030d 
 
Following stack will be generated 
 
======================= 
0x0900000000589650 pthread_kill + 0xB0 
0x090000009AFBFBE4 sqloDumpEDU + 0xA4 
0x090000007694AD50 sqle_panic__Fv + 0x90 
0x090000007694AE6C sqle_trap__Fv + 0xC 
0x090000009AEED8B8 sqlzAssertFailedValist + 0x258 
0x090000009AEED984 sqlzAssertFailed + 0x64 
0x09000000BE3F81B8 
bsortGetBytesFirstTime__FP8sqeAgentP10SQLS_SLDESP10SQLS_SORTSPUi 
PUcT4P12SQLS_SORTDEFP10SQLS_KEYFDP18SQLS_BSORT_KEYINFOPdiN211_T4 
sT4T11_P17SQLS_BSORT_UCA_CBN24Pi + 0x1458 
0x09000000BE3F96E8 
bsortGetFirstPartialKey__FP8sqeAgentPUcPUiP10SQLS_SLDESP10SQLS_S 
ORTSiUiT3PiPUl + 0x688 
0x09000000BDC47500 
sqlsBinSort__FP8sqeAgentP10SQLS_SLDESP10SQLS_SORTS + 0xA20 
0x09000000BDC20594 
sqlsUseBinSort__FP8sqeAgentP10SQLS_SLDESP10SQLS_SORTSi + 0x54 
0x09000000BE2AD288 
sqlsopen__FP8sqeAgentiT2P10SQLD_DPREDT2PP8SQLD_CCBPcPUcP12sqlri_ 
vectorPP10SQLD_VALUE + 0x6A8 
0x09000000BC21C09C 
sqlrsopen__FP8sqlrr_cbP9sqlri_taoiT3P10sqlri_iudo + 0x19C 
0x09000000BCB9A764 sqlrisrt__FP8sqlrr_cb + 0x464 
0x09000000BC451C60 sqlriExecThread__FP8sqlrr_cbP12sqlri_opparm + 
0x500 
0x09000000BC4526D0 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 
0x4F0 
0x09000000BCC145B0 
sqlrr_process_fetch_request__FP14db2UCinterface + 0xDF0 
0x09000000BCC1833C 
sqlrr_open__FP14db2UCinterfaceP15db2UCCursorInfo + 0xD9C 
0x090000003DE3E7AC 
sqljs_ddm_opnqry__FP14db2UCinterfaceP13sqljDDMObject + 0x1EC 
0x090000003DDD5C38 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x238 
0x090000003DDD4B54 
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterface + 0x1F4 
0x090000003DDC270C sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 
0x3EC 
0x090000003DDC3D7C 
sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0x15C 
0x090000003DDC9C4C 
sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x2EC 
0x090000003DDCBB64 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0x264 
0x090000007693E8AC RunEDU__8sqeAgentFv + 0x3AC 
0x090000009B1E04D8 EDUDriver__9sqzEDUObjFv + 0x138 
0x090000009B1E06DC sqlzRunEDU__FPcUi + 0x3C 
0x090000009AFC85DC sqloEDUEntry + 0x67Cyes
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.1.1                                           * 
****************************************************************
Local Fix:
Disable Binary Sort by setting db2 registry: 
db2set DB2_BINSORT=false
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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
Upgrade to v10.1.1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
02.01.2013
02.01.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList