eG Monitoring
 

Measures reported by VMLDAPDColisnTest

If duplicate LDAP entries are created on two or more View Connection Server instances, this can cause problems with the integrity of LDAP data in View. This test checks the ADAM database at pre-configured intervals for the existence of collision references and colliding entries, and reports the count of such entries (if any are found), so that they can be removed with immediate effect to ensure data integrity.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Found_Colisn_Reference Indicates the number of collision references currently found in the ADAM database. Number Typically, the value 0 is desired for both these measures. A non-zero value indicates the existence of colliding entries. For example, this condition can happen during an upgrade while LDAP replication is inoperative.

When colliding entries exist in the LDAP directory (ADAM database), identify what those entries are and resolve the collision.
Found_Colisn_References Indicates the number of collision entries currently found in the ADAM database. Number
Found_Deleted_Reference Indicates the number of collision references currently deleted from the ADAM database. Number  
Local_View_LDAP_Dir Indicates whether any collision references were currently found in ADAM database or not.   If this measure reports the value clean, it indicates that no collision references were found in LDAP (ADAM database) directory.

The value Not Clean means there are collision references in LDAP (ADAM database) directory.

The numeric values that correspond to the measure values discussed above are as follows:

State Numeric Value
Clean 1
Not Clean 0

Note:

By default, this measure reports the above-mentioned States while indicating whether/not collision references were found in the LDAP directory. However, in the graph of this measure, the same will be indicates using the corresponding numeric equivalents of the states as mentioned in the table above.