Collision Rename Object Information

(Last modified: 09Mar2004)

This document (10062001) is provided subject to the disclaimer at the end of this document.

fact

Novell Directory Services 8

Novell eDirectory 8.7.0

Novell Directory Services 7

Novell Directory Services 6

goal

Collision Rename Object Information

symptom

Objects within an NDS database with the name of  0_0, 1_6, etc.

cause

These objects will occur because one of the following situations has been occurred therefore violating the rules of NDS:
1. Two objects have the same name in the same context
2. Two objects have the same creation timestamp (CTS)

The first number refers to the number of collisions on the object.  

The second number is the replica number where it collided.  If it is 0 then it is an external reference.  

fix

Depending on the object, both objects could be deleted.  If the collision (renamed) object is deleted, it is quite possible that obituaries will also be applied  to the 'good' object and therefore delete both of them.  

Usually the server that caused the collision rename will have the orginal object as well as the rename.

If the collision object or the object it collided with can not or should not be deleted (ie: a Server object or container), please call Novell Technical Support for additional assistance.

You can use dsbrowse > object search for CN=0_0, 1_6 etc  to look on that object F3> view attributes and check attribute CN which will tell you what the original name was.

note

It is possible to see collision renamed objects due to LDIF imports if the LDAP server does not hold a RW or M replica.

document

Document Title:	Collision Rename Object Information
Document ID:	10062001
Solution ID:	NOVL46386
Creation Date:	25Apr2001
Modified Date:	09Mar2004
Novell Product Class:	NetWare Novell eDirectory

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.