Novell Home

My Favorites

Close

Please to see your favorites.

Using Rebuild Operation Schema in DSRepair

(Last modified: 15May2002)

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

goal

Using Rebuild Operation Schema in DSRepair

fact

Novell Directory Services 8

Novell Directory Services 7

Novell Directory Services 6

Novell eDirectory 8.6 for All Platforms

Novell eDirectory 8.5 (85.xx)

fix

Rebuild Operation Schema is commonly run by Novell Support individuals, customers, and consultants.  When running this repair it is critical that you understand exactly why or why not to use this option.

The main issues with "rebuild operational schema" are:
    (1)  flags, and
    (2)  rules changes
that customers may have done to their tree schema in order to get their customized or third party applications working "correctly".

By default, when this option is selected we force the local dib schema to comply with what the current loaded DS knows to be its original schema definitions (i.e., flags, rules, OIDs, boundaries, etc.), we leave additions to rules alone, but would add back any removed original rule to the class being checked.  

If the current flags found in the dib don't match what the loaded DS believes to be the real definitions, we change them to comply with it.  However, this action may have an undesirable consequence for applications the customer may have installed.

An advanced mode "no flag" check allows DSRepair to rebuild the operational schema without modifying any flags that may have been changed by the customer or his/her specific application.  This flag is the (-anf) switch.

We only addressed flags because there were few choices to allow for removing or putting back flags on schema attributes/classes that were simple to use.   As we all know, we can now use schema editors to add or remove rules without much effort, so no switch was provided for those type of changes.

In essence we want to give customers the flexibility of making changes in an educated manner but still give him/her the option to fix their trees if such modifications were to cause problems.

How do you know if Rebuild Operational Schema is safe for your environment?

In the Local database repair, you deselect everything but:  "Use temporary NDS database during repair?"  -> YES,  and "Rebuild operational schema?"  -> YES.     You will then see what changes DSRepair is planning on doing to the dib set and have the option to accept the changes or not.     Using iMonitor/DSBrowse, you can then check the proposed changes to see if they would indeed affect working applications on your servers and decide whether or not you should save the changes.

Once you have determined whether these changes would adversely affect your system you will know whether or not to run the repair.

NOTE:  To verify that the schema is OK, from the server holding the Master of [Root]:
    SET DSTRACE = OFF
    SET DSTRACE = +SCHEMA
    SET DSTRACE = *SSD
    SET DSTRACE = *SSA
Change to the Directory Services screen and very an ALL PROCESSED = YES.  If the response is ALL PROCESSED = NO, address errors listed.

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:
  • 10069531
  • Solution ID: NOVL75354
  • Creation Date: 27Mar2002
  • Modified Date: 15May2002
    • NovellManagement Products

      NetWare

      BorderManager Services

      eDirectory

Did this document solve your problem? Provide Feedback