Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts. Register and secure your Critical IT infrastructure
Performance issues when connectivity is not available for Alarm Provider
Geo SCADA Knowledge Base
Access vast amounts of technical know-how and pro tips from our community of Geo SCADA experts.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
Invite a Co-worker
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.
📖HomeBack If Wonderware Alarm Provider cannot provide alarms to an InTouch system (for instance the module is installed but not in use or there is a communications problem), they will accumulate (up to 250 000 alarms).
The number of alarms it accumulates leads to a large Module Data file on the server which may lead to performance issues when saving and syncing it.
The large number of cached alarms will be causing fragmentation of the memory on the ClearSCADA server as the WonderwareAlarmProvider driver tries to allocate large blocks of contiguous memory every time the module data is saved to disc. This fragmentation of the memory can then lead to a server crash when a large contiguous block of memory can't be allocated.
Symptoms from Status tool/Snapshot log:
WonderwareAlarmProvider installed (ie in the modules list - it will however always have 0 objects configured, since no ClearSCADA objects are required.
Module data saves take a long time and may lead to exceptions:
13. Database File Statistics Id |File|Flush Pending|Last Save |File Size|Save Time|Flush Time|Updates|Status ==============+====+=============+=======================+=========+=========+==========+=======+====== ModuleData |- |No |05/01/2017 23:59:57.937|344.83 MB|16.50 s |2.632 s |36 |Ok
We recommend not installing Wonderware Alarm Provider if it is not in use, or disabling it if the Intouch system is expected to be out of commission for an extended period.