|
Problem IT19631
|
Status: Closed |
QUERY EXECUTION CAUSES DB2 SERVER TO TERMINATE ABNORMALLY |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
In rare circumstances, executing a SQL query may cause the DB2
server to terminate abnormally. The stack looks similar to this
example from Linux:
0x00007FB7ED415CE6
_Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm +
0x0356
0x00007FB7ED41592B ossDumpStackTraceV98 + 0x002b
0x00007FB7ED411AD7 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm +
0x00d7
0x00007FB7F49729F7 sqlo_trce + 0x03c7
0x00007FB7F4ACE729 sqloEDUCodeTrapHandler + 0x03a9
0x00007FB7FBC1C850 address: 0x00007FB7FBC1C850 ; dladdress:
0x00007FB7FBC0D000 ; offset in lib: 0x000000000000F850 ;
0x00007FB7F56BD075 _Z18sqlri_posstr_shortP8sqlrr_cb + 0x0095
0x00007FB7F57086CF _Z16sqlriComputeOnceP8sqlrr_cb + 0x007f
0x00007FB7F568FBF8 _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm
+ 0x04f8
0x00007FB7F50CB0C6 _Z19sqlriExecOpenThreadP8sqlrr_cb + 0x0026 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 11.1.2.2 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 version 11.1.2.2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.03.2017
26.06.2017
26.06.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
