My Oracle Support Banner

OID 10g DIP Sync Fails With Trace File Error: ODIException: Incorrect Format: First Line after TAG should be an attr:Val Pair (Doc ID 1266705.1)

Last updated on APRIL 28, 2021

Applies to:

Oracle Internet Directory - Version 9.0.4 to 10.1.4.3 [Release 10gR1 to 10gR3]
Information in this document applies to any platform.

Symptoms

Directory Integration Platform (DIP) synchronization updates from Active Directory (AD) to Oracle Internet Directory (OID) 10g stopped working.

The sync profile with debug level 63 shows the following error on the trace file:

Incorrect Format: First Line after TAG should be an attr:Val Pair
ODIException: Incorrect Format: First Line after TAG should be an attr:Val Pair
    at oracle.ldap.odip.engine.ConfigReader.readConfigInfo(ConfigReader.java:182)
    at oracle.ldap.odip.engine.Profile.initConfigInfo(Profile.java:551)
    at oracle.ldap.odip.engine.Profile.initialise(Profile.java:214)
    at oracle.ldap.odip.engine.Profile.initProfile(Profile.java:507)
    at oracle.ldap.odip.engine.SchedEntry.<init>(SchedEntry.java:65)
    at oracle.ldap.odip.engine.Scheduler.addToSyncList(Scheduler.java:975)
    at oracle.ldap.odip.engine.Scheduler.updateChanges(Scheduler.java:1461)
    at oracle.ldap.odip.engine.Scheduler.run(Scheduler.java:314)


Changes

After upgrading / applying patchset to OID, noticed that a lot of DIP sync updates were missed.  Tried to up the profile configuration delta time to 1000 from default 500 to catch up with the AD updates, but since then DIP sync stopped working.

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
Changes
Cause
Solution


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