DB2 - Problem description
Problem IT04135 | Status: Closed |
DB2 MIGHT PRODUCE SQL0901N WHEN EXECUTING QUERY CONTAINING MULTIPLE SUB-SELECTS AND DISTINCT CLAUSE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
Under rare scenarios, DB2 might produce a SQL0901N error message if the following conditions are true: 1) The query contains one or more subselects 2) Atleast one of the subselects contain a DISTINCT clause 3) Atleast one of the subselects is complex containing 2 or more tables Eg: SELECT 1 FROM T1 INNER JOIN T2 ON T1.c1 = T2.c1 INNER JOIN (SELECT DISTINCT C1, C2 from t2) tmp ON tmp.C2 = T2.C2 INNER JOIN (SELECT DISTINCT C1, C2 from T2 INNER JOIN T3 ON T2.C3 = T3.C3 ) tmp2 ON tmp.c1 = tmp2.C1 INNER JOIN T4 ON Tmp2.C2 = T4.C2; db2diag.log: 2014-08-20-10.47.20.802258-240 E355334A2819 LEVEL: Info (Origin) PID : 11665618 TID : 2058 KTID : 38600927 PROC : db2sysc INSTANCE: xxxxx NODE : 000 DB : TESTDB APPHDL : 0-19 APPID: *LOCAL.abhayans.140820144708 AUTHID : xxxxxx HOSTNAME: puma EDUID : 2058 EDUNAME: db2agent (TESTDB) FUNCTION: DB2 UDB, SW- common services, sqlnn_cmpl, probe:650 MESSAGE : ZRC=0x803100AF=-2144272209=SQLNN_E_BADNEWS "unexpected error but state is OK" DATA #1 : String, 62 bytes An unexpected error was detected during statement compilation. DATA #2 : Boolean, 1 bytes true DATA #3 : Boolean, 1 bytes false DATA #4 : Boolean, 1 bytes true DATA #5 : Boolean, 1 bytes false DATA #6 : Hex integer, 4 bytes 0x00000000 DATA #7 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 16 sqlerrmc: DOID1 is missing sqlerrp : SQLNQ11E sqlerrd : (1) 0x801A006D (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFFF83 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: Stack: pthread_kill ossPthreadKill sqloDumpEDU sqldDumpContext sqlrr_dump_ffdc sqlzeDumpFFDC sqlzeSqlCode sqlnn_erds sqlnq_sel_doid sqlnq_select_ofn_sm sqlnq_proc_enc sqlnq_qtb::add_doid sqlnr_addids sqlnr_selbox_merge | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * UNKNOWN * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 101 fix pack 5 * **************************************************************** | |
Local Fix: | |
Solution | |
The problem was first fixed in DB2 version 101 fix pack 5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 02.09.2014 12.08.2015 12.08.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 |