Duplicate Key Error while Load/Replication

[Former Member]

Dear Colleagues/Experts,

I'm trying to run replication on a table having very large number of entries. I've used reading type as 5-Sender Queue and have also defined range for initial load in advanced settings.

The Replication started with initial load. However towards the end when the load was almost done with very few records left, I received an abort message stating 'Duplicate KEY'.

On checking the range, I found that the last range had an overlap with the previous one. I've corrected them now.

My question is can the system consider the changes in the ranges and can resume the load or do I need to stop the replication and start again, for the logging tables to be re-created. It seems that I'll have to stop and re-start.

Seeking your advice.

Basically, due to a large number of records, majority of which is already loaded, I'm trying to avoid stop and start of replication.

Thanks.

Shushant

[Former Member]

Hello Shushant,

Please let me know the steps you have executed for the setting up the ranges.

also As this is you initial load the logging tables will not be coming into picture as the logging tbales  will be used to store the delta or change  of the records and not the initial load.

Please let me know if this helps.

Regards

Amar Ghuge

[Former Member]

Hi Amar,

Many thanks. I used the performance options in iuuc_repl_content. Created ranges manually where the last range overlapped the 2nd last, initially.

I didn't do initial load. Instead I started with Replication option directly and as I understand, it would first do the load, post which it would start replicating. Which means the status would be Replication(Initial load) first and later it would become 'Replication'.

Now the issue pops up when the status is still Replication(Initial Load), which as I mentioned was due to overlapping ranges.

My question is, now that I've fixed the ranges and have kept all ranges mutually exclusive of each other, can I resume the process without stopping and starting it again.

Regards,

Shushant

[Former Member]

Hello Shushant,

As per my understanding the restart for the replication of the table would be required, as once you define the ranges and start the replication system will first execute the pre-calculation job which will create a plan for execution of the table as this job run in a interval it might not pick up the new changes. thus restart would be required or preferable.

Also restarting the table replication wont take the same time as the data os already avialable in HANA also as per me it has that pointer from where it will do the next steps of load.

Please let me know you feedback on same.

Amar ghuge