IBM Support

IT40493: AFTER A MODE CHANGE TO QUIESCENT/SINGLE-USER, CONNECTION MANAGERNO LONGER ALLOWS DIRECT ACCESS TO THE SERVER

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

  • Putting a secondary server into quiescent or single-user mode
    for a period of time, then switching it back to multi-user mode,
    can leave a Connection Manager confused about the secondary
    server's state.
    
    Immediately after returning to multi-user mode, the Connection
    Manager would report 'two primaries' like this:
    
    15:11:48 Warning: The primary server named <primary_name> in
    cluster clst is currently active. You
    cannot change the primary server to <secondary_name>
    15:11:48 CLUSTER clst has multiple primary servers:
    <primary_name> and <secondary_name>.
    A cluster must contain only one primary server.
    Stop the Connection Manager, reconfigure the servers or modify
    the
    CM config file, and then restart the Connection Manager.
    15:11:48 <primary_name>.
    CLUSTER clst has multiple primary servers: <primary_name> and
    <secondary_name>.
    A cluster must contain only one primary server.
    Stop the Connection Manager, reconfigure the servers or modify
    the
    CM config file, and then restart the Connection Manager.
    15:11:48 ALARM 3003 detected multiple primary servers for one
    cluster <primary_name>.
    CLUSTER clst has multiple primary servers: <primary_name> and
    <secondary_name>.
    A cluster must contain only one primary server.
    Stop the Connection Manager, reconfigure the servers or modify
    the
    CM config file, and then restart the Connection Manager.
    15:11:48 Server <secondary_name> is in on-line mode.
    
    
    Afterwards connections to an SLA relaying straight to this
    secondary would get
    
      908: Attempt to connect to database server (<sla_name>)
    failed.,
    
    for at least a couple of seconds, under certain conditions even
    forever (until CM restart).
    
    These conditions apparently are:
    the secondary server's cluster name (replication port) is one of
    its DBSERVERALIASES (so not the DBSERVERNAME)
    and that alias is configured as its HA_ALIAS.
    
    Interestingly, while an SLA specifically picking this secondary
    would no longer work, another one picking this secondary more
    randomly would eventually pick it and connection would succeed.
    
    An SLA configured to connect to the primary initially would run
    on
    
      761: INFORMIXSERVER does not match either DBSERVERNAME or
    DBSERVERALIASES.
    
    Then, once successful again, it would connect to the secondary
    rather than primary - which again might be consistent with a CM
    confusion on who all is a primary.
    

Local fix

  • Only restarting the Connection Manager will solve such problem.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of Informix Server prior to 14.10.xC9.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Informix Server 14.10.xC9.                        *
    ****************************************************************
    

Problem conclusion

  • Fixed in Informix Server 14.10.xC9.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT40493

  • Reported component name

    INFORMIX SERVER

  • Reported component ID

    5725A3900

  • Reported release

    E10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-04-04

  • Closed date

    2022-09-30

  • Last modified date

    2022-09-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

    INFORMIX SERVER

  • Fixed component ID

    5725A3900

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSGU8G","label":"Informix Servers"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"E10"}]

Document Information

Modified date:
01 October 2022