|
Problem IC76175
|
Status: Closed |
THE CONNECT SUPPORT FEATURE UNDER THE SERVER SUPPORT SECTION IS NOT SELECTED BY DEFAULT TO BE INSTALLED |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When the following V97FP3a or V97FP4 DB2 product is installed:
DB2 Advanced Enterprise Server Edition (AESE)
DB Enterprise Server Edition (ESE)
DB2 Connect Server Edition (ConSV)
the "Connect Support" feature is not selected to be installed by
default. If it is a Custom GUI install, you will find this
feature is de-selected under the Server Support section on
the Feature Selection panel. If it is a GUI Typical install,
this Connect Support feature will not be installed too.
The cause of this problem is the install condition string became
too long after AESE is added/supported in V97FP3a. Since it is
over the length limit allowed by the install MSI's Condition
table, the install condition for this feature could not be set
when the install images are created. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* V97FP3a and V97FP4 ESE, AESE and ConSV on windows *
****************************************************************
* PROBLEM DESCRIPTION: *
* When V97FP3a or V97FP4 AESE, ESE or ConSV is installed, the *
* *
* Connect Support feature is not selected to be installed by *
* *
* default. If it is a Custom GUI install, you will find this *
* *
* feature is de-selected under the Server Support section on *
* the *
* Feature Selection Panel. If it is a GUI Typical install, *
* this *
* Connect Support feature will not be installed too. *
* *
* *
* *
* The cause of this problem is the install condition string *
* became *
* too long after AESE is added/supported in V97FP3a. Since it *
* is *
* over the length limit allowed by the install MSI's Condition *
* *
* table, the install condition for this feature could not be *
* set *
* when the install images are created. *
****************************************************************
* RECOMMENDATION: *
* There are two options to work-around this problem: *
* *
* 1). To install the DB2 product via a GUI install: choose *
* the *
* Custom install type, and select the Connect Suppprt feature *
* on *
* the Feature Selection panel; *
* *
* 2). To install the DB2 product via a response file based *
* silent *
* install: specify (or uncomment) the following keyword in *
* the *
* response file: *
* *
* COMP = CONNECT_SUPPORT *
**************************************************************** |
| Local Fix: |
There are two options to work-around this problem:
1). To install the DB2 product via a GUI install: choose the
Custom install type, and select the Connect Suppprt feature on
the Feature Selection panel;
2). To install the DB2 product via a response file based silent
install: specify (or uncomment) the following keyword in the
response file:
COMP = CONNECT_SUPPORT |
| available fix packs: |
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
As the fix will be delivered in v97fp5, this problem will not
happen in db2 v97fp5 and higher releases. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.05.2011
08.12.2011
08.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
