Informix Error -9630: Cannot drop type (type_name): still in use.
Cause and resolution
Cannot drop type (type_name): still in use.
An opaque type cannot be dropped while it is in use. Be sure that no casts, functions, or distinct type definitions are based on the type.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-9630 fires when a DROP TYPE statement targets an opaque type that's still in use — per the official guidance.
- A cast, function, or distinct type still based on the opaque type, per the official guidance — the direct, only cause.
Solutions / Resolution
- Make sure no casts, functions, or distinct type definitions are based on the type, per the official guidance, before dropping it.
Examples
N/A
No specific triggering statement is documented beyond dropping a type with dependents.
Diagnostic Checks
- Check the system catalog for casts, functions, or distinct types that reference the opaque type, and drop those first.
Related Errors / Related Topics
- -9640 — "Cannot drop type (type_name): distinct type defined over the type." The same class of in-use error, naming the specific dependent (a distinct type) rather than the general category.
The opaque type is still in use by a cast, function, or distinct type — drop those dependents first.