Hi Mohammed,
Jeff's description is very close.
The sap_hostavailable command is executed in DR Agent when the the 'failing' host is a failover situation is once again available.
The Replication paths and queues from that old host to the current HADR primary are purged (we don;t want any stale activity from the old HADR primary to corrupt what has already occurred at the new HADR primary). And to perform that asction in Replication Server, the server is placed in hibernation mode - queues are purged - and the hibernation mode is released.
In your case, it appears some prior process placed the Replication Server in hibernation mode, but did not complete its task.
I noticed in the first jpeg, the sap_hostavailable command failed because it thought the command was being executed against the wrong host. Perhaps this is an indication the initial failover itself did not execute successfully? ('sap_status task' shows the status ofthe last asynchronous task executed - if failover was the last task, the status may still be viewable).
Regardless of how we reached this state, Marks recommendation to execute sysadmin hibernate_off in the Replication Server, then re-run the sap_hostAvailable command.
Regards,
Stephen