unable to see the CI in sm51

[Former Member]

hi experts.

we are unable to see the central instance in sm51but we can able to all the application servers.

when i checked in sm21 i found the below logs.

12:17:36 DIA 006 100 SCOOPER EG D > Error locking table TBTCO

12:17:36 DIA 006 100 SCOOPER EG D > Error locking table TBTCO

12:17:36 DIA 006 100 SCOOPER EG D > Error locking table TBTCO

12:17:36 DIA 006 100 SCOOPER EG D > Error locking table TBTCO

12:17:36 DIA 006 100 SCOOPER EG D > Error locking table TBTCO

12:17:36 DIA 006 100 SCOOPER EG D > Error locking table TBTCO

12:17:36 DIA 006 100 SCOOPER EG D > Error locking table TBTCO

12:17:36 DIA 006 100 SCOOPER EG D > Error locking table TBTCO

12:17:36 DIA 006 100 SCOOPER EG D > Error locking table TBTCO

12:17:36 DIA 006 100 SCOOPER EG D > Error locking table TBTCO

12:17:36 DIA 006 100 SCOOPER EG D > Error locking table TBTCO

12:17:38 DIA 006 100 SCOOPER EG D > Error locking table TBTCO

12:17:38 DIA 006 100 SCOOPER EG D > Error locking table TBTCO

12:17:38 DIA 006 100 SCOOPER EG D > Error locking table TBTCO

12:17:38 DIA 006 100 SCOOPER EF W Cannot generate job count for job RFITEMGL

12:17:38 DIA 006 100 SCOOPER EG D > Error locking table TBTCO

12:17:41 DIA 006 100 SCOOPER EG D > Error locking table TBTCO

12:17:49 DIA 006 000 SAPSYS GI 0 Error calling the central lock handler

12:17:49 DIA 006 000 SAPSYS GI 2 > Unable to reach central lock handler

12:17:49 DIA 006 000 SAPSYS GH Z > Previous Message was Suppressed 1302 Times

12:17:51 DIA 012 100 EARCE GI 0 Error calling the central lock handler

12:17:51 DIA 012 100 EARCE GI 2 > Unable to reach central lock handler

12:19:20 DIA 009 100 ENGUYEN GI 0 Error calling the central lock handler

12:19:20 DIA 009 100 ENGUYEN GI 2 > Unable to reach central lock handler

12:19:20 DIA 009 100 ENGUYEN GH Z > Previous Message was Suppressed 9 Times

12:20:22 DIA 006 100 ZMOHAMMED GI 0 Error calling the central lock handler

12:20:22 DIA 006 100 ZMOHAMMED GI 4 > Dequeue All call failed

12:20:23 DIA 012 100 WF-BATCH GI 0 Error calling the central lock handler

12:20:23 DIA 012 100 WF-BATCH GI 2 > Unable to reach central lock handler

12:20:23 DIA 013 100 WF-BATCH GI 0 Error calling the central lock handler

12:20:23 DIA 013 100 WF-BATCH GI 2 > Unable to reach central lock handler

12:20:23 DIA 011 100 WF-BATCH GI 0 Error calling the central lock handler

12:20:23 DIA 011 100 WF-BATCH GI 2 > Unable to reach central lock handler

12:20:23 DIA 010 100 WF-BATCH GI 0 Error calling the central lock handler

12:20:23 DIA 010 100 WF-BATCH GI 2 > Unable to reach central lock handler

12:20:23 DIA 010 100 WF-BATCH GI 0 Error calling the central lock handler

12:20:23 DIA 011 100 WF-BATCH GI 0 Error calling the central lock handler

12:20:23 DIA 010 100 WF-BATCH GI 2 > Unable to reach central lock handler

12:20:23 DIA 011 100 WF-BATCH GI 2 > Unable to reach central lock handler

12:20:26 DIA 006 100 ZMOHAMMED GI 0 Error calling the central lock handler

12:20:26 DIA 006 100 ZMOHAMMED GI 4 > Dequeue All call failed

12:20:53 DIA 013 100 WF-BATCH GI 0 Error calling the central lock handler

12:20:53 DIA 013 100 WF-BATCH GI 2 > Unable to reach central lock handler

12:20:53 DIA 010 100 WF-BATCH GI 0 Error calling the central lock handler

12:20:53 DIA 010 100 WF-BATCH GI 2 > Unable to reach central lock handler

