SunOne iPlanet To OID Import Synchronization Fails With Trace Log Message: Required Attribs not found [(|(objectclass] <entry DN> (Doc ID 1056156.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Internet Directory - Version: 9.0.4 to 10.1.4 - Release: 10gR1 to 10gR3
Information in this document applies to any platform.

Symptoms

Using Oracle Internet Directory (OID) Directory Integration Platform (DIP) import synchronization of SunOne iPlanet to OID.

Bootstrap suceeded, but synchronization does not work.

$ORACLE_HOME/ldap/odi/log/IplanetImport.trc file shows:
start time Wed Jan 20 12:17:54 GMT-06:00 2010
Required Attribute list [uid, objectclass, (|(objectclass]
Required Attribs not found [(|(objectclass] uid=testuser,ou=People,dc=mycompany,dc=com


After examining the import sync profile entries, noticed that the Connected Directory Matching filter was configured as follows:
orclodipcondirmatchingfilter=(|(objectclass=users)(objectclass=group)

In looking an example of a SunOne's changelog entry, it shows as follows:
$ ldapsearch -h <Sun host> -p <port> -D "cn=directory manager" -w <password> -b "cn=changelog" -s one "(&(objectclass=changelogentry)(changenumber=<change#))"

changenumber=73,cn=changelog
objectClass=top
objectClass=changelogentry
targetDn=uid=testuser,ou=People,dc=mycompany,dc=com
changeTime=20100120164736Z
changeType=add
changes=mail: testuser@mycompany.com
uid: testuser
givenName: testuser
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetorgperson
sn: testuser
cn: testuser
userPassword: {SSHA}8wpymcogMmLw2XqacKCGLY7USvS9CqQZ/Vh2NQ==
creatorsName: cn=directory manager
modifiersName: cn=directory manager
createTimestamp: 20100120164736Z
modifyTimestamp: 20100120164736Z
changeNumber=73

Since the changelog entries does not include "objectclass=users," and that is not typically an objectclass for SunOne entries, tried modifying the import sync profile filter to the following instead:
orclodipcondirmatchingfilter=(|(objectclass=person)(objectclass=group)

And restarted odisrv process for sync, so the change takes effect.

However the same sync profile trace log message continued.

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