DIP DirSync Method Synchronization Spins When Synchronizing Active Directory Group With All Members Removed (Doc ID 1267097.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Internet Directory - Version: 10.1.4 and later   [Release: 10gR3 and later ]
Information in this document applies to any platform.

Symptoms

DIP DirSync method synchronization spins when attempting to synchronize a group from Active Directory (AD) that has had all it's members removed.

The synchronization profile trace log file in $ORACLE_HOME/shows lines similar to below, repeated indefinitely until the DIP sync java process is killed.

....
Searching For Attr: member;range=1000-1999 under DN: CN=Temps,CN=Groups,DC=oracle,DC=com
Searching For Attr: member;range=1000-1999 under DN: CN=Temps,CN=Groups,DC=oracle,DC=com
Searching For Attr: member;range=1000-1999 under DN: CN=Temps,CN=Groups,DC=oracle,DC=com
....


Stopping the odisrv synchronization process using oidctl... stop does not successfully stop the DIP java process. The Java process has to be killed manually.

The problem only occurs with groups that have been previously synchronized to OID with members.

The problem does not occur with the following events:
a) New group is added in AD with no members.
b) New group with no members that is already synchronized has any attribute other than member updated e.g. Description attribute updated in AD


Changes

A synchronized group that previously had members in AD has had all members removed.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms