|
Problem IC67175
|
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 / 980 - 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: *
* DB2 V9.8 FP2 *
****************************************************************
* 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 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V9.8 FP3 *
**************************************************************** |
| Local Fix: |
Dont keep the key word DB2.NAME blank in the response file |
| available fix packs: |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
Dont keep the key word DB2.NAME blank in the response file |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.03.2010
10.01.2011
10.01.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.3
|
 |
