|
Problem IC74973
|
Status: Closed |
FEDERATED QUERIES MIGHT RETURN INCORRECT RESULT SET WHEN RETRIEVING DATA FROM REMOTE DATABASE VIA NICKNAMES. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - 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.7 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 LUW Version 9.7 FixPak 5 or higher levels. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 LUW Version 9.7 FixPak 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.03.2011
17.01.2012
17.01.2012 |
| 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.5
|
 |
