DB to OID Sync Fails During Mapping When a DB Field is Null, Using 'trunc" in

(Doc ID 1054433.1)

Last updated on JULY 01, 2016

Applies to:

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


  1. Since patching OID from to, db to OID sync fails during mapping when one of the fields in the db is null, even though it's not mandatory.

  2. The profile .trc file shows:

    MAPPING: Attributes - Start
    MAPPING: Processing Map Rule : REPLACE
    MAPPING: Processing Map Rule : REPLACE
    Error in executing mapping null
            at oracle.ldap.odip.map.MapEngine.evaluate(MapEngine.java:918)
            at oracle.ldap.odip.map.MapEngine.evalstack(MapEngine.java:1256)
            at oracle.ldap.odip.map.MapEngine.ConvertValue(MapEngine.java:832)

  3. An edit rule is in use with 'trunc' function. For example:

    MIDDLE_NAME: : : :middleName: :inetOrgperson:trunc(MIDDLE_NAME,'^')


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