cancel
Showing results for 
Search instead for 
Did you mean: 

Lock in lock manager could not be set -> long text

Former Member
0 Kudos

Hi Experts,

We have a issue with the 124002 ID request for the ODS ZSDOD005 (request number REQU_6ROBVFEQ9SSOIJY5MDF2W9BTX).

It has green status, but if you open the monitor, the status is red.

If you search for more detail,  you can see the following message:

“Lock in lock manager could not be set -> long text”

The error refers to a lock in lock manager

Lock in lock manager could not be set -> long text

Message no. RSENQ009

Diagnosis

The lock in the lock manager could not be set.

An attempt is being made to set the lock in include LRSENQF00 in the form set_enqueue.

The lock table is table RSENQ_PROT_ENQ.

An attempt was made to lock the following object:

User/Object  = BWREMOTE/ZSDOD005

Object_typ/Action = ODS/UPD_ODS

Subobject  = REQU_6ROBVFEQ9SSOIJY5MDF2W9BTX

SubSubObject = 000001

This problem affects subsequent loads.

The InfoPackage ZPAK_6K641H103XV0MTRBAV9Q788IS loads data to three ODS ZSDOD001, ZSDOD003 and ZSDOD005.

None of the other ODS generated InfoPackage for 09.25.2013.

Our BASIS support team couldn’t see locks that impact in the procedure.

The InfoPackage ZPAK_6K641H103XV0MTRBAV9Q788IS is part of the Process Chain ZCP01 - Ventas (SD) Transaccional

If we tried to repeat the step we had obtained the following message:

  1. 02.10.2013 16:44:04 Job started
  2. 02.10.2013 16:44:04 Step 001 started (program RSPROCESS, variant &0000000032648, user ID BWREMOTE)
  3. 02.10.2013 16:44:04 Start process LOADING ZPAK_6K641H103XV0MTRBAV9Q788IS in run 7PZGWSRZS6GJGB093B9W72U5H of chain ZCP01
  4. 02.10.2013 16:44:04 Delta request REQU_6ROBVFEQ9SSOIJY5MDF2W9BTX is incorrect in the monitor
  5. 02.10.2013 16:44:04 A repeat needs to be requested
  6. 02.10.2013 16:44:04 Data target ZSDOD005 still includes delta request REQU_6ROBVFEQ9SSOIJY5MDF2W9BTX
  7. 02.10.2013 16:44:04 If the repeat is now loaded, then after the load
  8. 02.10.2013 16:44:04 there could be duplicate data in the data targets
  9. 02.10.2013 16:44:04 Request the repeat?
  10. 02.10.2013 16:44:04 Last delta incorrect. A repeat must be requested. This is not possible.
  11. 02.10.2013 16:44:05 Performing check and potential update for status control table
  12. 02.10.2013 16:44:05 Could not set request REQU_6ROBVFEQ9SSOIJY5MDF2W9BTX in DTA ZSDOD005 to red; terminated with error 5
  13. 02.10.2013 16:44:05 Job finished

This issue prevents subsequent loads of data.

It is abnormal that there is a green external status and a red one internal.

Could you, please check why are we having this lock error?

What are the steps to follow to avoid losing information or having it duplicated in this case?

Thanks,

Kiran

Accepted Solutions (0)

Answers (1)

Answers (1)

Manas_Vincit
Active Participant
0 Kudos

Hi Kiran ,

You can monitor Sm12 for this issue , Just check If it reached max no. of entries , if any lock overflow is there  . It will also appear in Sm21 system logs .

It is also possible some other jobs is consuming most of lock entries during that time ,causing this problem .

http://help.sap.com/saphelp_nw70ehp2/helpdata/en/47/ea5e27e97f486ee10000000a42189d/content.htm

Thanks

Manas Behra