DB2 FOR LUW / DB2FORLUW / 970 - DB2

If you run a query with UR isolation and that query deals with 
aliases (for example, uses the TABLE_NAME function) you might 
end up with stack corruption if at the same time another session 
is (re-)creating an alias used by the statement. 
 
The stack corruption will most likely prevent the trap file from 
containing a valid stack and will also prevent a debugger from 
unwinding the stack but a manual unwind would show 'memcpy()' 
issued from 'sqlrlResolveAlias()'. 
 
Key indicators would include a instruction pointer register 
indicating memcpy() and a signal address in thread stack memory.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See description above.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 FP10 or higher.                          * 
****************************************************************

n/a

First fixed in DB2 V9.7 FP10

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

31.07.2014
13.11.2014
13.11.2014

9.7.FP10