|
Problem IC64165
|
Status: Closed |
SEGMENTATION FAULT IN SQLEUAPPLICATIONINIT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Call to sqlfusys API caused sqgmentaion fault in
sqleuApplicationInit on the client. The client trap can happen
only if application is mixing connection and instance
attachment.
Stack Traceback:
Segmentation fault in sqleuApplicationInit.fdpr.chunk.1 at
0x900000002c04064 ($t1)
0x900000002c04064 (sqleuApplicationInit.fdpr.chunk.1+0x8c)
e8c60000 ld r6,0x0(r6)
(dbx) where
sqleuApplicationInit.fdpr.chunk.1(??, ??, ??) at
0x900000002c04064
sqleMappingFnClient__FP14db2UCinterfaceP5sqlca(??, ??) at
0x900000003304180
sqleMappingFnClient__FP14db2UCinterfaceP5sqlca@glue4A5(??, ??)
at 0x900000002917058
sqleriar.fdpr.chunk.3__FP12SQLE_DB2RA_T(??) at
0x900000002c01c9cdb2CfgCall.fdpr.chunk.3__FUiPvP5sqlcaT1(??, ??,
??, ??) at 0x9000000032a7b54
db2CfgSet(??, ??, ??) at 0x9000000032a7430
sqlfusys(??, ??, ??) at 0x90000000317f7c8 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* Call to sqlfusys API caused sqgmentaion fault *
* insqleuApplicationInit on the client. The client trap *
* canhappenonly if application is mixing connection and *
* instanceattachment.Stack Traceback:Segmentation fault in *
* sqleuApplicationInit.fdpr.chunk.1 at0x900000002c04064 *
* ($t1)0x900000002c04064 *
* (sqleuApplicationInit.fdpr.chunk.1+0x8c)e8c60000 ld *
* r6,0x0(r6)(dbx) wheresqleuApplicationInit.fdpr.chunk.1(??, *
* ??, ??) *
* at0x900000002c04064sqleMappingFnClient__FP14db2UCinterfaceP5sq
* ??) *
* at0x900000003304180sqleMappingFnClient__FP14db2UCinterfaceP5sq
* 0x900000002917058sqleriar.fdpr.chunk.3__FP12SQLE_DB2RA_T(??) *
* at0x900000002c01c9cdb2CfgCall.fdpr.chunk.3__FUiPvP5sqlcaT1(??,
* ??) at 0x9000000032a7b54db2CfgSet(??, ??, ??) at *
* 0x9000000032a7430sqlfusys(??, ??, ??) at 0x90000000317f7c8 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V97.2 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.10.2009
25.05.2010
25.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
