My Oracle Support Banner

DB to OID Sync Fails During Mapping When a DB Field is Null, Using 'trunc" in 10.1.4.3 (Doc ID 1054433.1)

Last updated on FEBRUARY 25, 2019

Applies to:

Oracle Internet Directory - Version 10.1.4.3 and later
Information in this document applies to any platform.

Symptoms

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

 

    1. The profile .trc file shows:

      MAPPING: Attributes - Start
      MAPPING: Processing Map Rule : REPLACE
      MAPPING: Processing Map Rule : REPLACE
      Error in executing mapping null
      java.lang.NullPointerException
              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)
              ...

 

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

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


Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


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