When performing "Fallback to Primary" for Control-M/Server, the progress bar hangs at 60% and Process Dialog stuck at "Primary host took control" in the Control-M Configuration Manager (CCM) but the fallback itself completes successfully

Knowledge Article

Article Number

000292390

Old Article Number

000131374

Article Type

Solutions to a Product Problem

Title

When performing "Fallback to Primary" for Control-M/Server, the progress bar hangs at 60% and Process Dialog stuck at "Primary host took control" in the Control-M Configuration Manager (CCM) but the fallback itself completes successfully

Summary

Product

Control-M/Server for UNIX and Microsoft Windows

Component

Control-M/Server for UNIX and Microsoft Windows

Applies to

Control-M/Server ; all versions

Problem

When performing "Fallback to Primary" for Control-M/Server, the progress bar hangs at 60% and the Process Dialog is stuck at "Primary host took control" in the Control-M Configuration Manager (CCM) but the fallback itself completes successfully where it shows running on "Primary (<machinename>)"

No issues with the "Failover to Secondary"

Cause

Primary Configuration Agent (CA) disconnects from the database prior to the Fallback and as a consequence fails to update the CMR_PROGRESS table.
As a result, the progress dialog in CCM does not show the completion of the fallback

Solution

Restart the Primary Control-M/Server Configuration Agent using shut_ca and start_ca commands prior to "Fallback to Primary" in Control-M Configuration Manager (CCM)

Note: In this situation the Control-M/Server fall back is successful, as indicated by the "Running on Primary" message on Control-M/Server properties panel in the Control-M Configuration Manager. The fail over status bar can safely be ignored and should clear automatically in a few days or with the next fail over.

Attachment(s):