ERROR: 'flags' field was changed from 00200003 to 00200023 Ambiguous containment flag

(Last modified: 04Oct2004)

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

fact

Novell NetWare 6.0

Novell NetWare 5.1

Novell eDirectory 8.6 for NetWare 6

Novell eDirectory 8.6 for NetWare 5.1

symptom

ERROR: 'flags' field was changed from 00200003 to 00200023
Ambiguous containment flag

Schema Class Definition, Object ID: 000006D0, RDN: dcObject
ERROR: 'flags' field was changed from 00200003 to 00200023
Ambiguous containment flag
Field 'flags' changed from 00200023 to 00200003

Schema Class Definition, Object ID: 000001CE, RDN: federationBoundary
ERROR: 'flags' field was changed from 00200013 to 00200033
Ambiguous containment flag
Field 'flags' changed from 00200033 to 00200013

Schema Class Definition, Object ID: 000001CE, RDN: partition
ERROR: 'flags' field was changed from 00200013 to 00200033
Ambiguous containment flag
Field 'flags' changed from 00200033 to 00200013

DSRepair is adding SF_Ambiguous_Containment flags to a schema class then immediately stripping them back off.

No errors in sync or report sync status. Schema is getting all processed = yes.

note

When troubleshooting schema during a server install to a production tree, you may see various errors including 609 errors on objects during partition adding during the install. If the objects are objects that can be re-created without issue, then purge objects.

cause

The newer versions of eDirectory (8.6 and 8.7) do not have containment defined for partition, federationBoundary, and dsObject.  For this reason, everytime DSREPAIR is ran against these databases, the SF_Ambiguous_Containment flag is added as defined in the default schema operational rules. 

NOTE: For more information on the use of the SF_Ambiguous_Containement flag, refer to solution NOVL80807 

There is another check in DSREPAIR that checks ruleids.  This basically looks at the flags set on a class and makes sure that the class definition agrees with the flags that are on the class.  If partition, federationBoundary or dsObject have containment defined on the class (older versions of NDS defined containement for these classes so in upgrade scenarios or mixed ring scenarios, there may be containement on these classes), DSREPAIR will strip the SF_Ambiguous_Containment flag off of the class which is correct.  The flag should not exist if there is containment on that class.

fix

The end result of this is that schema is fine.  The flag was added and stripped back off.  It is an annoyance because it increments the error count in DSREPAIR when this really is not an error.  To avoid this, run DSREPAIR with a -anf switch.  This switch will not perform the flag checks and so will not add or remove the flags.

document

Document Title:	ERROR: 'flags' field was changed from 00200003 to 00200023 Ambiguous containment flag
Document ID:	10069151
Solution ID:	NOVL74214
Creation Date:	13Mar2002
Modified Date:	04Oct2004
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.