on 03-04-2016 1:44 PM
Hi,
Is it possible to change the transfer behaviour from Array Insert into Single Insert when starting replication for tables?
The default method is Array Insert, but the problem is that table replication fails due to duplicate keys.
What I would like to achieve, instead of manually changing the transfer behaviour to Single insert for each table (almost 500), is that SLT uses Single Insert automatically when starting replication.
Regards,
Jaap
Hi
Im facing the same issue of duplicate key in SLT.
Could you please help me out with the process to change the transfer behavior option to 3.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your reply.
I have tried both the notes - 1919356 & 1905253 . But still showing the same error in one table .
and another table giving the below errors -
I have check the FM from MWBDISP tcode. but there its not showing any syntax error while I tried to activate it.
Regards
Sudip
Yes, we have resolved this issue by modify the transfer behavior to option 3. Array Modify.
Murali Cheekati
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, when ever, replication failing with duplicates keys, to process those errors for that table, need to change - transfer behavior to option 3. Array Modify.
For example, Recently we replicated KONV, BSEG to Oracle, got few errors with duplicate keys, Changed the transfer behavior to option 3. Array Modify, all the error records processed.
Murali Cheekati
Hi J,
Will this change in table level take as a part of continuous replication?
I replicated a table from Hana to ECC. it failed with error saying duplicate records similar to your case.
I modified the transfer behaviour to 3 and it allowed all records.
but now when the Hana source system has new entries and modifications happening, they dont get replicated to ECC.
while creating from hana to ecc slt configuration, i selected scenario as standard rfc scenario.
For replicating real time from haan to ecc, which scenario should be selected?
Regards,
Saritha
Yes I have tried that re-activating it as well. It allows hana data to be pulled in ECC table if its empty, errors out if it contains existing values in the table giving duplicate error. And after loading, if there are new entries coming in source(hana), they do not get reflected. Not sure what additional setup needs to be done here to take care of future changes.
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.