Preliminary Considerations
To ensure a smooth operation during System Maintenance tasks, the following prerequisites must be met:
1. Run the System Maintenance tasks from a workstation with at least 16GB of RAM.
2. In "Monitoring Console > Workflow Monitor", sort workflow by "Workflow status" and delete workflows with "Aborted" or "Faulted" status.
3. In Workflow Monitor, sort workflow by "Action" and delete pending actions for user response, e.g. file exist, and delete those actions in waiting status for over a week/month.
When to perform it?
As viewed in the previous chapter, the maintenance operations must be performed every time the program has been modified. Still, there are some specific cases when this operation must be completed, each with different parameters depending on the purpose of the maintenance. These cases include:
• On the First Etere Run
The Etere Maintenance Tasks must be launched right after the installation of Etere software to perform the maintenance of the central archive to create tables necessary for the correct functioning of Etere software; the maintenance options that must be performed are:
- Check database structure
- Update screen language
- Full-text search
• After an Update
On an Ad-hoc basis, Etere releases new versions of its modules to its customers; if you have just updated your system with the released version, it's highly recommended to perform System Maintenance by enabling the following parameters:
- Check database structure
- Update screen language
• SQL SERVER Shutdown
If the PC where the SQL SERVER is running malfunctioned and resulted in a server shutdown, a database failover might occur (i.e., malfunctioning of T-workflows, service broker problems, etc.). To resume the database to its previous state, you would need to perform system maintenance with the following options:
- Check database structure
- Select the scripts before performing the maintenance:
003_Workflow_1_Schema (wf_admin_resetSysworker): Reset and reconstruct the Service Broker.
003_Workflow_2_Runtime (wf_runtime_restartAllRunningInstances): Restart all the stuck jobs and T-workflows in the queue before the shutdown.
Once the system maintenance is completed, you must manually execute the updated scripts from the Microsoft SQL Management Studio application; please refer to the chapter How to Reconstruct Service Broker after a System Crash.
Note: To prevent an informational message from popping up when you launch any Etere module while the System Maintenance executes, set the value of the following System Parameter to "0".
Global.ini/Database Maintenance/Executing