|
|
symmetricDS.jpg (65,254 bytes) |
|
|
So you're using a custom trigger to populate sym_data, but SymmetricDS gets an exception when processing it. What is the exception? Did you try using the sym_trigger.stream_row = 1 feature? It captures only the PK values for the table, which makes the trigger very efficient. It will query for the row during extraction instead. |
|
|
we got it working using our custom trigger on the iSereis... when we output to sym_data we first make sure that the max(trigger_hist_id) in sym_trigger_hist contains ONLY the key values in sym_trigger_hist... if not, the trigger goes ahead and updates PK_DATA with those column names only... it then carries that trigger_hist_id over to sym_data when it inserts the changed row data... this has provided success for us and the results we need (since I put the original issue in your system)... are there any pitfalls to look out for this method? this table has 306 columns and the default symmetricDS trigger was just taking too long... our new trigger submits the request to batch (and does the above method)... |
- Anonymous