| Previous | Next |
| ERROR_DS_BAD_RDN_ATT_ID_SYNTAX | ERROR_DS_EXISTS_IN_SUB_CLS |
ERROR_DS_EXISTS_IN_AUX_CLS
The class remains in an auxiliaryClass dependency list
A schema class can augment another class through auxiliaryClass or systemAuxiliaryClass. This status reports that a class targeted for removal or deactivation is still referenced in such a relationship. Removing it would invalidate the schema of every class that depends on its auxiliary attributes and inheritance contribution.
Search the schema naming context for reverse references to the target class. Then determine whether the dependency belongs to a custom extension or a system definition. Schema cleanup must proceed from dependent definitions toward the referenced class, and production schema elements are commonly treated as permanent. Deleting the target first is not a safe way to unwind an extension.
What to inspect
- Find class definitions containing the target in auxiliary-class lists.
- Identify deployed object classes and applications that rely on the auxiliary relationship.
- Use a documented schema migration or defunct strategy instead of forceful deletion.
References
Looking for a different code? Search another status or error code.