When the primary SCADA node is in Maintenance Mode, iClients consider the secondary SCADA node to be the active SCADA node. The Database Manager behaves differently than the other iFIX applications on an iClient in that it can connect to the primary SCADA node in Maintenance Mode.
IMPORTANT: This connection between the Database Manager and the SCADA node continues even when there is a SCADA role change, which may result in a connection to a standby node. To prevent this situation, always enter Maintenance Mode before connecting to a SCADA node and always close the Database Manager before exiting Maintenance Mode.
When the Database Manager runs on a remote client, only one of the SCADA nodes is shown in the list of available nodes. When a SCADA node is in standby or when its partner is in Maintenance Mode, the SCADA node is considered unavailable.
When the Database Manager runs locally on one of the SCADA nodes, the local SCADA node is added to the list of available nodes. Both SCADA nodes are displayed in the list of available nodes. The local SCADA node is considered available even when it is in standby, or its partner is in Maintenance Mode. A warning message displays if you select the local SCADA node when the node is in standby or its partner is in Maintenance Mode.
IMPORTANT: If the Database Manager is run locally on the secondary SCADA node, take extra care to ensure that the changes made do not disrupt iClient operations and that any process database files saved will not be overwritten when Maintenance Mode is exited.
TIP: Check the Database Manager title bar, which shows the logical and physical name of the SCADA nodes and whether the connected SCADA node is the primary or the secondary node.
