We Value Your Feedback! Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services. Learn more about the survey or Click here to Launch the survey Schneider Electric Services Innovation Team!
Repeated Databse Lock alarm thrown @GEO SCADA!!!
EcoStruxure Geo SCADA Expert Forum
Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-08-0812:30 AM
First off, a periodic high database lock may be perfectly normal, so don't panic!
It's indicating the system has a busy period. If you expect this, then just alter the lock period. Right click the root group, select Configure. Click the Performance tab and edit the alarm levels. You might want to increase the averaging period.
Good, temporary, reasons for long high lock periods include the execution of reports which make complex/long queries, or at the other end, outstations set to report data all at the same time. You could stagger the execution to reduce load.
So, there may be things you can do to improve matters and ensure good performance to users. Look at the Logic (see in Queries - Logic Execution Status) to see if you have excessive runs/frequency, overruns. For further help see the Knowledge Base sections on performance.