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

SQL0901N RETURNED WITH REASON CODE "INVALID QNC ASSIGNMENT"

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 may return SQL0901N with reason code "invalid qnc 
assignment" and the following call stack 
 
sqlnn_cmpl[370] 
sqlnr_exe[400] 
sqlnr_rcc[100] 
sqlnr_seq[100] 
sqlnr_comp[110] 
sqlnr_start_action[20] 
sqlnr_rcc[100] 
sqlnr_seq[100] 
sqlnr_comp[110] 
sqlnr_endqtb_action[10] 
sqlnr_rcc[100] 
sqlnr_seq[100] 
sqlnr_comp[110] 
sqlnr_rijel_action[40] 
sqlnq_pid::update_qnc[100] 
sqlnq_pid::replace_qnc[100] 
 
This problem may be found in a SQL statement containing inner 
joins between primary key columns and foreign key columns of two 
or more tables. 
 
<The script below is a reproduction of the problem. I will leave 
it to you to decide whether you want to include in the APAR text 
or not.> 
 
create table t1(pk int not null primary key, c1 varchar(1)); 
create table t2(pk smallint not null primary key, fk1 int not 
null, fk2 int not null, c1 varchar(1)); 
alter table t2 add foreign key (fk1) references t1(pk); 
alter table t2 add foreign key (fk2) references t1(pk); 
create table t3(fk smallint not null, c1 varchar(1)); 
alter table t3 add foreign key (fk) references t2(pk); 
 
select * from t1,t2,t3 where t1.pk=t2.fk1 and t2.pk=t3.fk;
Problem Summary:
DB2 may return SQL0901N with reason code "invalid qnc 
assignment" and the following call stack 
 
sqlnn_cmpl[370] 
sqlnr_exe[400] 
sqlnr_rcc[100] 
sqlnr_seq[100] 
sqlnr_comp[110] 
sqlnr_start_action[20] 
sqlnr_rcc[100] 
sqlnr_seq[100] 
sqlnr_comp[110] 
sqlnr_endqtb_action[10] 
sqlnr_rcc[100] 
sqlnr_seq[100] 
sqlnr_comp[110] 
sqlnr_rijel_action[40] 
sqlnq_pid::update_qnc[100] 
sqlnq_pid::replace_qnc[100] 
 
This problem may be found in a SQL statement containing inner 
joins between primary key columns and foreign key columns of two 
or more tables. 
 
<The script below is a reproduction of the problem. I will leave 
it to you to decide whether you want to include in the APAR text 
or not.> 
 
create table t1(pk int not null primary key, c1 varchar(1)); 
create table t2(pk smallint not null primary key, fk1 int not 
null, fk2 int not null, c1 varchar(1)); 
alter table t2 add foreign key (fk1) references t1(pk); 
alter table t2 add foreign key (fk2) references t1(pk); 
create table t3(fk smallint not null, c1 varchar(1)); 
alter table t3 add foreign key (fk) references t2(pk); 
 
select * from t1,t2,t3 where t1.pk=t2.fk1 and t2.pk=t3.fk;
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Defect   => wsdbu00623060 
Fixed in => V9.7 + FP2 
Module   => ENGN_SQNR
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC66945 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.03.2010
10.06.2010
10.06.2010
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList