|
Problem IC80732
|
Status: Geschlossen |
DB2 SHUTS DOWN AFTER EXECUTING SELECT STATMENT USING DISTINCT KE YWORD,WHEN THE DATABASE IS CREATED USING COLLATING SEQUENCE "UCA |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
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 |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v9.7.6 *
**************************************************************** |
| Local-Fix: |
Disable Binary Sort by setting db2 registry:
db2set DB2_BINSORT=false |
| verfügbare FixPacks: |
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
|
| Lösung |
Upgrade to v9.7.6 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 09.01.2012
17.07.2012
17.07.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.6
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.6
|
 |
