|
Problem IC99322
|
Status: Closed |
DB2 NOT REGISTERED AS THE DEFAULT COPY WHEN IT IS THE ONLY COPY AND DEFAULT_COPY=NO & DEFAULT_CLIENT_INTERFACE_COPY=NO |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
The following two keywords in a DB2 installation response file
direct the installer to not set this DB2 installation as the
default copy.
DEFAULT_COPY=NO
DEFAULT_CLIENT_INTERFACE_COPY=NO
However, when there are currently no copies of DB2 on the
system, DB2 should be installed as the default copy as it is the
only copy of DB2 on the system. This APAR will allow DB2 to be
properly registered as the default copy when it is the only copy
on the system.
Some symptoms of not having DB2 as the default copy include:
- Only the ODBC driver named "IBM DB2 ODBC DRIVER - DB2COPY1" is
registered. The default copy version of the driver named "IBM
DB2 ODBC DRIVER" is not registered.
- DB2 in the start menu doesn't have the word "Default" beside
"DB2COPY1 (Default)". |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Windows *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.1 Fixpack 4 *
**************************************************************** |
| Local Fix: |
It is possible to make DB2 the default copy after installing by
running the db2swtch command ("Default DB2 and Database Client
Interface Selection wizard" in the start menu). This will
result in also adding the default drivers such as "IBM DB2 ODBC
DRIVER". |
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 10.1 Fixpack 4 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC99342
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.02.2014
16.06.2014
16.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
