home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 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

DB2 - Problem description

Problem IC83432 Status: Closed

UNACCEPTABLE CUSTOMER SPATIAL QUERY PERFORMANCE DUE TO DIRECT WRITE/READ

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Spatial queries that invoke a spatial constructor a large number 
of times result in many direct write and read operations which 
may make performance unaccepable, especially for online 
applications. 
 
A particularly common application is finding what polygon a 
point is in given a table of polygons and a table with 
locations. 
 
In this example, there is a table of zipcode polygons and a 
table of customers with the location in latitude and longitude: 
 
select c.cust_name, z.zip 
from customers AS c 
   ,zippoly AS z 
where 
db2gse.st_contains(z.shape,db2gse.st_point(longitude,latitude,1) 
) = 1
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Spatial Extender                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Poor performance of spatial queries due to excessive direct  * 
* write and direct read operations.                            * 
*                                                              * 
* This problem can be identified by at db2batch or snapshot    * 
* information and checking the number of direct write and      * 
* direct read operations that occurred in evaluating the       * 
* query.  If the number of direct write and direct read        * 
* operations are more than twice the number of table rows      * 
* processed in evaluating the query, this is the likely cause. * 
*                                                              * 
* The product fix will eliminate most of the direct operations * 
* in most cases, especially when spatial point data is being   * 
* queried.                                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply V9.7 fixpack 7                                         * 
****************************************************************
Local Fix:
available fix packs:
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
Apply V9.7 fixpack 7
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC85761 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.05.2012
23.10.2012
23.10.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP7
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.7 FixList