Cross platform method to mutate unknown objects with iMonitor

  • 7004408
  • 09-Sep-2009
  • 26-Apr-2012

Environment

Novell eDirectory 8.8 for All Platforms
Novell eDirectory 8.7.3.10 for All Platforms

Situation

Unknown Objects in the tree
Mutating unknown objects with iMonitor

Resolution

- The easiest way to address this issue is removing and recreating the object.  There's some situations where this isn't possible, eg the object in question is a container.  In that case, the following cross platform procedure can be used.

1. Start iMonitor

2. Click on NDS iMonitor in the upper left corner of the frame.  In the "NDS iMonitor Configuration" section, choose the 'Enabled' radio buttion and click on 'Submit'.

3. Navigate to the object in question.

4. Choose Advanced Options -> Mutate Entry.  If this doesn't succeed, two error codes could be returned.

-609 (Missing Mandatory)

The mutate doesn't complete as a mandatory attribute for the class is missing, eg surname on a user object.  In some cases, the attribute can be added via iManager or an ldif file.

-603 (No Such Attribute)

The mutate doesn't complete as the unknownbaseclass attribute is missing.  Determine the appropiate class and add it via iManager.

5. Additional Advanced Options need to be added.  Navigate to the object in question and add '&op=all' to the end of the URL.

6. Choose Advanced Options -> Mark Entry New.  (This removes the reference flag from the object and allows the changed to synch to the other servers.)

In some cases, the object still won't synch immediately.  If this needs to be done, choose Advanced Options -> TimeStamp Entry.

Note: A NetWare specific procedure is detailed below.  However, it can only be used with NetWare 5.1 and previous versions, as it requires dsdiag.nlm.  This utility isn't supported any longer.

Verify schema synchronization.

If objects are known on one database and not on another, run DSREPAIR -P | Advanced Options | Repair Local Database | Check Local References on the databases with unknown objects.

If all databases show the objects unknown, grab a DIB set (DSREPAIR -RC) and then follow the instructions that follow.

***This must be preformed on a WRITABLE (MASTER or READ/WRITE) copy of the partition.

NOTE:  This will only work if the unknown object as an attribute called Unknown Base Class.  Load DSBROWSE | High Light the unknown object | F3 |Check to see if there is an attribute called Unknown Base Class.  If there is this attribute, then the DSDIAG will make the object known again.

Using DSDIAG   (DSDIAG ships with NW5, however it does not with NW4.11, but it can be downloaded from our web site)

1) Load DSDIAG -DA
2) Choose Preferences  |  Manage Identities
3) Login as Admin, or Admin equiv.   You will get a list, if Admin is not on the list, press INS and type in cn=admin.o=<organization name>   You must use the fully distinguished name.
4) Go back to the main menu
5) Choose Distributed repair (or repair tools)   |   Mutate Unknown objects
6) At this point a new menu comes up and you will have to fill in the following options
     - Retrieve Partition Roots Using:   NDS   (Leave this at NDS)
     - Context: enter the context (see Step 3 above for the format) that the unknown objects are in
     - Depth:  Subtree (this mean that from the context down it will search for unknown objects)
     - Mutate unknown entries: On  (default is off - change to ON)
     - Delete Unknown base class:  Before (the choice of before or after is available)
     - resend mutate objects: On  (the default is off - change to ON)
     - Report file:  this is a report file that is available.  You can choose to have it or not.
7) run the repair (F10)
8) when finished, check NWADMIN and see if the objects are known.

Additional Information

Missing mandatory attribute(s).
Formerly known as TID# 10019291

Feedback service temporarily unavailable. For content questions or problems, please contact Support.