IBM Support

IC83770: CM - FAILOVER MIGHT NOT WORK PROPERLY IF THERE ARE MORE CMS CONN ECTED TO MACH11 CLUSTER AND ONE OF THEM HAS FOC SET TO DISABLED

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • If you have a MACH11 cluster with several Connection Managers
    (CM) connected to it and one of these CMs has the failover
    configuration (FOC) set to ORDER=DISABLED, the failover might
    not work as expected if this particular CM is registered as the
    first one in the cluster. This might happen when:
    - the CM with disabled FOC is started before the other CMs (on
    other words as the first one)
    - or when the other running CMs are for some reason restarted
    while the one with disabled FOC is not
    
    You can identify this situation by checking the 'Failover
    Configuration' part of the 'onstat -g cmsm' output on the MACH11
    primary.
    If there is no CM marked as 'Active arbitrator', the failover
    will not work in case of primary's crash:
    
    Failover Configuration:
    Connection Manager name        Rule                Timeout
    State
    cm_nofoc
                                   DISABLED                  0
    Failover is disabled
    cm_foc
                                   PRI+HDR                  30
    Primary is up
    
    The same output for the situation there is an active arbitrator:
    
    Failover Configuration:
    Connection Manager name        Rule                Timeout
    State
    cm_foc
                                   PRI+HDR                  30
    Active Arbitrator, Primary is up
    cm_nofoc
                                   DISABLED                  0
    Failover is disabled
    
    If the MACH11 primary crashes when there is no active
    arbitrator, the log of the CM with disabled FOC shows:
    
    11:05:04 DEBUG:Connection Manager disconnected from tcp_1150uc8
    sqlcode=-1803 [cmsm_er.ec:cmsm_er_monitor:2357]
    11:05:04 Connection Manager disconnected from tcp_1150uc8
    11:05:04 DEBUG:Arbitrator detected down server, svr=tcp_1150uc8,
    type=1 [cmsm_arb.c:arb_server_down:991]
    11:05:04 Arbitrator failover processing is DISABLED.
    11:05:04 ALARM 2003 failover arbitrator automated failover is
    disabled
    11:05:04 DEBUG:Monitor tcp_1150uc8 exit by arbitrator
    [cmsm_er.ec:cmsm_er_monitor:2374]
    11:05:04 ALARM 3002 detected lost connection to Informix server
    tcp_1150uc8
    
    At the same time the logs of the other CMs will show this:
    
    11:05:04 DEBUG:fetch sysrepstats_cursor SQLCODE = (-25582,0,)
    [cmsm_er.ec:cmsm_er_event_process:1570]
    11:05:04 DEBUG:Connection Manager disconnected from tcp_1150uc8
    sqlcode=-1803 [cmsm_er.ec:cmsm_er_monitor:2357]
    11:05:04 Connection Manager disconnected from tcp_1150uc8
    11:05:04 DEBUG:Arbitrator detected down server, svr=tcp_1150uc8,
    type=1 [cmsm_arb.c:arb_server_down:991]
    11:05:04 DEBUG:Arbitrator = cm_foc not active, waiting to detect
    primary [cmsm_arb.c:arb_server_down:1045]
    11:05:04 DEBUG:Arbitrator detected down server, svr=tcp_1150uc8,
    type=1 [cmsm_arb.c:arb_server_down:991]
    11:05:04 DEBUG:Arbitrator = cm_foc not active, waiting to detect
    primary [cmsm_arb.c:arb_server_down:1045]
    
    The last 2 messages will be generated in a loop. Please note the
    messages starting with 'DEBUG' string will be displayed only
    when
    the CM configuration file has the DEBUG parameter set to 1 or 2.
    

Local fix

  • Set the failover configuration to be the same on all connection
    managers in the cluster
    or
    get sure the CM with FOC disabled is started as the last one.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of Cluster environment with multiple Connection        *
    * Managers.                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Update to IDS-11.70.xC6                                      *
    ****************************************************************
    

Problem conclusion

  • Problem Fixed In IDS-11.70.xC6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC83770

  • Reported component name

    IBM IDS ENTRP E

  • Reported component ID

    5724L2304

  • Reported release

    B15

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-25

  • Closed date

    2012-10-30

  • Last modified date

    2012-10-30

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

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

Fix information

  • Fixed component name

    IBM IDS ENTRP E

  • Fixed component ID

    5724L2304

Applicable component levels

  • RB15 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGU8G","label":"Informix Servers"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B15","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 October 2012