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

DB2 INSTANCE MAY ABEND EXECUTING A QUERY REFERENCING A
PRIMARY/FOREIGN KEY ON A NICKNAME

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
A query being executed may cause the DB2 instance to abend if 
the following conditions are satisifed: 
 
1) One or more tables in the query reference a primary or 
foreign key on a nickname 
2) No nicknames are directly or indirectly referenced in the 
query 
. 
The stack trace from such an abend may look something like: 
sqlnt_main 
sqlno_final_phase 
sqlno_exe 
sqlno_exe 
sqlnn_cmpl 
 
 
or 
 
 
sqlnd_qun_pda 
sqlno_djx_qun_server 
sqlno_crule_access_root 
sqlno_crule_access 
sqlno_plan_qun 
sqlno_call_sf 
sqlno_each_opr 
sqlno_call_sf 
sqlno_walk_qun 
sqlno_call_sf 
sqlno_each_opr 
sqlno_call_sf 
sqlno_walk_qun 
sqlno_call_sf 
sqlno_each_opr 
sqlno_call_sf 
sqlno_walk_qun 
sqlno_call_sf 
sqlno_each_opr 
sqlno_call_sf 
sqlno_walk_qun 
sqlno_call_sf 
sqlno_each_opr 
sqlno_call_sf 
sqlno_top_qtb 
sqlno_call_sf 
sqlno_each_qur 
sqlno_call_sf 
sqlno_scan_qgm 
sqlno_planning_scan 
sqlno_planning_phase 
sqlno_exe 
sqlnn_cmpl
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* EE or EEE                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 1.                       * 
****************************************************************
Local Fix:
No feasible workaround exists aside from removing the 
referential integrity constraint between the affected table(s) 
and nickname(s).
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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
Problem was first fixed in DB2 Version 9.7 Fix Pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.08.2009
19.02.2010
19.02.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList