| Previous | Next |
| ERROR_DS_CANT_REMOVE_ATT_CACHE | ERROR_DS_CANT_RETRIEVE_DN |
ERROR_DS_CANT_REMOVE_CLASS_CACHE
A cached class still has relationships that prevent clean removal
Class definitions participate in an inheritance and placement graph: subclasses point to superclasses, classes can use auxiliary classes, and possible-superior lists reference other classes. This status occurs when the directory cannot remove a class cleanly from its in-memory schema state. It is therefore closely tied to schema dependency integrity.
Inspect reverse references to the class before treating the cache as corrupt. A class still used in subClassOf, auxiliary-class lists, or possible-superior lists has semantic dependents that must remain resolvable. If the error follows a custom schema change, compare the modification sequence with the extension design and locate the first dependency error that preceded cache cleanup.
What to inspect
- Find subclasses, auxiliary references, and possible-superior references to the class.
- Correlate the failure with the exact schema object changed immediately beforehand.
- Use supported schema migration procedures instead of attempting to force cache deletion.
References
Looking for a different code? Search another status or error code.