Novell Home

My Favorites

Close

Please to see your favorites.

Dstrace shows 646 errors on collision renamed objects in eDirectory 8.7.0

(Last modified: 19Jun2003)

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

fact

Novell NetWare 5.1

Novell NetWare 6.0 Support Pack 2

Novell eDirectory 8.7 for All Platforms

symptom

Dstrace shows error 646 bad naming attributes on collision renamed objects (IE., 0_1)

Dstrace shows error 609 missing mandatory attribute on non-present and\or collisioned renamed objects.

Trace shows all processed=yes but the transitive vectors will not merge

Replica stuck in a new state

Xref servers give a 601 back to the collision renamed object

Obituaries will not clear and iMonitor shows high max ring deltas

change

eDirectory was upgraded to version 8.7.0

cause

There is an issue with eDirectory 8.7 where DS sees that there is an object with a duplicate creation timestamp but contains different naming values.  This will effectively stop synchronization, partition ops and obit processing.

fix

The collisioned rename objects need to be deleted. Please refer to  TID 10062001.

This can be prevented in the future by applying the latest eDirectory patch for 8.7.0 - 8.7.0.3 or greater.

For additional information on eDirectory 8.7, please see the following solution.  NOVL81742 - eDirectory 8.7 Readme Addedum

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.

  • Document ID:
  • 10077923
  • Solution ID: NOVL85085
  • Creation Date: 18Dec2002
  • Modified Date: 19Jun2003
    • NovellNetWare

      eDirectory

Did this document solve your problem? Provide Feedback