Symptom
The ERS instance does not start. Below errors are shown in the following trace files (that are located in the "work" directory of the ERS instance - “/usr/sap/<SID>/ERSxx/work").
dev_enrepsrv
[Thr 139910247598976] Replication server start with instance number <SCSID set in instance profile>
[Thr 139910247598976] *** ERROR => RepIOConnector:constr.: NiHostToAddr for '' failed with rc -2 [enrepservio. 117]
[Thr 139910247598976] *** ERROR => RepServer: main: Cannot connect to enqueue server: RepIOConnector: cannot resolve hostname [enrepserv.cp 729]
stderr0
(1794491) Starting local Command:
Command: er.sap<SID>_ERS<instance_number>
pf=/usr/sap/<SID>/ERS<instance_number>/profile/<SID>_ERS<instance_number>_<hostname>
NR=<SCSID set in instance profile>
er.sap<SID>_ERS<instance_number>=>sapparam(2): fopenU("/usr/sap/<SID>/ERS<instance_number>/profile/<SID>_ERS<instance_number>_<hostname>" ","r"): No such file or directory
Cannot connect to enqueue server: RepIOConnector: cannot resolve hostname
Read more...
Environment
- SAP NetWeaver based product
- ABAP Platform based product
Product
Keywords
Enqueue Replication Server, enserver, enrepserver, fail, ERS not working, High Availability, failover, replication, enque, doesn't,cannot start,_PF,DIR_PROFILE , KBA , BC-CST-EQ , Enqueue , Problem
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.