home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC62284 Status: Geschlossen

INSTANCE CRASHES WITH SIGNAL #11 (SIGSEGV) WHEN A PARAMETER OF TYPE
"C STRING" CONTAINS INVALID DATA.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Instance crashes with Signal #11 (SIGSEGV) when a parameter of 
type "C string" contains invalid data. 
 
For example, if ValueType is SQL_C_CHAR, SQL_C_DBCHAR or 
SQL_C_WCHAR and the string size of the C string pointed to by 
ParametervaluePtr is greater than ColumnSize in 
SQLBindParameter() api parameters, this error will be triggered. 
 
The failing stack looks similar to the following: 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x000000000000F524 ?unknown + 0x0 
0x09000000032B5F44 sqlribniCbDrda__FP14db2UCinterface - 0x200 
0x09000000032B55DC sqlribni__FP8sqlrr_cb + 0x100 
0x0900000003502898 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 
0x14 
0x090000000311C8C8 
@64@sqlrr_process_open_request__FP8sqlrr_cbPUlT2P15db2UCCursorIn 
fo + 0x84 
0x09000000034E94CC 
sqlrr_open__FP14db2UCinterfaceP15db2UCCursorInfo + 0x3C 
0x09000000036AB5A4 
sqljs_ddm_opnqry__FP14db2UCinterfaceP14sqljsDDMObject - 0x148 
0x0900000003260964 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP14sqljsDDMObjectP14db2U 
Cinterface + 0x4 
0x090000000325898C 
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterface + 0x274
Problem-Zusammenfassung:
INSTANCE CRASHES WITH SIGNAL #11 (SIGSEGV) WHEN A PARAMETER OF 
TYPE "C STRING" CONTAINS INVALID DATA.
Local-Fix:
N/A
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 V9.7 Fixpak 1
Workaround
N/A
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
30.07.2009
04.01.2010
04.01.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version
9.7.0.1 FixList