replication task issued the following warning: Source changes that would have had no impact were not applied to the target database. Refer to the 'attrep_apply_exceptions' table for details.
I have validated the data too,but there was no data missing which is odd from the warning message we have being getting
I think we can better triage this if we had a support case where we can request for task diagnostics and verify the settings/logs. Warnings are indications that the issue is not a show stopper but some settings needs some tuning to work better.
"Source changes that would have had no impact were not applied to the target database" : It's for information purposes only and says that the task received change record from source which was same as target data and did not get applied since there are no changes to apply.
I think we can better triage this if we had a support case where we can request for task diagnostics and verify the settings/logs. Warnings are indications that the issue is not a show stopper but some settings needs some tuning to work better.
"Source changes that would have had no impact were not applied to the target database" : It's for information purposes only and says that the task received change record from source which was same as target data and did not get applied since there are no changes to apply.
Thank you,
IMHO this explanation is NOT specific enough. This warning is often/mostly generate for UPDATE operations where the target row is not, or no longer, available and thus the changes could not be applied and would make no changes.
That may be bad or may be fine depending on DATA specifics. You need to fully investigate one, or a few, example instances to judge what is the root cause. That's best done by rolling the log, temporarily switching task logging to TARGET APPLY - VERBOSE until the warning re-occurs. Then revert to INFO and roll the log again. Now check the log for the error time and check the attrep_apply_exceptions table for the entries for that task and time.
If you for example find that a row to be updated was not there then you need to decide whether that's ok, perhaps because not all data was loaded, a backup + start by timestamp for example. Sometimes it is reasonable to switch the task apply error/exception handling to "No record found for applying an UPDATE: INSERT the missing target record", or "Ignore record". That will eliminate further warnings.
