Mapping the changes to a target table and storing the transaction history in a history table
Many businesses, these days, have a requirement to keep a transaction history of the data. This could be due to regulatory requirements or even for management reporting. Oracle GoldenGate's flexible architecture allows you to track the old value of a record before a change is applied to it. You can then map these changes to a different table to maintain a transaction history.
In this recipe we will look into how we can track the changes occurring on a source database table and replicate them to a target database table and also maintain the transaction history in a separate table.
Getting ready
For this recipe we will set up a replication between the EMP
Get Oracle GoldenGate 11g Complete Cookbook now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
