DB2 - Problembeschreibung
Problem IC86511 | Status: Geschlossen |
WHILE UPGRADING A DB2 INSTANCE WITH SPATIAL EXTENDER IN DB2 V10.1 IT GIVES ERROR OF PRODUCT NOT INSTALLED. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
While upgrading a db2 v9.7 instance with spatial extender to v10.1 it gets error as follows DBI1183W Spatial Extender not installed. However with force option it gets installed. Steps to recreate the issue 1) Install DB2 9.7 FP6 AESE (ESE should be also ok) 2) create a test instance 3) Install 9.7 FP6 spatial extender (via db2setup) and update the existing test instance during the installation. 4) Install DB2 10.1 GA release to another directory without migrating the existing instance. IMPORTANT: Choose custom installation and select "SPATIAL_EXTENDER_SERVER_SUPPORT" and "SPATIAL_EXTENDER_CLIENT_SUPPORT". 5) Switch to the 10.1 installation instance directory and execute: db2iupgrade <9.7 testinstance> -> you will receive the described error. Please note: A separate install is not needed for Spatial extenders starting DB2 10.1. DB2 Spatial Extender is now included in the DB2 database product media. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Galileo v 10.1 users * **************************************************************** * PROBLEM DESCRIPTION: * * While upgrading a db2 v9.7 instance with spatial * * extender * * to v10.1 it gets error as follows * * * * DBI1183W Spatial Extender not installed. * * * * However with force option it gets installed. * * * * Steps to recreate the issue * * * * 1) Install DB2 9.7 FP6 AESE (ESE should be also ok) * * * * 2) create a test instance * * * * 3) Install 9.7 FP6 spatial extender (via db2setup) and * * update * * the * * existing test instance during the installation. * * Download: * * http://www.ibm.com/eserver/support/fixes/fixcentral/swg/quic * * kord * * er?brand * * id=1&productid=DB2&vrmf=9.7.*&platform=Linux+64-bit,x86_64&s * * earc * * htype=fi * * x&fixes=*gse*FP006 (this is the 64bit linux image) * * * * 4) Install DB2 10.1 GA release to another directory without * * migrating * * the existing instance. * * IMPORTANT: Choose custom installation and select * * "SPATIAL_EXTENDER_SERVER_SUPPORT" and * * "SPATIAL_EXTENDER_CLIENT_SUPPORT". * * * * 5) Switch to the 10.1 installation instance directory and * * execute: * * db2iupgrade <9.7 testinstance> -> you will receive the * * described * * error. * * * * * * Please note: * * * * A separate install is not needed for Spatial extenders * * starting * * DB2 * * 10.1. DB2 Spatial Extender is now included in the DB2 * * database * * product * * media. * **************************************************************** * RECOMMENDATION: * * Upgrade to db2 v10 fp2 * **************************************************************** | |
Local-Fix: | |
1.As a workaround you can "force" the migration via "db2iupgrade -F". 2.To workaround the issue, edit <v10_installpath>/instance/db2iupgrade_local script as below # Check if V8 Spatial Extender is installed if needed # if [ -f ${INSTHOME?}/sqllib/cfg/db2gse.lvl ]; then # if [ ! -f ${DB2DIR?}/cfg/db2gse.lvl ]; then # FORCEMIGREQ=${TRUE?} # display_msg ${DB2CAT?} 183 'DBI1183W Spatial Extender not installed.\n' # fi # fi | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
Lösung | |
Workaround | |
1.As a workaround you can "force" the migration via "db2iupgrade -F". As the spatial extender works fine afterwards this looks like a cosmetical problem/defect. 2.To workaround the issue, edit <v10_installpath>/instance/db2iupgrade_local script as below # Check if V8 Spatial Extender is installed if needed # if [ -f ${INSTHOME?}/sqllib/cfg/db2gse.lvl ]; then # if [ ! -f ${DB2DIR?}/cfg/db2gse.lvl ]; then # FORCEMIGREQ=${TRUE?} # display_msg ${DB2CAT?} 183 'DBI1183W Spatial Extender not installed.\n' # fi # fi | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 12.09.2012 01.04.2013 01.04.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.2 | |
10.5.0.2 |