Start Replication

Before you begin

  1. Stop all the SOA and Plant Applications services.
  2. In the AWS DMS console, stop the AWS DMS task. If you do not do so, the TLOG truncation warning message will appear for the AWS DMS task.

About this task

You must start the AWS DMS task to replicate the latest changes in ProductionDB to CloneDB.

Procedure

  1. Update the name of the AWS DMS endpoint that you created while setting up AWS DMS for replication:
    1. In the AWS DMS console, select AWS DMS Endpoint with target SQL Server.
    2. Select Action and then select Modify.
    3. Enter the name of the filtered database in the Database field, and then select Save.
      A message appears, asking whether you want to update the endpoint.
    4. Select OK.
  2. Modify the AWS DMS task that you created while setting up AWS DMS for replication.
    1. In the AWS DMS console, select Database migration task, then select migration for purging.
    2. Select Action and then select Modify.
    3. Under CDC start mode for source transactions, enable the custom CDC start mode.
    4. Under Custom CDC start point for source transactions, select Specify a custom start time (UTC) and specify the start time of the full backup taken in UTC.
    5. In the task settings, switch to the JSON editor and update the following parameters:
      • ApplyErrorInsertPolicy from LOG_ERROR to INSERT_RECORD.
      • ApplyErrorUpdatePolicy from LOG_ERROR to UPDATE_RECORD.
    6. Under CDC stop mode for source transactions, enable custom CDC stop mode.
    7. Under Custom CDC stop time (UTC) for source transactions, select Specify server stop time, and specify the time of the SOA services stop completion in UTC (that is, start time of Downtime).
    8. Save the task.
  3. Start the modified AWS DMS task for replication:
    1. Access the AWS DMS console, and select the modified task.
    2. Select Action, then select Start and then Restart.
  4. Wait for the task to start replication and monitor the table statistics. The task will take some time to initialize and configure the replication.
  5. The task will auto stop once the data replication reaches the CDC stop time mentioned in the task.
  6. Verify the replicated data at ClonedDB using SQL checks and counts.

Results

The replication has begun.

What to do next

If you have disabled triggers on CloneDB, enable them. If not, disable ProductionDB replication.