Informix - Problem description
Problem IT40493 | Status: Closed |
AFTER A MODE CHANGE TO QUIESCENT/SINGLE-USER, CONNECTION MANAGERNO LONGER ALLOWS DIRECT ACCESS TO THE SERVER | |
product: | |
INFORMIX SERVER / 5725A3900 / E10 - | |
Problem 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 in cluster clst is currently active. You cannot change the primary server to 15:11:48 CLUSTER clst has multiple primary servers: and . 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 . CLUSTER clst has multiple primary servers: and . 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 . CLUSTER clst has multiple primary servers: and . 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 is in on-line mode. Afterwards connections to an SLA relaying straight to this secondary would get 908: Attempt to connect to database server () 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. | |
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. * **************************************************************** | |
Local Fix: | |
Only restarting the Connection Manager will solve such problem. | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 14.10.xC9. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 14.10.xC9. * **************************************************************** | |
Comment | |
Fixed in Informix Server 14.10.xC9. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.04.2022 30.09.2022 30.09.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |