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 IT10164 Status: Closed

COORDINATES CAN ONLY BE TRANSFORMED IF THEIR SPATIAL REFERENCE SYSTEMS
REFER TO THE SAME COORDINATE SYSTEM

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The DB2GSE.ST_Transform() funtion can be used to change the 
Spatial Reference System (SRS) of a geometry, but only if the 
Spatial Reference System (SRS) is based in the same geographic 
coordinate system. This APAR removes the above restriction from 
DB2GSE.ST_Transform(). 
 
Note that there are still some limitations. You cannot transform 
to or from SRS 0 because that refers to an 'undefined' 
coordinate system. 
 
Sometimes an intermediate transform to a worldwide SRS may be 
required (as in transforming from North America (1) to Germany 
(1004) would require an intermediate transform to Worldwide 
(1003) ). 
 
Finally, transforming from a Worldwide to a Regional SRS should 
work, but some points may fail if they are outside the Regional 
extent.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of Spatial Extenders                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 FP7                                      * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 10.5 FP7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.07.2015
28.01.2016
28.01.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList