Skip to Content
author's profile photo Former Member
Former Member

RSICENQ can not be locked

Hello All,

In our Porudction system we are facing a major problem of RSICENQ can not be locked.We have number of ODSs and their loads and activation are scheduled inbackground using autosys.

Whenever two activations are running simulataneously,one job definately fails with message "RSICENQ can not be locked".And one strange thing is that the activation fails during 600-700 seconds time.If any activation job crosses this figure ,it means the job is going to be successful.We are facing this problem currently everyday.Even right now SAP is also not able to provide proper solution for this.If anybody of you have faced this problem ,please let me know your views.

Thanks and regards

Yogesh Mali

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Jun 17, 2004 at 06:39 PM

    Hello Yogesh,

    I assume you are talking about message RT 040 (it always helps to specify the exact message number). Did you check the CCMS self-monitoring section (transaction RZ20)? It should contain more information.

    Also please check SAP note 716506. This might be the solution.

    Regards,

    Marc

    SAP NetWeaver RIG, US BI

    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.