Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Production Management

Remote state database configuration for graceful shutdown

Remote state database configuration for graceful shutdown

  • Last UpdatedSep 06, 2023
  • 2 minute read

You can set up the AVEVA Production Management service to stop automatically when the remote state database reaches a certain threshold or after a specified timeout limit—whichever comes first—for a graceful shutdown.

To do this, you need to configure the state database parameters in the Ampla service configuration file. For detailed steps, see Configure state database shutdown parameters . With the cache length threshold limit configuration, the application notifies you when it reaches 80% of the threshold limit through a message window. When it reaches the maximum specified limit, another notification is sent, signaling an automated shutdown is on the way.

Suppose that you improve the cache size after the first notification, so it drops to 70%, then rises back to 80%. In this scenario, there won't be a notification until it goes below 50% first and then reaches the 80% limit again.

If you need to check the logs to see instances of these automated shutdowns, the application logs messages with the keyword Auto-stopping to help users identify them. For example: Auto-stopping Ampla service host control due to DB operation timeout.

If the AVEVA Production Management service is stopped while there's a state database connection loss, any Metrics calculations scheduled in the operations queue are written to a .csv file to ensure they are not lost.

When the service is up and the state database connection is restored, you can inspect the .csv file from <Drive>:\ProgramData\Citect\Ampla\Projects\<AmplaProjectName> and manually trigger a recalculation of any Metrics if necessary. For every database outage, a .csv file is created, including a timestamp format of YYYYMMddHHmmssff on its filename. For example: MetricsCalculationSchedules_2023052515054440.csv. This allows you to manage file versions and delete those you no longer need.

For information on managing database outages, see Guidance on managing remote database outages in the AVEVA Production Management Installer Guide.

TitleResults for “How to create a CRG?”Also Available in