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 IC64254 Status: Geschlossen

DB2 CONNECT SEGMENTATION FAULT DURING ODBC CLIENT
INITIALIZATION.

Produkt:
DB2 CONNECT / DB2CONNCT / 950 - DB2
Problembeschreibung:
DB2 Connect does segmentation fault on ODBC connect 
initialization. 
 
Here is the stack backtrace of the problem: 
 
Program received signal SIGSEGV, Segmentation fault. 
0x000000367b2790a4 in strncpy () from /lib64/libc.so.6 
(gdb) bt 
#0  0x000000367b2790a4 in strncpy () from /lib64/libc.so.6 
#1  0x00002abd0ce66355 in ossStrNCopyInternal () 
   from /opt/ibm/db2/V9.5/lib64/libdb2.so.1 
#2  0x00002abd0d560aba in sqljrAllocTransport () 
   from /opt/ibm/db2/V9.5/lib64/libdb2.so.1 
#3  0x00002abd0d561266 in sqljrAllocAndLinkTransport () 
   from /opt/ibm/db2/V9.5/lib64/libdb2.so.1 
#4  0x00002abd0d562140 in sqljrGetTransport () 
   from /opt/ibm/db2/V9.5/lib64/libdb2.so.1 
#5  0x00002abd0d5622ce in sqljrGetTransportFromPool () 
   from /opt/ibm/db2/V9.5/lib64/libdb2.so.1 
#6  0x00002abd0d563229 in performSingleThreadTests () 
   from /opt/ibm/db2/V9.5/lib64/libdb2.so.1 
#7  0x00002abd0d560953 in main () from 
/opt/ibm/db2/V9.5/lib64/libdb2.so.1 
#8  0x000000367b21d974 in __libc_start_main () from 
/lib64/libc.so.6 
#9  0x000000000040fb19 in _start () 
 
...
Problem-Zusammenfassung:
USERS AFFECTED: 
The users utilizing ODBC on Linux 
 
PROBLEM DESCRIPTION: 
Trap in performSingleThreadTests() when running ODBC application 
on RHEL. 
 
Program received signal SIGSEGV, Segmentation fault. 
0x000000367b2790a4 in strncpy () from /lib64/libc.so.6 
(gdb) bt 
#0  0x000000367b2790a4 in strncpy () from /lib64/libc.so.6 
#1  0x00002abd0ce66355 in ossStrNCopyInternal () 
   from /opt/ibm/db2/V9.5/lib64/libdb2.so.1 
#2  0x00002abd0d560aba in sqljrAllocTransport () 
   from /opt/ibm/db2/V9.5/lib64/libdb2.so.1 
#3  0x00002abd0d561266 in sqljrAllocAndLinkTransport () 
   from /opt/ibm/db2/V9.5/lib64/libdb2.so.1 
#4  0x00002abd0d562140 in sqljrGetTransport () 
   from /opt/ibm/db2/V9.5/lib64/libdb2.so.1 
#5  0x00002abd0d5622ce in sqljrGetTransportFromPool () 
   from /opt/ibm/db2/V9.5/lib64/libdb2.so.1 
#6  0x00002abd0d563229 in performSingleThreadTests () 
   from /opt/ibm/db2/V9.5/lib64/libdb2.so.1 
#7  0x00002abd0d560953 in main () from 
/opt/ibm/db2/V9.5/lib64/libdb2.so.1 
#8  0x000000367b21d974 in __libc_start_main () from 
/lib64/libc.so.6 
#9  0x000000000040fb19 in _start () 
 
PROBLEM SUMMARY: 
As above.
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 UDB Version 9.5, FixPak 5 (s091123).
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC64395 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
30.10.2009
18.02.2010
18.02.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.
Problem behoben lt. FixList in der Version
9.5.0.5 FixList