|
Problem IC88703
|
Status: Closed |
SPATIAL QUERY USING BOTH THE ST_NEARESTPOINTS AND ST_DISTANCE FUNCTIONS MAY FAIL WITH THE SQL0430N ERROR. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
A spatial query using both the ST_NearestPoints and ST_Distance
functions may fail with the error:
SQL0430N User defined function "DB2GSE.GSENATIVEDISTANCE"
(specific name "GSENDIST") has abnormally terminated.
SQLSTATE=38503
The ST_NearestPoints function is typically used to find the
point(s) on a line "nearest" to a specified point location, such
as querying a table of highway segments to find the highway
segments and the closest points to a specified point. This would
normally be qualified by a distance to avoid scanning the entire
table.
An example query is:
with test_point(point) as (
values(db2gse.ST_Point (-108.21461,44.77150 , 1))
)
select objectid
,db2gse.ST_NearestPoints(route.shape, point) as np
from highways, test_point
where db2gse.st_distance(shape, point) < 0.1 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 2. *
**************************************************************** |
| Local Fix: |
There is no workaround. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.1 Fix Pack 2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.11.2012
28.01.2013
28.01.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
