|
Problem IC67485
|
Status: Closed |
SPATIAL MIGRATION TO V9.7 FAILS FOR DATABASE ORIGINALLY CREATED ON V7 |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If a database was originally created and spatially-enable on DB2
V7 and subsequently migrated to DB2 V8, when the 'db2se migrate'
or 'db2se upgrade' command is used to upgrade this data base to
V9.7, it will likely fail with the messages:
Upgrading database. Please wait ...
GSE0219N An EXECUTE IMMEDIATE statement failed. SQLERROR =
"SQL0723N An error occurred in a triggered SQL statement in
trigger
"DB2GSE.GSE_CS_ID". Information returned for the error includes
SQLCODE "-443", SQLSTATE "38S68" and message tokens
"*ISEERROR||GSE1044N The specified coordin". SQLSTATE=09000".
This is due to an internal conflict between the coordinate
system with the name 'UNKNOWN' created in a V7 spatial database
and the coordinate system with the name 'UNSPECIFIED' added in
an upgrade to V8 or V9 spatial databases. The coordinate system
with the name 'UNKNOWN' is obsolete and has been deprecated. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 Spatial Extenders migrating a database originally *
* spatially-enabled with DB2 V7 *
****************************************************************
* PROBLEM DESCRIPTION: *
* If a database was originally created and spatially-enable on *
* DB2 *
* V7 and subsequently migrated to DB2 V8, when the 'db2se *
* migrate' *
* or 'db2se upgrade' command is used to upgrade this data base *
* to *
* V9.7, it will likely fail with the messages: *
* *
* Upgrading database. Please wait ... *
* *
* GSE0219N An EXECUTE IMMEDIATE statement failed. SQLERROR = *
* *
* "SQL0723N An error occurred in a triggered SQL statement in *
* *
* trigger *
* *
* "DB2GSE.GSE_CS_ID". Information returned for the error *
* includes *
* *
* *
* SQLCODE "-443", SQLSTATE "38S68" and message tokens *
* *
* "*ISEERROR||GSE1044N The specified coordin". *
* SQLSTATE=09000". *
****************************************************************
* RECOMMENDATION: *
* Apply V9.7 fixpack 3 before running spatial upgrade to V9.7. *
**************************************************************** |
| Local Fix: |
Issue the following query to verify the problem and check that
two rows are returned:
select coordsys_name from db2gse.gse_coordinate_systems where
coordsys_name like 'UN%'
Then issue the statement:
delete from db2gse.gse_coordinate_systems where coordsys_name =
'UNKNOWN'. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Apply V9.7 fixpack 3 before running spatial upgrade to V9.7 |
| Workaround |
Issue the following query to verify the problem and check that
two rows are returned:
select coordsys_name from db2gse.gse_coordinate_systems where
coordsys_name like 'UN%'
Then issue the statement:
delete from db2gse.gse_coordinate_systems where coordsys_name =
'UNKNOWN'. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC69154
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.03.2010
16.09.2010
16.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.,
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
