|
Problem IT22199
|
Status: Closed |
POSSIBLE TRAP IN SQLNGSECTALLOCATEINTERNAL() WHEN RUNNING LARGE AND COMPLEX QUERIES
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
It is possible to trap (SEGV) in sqlngSectAllocateInternal()
when running a large and complex query.
This case for example was a SELECT statement of 200K containing
around 2100 UNIONs.
The top of the stack will show up like this:
0x0900000038C351D8 sqlngSectAllocateInternall + 0x818
0x0900000038C3D41C sqlngSectLinearize + 0x59C
0x090000003C48754C sqlng_main + 0x358C
0x090000003AD76794 sqlnn_cmpl + 0x6174
0x090000003AD705A8 sqlnn_cmpl + 0x28
0x090000003AD67960 sqlra_compile_var + 0xB80
0x0900000039E641CC sqlra_find_var + 0x9EC
0x0900000039E458A0 sqlra_get_var + 0xFA0
0x09000000398D9348 sqlrr_prepare + 0x588 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 Fix Pack 10 or higher *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.08.2017
19.07.2018
19.07.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
