Capturing the DML changes on the source and writing to a temporary table

Question

Am trying to set up a change data capture where both the source and target would be the same database.
like in my case i would like to capture changes from a table schema.xyz in a orcl database and write it to a temp table within the same database. My concern here is , the table schema.xyz is already replicating to a different database on a different server.
Any ideas on how this can be achieved?
I thought of setting up a different extract process and capture the changes and write to the temp table , but not sure if this is manageable.
Thanks,
Venky.

Answer 1

Just tap into the existing trail if the change data is already there. There's no need to have a second extract in that case. So ADD REPLICAT and specify the EXTTRAIL the same as the EXTTRAIL for the redo log extract.
OGG won't pick up truncates by default. If the row is gone before the update arrives at the target table then you can use INSERTMISSINGUPDATES. When using this parameter make sure that you add supplemental logging (ADD TRANDATA) for columns that you need but that may not be updated (e.g. target columns with NOT NULL or FK constraints).
Good luck,
-joe