DIP 12C How to Align orclodipConDirLastAppliedChgNum When Changing the AD DC Server (Doc ID 2982241.1)

Last updated on NOVEMBER 08, 2023

Applies to:

Symptoms

 DIP synchronization has been configured between OID 12C and Active Directory, and now the AD server needs to be changed, from AD server Domain Controller 01 (DC01)
to AD server Domain Controller 02 (DC02), a second server in an AD multi-master configuration, where:
- both servers, the old one DC02 and the new one DC02 are in the same Windows domain
- FQDNs of the servers are DomainController01.<DOMAIN_NAME> and DomainController02.<DOMAIN_NAME>

This document is a follow up from Doc ID 735248.1 (which was from 10g and 11g DIP).

If for example the highestCommittedUSN on the second server (DomainController02) is much lower than on the original server (DomainController01), due to the number of changes (usn) being different at the AD DC server level in the same Windows domain per the USN change approach theory in AD.

Because of this difference, the OID synchronization profile will not store any changes until the lower highestCommittedUSN catches up with the orclodipConDirLastAppliedChgNum in the profile.

Nevertheless, in the same Windows domain, objects (users, groups, etc.) are replicated between all AD DC servers.

This document describe how to re-align the highestCommittedUSN values in the profile in order to continue DIP synchronisation.

Changes

 New AD server from the same windows domain need to be used with DIP 12c

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.