DB2 FOR LUW / DB2FORLUW / 950 - DB2

We seem to be dumping in sqlnn_cmpl. 
 
Stack #1             Signal #12        Timestamp 
2011-09-29-16.14.42.671388 
0        ossDumpStackTraceEx 
1        OSSTrapFile::dumpEx 
2        sqlo_trce 
3        sqloDumpDiagInfoHandler 
4        __pthread_mutex_cond_lock 
5        pthread_kill 
6        sqloDumpEDU 
7        sqldDumpContext 
8        sqlrr_dump_ffdc 
9        sqlzeDumpFFDC 
10       sqlzeMapZrc 
11       sqlnn_erdm 
12       sqlnn_cmpl 
13       sqlnn_cmpl 
14       sqlra_compile_var 
15       sqlra_find_var 
16       sqlra_get_var 
17       sqlrr_execute_immediate 
18       sqlrr_execimmd 
19       sqljs_ddm_excsqlimm 
20       sqljsParseRdbAccessed 
21       sqljsParse 
22       sqljsSqlam 
23       sqljsDriveRequests 
24       sqljsDrdaAsInnerDriver 
25       sqljsDrdaAsDriver 
26       sqeAgent::RunEDU 
27       sqzEDUObj::EDUDriver 
28       sqlzRunEDU 
29       sqloEDUEntry 
30       pthread_create@@GLIBC_2.2.5 
31       clone 
Enter frame number [0-31, default 0] : 14 
 
Repro: 
******** 
 
db2set DB2_OPTPROFILE=YES 
 
create table t1(c1 int,c2 int,c3 int); 
create index i1 on t1(c1); 
 
"Query: select * from t1 where c1+1>1; 
Optimizer profile content: 
<OPTGUIDELINES> 
<IXSCAN TABLE='T//1' INDEX='I1'/> 
</OPTGUIDELINES>; 
 
Compiling the query returns the following message: 
SQL0901N  The SQL statement failed because of a non-severe 
system error. 
Subsequent SQL statements can be processed. SQLSTATE=58004 
 
 
With the APAR fix, the query compilation will be complete and an 
explain diagnostic message 
EXP0009W will be logged in explain table.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* EXPLAIN OF A STATEMENT WITH AN OPTIMIZER GUIDELINE FAILS     * 
* WITH                                                         * 
* SQL0901N ERROR.                                              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.1 Fix Pack 10 or higher.            * 
****************************************************************

Correct the table name in optimizer profile.

First fixed in DB2 Version 9.1 Fix Pack 10

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

21.11.2011
22.08.2012
22.08.2012

9.1.FP10