|
Problem IC66112
|
Status: Closed |
INSTALLATION COMPLETES SUCCESSFULLY BUT INSTANCE IS NOT MIGRATED CORRECTLY IN SILENT INSTALL IF DB2.NAME IS KEPT BLANK |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
In a response file based silent migration installation, if the
keywords are set as the following in the response file:
DB2.NAME = <blank>.
UPGRADE_PRIOR_VERSIONS = TRUE
then even the installation completes successfully, the existing
instance(s) are not migrated properly.
After the installation, db2start falis with SQL1042C |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users prior to V9.7 FP2 *
****************************************************************
* PROBLEM DESCRIPTION: *
* In a response file based silent migration installation, *
* ifthekeywords are set as the following in the response *
* file:DB2.NAME = <blank>.UPGRADE_PRIOR_VERSIONS = TRUEthen *
* even the installation completes successfully, *
* theexistinginstance(s) are not migrated properly.After the *
* installation, db2start falis with SQL1042C *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V9.7 FP2 *
**************************************************************** |
| Local Fix: |
Dont keep the key word DB2.NAME blank in the response file |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in V9.7 FP2 |
| Workaround |
Dont keep the key word DB2.NAME blank in the response file |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC67175
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.02.2010
22.06.2010
22.06.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
