cancel
Showing results for 
Search instead for 
Did you mean: 

Ensmon showing Enque Replication status not enabled in HA installed system

Former Member
0 Kudos

Hello Experts,

In our client system which is installed as High Availability system in MSCS cluster the command ensmon.exe pf=D:\usr\sap\SID\SYS\profile\SID_ERS01_HOSTNAME showing no replication server is connected as shown below

Replication is enabled in server, but no repl. server is connected

But it has to show repl.server is connected.

System Details :

ECC 6.0 SR3 Dual Stack System installed on two nodes with CI & DI with different system numbers.

Applications on both nodes are up and running and the application on second node is working as DI during normal time.

Enque replications services are up and running on both nodes.

Kindly suggest on what should be the enque replication server status if node2 is working as DI during normal time.

Thanks,

Bharath.

Accepted Solutions (0)

Answers (2)

Answers (2)

Sriram2009
Active Contributor
0 Kudos

Hi Reddy


In windows MSCS environment ERS instance is acting as active/ passive mode, In which node owning the SAP Cluster Group in that node ERS will be active another node will be passive mode. For this refer the screen shot


In both cluster node ERS installed on the local disk, in both system instance numbers for ABAP & JAVA should same 


System Details :

ECC 6.0 SR3 Dual Stack System installed on two nodes with CI & DI with different system numbers.

For example  In CI - Node 1 instance 01 & DI - Node 2 instance number 00

in both cluster node system number should be same,  because when the resources are fail-over from node 1 instance number 01 to node 2 instance number 00,in that time all the client SAPGUI configuration have to change

In windows MSCS environment all the instance number should be same to another node.



Regards

Sriram

Former Member
0 Kudos

Hi Sriram,

Thanks for your content.

I have seen ERS concept in below link

Enqueue Replication Server Part 1 - What is ERS - Netweaver Technology - SCN Wiki

And in this it is stating that locks are carried to Node2 by ERS server in case of failover.

But those locks on node2 should be deleted manually from sm12?

Kindly suggest on this.

Thanks,

Bharath.

Sriram2009
Active Contributor
0 Kudos

Hi Bharath

    No need to clear the locks manually, ERS instance will takecare to clear the SM12 & SAP on Windows MSCS internal locks.

Regards

Ram

Former Member
0 Kudos

Sriram,

I have checked with system failover in our cluster environment but in Node2 the locks are still held on tables which are subjected for modification before failover.

I have checked with ERS status and it is showing same no of lock entries before and after fail over.

Kindly suggest on where to analyze to fix this for  ERS instance will takecare to clear SM12 locks.

Thanks,

Bharath.

Former Member
0 Kudos

bharath reddy c wrote:

I have checked with system failover in our cluster environment but in Node2 the locks are still held on tables which are subjected for modification before failover.

Can you explain in more detail instance distribution between nodes before system failover checking? What instance are you tried to fail over?


I have checked with ERS status and it is showing same no of lock entries before and after fail over.

Everything works as designed. The main goal of ERS instance is to preserve lock table entries.

Former Member
0 Kudos

Hi Roman,

We have ASCS,SCS and DATABASE instances are installed on cluster for failover.

Central instance with system no 05 is installed on local disk of Node1.

Dilogue instance with system no 06 is installed on local disk of Node2.

ERS instance for ABAP & JAVA are installed on local disks of both nodes with instance numbers

20 & 21 respectively.

Kindly suggest on how to release the locks in sm12 after failover from Node1 to Node2?

Thanks,

Bharath.

Former Member
0 Kudos

What are the reasons why you are trying to to release locks? The main goal of ASCS/ERS instances is to preserve these locks.

Former Member
0 Kudos

Roman,

After failover users get disconnected and again connected to dialogue instance at that point when user1 try to do same activity then he is going to get the table is locked by the user1.

Kindly suggest on how to deal in that situation.

Thanks,

Bharath.

Former Member
0 Kudos

When user attempts to connect to system a warning about already opened sessions for that user appears. It must select option to close all already opened sessions and all locks will be released automatically.

Sriram2009
Active Contributor
0 Kudos

Hi Bharath

Kindly refer the links about your query's

Replication and Failover (SAP Library - The SAP Lock Concept (BC-CST-EQ))

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/405f3bee-0c69-2a10-7b84-af7c1cb43...

In this PDF refer the Chapter 8 High Availability with Microsoft Cluster Service and ERS testing Chapter 8.4.1.1

Regards

Ram

Former Member
0 Kudos

Experts,

In link   http://scn.sap.com/docs/DOC-25454

it is referring for Threshold in MSCS cluster as below

What is the "Threshold"?

Within MSCS the term Threshold is referred to the number of failures before a resource fails over to the second cluster node. Please note that if you are using the Replication Server it is very important to set the “Threshold” to “0”. Otherwise the replication will not work

Kindly suggest where to set the Threshold value in MSCS cluster.


Thanks,

Bharath.

Former Member
0 Kudos

Experts,

Now it is showing enque replication is active after changing the instance resource name as per the value of enque/enrep/HAResourcename parameter in ERS instance profile.

The resource name was SAP_SID_00_Instance and i changed to the value of

enque/enrep/HAResourcename parameter.

Thanks,

Bharath.