Qlik Community

Support Knowledge Base

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Setting up Bi-Directional Replication

Digital Support
Digital Support

Setting up Bi-Directional Replication



Link to Video Transcript:



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: 

  1. Schemas should be specified exactly as they are in the database with the correct case-sensitivity. 
  2. The Bidirectional Source Schema should be equal to the Target Schema in the second Task, and the case-sensitivity should be correct. 
  3. 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: 

  1. If having a Primary and you get a warning about the PK. 
  2. If the loopback_prevention table is added to the UI capture list (attrep_loopback_prevention). 
  3. If updated Oracle and see that the SQL to Oracle Task's statistics got updated, or the opposite direction. 
Labels (1)
Version history
Revision #:
6 of 6
Last update:
‎2020-09-02 09:09 AM
Updated by: