DB2 - Problembeschreibung
Problem IC74971 | Status: Geschlossen |
FEDERATED QUERIES MIGHT RETURN INCORRECT RESULT SET WHEN RETRIEVING DATA FROM REMOTE DATABASE VIA NICKNAMES. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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: | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 UDB Version 9.5 FixPak 8. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC74973 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 10.03.2011 30.06.2011 30.06.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5. | |
Problem behoben lt. FixList in der Version | |
9.5.0.8 |