| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC92342 | Status: Closed |
UPDATING A MEMBER OR CF TO ADD A NETWORK INTERFACE LOSES THAT UPDATED AFTER A REBOOT OR FAILOVER | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
When updating a member with an additional network interface e.g. using : db2iupdt -add -m pocm0 -mnet pocm0-ib0,pocm0-ib1 -i db2ssh1 db2sdin1 the db2nodes.cfg will be updated with the additional netname reflected in the db2instance -list output : db2sdin1@pocm0$ db2instance -list ID TYPE STATE HOME_HOST CURRENT_HOST ALERT PARTITION_NUMBER LOGICAL_PORT NETNAME -- ---- ----- --------- ------------ ----- ---------------- ------------ ------- 0 MEMBER STARTED pocm0 pocm0 NO 0 0 pocm0-ib0,pocm0-ib1 1 MEMBER STARTED pocm1 pocm1 NO 0 0 pocm1-ib0,pocm1-ib1 2 MEMBER STARTED pocm2 pocm2 NO 0 0 pocm2-ib0,pocm2-ib1 128 CF PRIMARY poccf1 poccf1 NO - 0 poccf1-ib0,poccf1-ib1 129 CF PEER poccf2 poccf2 NO - 0 poccf2-ib0,poccf2-ib1 The problem in this apar is that this information is not permanently stored in the HA registry file which can be viewed using db2hareg -dump : ... NL,0,pocm0,0,pocm0-ib0,-,MEMBER NL,1,pocm1,0,pocm1-ib0,-,MEMBER NL,2,pocm2,0,pocm2-ib0,-,MEMBER ... -> only 1 netname is listed. As a result, when there is a reboot or a failback after a failover , the member or the Cluster Caching Facility which previously had the netname added, will lose this information. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Purescale users. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade the database server to V10.1 Fix Pack 3 * **************************************************************** | |
| Local Fix: | |
Instead of updating a member or CF , drop and add the member or CF as follows : db2iupdt -drop -m pocm0 db2iupdt -add -m pocm0 -mnet pocm0-ib0,pocm0-ib1 -i db2ssh1 db2sdin1 | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
This problem was first fixed in DB2 V10.1 Fix Pack 3 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 16.05.2013 21.10.2013 21.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 |
|
| 10.1.0.3 |
|