|
Problem IC90017
|
Status: Closed |
CRASH IN SQLRIMOVEDATALEN FOR A RECURSIVE QUERY WITH UNION AND HOST VARIABLES |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When a query is compiled, it creates a binary executable of
the query called a section.
If a recursive query is run, such that one of the columns in the
recursive row also has a predicate comparing against host
variable, then there is a chance that the compilation of this
query will produce an invalid section and cause a crash when
this query is run.
The thread will crash with a stack similar to the following
stack:
<StackTrace>
0x090000002CB94D74 sqlriMoveDataLen__FP8sqlrr_cb + 0xB4
0x0900000028433F80
sqldDataFetch__FP8SQLD_CCBP8SQLZ_RIDUlP7SQLI_CB + 0x3E0
0x0900000028436CE4
.@161@sqliScanLeaf2.fdpr.clone.28381__FP7SQLI_CBP11SQLI_SFGLOB +
0x924
0x0900000028437F30
.sqlifnxt.fdpr.clone.5344__FP7SQLI_CBP11SQLI_SFGLOB + 0x34C
0x0900000028442C3C
.sqlirdk.fdpr.clone.4556__FP8sqeAgentP10SQLI_IXPCRP9SQLD_IXCB
UlP8SQLD_KEYP12SQLI_KEYDATAP9sqli_scanPi + 0xA4C
0x09000000284177FC
.sqldIndexFetch.fdpr.clone.1663__FP8SQLD_CCBP8SQLZ_RID + 0x688
0x09000000284168A4
sqldRowFetch__FP8sqeAgentP8SQLD_CCBUlT3PP10SQLD_VALUEP8SQLZ_R
IDT3P12SQLD_ID_LISTP9SQLP_LSN8 + 0xD3C
0x0900000028413CF8
.sqlriFetch.fdpr.clone.45__FP8sqlrr_cbP9sqlri_taol + 0x2A4
0x0900000028413764 sqlriNljnNonPiped__FP8sqlrr_cb + 0x76C
0x0900000028408C60 sqlriunn__FP8sqlrr_cbP10sqlri_stob + 0x170
0x09000000292F723C sqlriset__FP8sqlrr_cb + 0x1D0
0x09000000284147AC sqlrievl__FP8sqlrr_cb + 0x20
0x0900000028412DC8 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm +
0x24
0x090000002822C868
sqlrr_process_fetch_request__FP14db2UCinterface + 0xF60
0x0900000028C649F8
sqlrr_open__FP14db2UCinterfaceP15db2UCCursorInfo + 0x17F0
(...) |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Any using recusive query with host variable *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10 fixpack 3 or later *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in DB2 version 10 fixpack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.02.2013
28.10.2013
28.10.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
|
|
