Timeout in LC10 -> "Determining Version Info"

[former_member1012268]

Hello World,

after a somewhat messy upgrade to SP14 on our SCM5.0 system (in preparation to the final upgrade to SCM7),  we can't connect to our LiveCAche no more.

The only reason why I am keeping this thread open is that now the short dumps are gone, but the system won't connect to the LiveCache no more.

Calling LC10 results in the following error (after being stuck a while trying to retrieve version info):

>DBM_EXECUTE

>dbm_version

>command timeout exceeded

We can start and stop the LC DB just fine via dbmcli.

Here is the enum info:

dbmcli -U c db_enum

OK

APP /sapdb/APP/db                           7.6.00.36 fast running

APP /sapdb/APP/db                           7.6.00.36 quick offline

APP /sapdb/APP/db                           7.6.00.36 slow offline

APP /sapdb/APP/db                           7.6.00.36 test offline

LCP /sapdb/LCP/db                           7.6.02.08 fast running

LCP /sapdb/LCP/db                           7.6.02.08 quick offline

LCP /sapdb/LCP/db                           7.6.02.08 slow offline

LCP /sapdb/LCP/db                           7.6.02.08 test offline

APP -> APO SCM5.0 Production

LCP -> LiveCache AddOn

I sure as heck didn't touch the LC database, so why is it now acting like its no longer in talkative mood?

Any help with this is highly appreciated.

PS: The box runs on Linux SLES12

[JamesZ · Accepted solution]

Dear Donaldo,

what is the result from db59 connection test? please give me with the screenshot.

Best regards,
James

[former_member1012268 · Accepted solution]

[former_member229109 · Accepted solution]

Hello,

from posted information, you have the symptom from the SAP note:

1128989 - "command timeout exceeded" with DBMRFC session mode

- Check on the workaround in this note.

- I recommend on workaround, as you will run the liveCache/client on appl. server upgrade as one of the steps from upgrade SCM system & the issue should be resolved.

Best regards, Natalia Khlopina

[JamesZ · Accepted solution]

Hello,

Seems RFC SAPDB_DBM_DAEMON is not working?

Please check the recommendation from 'Natalia Khlopina', this is very important.

Best regards,
James

[former_member1012268 · Accepted solution]

Unfortunately that note is very misleading, as the DB update it recommends screwed up our whole system.

Not even SAP would start anymore afterwards.

But by sheer accident I found in one of the log files the correct answer.

MaxDB version 7.0.6.x with LC requires client version 7.0.7.x and once I installed that one (not via SDBUPD but via SDBINST) LC10 worked again like a charm.

SDBUPD would have upgraded the whole DB, but SDBINST allowed for just the new client version to be installed.

But you were right about SUM later on demanding an upgrade of the whole DB to 7.0.9, which included a client upgrade and kind of made the whole procedure with upgrading the client seperately mood & void.