DB2 - Problembeschreibung
Problem IT03664 | Status: Geschlossen |
SYSTEM ODBC DSNS ARE REMOVED AFTER UPGRADING DB2 FROM AN OLDER RELEASE ON WINDOWS | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
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. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Windows * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.5 Fixpack 7 * **************************************************************** | |
Local-Fix: | |
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 | |
Lösung | |
First fixed in DB2 10.5 Fixpack 7 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 08.08.2014 21.01.2016 21.01.2016 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.7 |