Qlik Replicate: Task from SQL Server source to Oracle target stuck after Oracle duplicate column name error

[shashi_holla]

A Qlik Replicate task replicating from an SQL server to an Oracle target may fail/get "stuck" with a duplicate column name error. 

Resolution

Verify that no duplicate column names exist.

This can be done from the Qlik Replicate console:

1. Open the Task in Designer mode
2. Open the Global Rules
3. Verify that no duplicate column names exist in the Global Rules
   
   
   
   
4. Navigate to Table Settings
5. Open Transform and verify that no duplicate column names exist there either.
   
   
   
   
6. Address any potential duplications.

Cause 

A possible root cause may be global rules set to add columns to the target table with a modified data type, but those columns were already part of the table and had to be removed from the table settings. An instance where this may occur could be code being moved from a development to a production environment. It is always recommended to test all possible scenarios before moving to production.

Environment

Qlik Replicate