Sybase replication server - Duplicate transaction handling .

[former_member628057]

Hi All,

Good Day !

Need you suggestion here.

We have setup of table level replication with source as DB2 , target as HANA & replication is taken care by 1 sybase replication server.

Now whenever duplicate record found DSI shut downs, as of now we have not set any error class or auto correction feature.

But my client need is that DSI wont go down , or if in case it go down it resume itself (say via script code) & also duplicate record get logged so that one can check & decide it whether need to apply or skip that tran.

As per my understanding auto correct feature at connection level just converts insert/update to delete followed by insert . Which means it does not log or keep a track for duplicates transaction as its already taken care . Am I correct here ?

Also same is with (set dsi_command_convert to 'i2none,u2none,d2none' ) , as it too perform semi auto correct operation. So it too wont log duplicate transactions information as its already taken care.

But as per my client need , I believe "Exception Error class" will help me to meet the need. As it will keep on running even if duplicate record found, it will send to exception table & so DSI wont be down , latter we can act on duplicate transaction in error class & decide what to do . Is my understanding correct on this & till now ?

Or can we achieve this with some other way also? Kindly suggest & share your thoughts on this.

Thanks & Regards

Sukriti V

[former_member628057]

Thanks for reply Mark , you almost cleared my doubts .Also after reading your comment & suggestion , I have new doubts as below.

1). Will i2di/u2di get logged in exception log ? As Auto correction & i2none/u2none wont.

2). With error class action can you please clear my understanding.

Is skipping a transaction is instructing Replication Server to roll back the current transaction ??

=> Ignore ( Just skip of that duplicate transaction with not logging information to exception log. ) Instructs Replication Server to ignore the error and continue processing. ignore should be used when the data server error code indicates a successful execution or an inconsequential warning.

=> log ( It will also skip duplicate transaction but it will log detail in exception log) Instructs Replication Server to roll back the current transaction, log it in the exceptions log, and then execute the next transaction.

@@Mark : Can you please share such script with me (sukritiverma9@gmail.com) if its handy with you. It will be big help.

Thanks & Regards

Sukriti

[Mark_A_Parsons]

1 - no, none of the dsi_command_convert settings cause transactions to be dumped to the exceptions log

2 - an error causes a rollback; whether a skipped/rolled-back transaction gets written to the exceptions log depends on which option you set for the error number in question

I suggest you setup a test RS environment and try out the various items I mentioned (above); then you send through some 'duplicate' transactions and see what happens.