Live Cache start extremely slow

[Former Member]

Hi,

Post system copy, our LC takes a very very very long time to start.

Version: 7.7.07.35.

It eventually does start but the start status remains yellow.

The log says:

Start with Script lcinit (Using Function Module)

Start:     05/31/2012 22:04:52

End:       Unknown

----------------------------------------------------------

The action was terminated before this step of the process was marked as

complete. The cause for this cannot be determined. Possible causes:

short dump or error message.

& Postprocessing Report SLCA_LCK_SYNCHOWNERS is not executed.

The Max DB logs say return code 0.

Please advise..what could be the issue.

The LC checks etc. are all Ok..

Thank you.

-S.

[former_member229109]

Hello,

1. As SAP customer you have the option to create the SAP message and get SAP support.

2. From the posted information I see that you didn't check KnlMsg liveCache log.

    Was the liveCache restarted in admin & then shutdown/crashed before to reach the online status?

Regards, Natalia Khlopina

[Former Member]

Hi Natalia,

Thank you for your reply !

I did check the KnlMsg logs & they all say return code 0.

Also, the LC consistency checks are Ok & "Operational State" & "Status" in LC10 is green.

The only issue is the long time it takes for Stop/Start & the yellow sign at "Last Start/Stop action" with the error as described above.

We used the regular Start/Stop action via LC10.

I found some Notes but they apply to old LC versions..

Thank you.

Saba.

[former_member229109]

Hello Saba,

Did you check dbm.prt file & saw the RC 0 for the restart of the liveCache online?

Best will be if you create the SAP message and get SAP support.

First the KnlMsg file need to be checked after the liveCache restart online or during restart online to see which step took long time.

Check RAM and CacheMemorySize parameter value to see if you have RAM memory for the memory allocation during the liveCache restart.

Regards, Natalia Khlopina

[Former Member]

Hi Natalia,

Thank you so much for your replies !!!

I do see this one message repeatedly in the Knlmsg file..post this message the state goes to admin Ok:

TASKING    12886:  Maximum single aligned task stack size  1500KB

Thread        0x1 Task      -  2012-05-31 22:04:59     TASKING    12886:  Size of single task guard area     4KB

Thread        0x1 Task      -  2012-05-31 22:04:59     TASKING    12886:  Task stack chunk area [ 0x1791580000 - 0x17de8b8fff ]

Thread        0x1 Task      -  2012-05-31 22:04:59 WNG TASKING    12446:  Protecting task stack at [ 0x1791580000 - 0x1791580fff ] failed (continue unprotected)

Thread        0x1 Task      -  2012-05-31 22:04:59 WNG TASKING    12446:  Protecting task stack at [ 0x17916f8000 - 0x17916f8fff ] failed (continue unprotected)

Thread        0x1 Task      -  2012-05-31 22:04:59     TASKING    12886:  Physical memory used for task stacks 1144500KB

Thread        0x1 Task      -  2012-05-31 22:04:59     TASKING    12886:  Physical memory used for guard areas   3836KB

Also, I see the below in the dbm.prt file:

1 DBMSrvCo A DBM Server client connection was established at 2012-05-18 10:04:39 (client process has process ID 20775014

2012-05-18 10:04:39 0x01030046 INF        283 DBMSrv   Command 'db_standby <server>' is being executed.

2012-05-18 10:44:41 0x01030046 ERR     -24580 DBMSrv   ERR_COMMAND_FAILED: Command 'db_standby' has ended and failed with return code -100.

                    0x01030046 ERR     -24778 DBMSrv   -100,ERR_DBMSRV_NOSTART: Could not start DBM

2012-05-18 10:44:41 0x01030046 INF          2 DBMSrvCo A DBM Server client connection was released (client process has process ID 20775014 on computer

2012-05-18 10:44:41 0x009a00fe INF        419 DBMSrv   Command 'exec_lcinit' has ended with return code 0.

I'll raise the OSS if nothing else works out..

Please advise n thank u !

-S.