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

DATABASE MIGRATION FAILS WHEN UPGRADING FROM PRE-V8.2 GA (V8.1 FIX PACK 7)
TO V9.1 FIX PACK 8

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
Database migration will fail when attempting to upgrade a 
database from pre-v8.2 GA (a.k.a. v8.1 Fix Pack 7) to v9.1 Fix 
Pack 8. 
 
If you attempt to restore databases at this level directly into 
v9.1 Fix Pack 8, you will encounter the following message: 
 
SQL2519N  The database was restored but the restored database 
was not migrated 
to the current release.  Error "-20158" with tokens "*N" is 
returned. 
 
If you perform migration by running the MIGRATE DATABASE 
command, you will see the following message: 
 
SQL5005C  System Error.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 Version 9.1 Fix Pack 8 servers, migrating databases  * 
* from v8.2 GA or earlier.                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Infrastructure type changes required for fixing APAR IZ38607 * 
* introduced this issue encountered in the migration codepath. * 
*  Migration logic needs to have the ability to read the older * 
* v8.1 version of the database configuration file to complete  * 
* migration successfully.  Databases at the v8.2 level will    * 
* have the newer database configuration file, where no problem * 
* exists.                                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.1 Fix Pack 9 to perform the         * 
* upgrade, or follow steps noted in the "Local Fix".           * 
****************************************************************
Local Fix:
Apply v8.2 GA (v8.1 FP7) or later fix pack, connect to your 
databases in that instance and disconnect.  Then upgrade to v9.1 
FP8. Alternatively, apply v9.1 FP7 to perform your upgrade, then 
apply v9.1 FP8 after upgrade is complete.
available fix packs:
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
Problem is first fixed in DB2 Version 9.1 Fix Pack 9 and all 
subsequent Fix Packs.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IZ67243 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.12.2009
07.04.2010
07.04.2010
Problem solved at the following versions (IBM BugInfos)
9.1.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.9 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.