Livecache lock server not accessible after system refresh

[Former Member]

Hello,

I have performed a refresh of SCM + livecache from production to QA when starting the livacache from LC10 i get a message Livecache lock server not accessible. The livecache is started but when i look at the status there is a warning SQL access not possible.

I did an export of the config table and reimport and the server named are correctly defined for:

LCA

LDA

LEA

From the administration report of LCA

Initialize livecache

Follow-up Processing: /SAPAPO/DELETE_LC_ANCHORS

Start Livecache

Follow-up Processing: SLCA_LCK_SYNCHOWNERS

By running those program in se38

SLCA_LCK_SYNCHOWNERS (Livecache lock server not accessible)

SLCA_NON_LC_RELEVANT_CLIENT (Could not create a connection to livecache)

I checked and the relevant client is selected.

When i check the alert monitor from livecache - lca - connectivity - dbmrfc and native sql is in red with the following message:

SQL Statement Execution Instance Online, but no SQL access possible.

Also from SM21 i have errors saying Database error -4025 at CON

Let me know if you already encountered this issue and how it was resolved.

Thank you,

Martin Mayer

Edited by: Martin Mayer on Jan 4, 2012 4:02 PM

Edited by: Martin Mayer on Jan 4, 2012 4:07 PM

[former_member188883 · Accepted solution]

Hi Martin,

Refer to thread

Similar problem is mentioned and resolved by adjusting the user .

Regards,

Deepak Kori

[Former Member · Accepted solution]

I have checked that tread already the thing is when performing the check In db59, I´ve the LCA,LDA,LEA it fails.

1. Connect. test with "dbmcli db_state" Successful

2. Connect. test with command mode "dbmrfc db_state" Successful

3. Connect. test with session mode "dbmrfc db_state" Successful

4. Connect. test with "native SQL" ( LCA ) No connection

SQL Code: 4025

Edited by: Martin Mayer on Jan 4, 2012 5:26 PM

[Former Member · Accepted solution]

Thanks finally it was something due to the user used from the LC10 integration after resetting the values and restarting livecache the issue was fixed.

Martin Mayer

Edited by: Martin Mayer on Jan 4, 2012 7:18 PM