Skip to Content

Do we need to delete Enqueue Locks Manually On Node2 After Failover In cluster Environment?

Hello Experts,

As per ERS concept as in below link that locks are carried to Node2 by ERS server in case of failover.

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

If the user1 wants to resume the last activity of Node1 in Node2 then it will show the table is being locked by

the user1(same user name)

In this case do we need to delete locks on node2 manually from sm12?

For every time during failover do we need to perform this activity?

Kindly suggest on this.



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Feb 10, 2014 at 08:03 AM

    Hi Bharath,

    What's are the components running on Node1 & what's are the components failed over to Node 2. If CI or any app server running on Node1 and user's session was part of that app server then I think you need to delete lock entry manually after the user logoff from the system & not active BTC jobs running with user's name.

    If my assumption is correct then I think this is program crash situation as mentioned by Clebio.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Bharath

      1. I can only disable ERS if the system is not configured for load balancing. Users will connect to CI during normal operation and will connect to DI with another entry in logon pad.

      If you are Disable the Enqueue replication server, In SAP system Enqueue service will not work. for that kindly refer the below screen shot

      2. I have to delete some sm12 locks manually after each failover from node1 to node2.?

      In this case you can raise the SAP OSS ticket, in better way they can explain & guide you



      Capture.JPG (85.4 kB)
  • Posted on Feb 08, 2014 at 10:36 PM

    you should never manually delete locks after a failover.

    Indeed you should never manually delete locks in any situation. The release of a lock is a task to the program that create it,

    If a program returns an error, after the failover, regarding an object already locked, the program is facing some problem. The lock operations in enqueue should be transparent to the program during and after the failover.

    This kind of situation (object already locked) only can occurs if the program crash due some issue and is not able to handle already created locks.



    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.