Symptom
You installed a high availability HANA system H00 using 00 as the instance number, and then another HANA system H01 using intance number 01 on the same host.
After that you found the two HANA systems could not be started at the same time.
When H00 is running, you cannot start H01. You can see the following errors in the nameserver trace.
sr_dataaccess DisasterRecoveryPrimaryImpl.cpp(00637) : Listener cannot be started, because port 30101 is already in use!
sr_dataaccess DisasterRecoveryPrimaryImpl.cpp(00638) : A system replication primary uses replication ports in the range of the next instancenr (own=00, next=01)
sr_dataaccess DisasterRecoveryPrimaryImpl.cpp(00639) : Please check, that there is no other system on this machine using instancenr 01! This is just a hint and possibly not the root cause ..
sr_dataaccess DisasterRecoveryPrimaryImpl.cpp(00640) : In general the port range 30100-30199 must not be used by any other process when system replication is turned on!
PersistenceLayer PersistenceController.cpp(00604) : startup failed exception 1: no.2110008 (Basis/IO/Stream/impl/NetworkChannel.cpp:736)
Error address in use: $msg$, rc=98: Address already in use
Read more...
Environment
- SAP HANA Platform 1.0 all Revisions
- SAP HANA Platform 2.0 SPS00
- Single Container
Product
Keywords
primiary, secondary, replication, HA, cluster, Instance numbers, HANA high availability environment, Listener, replication port, Multitenant Database Containers , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.