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 IT06630 Status: Closed

QUERY WITH UNION MIGHT FAIL WITH SQL0901N ALONG WITH REASON
"RID_QNCP'S QUN IS NOT IN TABLES SET"

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Following error might occur when query with union is executed: 
 
SQL0901N  The SQL statement or command failed because of a 
database system error. (Reason 
"rid_qncp's qun is not in Tables set".)  SQLSTATE=58004 
 
possible db2diag.log entries: 
 
2015-01-12-20.37.08.159955-480 I13290138A901        LEVEL: 
Severe 
PID     : 11927668             TID : 19792          PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
SAMPLE 
APPHDL  : 0-22082              APPID: 
*LOCAL.db2inst1.142340440535 
AUTHID  : USER1              HOSTNAME: host1 
EDUID   : 19792                EDUNAME: db2agent (SAMPLE) 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: 35 
 sqlerrmc: rid_qncp's qun is not in Tables set 
 sqlerrp : SQLNG003 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFC61      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
 
[...] 
 
2015-01-12-20.37.08.337528-480 E13343640A2964       LEVEL: Info 
(Origin) 
PID     : 11927668             TID : 19792          PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
SAMPLE 
APPHDL  : 0-22082              APPID: 
*LOCAL.db2inst1.142340440535 
AUTHID  : USER1              HOSTNAME: host1 
EDUID   : 19792                EDUNAME: db2agent (SAMPLE) 0 
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 
false 
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: 35 
 sqlerrmc: rid_qncp's qun is not in Tables set 
 sqlerrp : SQLNG003 
 sqlerrd : (1) 0x801A006D      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFC61      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
DATA #8 : Hex integer, 4 bytes 
0x00000040 
DATA #9 : String with size, 1000 bytes 
 
<query in question> 
 
DATA #10: String, 589 bytes 
Compiler error stack for rc = -2144272209: 
sqlnn_cmpl[415] 
sqlng_main[3253] 
sqlng_main[1714] 
sqlng_build_thread[859] 
sqlngProcessLolepop[543] 
sqlng_process_return_op[1666] 
sqlngProcessLolepop[543] 
sqlng_process_pipe_op[881] 
sqlngProcessLolepop[543] 
sqlng_process_mate_op[1484] 
sqlngProcessLolepop[543] 
sqlng_process_set_op[11053] 
sqlng_build_SET_op[11478] 
sqlng_build_thread[859] 
sqlngProcessLolepop[543] 
sqlng_process_pipe_op[881] 
sqlngProcessLolepop[543] 
sqlng_process_mate_op[1484] 
sqlngProcessLolepop[543] 
sqlng_process_iscan_op[5458] 
sqlng_build_TA_op[1299] 
sqlng_build_TAOB_obj[927]
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description above.                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version V10.1 Fix Pack 5.                     * 
****************************************************************
Local Fix:
Solution
Fixed in Version V10.1 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.01.2015
23.10.2015
23.10.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