We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE:[sap-basis] Central Lock Handler unavailable

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Posted by KentN (Director of SAP Basis)
on Feb 2 at 4:01 PM
Mark this reply as helpfulMark as helpful
Yes, I would be concerned over this one. What are the versions of everything you are running? DB, OS, Patch, Kernel.

Is this happening on the central instance or an app server? If on the app server, it may be due to lost connectivity to the central instance.

Regards,
Kent

---------------Original Message---------------
From: sap basis
Sent: Tuesday, February 02, 2010 2:45 PM
Subject: Central Lock Handler unavailable

> Good evening,<br/>I have a system with the following sm21 log entries regarding the central lock handler. <br/>rror calling the central lock handler<br/>An error occurred when calling the central lock handler.<br/>You will find more information on this in the following lines.<br/>Unable to reach central lock handler<br/>The central lock handler is unavailable.<br/>Therefore no lock requests can be processed.<br/>Please analyze this problem using the transaction SM12 -> Diagnosis.<br/>Possible causes:<br/>- The central message server is unavailable.<br/>- The central lock handler (enqueue server) is not connected to the<br/> central message server. (see transaction SM51.)<br/>- Incorrect system parameters. These could be the profile parameters:<br/> - rdisp/mshost<br/> - rdisp/msserv<br/> - rdisp/enqname<br/>When looking at sm12 the lock entries do fluctuate when you monitor it for a while indicating to me that the lock handler is handling requests. Also the SM12 diagnoses indicates no errors. And when in SM51 on this app server I am not really sure what to look for. What I do know is that there are no ENQ queue there are no enqueue entries waiting. <br/>Parameter enque/table_size is set to 64 000 on the DEFAULT.PFL. The following are all the statistics from SM12==> Statistics.<br/>Enqueue Operations 13511189<br/>rejected 215130<br/>Error occured 0<br/>Dequeue Operations 7314937<br/>Error occured 0<br/>Dequeue All Operations 3777450<br/>Cleanup Operations 4<br/>Backup Operations 366200<br/>Read Operations 891709<br/>Compress Operations 0<br/>Verify Operations 0<br/>Records written 3885493<br/>to the backup file 3828460<br/>Maximum Number of Lock Owners 57033<br/>Maximum Fill level 217<br/>Current Fill Level 69<br/>Maximum Number of Lock Arguments 57033<br/>Maximum Fill level 7943<br/>Current Fill Level 271<br/>Maximum Number of Lock Entries 57033<br/>Maximum Fill level 7964<br/>Current Fill Level 279<br/>Update; Fill Level at Maximum 21<br/>Current Fill Level 0<br/>Time in Lock Table /Seconds 683.695041s<br/>Wait for Lock Table /Seconds 288.930456s<br/>Time in Lock Server /Seconds 1742.568391s<br/><br/>I did follow the following link http://help.sap.com/saphelp_nw70/helpdata/EN/f0/b57 338788f4d72e10000009b38f8cf/content.htm and I have ruled out note 734728 and 488036. <br/>I am wondering whether I should be concerned about these entries at all, the wp's or app server has not been restarted anytime close to these entries being written in the system log. The system is an SAP 3CC 6.00 system. <br/>Please advise, I have found similar articles on here but not with specific information.<br/>Regards,<br/>Johan
__.____._
Copyright © 2010 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
KentN
SAP Basis Helper

Posted helpful replies on 5 threads in a group to earn a Bronze Achievement
In the Spotlight
Share Knowledge About SAP Scripting. Join the New Discussion Group
_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language