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

initialize the liveCache

Good Morning

I’m Michele. I have a problem with livecache.

I have installed SAP SCM 4.0 server.

I have installed SAPliveCacheServer for SAP SCM Server 4.0.

I have problem with initialization livecache istance.

I have executed the following instructions:

Setting up Connection to the liveCache Instance

Before checking the connection, you must initialize the liveCache instance using transaction


1. Start the SAP SCM instances:

2. Log on to the SAP SCM System as user DDIC (production client).

3. Apply SAP Note 305634 RFC destination for global working on the liveCache

4. To maintain the liveCache connection in table DBCON, call transaction LC10.

The liveCache: Initial Screen appears.

5. In the Name of database connection field, enter LCA and then choose Integration.

6. Name the physical liveCache <LC_NAME>, the liveCache server <LC_HOST>, user data

and the corresponding passwords and make sure that Central Authentication is enabled.

8. Enter the administration report /SAPAPO/DELETE_LC_ANCHORS in field Follow-up

Procedures of section Initialize liveCache.

9. Save your entries.

10. To initialize the liveCache instance LCA:

a. Choose Back (F3). The liveCache: Initial Screen re-appears.

b. Enter LCA in the Name of database connection field.

c. Choose liveCache: Monitoring.

When I execute monitoring appear following message:

Name and Server LCA – bw


Command: dbm_version

Error: DBM: Error

Return Code: -2

Error message: ERR_USRFAIL: user authorization failed

Please inform me how can I solve this problem

Thank you for your collaboration.

Best regards

Michele medaglia

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on May 18, 2005 at 12:19 PM

    Hello Michele,

    we handle liveCache issues really only over OSS/CSS messages, so I will have to ask you to open such a message (for queue BC-DB-LVC).

    From your problem description, you seem to have a problem with the user authorization. You could try to connect the following:

    1. dbmcli -d <SID> -u <dbm-user>,<pwd> db_state

    (The dbm-user normally is 'control'.)

    2. Test the LCA connection in transaction DB59.

    Please put any output of the above in the OSS message.

    Kind regards,


    Add a comment
    10|10000 characters needed characters exceeded

    • Hello David,

      yes, from a certain Basis SP, you can use the transaction DB59 to integrate both OLTP and liveCache instances into your system, similar to what you normally do in LC10 - Integration. One extra feature in transaction DB59 is the option to test the connection. That is why I wrote it.

      But as said, for liveCache issues, we prefer official OSS/CSS messages.



  • author's profile photo Former Member
    Former Member
    Posted on May 19, 2005 at 12:36 PM

    The cause of your problem is probably incorrect user credentials. Check the SAPDB users (CONTROL, SUPERDBA, SAPR3). There are numerous notes in OSS available which describe how to change/recreate these users, for example:

    11593, 644332, 39439, 653887, 442944, 739985.

    Please check the logfiles in /sapdb/data/wrk/<SID>:

    knldiag.err, lcinit.log

    Also the system log or ABAP dumps can be checked.

    Goodluck. If you need more help, please post the logfiles, etc in this message.

    Best regards,

    -Chung Yan Lam.

    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.