|
Problem IC64254
|
Status: Closed |
DB2 CONNECT SEGMENTATION FAULT DURING ODBC CLIENT INITIALIZATION. |
| product: |
DB2 CONNECT / DB2CONNCT / 950 - DB2 |
| Problem description: |
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 Summary: |
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: |
|
| available fix packs: |
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
|
| Solution |
First fixed in DB2 UDB Version 9.5, FixPak 5 (s091123). |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC64395
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.10.2009
18.02.2010
18.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.5
|
 |
