home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC89050 Status: Closed

DB2SET DB2_DISABLE_NETWORK_ADAPTER_ADD=FALSE FAILS WITH ERROR
"DBI1302E INVALID PARAMETER DETECTED"

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
DB2_DISABLE_NETWORK_ADAPTER_ADD is used to add the missing 
adpater back via db2cluster -cm -verify -resources as follows: 
 
$ db2set DB2_DISABLE_NETWORK_ADAPTER_ADD=false 
 
But it fails with error : 
 
$ db2set DB2_DISABLE_NETWORK_ADAPTER_ADD=false 
 
DBI1302E  Invalid parameter detected. 
 
Explanation: 
 
An invalid parameter was used.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Customer using DB2 HADR                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1                                         * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
fixed in   DB2 V10.1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.12.2012
22.10.2013
22.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList