Incremental Recon Job Is Updating Sync Token Of Another Incremental Job
(Doc ID 2506284.1)
Last updated on JULY 27, 2021
Applies to:Identity Manager - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
If a 2nd incremental reconciliation job is created from same original incremental recon task which already had an incremental job created against it, then running the new/2nd incremental job will update the "Sync Token" of the first recon job.
Install a 188.8.131.52.0 DBAT Connector and configure it with a 'changeLogColumn' (in DBATConfiguration.groovy file).
If setup as a target resource then you will have an incremental recon job called 'DBAT Trusted Incremental User Reconciliation' out of the box (ootb). This job works fine, without problems.
If you create a new/2nd job called 'DBAT Trusted Incremental User Reconciliation Part2' against the same 'DBAT Trusted Incremental User Reconciliation' task then when you run this new job it will update the 'Sync Token' of the first job (i.e. 'DBAT Trusted Incremental User Reconciliation') but it does not update its own 'Sync Token' parameter.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!