How to manually restore the High Availability Control-M Enterprise Manger primary node, when the HA failover hangs in the Control-M Configuration Manager GUI

Knowledge Article

How to manually restore the High Availability Control-M Enterprise Manger primary node, when the HA failover hangs in the Control-M Configuration Manager GUI
How to manually restore the High Availability Control-M Enterprise Manger primary node, when the HA failover hangs in the Control-M Configuration Manager GUI
Control-M/Enterprise Manager
Control-M/Enterprise Manager
Control-M Enterprise Manager in High Availability mode
Control-M/Enterprise Manager
Control-M/Enterprise Manager
Control-M Enterprise Manager in High Availability mode
- How to manually restore the High Availability Control-M Enterprise Manager Primary node, when the HA failover hangs in the Control-M Configuration Manager GUI?
- What to do if the Primary Node of the Control-M Enterprise Manager HA fails to complete or hangs during failover?

To restore the primary or secondary node of the Control-M Enterprise Manager, you can use the "em emcha" command with the appropriate parameters.

To restore the primary node on the Primary Control-M Enterprise Manager host, run the following command:
em emcha -restore primary

If only the secondary Control-M Enterprise Manager is accessible, run the following command to restore it as a secondary:
em emcha -restore secondary

The syntax for the em emcha command is: 
cha [-restore primary|secondary]
Control-M/Enterprise Manager
Control-M/Enterprise Manager
Control-M Enterprise Manager in High Availability mode
Attachment(s):