By Sylvain Duloutre-Oracle on Aug 19, 2010
The DPS 6.x and 7.x default configuration must be slightly changed to be
able to work smoothly with OID. Indeed, the DPS health-check engine might compute OID operational state incorrectly and
consider OID down when it is up and running.
There are 2 ways to fix that: either disable the proactive health-check monitoring or (recommended) change the LDAP query done to determine the backend operational state. To do so, make sure DPS is running and launch the command below on each ldap data source associated with an OID instance:
dpconf set-ldap-data-source-prop <data source> monitoring-search-filter:(objectclass=\*)
Note: this configuration is not specific to OID and works well with other directory server instances, including DSEE.