|
Problem IC77364
|
Status: Closed |
SPATIAL QUERY MISSING ROWS THAT SHOULD BE IN RESULT SET. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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. |
| available fix packs: |
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 |
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-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC77429
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.07.2011
07.03.2012
07.03.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.9
|
 |
