Introduction
The Delft-FEWS client-server system consists of the Master-Controllers, Forecasting Shell Servers and Operator Clients and optionally a PiService. In rare cases there are errors that make it is necessary to remove some records from the client-server system. Removal is not always straightforward since synchronisation may cause these records to be synchronised back to the central database system. The following steps will prevent this happening. Note that for several different removal methods of records from the central database are made available within the MCRecoveryTool. Note that some types of records are uploaded by the Operator Clients (manual edits / synchLevel 5) in which case it is necessary to remove the OC local datastores as well.
Methods for deleting records
- Automatically by the RollingBarrel based on expiry time
- Populator (wipes the central database)
- MCRecoveryTool (specialised removal actions)
- Sql script in sql script or via DBVisualiser or another jdbc client. See examples below
- ImportAmalgamate (this is for merging external historical data), see also ImportAmalgamate
Removal of records with a single master-controller
- Remove all forecasting shell / PI Service local datastores and cache files.
- Delete the records from the central database.
Removal of records with multiple Master-Controllers
- Suspend all MC-MC Synchronisation tasks.
- Remove all forecasting shell / PI Service local datastores.
- Remove the records from all central databases
- Resume the MC-MC synchronisation tasks.
Examples of custom deletions (e.g. via DBVisualizer)
Always make sure you are connected to the correct database schema first.
Before deletion, always do a select of the data to delete. If possible inquire whether a recent backup of the database is available.
Bulk deletion of workflowmappings
The MCRecoveryTool -clear_config_all option is available to clear all configuration and will also remove the workflowmappings. But in some cases, a custom delete statement can be quicker to clear all the workflowmappings for non- MC workflows without the need for uploading the configuration again.
Before deleting workflowmappings, it can be beneficial to download the current configuration first via the AdminInterface.
DELETE FROM WorkflowTargetFSSs WHERE workflowId NOT LIKE 'MC:%' AND workflowId NOT LIKE 'MC_:%'
