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

THE SPATIAL MIGRATION UTILITY INCORRECTLY PROHIBITS MIGRATION WHEN VIEWS
OR FUNCTIONS REFERENCE SPATIAL CONSTRUCTORS.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Attempting to run the Spatial Extender migration utility with a 
command like 'db2se migrate <dbname> -messagesFile <msgfile>' 
produces messages in the message file like: 
***CAN NOT BE MIGRATED *** 
: View <viewname> --> Function "DB2GSE"."ST_POINT"
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Spatial Extender users migrating to V9.7                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The spatial migration utility incorrectly prohibits          * 
* migration when user-defined views or functions reference     * 
* spatial constructors.                                        * 
*                                                              * 
* Attempting to run the Spatial Extender migration utility     * 
* with a command like 'db2se migrate <dbname> -messagesFile    * 
* <msgfile>'                                                   * 
* produces messages in the message file like:                  * 
* ***CAN NOT BE MIGRATED ***                                   * 
* : View <viewname> --> Function "DB2GSE"."ST_POINT"           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* A workaround is to manually drop the referenced user-defined * 
* views or functions, perform the spatial migration and then   * 
* re-create the user-defined views or functions                * 
*                                                              * 
* However this approach should not be used if any of the       * 
* function or view definitions is longer than 4000 bytes as    * 
* this may cause a DB2 crash.                                  * 
*                                                              * 
* Install fixpack 2                                            * 
****************************************************************
Local Fix:
Manually drop identified view or function names, perform 
migration and recreate the view or function.
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
Install fixpack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.03.2010
25.05.2010
25.05.2010
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList