DB2 CONNECT / DB2CONNCT / A10 - DB2

When installing DB2 v9.7 on Windows as a non-default copy, DB2 
updates the machine.config file. 
 
For another copy of DB2 that currently exists, it could cause an 
application to fail as it might try to load the new DB2 v9.7 
.NET data provider that was just installed, instead of the 
default copy that it was intended to use. 
 
This APAR will ensure that the machine.config file does not get 
updated/modified during the installation when a non-default copy 
of DB2 is being installed.   This APAR will also ensure that 
when a db2swtch operation is performed that the machine.config 
file does get updated for the new default copy that is being 
registered.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows users, using DB2 .NET                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1, Fixpak 1                               * 
****************************************************************

Manually remove the created entries from the machine.config 
file.   The entries will look like this: 
 
      <dependentAssembly> 
        <assemblyIdentity name="IBM.Data.DB2" 
publicKeyToken="7c307b91aa13d208" culture="" /> 
        <bindingRedirect oldVersion="8.0.0.0-9.0.0.4" 
newVersion="9.7.4.4" /> 
      </dependentAssembly>

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First fixed in DB2 v10.1, Fixpak 1

see Local fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

14.06.2012
05.11.2012
05.11.2012