Informix - Problem description
Problem IT09780 | Status: Closed |
AFTER FAILOVER INVOLVING PRIMARY, RSS AND CM... AN RSS SERVER PROMOTED TO HDR, THEN PRIMARY IS STILL REGISTERED AS AN HDR | |
product: | |
INFORMIX SERVER / 5725A3900 / B70 - IDS 11.70 | |
Problem description: | |
To reproduce issue, Bring up two instances of IDS 12.10.FC3 and use CM as an arbitrator. Join the two instances together, one as Primary, one as RSS. Bounce the Primary to initiate failover. During failover, allow the RSS to become HDR, then allow that HDR to become Primary. Bring former Primary back online as an RSS server. Attempt to promote the new RSS server to an HDR and you will receive the following: The primary node already has a secondary node. To promote the RSS node into a secondary, you need to convert the primary into a standard node or change the secondary node to the RSS node. So, the new Primary seems to also be registered as its own HDR. After this occurred, an attempt to upgrade the RSS from 12.10.FC3 to 12.10.FC5 was made, at which point the following message was received: 2015-06-26 01:13:23 cmalarm: Unhandled event 3003 cmalarm: EVENT_MSG='detected multiple primary servers for one cluster' cmalarm: EVENT_ADD_TEXT='Connection Unit apim: apim_config_VMWAHARKJWAIYIWM. CLUSTER apim has multiple primary servers: apim_config_VMWAHARKJWAIYIWM and apim_ha_config_VMWAHARKJWAIYIWM. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to IBM Informix Server 12.10.xC6 * **************************************************************** | |
Local Fix: | |
Solution | |
Problem Fixed In IBM Informix Server 12.10.xC6 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.06.2015 30.12.2015 30.12.2015 |
Problem solved at the following versions (IBM BugInfos) | |
12.10.xC6 | |
Problem solved according to the fixlist(s) of the following version(s) |