Skip to Content

RSPLSE Locks_Concurrency Lock

Hi,

We are on SAP NW BPC 10,BW7.3,EPM-SP14.

One user's clear DMP failed with Error Obtaining Concurrency lock(Foreign_lock)message.

I have checked RSPLSE locks.At that time no locks were there.

Checked DMP logs.At that particular time there was a currency conversion job running.

But the organizations in Clear and Currency Conversion DMPs are different.

As per my understanding,locks will not happen even at that time some users trying to read the data.

Issue2:

And today I have observed RSPLSE lock entry today.

One job is currency conversion and other job is tax calculation.Here also organizations are not same.

But still there is an entry in RSPLSE.

So what are the overlapping criteria for locking mechanism?

Thanks,

Manohar

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Oct 24, 2015 at 12:11 AM

    Hi Manohar,

    Issue 1: did you see concurrency lock that has time later than error in your DMP? If yes, then your error was overridden by next error. RSPLSE keeps only last error. Additionally, do you have 1 App server in that box or more than 1?

    Issue 2: BPC locks data sometimes on each individual member and sometimes on intervals. So, if one process locked A - C and another is trying to lock B - you'll get an error. So, please check in those 2 lock if at least one of them is on interval? Also, please check if you see 2 user IDs in Locking Conflict screen or second ID field is empty?

    Regards,

    Gersh

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Manohar,

      Yes, you can control that.

      Perhaps one of the Packages was running on multiple Org members. BPC decided that it's too many to lock them individually and locked as an interval. Org member(s) for the other Package probably fell inside that interval.

      Let's say 1st Package ran on Orgs ABC, ...,  KLM and the 2nd Package ran or Org DEF. 1st Package will create a lock on ABC - KLM and 2nd will try locking DEF. This will create a locking conflict.

      So, solution would be to make BPC think that 1st lock doesn't have enough members to lock them as interval. For this you have to find out how many members of Org Dimension can be in one Package and make RECLEVEL_NR and INTERVAL_NR at least that big. Then BPC will lock them individually and if 2nd Package runs on different Orgs they won't lock each other.

      Just don't make those parameters too big because it will slow the locking down.

      Regards,

      Gersh

  • Oct 26, 2015 at 02:39 AM
    Add comment
    10|10000 characters needed characters exceeded

  • Oct 23, 2015 at 03:00 PM

    Hi Manohar,

    please read note 928044 (sizing of the BW enqueue server) and the BW standard-specific usage of the BW lock server.

    Regards,

    Gregor

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Manohar,

      - ensure that you use the right BPC generated InfoCube name (something /CPMB/...)

      - if nothing was explicitly maintained in RSPLSE all characteristics are lock relevant (RSPLSE, second tab, table on the right hand side; don't forget to press ENTER after input of the technical InfoCube name

      - if there is no lock relevant characteristic each lock request would try to lock the whole InfoCube

      - the most relevant RSPLSE settings in the BPC usage are explained in the above sizing note, so make 'reasonable' settings for

      -- Lock Attempts

      -- Wait Time in Seconds

      (read the F1 help...) in RSPLSE, in expert mode. And read the BPC Administration Guide, Write Back Parameters.

      Regards,

      Gregor