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

DATABASE MIGRATION ON WINDOWS FAILS WITH SQL1091

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When attempting to migrate DB2 to v9.5 on Windows using the 
"Work with existing DB2 copy ..." option from the GUI setup it 
returns: 
 
SQL1091C The release number of the database is not valid. 
 
Attempting to issue the commands below also return SQL1091C: 
 
LIST DB DIRECTORY 
MIGRATE DB <database name>
Problem Summary:
See ERROR DESCRIPTION.
Local Fix:
A) Drop and recreate the instance 
   - Check instance name: db2ilist 
   - Drop the instance: db2idrop <instance name> 
   - Create a new instance: db2icrt <instance name> 
   - Recatalog database(s) 
 
OR 
 
B) When installing v9.5 via the GUI tools do not select the 
"Work with existing DB2 copy" option.
available fix packs:
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 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
Problem was first fixed in version 9.7 FixPak 1 (s091114).  At 
minimum the fix should be applied to the server.
Workaround
See LOCAL FIX.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.10.2009
21.12.2009
21.12.2009
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList