IBM Support

IC61754: CONNECTION MANAGER FAILS TO REGISTER ON PRIMARY DATABASE SERVER WHEN USING MULTIPLE CONNECTION MANAGERS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • With multiple connection managers running in a cluster, if the
    primary node is bounced and failover does not occur, then the
    active failover arbitrator within that connection manager can
    detect when the original primary is active again. However, the
    inactive failover arbitrators running on the remaining
    connection managers are not able to detect when the original
    primary is active.
    .
    The cm log continue to display the following error message:
    Arbitrator = xxx_cm not active, waiting to detect primary
    [cmsm_arb.c:938]
    

Local fix

  • Bounce the connection manager.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users using the connection manager oncmsm.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * With multiple connection managers running in a cluster, if   *
    * the primary node is bounced and failover does not occur,     *
    * then the active failover arbitrator within that connection   *
    * manager can detect when the original primary is active       *
    * again. The inactive failover arbitrators running on the      *
    * remaining connection managers are not able to detect when    *
    * the original primary is active.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Please upgrade to ClientSDK 3.50.xC6 and above.              *
    ****************************************************************
    

Problem conclusion

  • Problem fixed in ClientSDK 3.50xC5.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC61754

  • 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

    2009-06-26

  • Closed date

    2010-01-22

  • Last modified date

    2010-01-22

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

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

    IT01452

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:
22 January 2010