Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel

Repeated Databse Lock alarm thrown @GEO SCADA!!!

EcoStruxure Geo SCADA Expert Forum

Find out how SCADA systems and networks, like EcoStruxure Geo SCADA Expert, help industrial organizations maintaining efficiency, processing data for smarter decision making with IoT, RTU and PLC devices.

Lt. Commander
Lt. Commander

Repeated Databse Lock alarm thrown @GEO SCADA!!!

Hello There,


GEO SCADA continuously pop ups  Databse Lock alarm with high rate range from 87% to 99% almost every week !!


-> What could be the causes?

-> How can we prevent GEO SCADA servers from encountering database locks?

1 Reply 1
Janeway Janeway

Re: Repeated Databse Lock alarm thrown @GEO SCADA!!!

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.