Qlik Community

Qlik Replicate

Discussion board for collaboration on Qlik Replicate.

QlikWorld 2022, LIVE in Denver CO., May 16-19, 2022. REGISTER NOW TO RECEIVE EARLY BIRD PRICING
Showing results for 
Search instead for 
Did you mean: 

Index naming


I'm replicating (ver from Oracle to Oracle and using the Drop and Create Table option. 

Replicate did not automatically identify a unique index to use (I think because the source indexes are function based), so I have configured a key manually on the Transform tab.

Is there any control over the name it creates for the destination index?

Ideally I would be able to keep the naming convention of the source as it does for the automatically detected indexes.



Labels (1)
2 Replies

Hello @IanM ,

Not sure what's your Oracle source table creation DDL, let's start from the general Index Naming rule.


1. If the table has PK, then replicate defines PK in target table. No Unique Index (UI) will be created in target table.

2. If the table has not PK, and there is only one Unique Index in source table (as you already know, Function-based indexes are not supported)

    Replicate will create the same UI (columns list, same below) in target table. The UI name would be like <target Table Name> + "_PK"

3. If the table has not PK, and If there are multiple UIs in source table

    Replicate defines only one index on the target table, by default it's the first UI (according to alphabetical order) of the source table. The UI name would be like <target Table Name> + "_PK"

    If you choose a non-default UI/PK, then see (4) below.

4. If the table has not PK, and you choose KEY in Console GUI manaually (for example, the source table has not PK/UI, or you choose a non-default UI)

    Replicate defines the index on target table, the UI name would be like

    <taget Table Name>+"_"+<unixepoch format of current time>+"_PK"

    By adding Unix Epoch time to make sure the UI name uniqueness.  However Replicate will truncate the UI name length to 30. For example the Index name is "KITNOUI_T_1618495151441352_PK" if you run the task around 2021.04.15T21:56:00 where the table table name is defined as "KITNOUI_T".  

Unfortunately, there is no explicit easy way to control the UI name. You may raise feature request if you want. To submit Feature Requests  please use our Qlik Community "Product Insight and Ideas" forum.

Hope this helps.




Thanks John, 

Looks like I'm going to have to live with it for now. Not an issue, I just wondered if I had missed something.