Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC74971 Status: Closed

FEDERATED QUERIES MIGHT RETURN INCORRECT RESULT SET WHEN RETRIEVING DATA
FROM REMOTE DATABASE VIA NICKNAMES.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
This problem affects SQL queries on nicknames which reflect to 
tables on remote database. 
 
It might happen only when all of the necessary conditions are 
met: 
1. References nickname whose remote source table has index. 
2. The federated query has an OR predicate. 
3. All OR subterms have comparison predicates of format 
"nickname.column <relop> literal", where <relop> is "<", "<=", 
"=", ">=", or ">" . 
4. All OR subterms reference nickanme column whose remote 
counterpart is the leading index key. 
5. Some but not all OR subterms references non-leading index 
key. 
 
SQL queries on local tables are not affected. 
 
To verify the problem, generate db2exfmt output file, search 
"Remote statement" and check if non-leading index key predicate 
is added there.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 9.5 on Linux, Unix and Windows          * 
* platforms.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* This problem affects SQL queries on nicknames which reflect  * 
* to tables on remote database.                                * 
*                                                              * 
* It might happen only when all of the necessary conditions    * 
* are met:                                                     * 
* 1. References nickname whose remote source table has index.  * 
* 2. The federated query has an OR predicate.                  * 
* 3. All OR subterms have comparison predicates of format      * 
* "nickname.column <relop> literal", where <relop> is "<",     * 
* "<=", "=", ">=", or ">" .                                    * 
* 4. All OR subterms reference nickanme column whose remote    * 
* counterpart is the leading index key.                        * 
* 5. Some but not all OR subterms references non-leading index * 
* key.                                                         * 
*                                                              * 
* SQL queries on local tables are not affected.                * 
*                                                              * 
* To verify the problem, generate db2exfmt output file, search * 
* "Remote statement" and check if non-leading index key        * 
* predicate is added there.                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.5 FixPak 8 or higher levels.    * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 UDB Version 9.5 FixPak 8.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC74973 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.03.2011
30.06.2011
30.06.2011
Problem solved at the following versions (IBM BugInfos)
9.5.
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.