Knowledge Base: Filter deletes from being propagated to integrate location

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #22422

    Donna Zehl
    Keymaster

     

    Problem Summary:

    My customer is capturing transactions from a MySQL database to a target data warehouse. They want the source production database to contain only the most recent month or years data while target can store historical data. This means when activity to purge occurs on the source, the old data is deleted from it but how can HVR filter the delete transactions and not delete them on the downstream data warehouse just on the source ?

    Usually we can do it for an Oracle source with Capture using the /IgnoreSessionName, but it not work on MySQL. Is there any other solution can make it?

     

    Answer:

    We can do this for MySql database defining the action on the Source to ignore deletes.

         /CaptureCondition="{hvr_op}!=0".

    Deletes are not captured.

     

    Interestingly, if you put it on the Integrate side as a Restrict action with ‘/IntegrateCondition=”{hvr_op}!=0″,  you will get an error:

         2019-08-22T14:18:35+01:00: o2o_nodelfil-integ-otgt: F_JD223D: Unknown variable {hvr_op} encountered 
          while parsing SQL expression '{hvr_op}!=0'.

    Note: The value for hvr_op values are 0, 1, 2, 3, 4, 5 (which indicate the operators: delete, insert, after row update, before key update, before non-key update, truncate respectively). This value cannot be transformed and/or post transformation such as values like D, I, UA, etc.

     

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

© 2019 HVR

Live demo Contact us