|
Problem IC63968
|
Status: Closed |
DB2 crash with SIGSEGV in sqlnq_qtbqunchild2 or sqlnq_qtboprparent2 |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
DB2 instance abend with SIGSEGV (signal 11) in either
sqlnq_qtbqunchild2 or sqlnq_qtboprparent2 function during query
processing.
Here are some examples of the SIGSEGV traps -
Example #1 -
_ZN17sqlnq_qtbqunchild2ppEv
_Z17sqlnr_sop_fix_hxpP9sqlnq_oprPiP3loc
_Z21sqlnr_setophxp_actionP10sqlnr_qrwaPiP14sqlnr_progress
_Z10sqlnr_compPiiP16sqlnr_rule_stateP10sqlnr_qrwaP14sqlnr_progre
ss
_Z9sqlnr_seqPiP10sqlnr_qrwaP14sqlnr_progressP12sqlnr_rclass
...
Example #2 -
_ZN18sqlnq_qtboprparent2opEv
_Z17sqlnr_sop_fix_hxpP9sqlnq_oprPiP3loc
_Z21sqlnr_setophxp_actionP10sqlnr_qrwaPiP14sqlnr_progress
_Z10sqlnr_compPiiP16sqlnr_rule_stateP10sqlnr_qrwaP14sqlnr_progre
ss
_Z9sqlnr_seqPiP10sqlnr_qrwaP14sqlnr_progressP12sqlnr_rclass
... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* DB2 instance abend with SIGSEGV (signal 11) in either *
* *
* sqlnq_qtbqunchild2 or sqlnq_qtboprparent2 function during *
* query *
* processing. *
* *
* *
* *
* Here are some examples of the SIGSEGV traps - *
* *
* *
* *
* Example #1 - *
* *
* *
* *
* _ZN17sqlnq_qtbqunchild2ppEv *
* *
* _Z17sqlnr_sop_fix_hxpP9sqlnq_oprPiP3loc *
* *
* _Z21sqlnr_setophxp_actionP10sqlnr_qrwaPiP14sqlnr_progress *
* *
* _Z10sqlnr_compPiiP16sqlnr_rule_stateP10sqlnr_qrwaP14sqlnr_prog
* ss *
* *
* _Z9sqlnr_seqPiP10sqlnr_qrwaP14sqlnr_progressP12sqlnr_rclass *
* *
* ... *
* *
* *
* *
* Example #2 - *
* *
* *
* *
* _ZN18sqlnq_qtboprparent2opEv *
* *
* _Z17sqlnr_sop_fix_hxpP9sqlnq_oprPiP3loc *
* *
* _Z21sqlnr_setophxp_actionP10sqlnr_qrwaPiP14sqlnr_progress *
* *
* _Z10sqlnr_compPiiP16sqlnr_rule_stateP10sqlnr_qrwaP14sqlnr_prog
* ss *
* *
* _Z9sqlnr_seqPiP10sqlnr_qrwaP14sqlnr_progressP12sqlnr_rclass *
* *
* ... *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.7 fix pack 1 *
**************************************************************** |
| Local Fix: |
n/a |
| available fix packs: |
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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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
|
| Solution |
Fixed in DB2 version 9.7 fix pack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.10.2009
17.02.2010
17.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
