You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

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

  1. Automatically by the RollingBarrel based on expiry time
  2. Populator (wipes the central database)
  3. MCRecoveryTool (specialised removal actions)
  4. Sql script in sql script or via DBVisualiser or another jdbc client.
  5. ImportAmalgamate (this is for merging external historical data), see also ImportAmalgamate

Removal of records with a single master-controller

  1. Remove all forecasting shell / PI Service local datastores and cache files.
  2. Delete the records from the central database.

Removal of records with multiple Master-Controllers

  1. Suspend all MC-MC Synchronisation tasks.
  2. Remove all forecasting shell / PI Service local datastores.
  3. Remove the records from all central databases
  4. Resume the MC-MC synchronisation tasks.

 

  • No labels