DB2 - Problem description
Problem IC78202 | Status: Closed |
BIND FILES UNDER SQLLIB/BND DIRECTORY MAY NOT GET UPGRADED BY FIXPACK INSTALL ON WINDOWS IF MODIFIED BY A SPECIAL BUILD | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
If a special build was applied to the system and the special build contains special versions of .bnd or .lst files under under the SQLLIB/BND folder, they may not get upgraded by the Fixpack install. This happens because the files under SQLLIB/BND are not versioned. The Windows Installer architecture will only replace unversioned files if they have not been modified since the last install. Since a special build may contain fixes in files under SQLLIB/BND, Windows Installer will not upgrade them. To avoid this issue, this APAR will introduce file versioning to the files under the SQLLIB/BND directory. This way it will enforce Windows Installer to upgrade the files regardless if they were modified or not. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Windows * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 6 * **************************************************************** | |
Local Fix: | |
The files that were not upgraded can be manually updated by copying them from an existing install at the same Fixpack level and replacing the old files that were not upgraded properly | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 9.7 Fix Pack 6 | |
Workaround | |
The files that were not upgraded can be manually updated by copying them from an existing install at the same Fixpack level and replacing the old files that were not upgraded properly | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.08.2011 11.07.2012 11.07.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 |