If you want to record copies of the modified records in the target system, you can do this using the Golden Gate Software and not have to do much to deplete the source resources. Also, you do not need to make any changes to the source database to implement this solution.
Golden Gate resets retry logs for transactions, referring to a list of tables of interest to you. These changes are recorded in the "Trail File" and can be applied to another scheme in the same database or sent to the target and applied there (ideal for reducing the load on the source system).
As soon as you receive the trail file in the target system, there are some settings, you can set the option for auditing, and if necessary, you can call two Golden Gate functions to get information about the transaction:
1) Set the replication parameter INSERTALLRECORDS to insert a new record into the target table for each change operation made to the original table. Remember that this can eat a lot of space, but if you need a comprehensive audit, this is probably expected.
2) If you do not already have CHANGED_BY_USERID and CHANGED_DATE attached to your records, you can use the Golden Gate functions on the target side to get this information for the current transaction. Check out the following features of the GG Reference Guide: GGHEADER ("USERID") GGHEADER ("TESHETAMR")
Thus, it is not free (requires licensing through Oracle), and it will take some effort to roll out, but probably a lot less effort / expense than implementing and maintaining your own solution that reduces your own, and you have the added advantage of sending data to a remote system so you can guarantee minimal impact on the source database.
David mann
source share