DB2 - Problembeschreibung
Problem IC77364 | Status: Geschlossen |
SPATIAL QUERY MISSING ROWS THAT SHOULD BE IN RESULT SET. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
Spatial joins are only returning the first row of the result set when the spatial index is exploited and polygons being indexed are significantly larger than the largest grid size specified. When the spatial index grid size is increased, all rows are returned correctly. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Spatial Extender applications * **************************************************************** * PROBLEM DESCRIPTION: * * Rows may be missing from the result set of a spatial query * * in the following conditions: * * - spatial join where one or more tables has large line or * * polygon features * * - coordinates in the X (typically latitude) direction are * * negative * * - spatial index is defined where the largest grid size is * * significantly smaller than the large lines or polygons * * * * This problem should only occur when the spatial index grid * * sizes are not correctly specified, causing some spatial * * values to be indexed on the 'overflow' level of the spatial * * index. * **************************************************************** * RECOMMENDATION: * * Install V9.5 fixpack 9 * **************************************************************** | |
Local-Fix: | |
Recreate the spatial index with larger grid sizes. | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows | |
Lösung | |
Install V9.5 fixpack 9 | |
Workaround | |
Use the spatial index advisor tool provided with Spatial Extender to identify appropriate grid sizes and recreate the spatial index with these values. | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC77429 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 06.07.2011 07.03.2012 07.03.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP9 | |
Problem behoben lt. FixList in der Version | |
9.5.0.9 |