|
Problem IC92698
|
Status: Geschlossen |
SPATIAL UPGRADE FROM V9.5 TO V9.7 FAILS |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
A command like the following may fail with the indicated message
db2se upgrade mydb -force 1 -messagesFile
/home/db2inst1/se.upgrade.log
Upgrading database. Please wait ...
GSE0214N An INSERT statement failed. SQLERROR = "SQL0727N An
error
occurred during implicit system action type "5". Information
returned
for the error includes SQLCODE "-117", SQLSTATE "42802" and
message
tokens "". SQLSTATE=56098". |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* Spatial extender users upgrading to V10.1 who have *
* user-defined functions based on spatial functions *
****************************************************************
* PROBLEM DESCRIPTION: *
* When a DB2 Spatial Extender upgrade is permed using a *
* command like *
* ==> db2se upgrade mydb -force 1 -messagesFile upgrade.log *
* *
* It may fail with messages like the following: *
* *
* Upgrading database. Please wait ... *
* GSE0214N An INSERT statement failed. SQLERROR = "SQL0727N *
* An error *
* occurred during implicit system action type "5". Information *
* returned *
* for the error includes SQLCODE "-117", SQLSTATE "42802" and *
* message *
* tokens "". SQLSTATE=56098". *
****************************************************************
* RECOMMENDATION: *
* Apply DB2 V10.1 fixpack 3 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
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
|
| Lösung |
Apply DB2 V10.1 fixpack 3 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 31.05.2013
24.10.2013
24.10.2013 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
