IBM Support

IT19139: SET PRIMARY CF USING COMMAND "DB2CLUSTER -CM -SET -OPTION PPRIMARY -VALUE ***" NOT WORKING CORRECTLY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error 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.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher               *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 11.1 Mod 2 Fix Pack 2
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT19139

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-06

  • Closed date

    2017-06-23

  • Last modified date

    2017-06-23

  • APAR is sysrouted FROM one or more of the following:

    IT08817

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
29 June 2020