12:20:57 DIA 003 100 ZMOHAMMED GI 0 Error calling the central lock handler

12:20:57 DIA 003 100 ZMOHAMMED GI 4 > Dequeue All call failed

12:20:57 DIA 008 100 JENJAM GI 0 Error calling the central lock handler

12:20:57 DIA 008 100 JENJAM GI 2 > Unable to reach central lock handler

12:20:57 DIA 008 100 JENJAM GH Z > Previous Message was Suppressed 2 Times

12:20:57 DIA 013 100 WF-BATCH GI 0 Error calling the central lock handler

12:20:57 DIA 013 100 WF-BATCH GI 2 > Unable to reach central lock handler

12:20:57 DIA 012 100 WF-BATCH GI 0 Error calling the central lock handler

12:20:57 DIA 012 100 WF-BATCH GI 2 > Unable to reach central lock handler

12:20:57 DIA 012 100 WF-BATCH GI 0 Error calling the central lock handler

12:20:57 DIA 012 100 WF-BATCH GI 2 > Unable to reach central lock handler

12:21:00 DIA 003 000 SAPSYS EB 9 Batch scheduler: Unable to perform job ADD ER EMERGENCY ROLE

12:21:00 DIA 003 000 SAPSYS EB 7 > Cause: Error within the lock operation

12:21:00 DIA 003 000 SAPSYS EB 9 Batch scheduler: Unable to perform job RHAUTUPD_NEW

12:21:00 DIA 003 000 SAPSYS EB 7 > Cause: Error within the lock operation

12:21:00 DIA 003 000 SAPSYS EB 9 Batch scheduler: Unable to perform job ER ADD USER ROLES

12:21:00 DIA 003 000 SAPSYS EB 7 > Cause: Error within the lock operation

12:21:32 DIA 003 100 ZMOHAMMED GI 0 Error calling the central lock handler

12:21:32 DIA 003 100 ZMOHAMMED GI 4 > Dequeue All call failed

12:21:49 DIA 003 000 SAPSYS GI 0 Error calling the central lock handler

12:21:49 DIA 003 000 SAPSYS GI 2 > Unable to reach central lock handler.

and in st22 we found below message.

START_CALL_SICK .

after restarting CI and app servers we are good.Now everything is working fine and smoothely.

here my question is what could be the reason to happen this kind of problems.

please help me to find out the root cause for this problem.

thanks&regards

enjam.

[Former Member · Accepted solution]

Hello

There are inconsistency arised in your system, have you recently apply kernel and other patches in your system with warning.

Note 562388 - Runtime error "START_CALL_SICK"

we found below message. START_CALL_SICK . after restarting CI and app servers we are good.Now everything is working fine and smoothely. here my question is what could be the reason to happen this kind of problems. please help me to find out the root cause for this problem

Regards

Anwer Waseem

SAP NetWeaver Basis

[former_member185031]

>>Cause: Error within the lock operation 12:21:00 DIA 003 000 SAPSYS EB 9 Batch scheduler: Unable to perform job >>RHAUTUPD_NEW 12:21:00 DIA 003 000 SAPSYS EB 7 > Cause: Error within the lock operation 12:21:00 DIA 003 000 >>SAPSYS EB 9 Batch scheduler: Unable to perform job ER ADD USER ROLES 12:21:00 DIA 003 000 SAPSYS EB 7 > Cause: >>Error within the lock operation 12:21:32 DIA 003 100 ZMOHAMMED GI 0 Error calling the central lock handler 12:21:32 DIA 003 >>100 ZMOHAMMED GI 4 > Dequeue All call failed 12:21:49 DIA 003 000 SAPSYS GI 0 Error calling the central lock handler >>12:21:49 DIA 003 000 SAPSYS GI 2 > Unable to reach central lock handler. and in st22 we found below message. >>START_CALL_SICK

It looks like problem with enqueue serivce.

Regards,

Subhash

[Former Member]

Hi,

I dont think the message server is down. If it is down then the entire system will be down.

So goto tcode SMMS->message server monitor..

Hope this helps.

Regards,

Raja. G

[Former Member]

The main feature that you have on CI is the message service amd the enque service.And what i see rom the logs that that you were getting the error of locked tables.

Did you check that the CI was up.from next Time go and check in SMLG.

Did you try to run SICK transaction.

I think you CI was down due to some reason thet you can find out in the old logs of Dev_w*........

Thanks

Rishi Abrol