home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC61788 Status: Geschlossen

DATABASE UPGRADE FAILS IF METHODS CREATED PRIOR TO DB2 UDB V8 EXIST IN
DATABASE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Database upgrade fails if methods existing in the database were 
created at a pre-DB2 UDB Version 8 release. 
 
For example, it will return the following message: 
SQL2519N  The database was restored but the restored database 
was not upgraded 
to the current release.  Error "-902" with tokens " Migration 
DMS rc=80040001: 
DB2GSE.SRID                         " is returned. 
 
The following gives an example of the types of db2diag.log 
messages seen during 
the failed upgrade attempt: 
 
  2009-06-29-10.11.09.759358-240 I276450A720    LEVEL: 
 Severe PID : 1159350 TID  : 1838  PROC : 
db2syscINSTANCE: jinzhou2 NODE : 000  DB  : 
V7MET  APPHDL  : 0-22      APPID: 
     *LOCAL.jinzhou2.090629141104 
   AUTHID  : JINZHOU2 
 EDUID  : 1838     EDUNAME: db2agent (V7MET   ) 
FUNCTION: DB2 UDB, catalog migration, sqlrlmGetMemSizePSM, 
probe:2313 
MESSAGE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT 
 "SQLCA has already been built" 
CALLED : DB2 UDB, catalog migration, sqlrlmLogErr 
RETCODE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT 
 "SQLCA has already been built" 
DATA #1 : String with size, 39 bytes 
Migration DMS rc=80040001: DB2GSE.SRID 
 
2009-06-29-10.11.09.760365-240 I277171A740   LEVEL: Severe 
PID : 1159350      TID  : 1838   PROC : 
db2syscINSTANCE: jinzhou2 NODE : 000  DB  : 
V7MET  APPHDL  : 0-22      APPID: 
     *LOCAL.jinzhou2.090629141104 
   AUTHID  : JINZHOU2 
 EDUID  : 1838     EDUNAME: db2agent (V7MET   ) 
FUNCTION: DB2 UDB, catalog migration, 
sqlrlmResetMemSizeForPSM, probe:2467 
   MESSAGE : 
ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT 
"SQLCA has already been built"        CALLED  : 
DB2 UDB, catalog migration, sqlrlmLogErr       RETCODE : 
ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT 
"SQLCA has already been built"        DATA #1 : 
String with size, 54 bytes     Migration 
DMS rc=801a006d: Set routinePD's pvmMemSize 
 
 
The following shows a sample callstack: 
 
-------Frame------ ------Function + Offset------ 
0x090000000047C6BC pthread_kill + 0x88 
0x09000000A46458CC sqloDumpEDU + 0x4C 
0x09000000A48A2DF8 sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2 + 
0x138 
0x09000000A4777F84 sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x644 
0x09000000A4770D18 sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x58 
0x09000000A47715F8 sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc 
+0x378 
0x09000000A476D208 sqlrrSqlCode + 0x2C8 
0x09000000A943EE28 sqlrlmLogErr__FP8sqlrr_cbUiUlilPcT3 + 0x288 
0x09000000A942E8BC 
sqlrlmGetMemSizePSM__FP8sqlrr_cbsPUcT3iT3N35Pi + 0x4BC 
0x09000000A942ECDC sqlrlmResetMemSizeForPSM__FP8sqlrr_cbsPUc + 
0x39C 
0x09000000A94340F4 
sqlrlm_postCatalogMigrationTasks__FP8sqeAgentsPUcP8sqlr_tidPUs 
+0x1674 
0x09000000A943C824 sqlrlm_catalog_migrate__FP8sqeAgentsP5sqlca 
+0x1D84 
0x09000000A9421070 sqlefmig__FPcP8SQLE_BWAP5sqlca + 0x5F0 
0x09000000A93FE64C sqlemigr__FP8SQLE_BWAP14db2UCinterface + 
0xF0C 
0x09000000A4986088 
sqleProcessConnectType__FP14db2UCinterfaceP8SQLE_BWAP8sqeAgentP5 
sqlcaP22SQLELOST_STATUS_VECTOR 
+ 0x4E8 
0x09000000A49885A0 
AppLocalStart__14sqeApplicationFP14db2UCinterface + 0x4A0 
0x09000000A4961B8C sqlelostWrp__FP14db2UCinterface + 0x4C 
0x09000000A4963CD0 sqleUCengnInit__FP14db2UCinterfaceUs + 0x4F0 
0x09000000A496995C sqleUCagentConnect + 0x137C 
0x09000000A5704764 
sqljsConnectAttach__FP13sqljsDrdaAsCbP14db2UCinterface + 0x224
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all DB2 Version 9.7 GA on Lunix, Aix and Windows platforms   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Database upgrade fails if methods existing in the database   * 
* were                                                         * 
* created at a pre-DB2 UDB Version 8 release.                  * 
*                                                              * 
* For example, it will return the following message:           * 
* SQL2519N  The database was restored but the restored         * 
* database                                                     * 
* was not upgraded                                             * 
* to the current release.  Error "-902" with tokens "          * 
* Migration                                                    * 
* DMS rc=80040001:                                             * 
* DB2GSE.SRID       " is returned.                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* See local fix or apply DB2 Version 9.7 fix pack 1 and        * 
* reissue database upgrade.                                    * 
****************************************************************
Local-Fix:
Drop and recreate those methods created pre DB2 UDB Version 8 
before performing database upgrade.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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

Lösung
The problem is fixed in DB2 Version 9.7 fix pack 1 and all 
subsequent fix packs.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
29.06.2009
04.01.2010
04.01.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP1
Problem behoben lt. FixList in der Version
9.7.0.1 FixList