Workflow for Configuring Large Purge
The following table provides the steps to configure large purge.
| Step Number | Description | Required or Optional? |
|---|---|---|
| 1 | Set Up AWS DMS for Replication. | This step is required. |
| 2 | Back up ProductionDB. | This step is required to ensure that there is no loss of data. |
| 3 | Create CloneDB using the ProductionDB backup. | This step is required. |
| 4 | Filter CloneDB. | This step is required. |
| 5 | Delete unreferenced rows in CloneDB. | This step is required only if there are unreferenced rows. For example, when you delete a parent table, the child tables may contain unreferenced rows. |
| 6 | Disable triggers. CloneDB contains all the triggers that the replicator added to ProductionDB. The triggers can modify the rows of CloneDB when an INSERT, UPDATE, or DELETE operation occurs on a ProductionDB table. |
This step is optional but we recommend that you perform this step to avoid any inadvertent changes to the data on CloneDB. |
| 7 | Stop all the SOA and Plant Applications services. | This step is required. |
| 9 | Start replication. | This step is required. |
| 8 | Enable triggers on CloneDB. | This step is required if you have disabled the triggers. |
| 10 | Disable ProductionDB replication. | This step is required. |
| 11 | Switch to CloneDB. | This step is required. |