DB2 FOR LUW / DB2FORLUW / A10 - DB2

After upgrading DB2 from an older release, ODBC SYSTEM DSNs will 
get removed from the system.  This only occurs when upgrading 
from one release to another (For example, v9.5 to v9.7), not 
Fixpacks within the same release.  This occurs because the act 
of upgrading releases uninstalls the old ODBC driver from the 
system then installs the new ODBC driver.  The ODBC driver 
uninstall act causes the SYSTEM ODBC DSNs to be removed. 
 
This APAR will allow the SYSTEM DSNs to be retained after 
upgrading.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 V10.1 users.                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 Fix Pack 5 or higher.                   * 
****************************************************************

1. Backup the ODBC configuration before upgrade with db2cfexp 
BACKUP from the current installation path 
2. Upgrade to the new release/version 
3. Import the ODBC configuration after upgrade with db2cfimp 
from the new installation path. 
 
See "Exporting and importing a profile" for more details. 
http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.i 
bm.db2.luw.qb.server.doc/doc/t0007301.html 
 
Alternately, the db2cli command can be used with the 
"registerdsn" option in order to register DSNs again after 
upgrading. 
http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2. 
luw.admin.cmd.doc/doc/r0002045.html

First fixed in DB2 V10.1 Fix Pack 5.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

08.08.2014
30.07.2015
30.07.2015