Informix Error -9271: Type <opaque_type_name> is not identically defined in all the databases used in the distributed queries. </opaque_type_name>
Cause and resolution
Type <opaque_type_name> is not identically defined in all the databases used in the distributed queries. </opaque_type_name>
The attributes of the user-defined data type <opaque_type_name> are different on the local and remote databases. A UDT used in a distributed queries must have the same attributes and type hierarchy in all databases accessed by the query. </opaque_type_name>
Examine the definition of the <opaque_type_name> UDT in both your local and remote databases. Modify one or both of the UDTs so that they are the same. </opaque_type_name>
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-9271 fires when a user-defined data type's attributes differ between the local and remote databases in a distributed query — per the official guidance.
- A UDT with different attributes or type hierarchy on the local vs. remote database, per the official guidance — the direct, only cause; a UDT used in distributed queries must have the same attributes and type hierarchy in every database the query accesses.
Solutions / Resolution
- Examine the UDT's definition in both the local and remote databases, per the official guidance.
- Modify one or both UDTs so they're identical, per the official guidance.
Examples
N/A
No specific triggering statement is documented beyond a UDT definition mismatch across databases.
Diagnostic Checks
- Compare the UDT's definition (attributes and type hierarchy) between the databases involved, using the system catalog, and reconcile the differences.
Related Errors / Related Topics
- -9270 — "Type <opaque_type_name> is unsupported in distributed queries." A related distributed-query UDT error, on outright non-support rather than a definition mismatch.
A UDT's definition differs between the local and remote databases in a distributed query — reconcile the type definitions.