Setting up Bi-Directional Replication

David_Fergen — Wed, 02 Sep 2020 13:09:20 GMT

Link to Video Transcript:

Description:

When setting up bi-directional Replication - be aware that schema names, table names and column names are very sensitive when it comes to case.

For example, if replicating using Oracle and SQL Server

Oracle table "MYSCHEMA"."TEST"

SQL Server table [myschema].[TEST]

In Task settings

TASK 1 - Oracle to SQL

Metadata Tab - Target Metadata --> myschema

Bidirectional Tab -

Source Schema --> MYSCHEMA

Target Schema --> myschema

Task 2 - SQL to Oracle

Metadata Tab- Target Metadata --> MYSCHEMA

Bidirectional Tab-

Source Schema --> myschema

Target Schema --> MYSCHEMA

If column names are in different cases ensure these are matched in "Table Settings" and the "Transform Tab".

These are the rules:

Schemas should be specified exactly as they are in the database with the correct case-sensitivity.
The Bidirectional Source Schema should be equal to the Target Schema in the second Task, and the case-sensitivity should be correct.
If the metadata is different (field names), they should be mapped correctly taking into account the "correct" case-sensitivity of both databases.

If experiencing any of these behaviors, it means the Tasks are not setup correctly:

If having a Primary and you get a warning about the PK.
If the loopback_prevention table is added to the UI capture list (attrep_loopback_prevention).
If updated Oracle and see that the SQL to Oracle Task's statistics got updated, or the opposite direction.

article Setting up Bi-Directional Replication in Official Support Articles