Solution : https://service.sap.com/sap/support/notes/1054467 (SAP Service marketplace login required)
Summary :
This SAP Note addresses an issue where SAP instances fail to start due to the local hostname resolving to a loopback address. This occurs when the SAP ABAP Server's dispatcher performs a check for unique IP addresses, crucial for the cluster interface. From specific patch levels onwards, instances won’t start if the hostname points to a loopback IP. A temporary workaround involves setting the “rdisp/tolerate_loopback_addr” parameter, though this could lead to issues when accessing cluster tables. For a permanent fix, ensure hostnames resolve to unique network IP addresses. Verification can be done using the 'niping' tool to ensure proper IP configuration.
Key words :
prevent data losses caused, > niping -vhostname/nodeaddr verification, coinciding cluster time stamps, '%windir%\system32\drivers\, standalone test systems, sap abap server, local service resolves, mini test system, dispatcher emergency shutdown, general database interface
Related Notes :
| 1229914 | Composite SAP: NiMyAddrVerify and DBIF_RSQL_INVALID_REQUEST |
| 954717 | Error in NiMyAddrVerify |
| 520658 | Couldn't get host's IP address while accessing cluster |
| 480610 | Coinciding cluster time stamp |
| 21151 | Multiple Network adapters in SAP Servers |