|
Problem IC95297
|
Status: Closed |
DB2 TRAPPED WITH SIGSEGV IN SQLTGETS |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
DB2 trapped with SIGSEGV in sqltgets and the following stacks:
0 ossDumpStackTraceInternal
1 ossDumpStackTraceV98
2 OSSTrapFile::dumpEx
3 sqlo_trce
4 sqloEDUCodeTrapHandler
5 __PRETTY_FUNCTION__.6770
6 sqltgets
7 pdCollectPDContext
8 pdLogInternal
9 pdLog
10 sqlucPdLog
11 sqluCFormatter::iCleanUp
12 sqluLoadEDUDriver
13 sqloEDUEntry
14 pthread_timedjoin_np
15 clone
Typical error records seen in db2diag.log:
2013-03-28-11.05.44.508685-300 E78810243E593 LEVEL:
Severe
PID : 67394 TID : 46912765945600 PROC :
db2wdog 32 [db2admn]
INSTANCE: db2admn NODE : 032
HOSTNAME: br95db66
EDUID : 2 EDUNAME: db2wdog 32 [db2admn]
FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog, probe:20
MESSAGE : ADM0503C An unexpected internal processing error has
occurred. All
DB2 processes associated with this instance have been
shutdown.
Diagnostic information has been recorded. Contact IBM
Support for
further assistance.
2013-03-28-11.05.52.370368-300 E78810837E469 LEVEL:
Error
PID : 67394 TID : 46912765945600 PROC :
db2wdog 32 [db2admn]
INSTANCE: db2admn NODE : 032
HOSTNAME: br95db66
EDUID : 2 EDUNAME: db2wdog 32 [db2admn]
FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog, probe:8089
DATA #1 : Process ID, 4 bytes
67441
DATA #2 : Hexdump, 8 bytes
0x00002AAABABFD240 : 0101 0000 0B00 0000
........ |
| Problem Summary: |
DB2 TRAPPED WITH SIGSEGV IN SQLTGETS |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.08.2013
31.03.2014
31.03.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
