home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT07114 Status: Closed

EXPLAINING A QUERY WHICH INVOLVES FGAC PROTECTED TABLES AND A UNION
OPERATOR MAY RESULT IN SQL901N

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When explaining a query which involves FGAC protected tables and 
a UNION operator where the inputs to the UNION have different 
data types a SQL0901N internal error is returned and a FODC 
directory is 
created. 
The actual processing of the query is unaffected by the SQL0901 
and full FGAC protection is in effect for the query execution. 
 
The impact of this error is: 
1) A row in the EXPLAIN_STATEMENT table with EXPLAIN_LEVEL='F' 
will not exist. 
2) In db2exfmt output the reverse SQL under the following label 
will be missing. 
 
Statement With FGAC Applied: 
--------------------------- 
SELECT 
 
 
Here are the db2diag.log errors and stack: 
 
2015-02-09-10.45.27.312212-420 I51326520A887        LEVEL: 
Severe 
PID     : 3211310              TID : 57844          PROC : 
db2sysc 0 
INSTANCE: db2cc              NODE : 000           DB   : CCIDS 
APPHDL  : 0-11211              APPID: *N0.db2cc.150209174513 
AUTHID  : DB2CC             HOSTNAME: test 
EDUID   : 57844                EDUNAME: db2agent (CCIDS) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:300 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 21 
sqlerrmc: Unexpected NULL value 
sqlerrp : SQLNX099 
sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 0x00000000 
           (4) 0x00000000      (5) 0xFFFFFFC3      (6) 
0x00000000 
sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
sqlstate: 
 
2015-02-09-10.45.27.312663-420 I51327408A220      LEVEL: Severe 
 
Dump File:/db2cc/db2dump/FODC_AppErr 
 
instance name: db2ccgu1.000 
EDU name     : db2agent (CCIDS) 0 [-] 
EDU ID       : 14590 
Signal #31 
uname: S:AIX R:1 V:6 M:00C61EDD4C00 N:euizp4000a 
process id: 3211310 
parent process id: 3277042 
thread id : 14590 (0x38FE) 
kthread id : 34144849 
 
... 
 
x0900000000865E94 pthread_kill + 0xD4 
0x090000000727D908 sqloDumpEDU + 0xD0 
0x0900000007B150EC sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2 + 
0x104 
0x0900000008053FD4 sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x52C 
0x0900000008051A48 sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x28 
0x0900000008051BF0 sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc + 
0xCC 
0x090000000805497C sqlnn_erds__FiN41e + 0x134 
0x090000000B67637C 
@137@sqlnx_exp_gsql_proc_sel_list__FP20sqlnx_exp_gsql_parmsP9sql 
nq_oprT2 + 0x6FC 
0x090000000B66CF54 
@137@sqlnx_exp_gsql_std__FP13sqlno_globalsP20sqlnx_exp_gsql_parm 
sP9sqlnq_qtbT3 + 0x6D0 
0x090000000B66F464 
@137@sqlnx_exp_gsql_std__FP13sqlno_globalsP20sqlnx_exp_gsql_parm 
sP9sqlnq_qtbT3 + 0x2BE0 
0x090000000B670DB0 
@137@sqlnx_exp_gsql_proc_tab__FP20sqlnx_exp_gsql_parmsP9sqlnq_qu 
n + 0x3DC 
0x090000000B66D8BC 
@137@sqlnx_exp_gsql_std__FP13sqlno_globalsP20sqlnx_exp_gsql_parm 
sP9sqlnq_qtbT3 + 0x1038 
0x090000000B670DB0 
@137@sqlnx_exp_gsql_proc_tab__FP20sqlnx_exp_gsql_parmsP9sqlnq_qu 
n + 0x3DC 
0x090000000B66D8BC 
@137@sqlnx_exp_gsql_std__FP13sqlno_globalsP20sqlnx_exp_gsql_parm 
sP9sqlnq_qtbT3 + 0x1038 
0x090000000B670DB0 
@137@sqlnx_exp_gsql_proc_tab__FP20sqlnx_exp_gsql_parmsP9sqlnq_qu 
n + 0x3DC 
0x090000000B66D8BC 
@137@sqlnx_exp_gsql_std__FP13sqlno_globalsP20sqlnx_exp_gsql_parm 
sP9sqlnq_qtbT3 + 0x1038 
0x090000000B670DB0 
@137@sqlnx_exp_gsql_proc_tab__FP20sqlnx_exp_gsql_parmsP9sqlnq_qu 
n + 0x3DC 
0x090000000B66D8BC 
@137@sqlnx_exp_gsql_std__FP13sqlno_globalsP20sqlnx_exp_gsql_parm 
sP9sqlnq_qtbT3 + 0x1038 
0x090000000B670DB0 
@137@sqlnx_exp_gsql_proc_tab__FP20sqlnx_exp_gsql_parmsP9sqlnq_qu 
n + 0x3DC 
0x090000000B66D8BC 
@137@sqlnx_exp_gsql_std__FP13sqlno_globalsP20sqlnx_exp_gsql_parm 
sP9sqlnq_qtbT3 + 0x1038 
0x090000000B670DB0 
@137@sqlnx_exp_gsql_proc_tab__FP20sqlnx_exp_gsql_parmsP9sqlnq_qu 
n + 0x3DC 
0x090000000B66D8BC 
@137@sqlnx_exp_gsql_std__FP13sqlno_globalsP20sqlnx_exp_gsql_parm 
sP9sqlnq_qtbT3 + 0x1038 
0x090000000B670DB0 
@137@sqlnx_exp_gsql_proc_tab__FP20sqlnx_exp_gsql_parmsP9sqlnq_qu 
n + 0x3DC 
0x090000000B66D8BC 
@137@sqlnx_exp_gsql_std__FP13sqlno_globalsP20sqlnx_exp_gsql_parm 
sP9sqlnq_qtbT3 + 0x1038 
0x090000000B670DB0 
@137@sqlnx_exp_gsql_proc_tab__FP20sqlnx_exp_gsql_parmsP9sqlnq_qu 
n + 0x3DC 
0x090000000B66D8BC 
@137@sqlnx_exp_gsql_std__FP13sqlno_globalsP20sqlnx_exp_gsql_parm 
sP9sqlnq_qtbT3 + 0x1038 
0x09000000085928DC 
sqlnx_exp_qgm_to_sql__FP3locP9sqlnq_qtbPPcPiiT5bT7 + 0x69C 
0x090000000914923C sqlnq_compile_fgac__FP9sqlnq_qur + 0x1A4 
0x09000000085F26F4 sqlns_qgs__FP9sqlnq_qur17sqlnq_requestTypePc 
+ 0x2A0 
0x090000000843F548 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_enviT7PP9sqlnq_qur + 0x3F0 
0x090000000844210C 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_env + 0x50 
0x090000000820B65C 
sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P14SQLP_ 
LOCK_INFOP16sqlra_cached_varPi + 0x758 
0x0900000007E07520 
sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idUi 
T4PUcT4UsUcP14sqlra_cmpl_env15sqlra_fill_modePiiT12_N31 
3_T12_P14SQLP_LOCK_INFOPP16sqlra_cached_varT12_b + 0x6A0 
0x09000000082179F4 sqlra_get_var__FP8sqlrr_cbiT2bPbT5 + 0x1A4
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 UDB Version 10.1, FixPak 5                     * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 UDB Version 10.1, FixPak 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.02.2015
13.07.2015
13.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList