3430557 - During system replication takeover and failback the former primary, new secondary site database does not start

After restarting the VM of a primary site database in a system replication setup an issue occurred during failback procedure where the new secondary site database (former primary) does not start.

When the former primary is initialized as new secondary it does not start, some services are showing red status.

The traces of the non starting service show errors:

Example:

dpserver

e Stream           NetworkChannel.cpp(01019) : [6a4855f3c0ca1778,0.0.0.0:44046,-,UNK,0] Cannot bind to a local address: tcp port 4##46 on one of local interfaces => socket[22445], user ""dd-agent:###"
e sr_dataaccess    DisasterRecoveryPrimaryImpl.cpp(01349) : Listener cannot be started, because port 4##46 is already in use!

 "Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

SAP HANA Platform Version 2.0

HANA, start, Cannot bind to a local address, Listener cannot be started, is already in use, port , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , Problem