GoldenGate @GETENV("RECORD", "TIMESTAMP") replicat parameter gives COMMIT TIMESTAMP instead
edited Nov 26, 2013 4:28PM in GoldenGate, Streams and Distributed Database (MOSC) 8 commentsAnswered
I'm trying to capture the timestamp for individual components of a transaction using the "@GETENV("RECORD", "TIMESTAMP")" construct in the replicat COLMAP parameters, but it just gives me the commit timestamp for the entire transaction.
E.g. the following sequence of events occur on the extract (source) database:
-- At 11:05am the following is executed:
UPDATE TABLE A SET <etc>
-- At 11:10am the following is executed:
UPDATE TABLE B SET <etc>
-- At 11:15am the transaction gets committed:
COMMIT;
Both UPDATE statements are part of the same transaction so the commit timestamp (from @GETENV("GGHEADER", "COMMITTIMESTAMP")) is the same, but I want to capture the timestamp for each individual UPDATE within the transaction.
E.g. the following sequence of events occur on the extract (source) database:
-- At 11:05am the following is executed:
UPDATE TABLE A SET <etc>
-- At 11:10am the following is executed:
UPDATE TABLE B SET <etc>
-- At 11:15am the transaction gets committed:
COMMIT;
Both UPDATE statements are part of the same transaction so the commit timestamp (from @GETENV("GGHEADER", "COMMITTIMESTAMP")) is the same, but I want to capture the timestamp for each individual UPDATE within the transaction.
0