Guidance on managing remote database outages
- Last UpdatedNov 07, 2024
- 2 minute read
-
If the state database downtime is expected to be brief, no action is required. AVEVA Production Management queues and submits operations when the database is back online.
-
When the remote database goes down, you need to have a plan in place for how to quickly and securely stop the application. This means keeping an eye on SQL Server's availability.
-
Because there's no AVEVA Production Management service dependency on a remote deployment:
-
You need to set up performance monitoring to alert you when remote databases go down to ensure that you can gracefully shutdown the AVEVA Production Management service using the service manager, or
-
Set up the AVEVA Production Management service to automatically stop when the state database cache reaches a certain limit or a specified timeout limit through the Ampla service configuration file.
For more information on setting up an automated shutdown, refer to Remote state database configuration for graceful shutdown in the Administrator (Studio) online help.
This is beneficial, especially if the state database downtime is expected to be long. While AVEVA Production Management can recover from short downtimes, longer downtimes or forced shutdowns while the state database is down could result in data loss. For more information on performance monitoring counters, see Performance counters in Administrator (Studio) Help.
-
-
If 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 AVEVA Production Management 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.
Note 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.