DB2 - Problem description
Problem IC90655 | Status: Closed |
DB2 SERVER TERMINATES ABNORMALLY COMPILING A QUERY WITH EXTENDED INDICATORS ENABLED | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
The DB2 server may terminate abnormally compiling a SQL query with extended indicators enabled. The server stack looks something like the following example from Linux: 0x00002AAAAEFEC892 _Z22sqlnn_rec_req_col_privP9sqlnq_qtbP10sqlnq_auth + 0x07c0 (.../sqllib/lib64/libdb2e.so.1) 0x00002AAAAEFDE0F4 _Z18sqlnn_authdep_listiP9sqlnq_qtbP9sqlnq_qunicb + 0x1a32 (.../sqllib/lib64/libdb2e.so.1) 0x00002AAAAEFDF626 _Z18sqlnn_authdep_listiP9sqlnq_qtbP9sqlnq_qunicb + 0x2f64 (.../sqllib/lib64/libdb2e.so.1) 0x00002AAAAEFDF626 _Z18sqlnn_authdep_listiP9sqlnq_qtbP9sqlnq_qunicb + 0x2f64 (.../sqllib/lib64/libdb2e.so.1) 0x00002AAAAEFDF626 _Z18sqlnn_authdep_listiP9sqlnq_qtbP9sqlnq_qunicb + 0x2f64 (.../sqllib/lib64/libdb2e.so.1) 0x00002AAAAEFD202A _Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq lrr_cmpl_enviiPP9sqlnq_qur + 0x8066 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.1 fix pack 3 * **************************************************************** | |
Local Fix: | |
Disable extended indicators if not required. Note that the DB2 Universal JDBC driver enables extended indicators by default. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 version 10.1 fix pack 3 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC92595 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.03.2013 27.09.2013 27.09.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 |