OUD11g - Getting Duplicate Schema After DSEE To OUD Migration

(Doc ID 2251458.1)

Last updated on MAY 12, 2017

Applies to:

Oracle Unified Directory - Version 11.1.2.0.0 and later
Information in this document applies to any platform.
- When doing an OUD migration, one of the custom schema objectclass is not replaced in 99-user.ldif by the new definition.
The older definition comes from the DSEE side with migrateUserSchema.
DSEE version: 11.1.1.7.X
OUD Version: 11.1.2.X.Y

- After running the DSEE to OUD migration, custom schema iplanet-am-managed-group objectclass
appears twice, The old and the new definition.

Symptoms

 - After running the DSEE to OUD migration, custom schema iplanet-am-managed-group objectclass
appears twice,  The old and the new definition.

For example in the 99-user.ldif file

$OUD_ORACLE_INSTANCE/OUD/config/schema/99-user.ldif

Observing

objectClasses: ( 2.16.840.1.113894.1009.1.105.1.1002.2.1 NAME
'iplanet-am-managed-group' DESC 'Managed Group OC' SUP top AUXILIARY MAY (
inetgroupstatus ) X-ORIGIN 'Sun Java System Identity Management' )

objectClasses: ( 2.16.840.1.113730.3.2.180 NAME 'iplanet-am-managed-group'
DESC 'Managed Group OC' SUP top AUXILIARY MAY ( iplanet-am-group-subscribable
$ inetgroupstatus ) X-ORIGIN 'Sun Java System Identity Management' )

 

Where the first is the new definition

Migrate procedure have many steps, those are documented,

i.e.
Fusion Middleware Transition Guide for Oracle Unified Directory

more concise:

4 Executing The Transition

the only last two of them which are related to schema

10) migrate User Schema

$OUD_ORACLE_INSTANCE/OUD/bin/ds2oud --migrateUserSchema
--odseeBindDN 'cn=Directory Manager' --odseeHostname <odseehost1> --odseePort <odseeport1> --odseeBindPasswordFile /tmp/migratepwd.robot --oudBindDN
'cn=Directory Manager' --oudHostname <oudhost2> --oudPort <oudport2> --oudBindPasswordFile /tmp/migratepwd.robot --oudAdminPort 4444 --no-prompt

11) Apply new UCS schema definitions

export JAVA_HOME=/home/oracle/jdk7u79
$OUD_ORACLE_HOME/bin/ldapmodify -h <oudhost> -p <oudsslport> -D 'cn=Directory Manager' -j /tmp/migratepwd.robot --trustAll
--useSSL --filename oud-schema.ldif

This is related to

Bug 22758833 - DUPLICATE SCHEMA AFTER DSEE TO OUD MIGRATION

Which was closed as not a bug, explaining that, this is due to a miss-configuration, after some proper configuration, as follow, it works fine

Changes

 Migrate ODSEE to OUD

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