|
Problem IC84447
|
Status: Closed |
MACHINE.CONFIG SHOULD NOT BE UPDATED FOR NON-DEFAULT COPY |
| product: |
DB2 CONNECT / DB2CONNCT / A10 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Windows users, using DB2 .NET *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v10.1, Fixpak 1 *
**************************************************************** |
| Local Fix: |
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> |
| available fix packs: |
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
|
| Solution |
First fixed in DB2 v10.1, Fixpak 1 |
| Workaround |
see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
05.11.2012
05.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
