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

DB2 INSTANCE MIGRATION DB2IMIGR TO V9 FAILS ON WINDOWS IF DB2INSTPROF
POINTS TO THE ROOT OF A DRIVE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
After DB2 is installed on a Windows system, a DB2 instance can 
be created using the root directory of a drive (eg. C:\) as it's 
instance path. For example, with the following command line: 
 
     C:\Program Files\IBM\SQLLIB\BIN>db2icrt TESTME -p C:\ 
 
You can set DB2INSTPROF=C:\ and the DB2 instance's directory is 
C:\[instName], or C:\TESTME for this example. 
 
However, if you try to migrate such an instance in to a higher 
version (eg. DB2 V9.5), either via a migration install or using 
db2imigr.exe, the instance migration fails with the DBI1920 
error. For example: 
 
     C:\SQLLIB95\BIN>db2imigr TESTME -p C:\ 
     DBI1920N  The DB2 instance profile path parameter is not 
               valid. 
 
The cause of this this problem is: DB2 instance migration code 
uses some Windows API function to check whether the instance 
path passed in is a valid directory, and stops it if it is not. 
For a root of a drive, it is not treated by the API function as 
a valid directory.
Problem Summary:
Users Affected: ALL 
 
Problem Description: See Error Description. 
 
Problem Summary:  See Error Description.
Local Fix:
The following are potential work arounds for this problem: 
 
(1) Do not use the root of a drive as the instance path. For 
    DB2 V9.5, the default path for DB2 instances (which is 
    recommended) is: 
    C:\Documents and Settings\All Users\Application Data\ 
    IBM\DB2\[CopyName] 
 
(2) If the root of a drive was already used to create some db2 
    instance and you want to migrate that instance to a higher 
    version, you can do the following: 
 
    a) Export the instance profile (db2cfexp), then drop that 
       instance (which uses the root of drive as its path), 
    b) Install DB2 of the higher version to a new copy 
    c) Then, create an instance with the same name in the new 
       copy, and import (db2cfimp) the instance profile you 
       exported earlier.
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 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

Solution
First fixed in DB2 UDB Version 9.7, FixPak 1 (build s091114)
Workaround
see LOCAL FIX.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.07.2009
15.12.2009
15.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