Manual failover appears to hang

When the NEWLOGPATH database configuration parameter is set to specify a different location for the transaction log files, the second failover that is triggered after this parameter is set appears to hang.


The second manual failover takes longer than expected to complete.

Resolving the problem

No intervention is needed. The takeover command typically runs within the value of the peer window setting. Subsequent failovers will run normally.

Do not interrupt the failover process. Doing so leaves the database in an inconsistent state.