Is it possible that when a task must be restarted, the full load is executed until a certain date and from there the CDC starts? Task has Oracle as source and S3 destination in Stored Changes mode.
I ask the question because a client works with the data loaded in the cloud from a certain point (when the initial full load ends, the full load files are generated and then the CDC files are generated), but when a new full load is done, this point changes. Any recommendation?
If a task enabled both of Full Load and CDC, while the task is starting up (the first run, or reload), two threads are working in parallel:
1- CDC thread : Start capture changes which are made from this point, and cache the changes
2- Full Load thread: transfer the history data records from source side to target side, until all tables all rows transferred
After 2. done, Replicate will start applying the cached changes to target tables.
So it's an automatic smooth progress, the CDC process will continue un rafter Full Load done, you need not care about the date/time when the task is started or wait for a time.
Hope this helps.
Regards,
John.
Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
