If you see this error in OIM:

[LDAP: error code 53 - Full resync required. Reason: The provided cookie is older than 
the start of historical in the server for the replicated domain : dc=domain,dc=com]; 
remaining name 'cn=Changelog'

I assume you also have OUD and are doing either LDAPSync or using the OID Connector for OUD. Here’s how you fix this.

You need to go to your OUD server’s $INSTANCE_HOME/OUD/bin and run this command:

./ldapsearch -h localhost -p 1389 -D "cn=directory manager" -w Password -s base -b "" "objectclass=*" lastExternalChangelogCookie

The results will look something like this:

dn:
lastExternalChangelogCookie: o=Users:000001485c79fa40000100027397 00000147e
 f369c32359b00000004;

In this case, your cookie is:

o=Users:000001485c79fa40000100027397 00000147ef369c32359b00000004

Note the spacing!! Here’s another example returned:

dn: 
lastExternalChangelogCookie: dc=demo,dc=idm,dc=guru:00000148d66dd4901aa2000
 00402;

In this case, the cookie is:

lastExternalChangelogCookie: dc=demo,dc=idm,dc=guru:00000148d66dd4901aa200000402

Once you have the cookie value (without the trailing ‘;’) you can paste that back into the Scheduled Tasks. Make sure there is no trailing “;” and if you get errors about “..Cannot decode the provided control..” it’s due to the spacing in the cookie.

Good luck!

PS – Oracle claims to have fixed this issue in OUD. BP01 for OUD R2 PS2 includes a fix for this. See the Oracle KB Doc: Information And Bug Listing of Oracle Unified Directory Bundle Patches: 11.1.2.2.x (11gR2PS2) Version (Doc ID 1905631.1), and see the entry for
“Unpublished Bug:18495042 OIM RECEIVES UNWILLING_TO_PERFORM WHEN THE COOKIE IS TOO OLD”

PS2 – There is another Oracle doc that touches this issue: LDAP: error code 53: Running LDAP Sync Recon Job (Doc ID 1931485.1), however it only mentions adjusting the LDAP connection pool size.