Last updated on OCTOBER 05, 2016
Applies to:Oracle Internet Directory - Version 10.1.4.3 and later
Information in this document applies to any platform.
Oracle Internet Directory (OID) with Directory Integration Platform (DIP).
The system date on the Infra/OID server was changed by mistake to a date of months ahead, .e.g, six months in this case, and the system administrator did not notice it.
The Infra tier was started, and everything seemed to work. The DIP profile's last applied change number (lacn or LastChangeNumber) that OID has been exposed to was, for example, 1397245.
After the system date was corrected to be the current date, the oidsrv process would now expect the next LastChangeNumber, e.g., 1397196.
However, DIP falls asleep for 15833630751 ms (~ half a year !), as seen in the odisrv log snippet below:
fine Before GC ..
fine After GC ..
fine Total Memory in the JVM: 133300224
fine Free Memory in the JVM: 131520440
Sun Feb 20 15:40:11 NOVT 2011: Scheduler_3: Sleeping for 120 000 ms
Sun Feb 20 15:40:11 NOVT 2011: Scheduler: Sleeping for 15736874179 ms
Dip provisioning seems to try to process changes, as there is activity in the profiles' .trc and .aud provisioning and/or synchronization log files in $ORACLE_HOME/ldap/odi/log.
As a result, some users were created by applications integrated with OID (such as OIM for example), however they are registered with OIM only and did not get provisioned via DIP to other integrated applications (such as EBS for example).
OID server system date was changed further in time, and then reverted to right value.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms