|
Problem IT19139
|
Status: Closed |
SET PRIMARY CF USING COMMAND "DB2CLUSTER -CM -SET -OPTION PPRIMARY -VALUE ***" NOT WORKING CORRECTLY |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
Setting the preferred primary CF host via the following command
is not working correctly:
db2cluster -cm -set -option -pprimary -value <hostname>
For example if we set the preferred primary CF host as node3 as
follows:
[db2inst1@node1 ~]$ db2cluster -CM -SET -OPTION PPRIMARY -VALUE
node3
The preferred primary CF has been changed to 'node3'.
[db2inst1@node1 ~]$ db2cluster -cm -list -pprimary
node3
And then proceed to start the DB2 instance:
[db2inst1@node1 ~]$ db2start
04/22/2015 11:19:29 1 0 SQL1063N DB2START processing
was successful.
04/22/2015 11:19:30 0 0 SQL1063N DB2START processing
was successful.
SQL1063N DB2START processing was successful.
It is observed via the "db2instance -list" command that the
primary CF still resides on node2:
[db2inst1@node1 ~]$ db2instance -list
ID TYPE STATE HOME_HOST
CURRENT_HOST ALERT PARTITION_NUMBER
LOGICAL_PORT NETNAME
-- ---- ----- ---------
------------ ----- ----------------
------------ -------
0 MEMBER STARTED node1
node1 NO 0 0
node1
1 MEMBER STARTED node3
node3 NO 0 0
node3
128 CF PRIMARY node2
node2 NO - 0
node2
129 CF CATCHUP node3
node3 NO - 0
node3
HOSTNAME STATE INSTANCE_STOPPED
ALERT
-------- ----- ----------------
-----
node2 ACTIVE NO
NO
node3 ACTIVE NO
NO
node1 ACTIVE NO
NO
This is incorrect behavior. In the above scenario, the primary
CF should have started on node2. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher *
**************************************************************** |
| Local Fix: |
n/a |
| available fix packs: |
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 11.1 Mod 2 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.02.2017
23.06.2017
23.06.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
