CODEWITHSUNDEEP
oracle-databasedatabase-replicationtungsten-replicatororacle-cdc
ento
ento

Reputation: 5889

How to provision Oracle-to-MySQL replication using synchronous CDC with no downtime?

I'm trying to provision Oracle-to-MySQL replication using the parallel extraction method outlined in the Tungsten Replicator documentation.

  1. Setup CDC tables in Oracle using the setupCDC.sh script provided by Tungsten.
  2. Start the parallel extractor, specifying the starting SCN of the CDC process given by the previous script.
  3. The parallel extractor will insert all existing data using flaskback queries of the form AS OF SCN ..., performing a point-in-time provisioning with data integrity.

The problem is the setupCDC script prints out an SCN only if the CDC is asynchronous. It's hinted in an official forum thread that this is to "get a single position for the whole schema snapshot."

Due to licensing restrictions, I can only use synchronous CDC. Is it safe to manually read the SCN recorded in the all_capture table and use it for provisioning? What are my options that can achieve both data integrity and minimum downtime?

Upvotes: 0

Views: 630

Answers (1)

ento
ento

Reputation: 5889

Is it safe to manually read the SCN recorded in the all_capture table and use it for provisioning?

For synchronous CDC, there is no entry in the all_capture table, which is for asynchronous capture processes.

Instead, each change table records the SCN at the time of its creation. You can determine the lowest SCN from the change_tables table and provide it as the argument to the provisioning command: trepctrl online -provision <scn>.

SQL> COL scn FORMAT 999999999999999
SQL> SELECT MIN(created_scn) scn FROM change_tables WHERE change_set_name = 'TUNGSTEN_CS_{service_name}';

(Replace {service_name} with your own service name.)

Upvotes: 0

Related Questions