Skip to Main Content

OGG trail file

user10126973Jul 21 2021

Hi All
In my source database one of the table has(16 columns) supplemental logging enabled for all columns
I have fired update stmnt like update table_name set col1= some where col2 = some_unique;
committed and updated 1 row
when I check in the target trail file or report file I am seeing all 16 columns are where clause
sometimes I am getting no data found issues as Its not matching values in the where clause source to target
How to avoid this kind of situations ?
How to get as it is update stamnt which i have fired in the source?
Please share your thoughts

Post Details
Added on Jul 21 2021
1 comment