|
Problem IC81685
|
Status: Closed |
MIGRATIONUTILITY DIALOG BOX CREATES db2dsdriver.cfg FILE IN THE INSTALL PATH AND NOT IN THE APPLICATION DATA PATH |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
db2dsdriver.cfg is created in the installation path ("C:\Program
Files\IBM\sqllib\cfg") and not in the common application data
path ("C:\Documents and Settings\All Users\Application
Data\IBM\DB2\DB2COPY1\cfg") |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2Connect Users *
****************************************************************
* PROBLEM DESCRIPTION: *
* MigrationUtility dialog box creates cfg file in the install *
* path directory and not in the application data path *
* directory with dsdriver *
* *
* 1) Install dsdriver on a machine where already client *
* package or RTCL is being installed *
* 2) Have some db's cataloged *
* 3) When the MigrationUtility dialog box " Create catalog *
* configuration file from existing DB2 default copy" screen *
* will popup, In that select the option "Create configuration *
* file" *
* *
* *
* Observations: *
* *
* After installing dsdriver we can observe that the cfg file *
* is created is in the install path directory and not in the *
* application data path directory. Since the utility calls *
* db2dsdcfgfill internally and with db2dsdcfgfill if we are *
* not specifying the /o ( output=path) option then cfg it will *
* be created in the application data path *
* *
* Snippet from db2dsdcfgfill from info centre *
* *
* -o output-path *
* The path where the db2dsdcfgfill command creates the *
* db2dsdriver.cfg configuration file. *
* *
* If you do not specify a value for this parameter, and *
* you have a copy of the db2dsdriver.cfg file from Version 9.7 *
* Fix Pack 2 or earlier, that copy is replaced. Otherwise, if *
* you do not specify a value for this parameter, the *
* db2dsdriver.cfg configuration file is created in a directory *
* that depends on your driver type and platform. For *
* information about the location of the db2dsdriver.cfg file, *
* see the topic about that file. *
* *
* http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.j *
* sp?topic=%2Fcom.ibm.swg.im.dbclient.config.doc%2Fdoc%2Fr0054 *
* 557.html&resultof=%22db2dsdcfgfill%22 *
* *
* The same behavior is observed with both GUI install as well *
* as silent install of dsdriver. *
****************************************************************
* RECOMMENDATION: *
* To get the fix customers can upgrade to v97fp6 *
**************************************************************** |
| Local Fix: |
db2dsdriver.cfg can be manually copied from install path
("C:\Program Files\IBM\sqllib\cfg") to Common application data
path ("C:\Documents and Settings\All Users\Application
Data\IBM\DB2\DB2COPY1\cfg") |
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
There is no harm if cfg file is created in install path since
back ward compatibility is supported. Customers can copy the
db2dsdriver.cfg file from install path to the Common application
data path. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC84441
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.02.2012
05.06.2012
05.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
