Informix Error -444
-444 Cannot use the ALTER TABLE statement to modify the extent size of
the specified external table.The size of extents cannot be changed for an external table, which resides in an extspace. An extspace refers to a storage location that the Informix database server does not manage.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-444 is a structural restriction on external tables: extent size is a storage-management concept
tied to Informix-managed dbspaces, but external tables live in an extspace — a storage location
managed independently of the Informix server (a flat file, or an external data source) — so
there's no extent size for ALTER TABLE to modify in the first place.
- An
ALTER TABLEstatement attempting to modify extent size on an external table — the direct, only cause. - Generic schema-management scripts written for ordinary tables, applied unmodified to an external table — the extent-size clause doesn't apply there and never will.
- Confusion about what an external table actually is — it's a mapping onto external storage, not an ordinary Informix-managed table with the usual physical storage attributes.
Solutions / Resolution
- Don't attempt to modify extent size on an external table, per the official guidance — it's architecturally not applicable, not just restricted.
- If storage layout needs to change, that has to happen at the level of the external storage
itself (the flat file or external data source), not through Informix's
ALTER TABLE. - For generic schema-management scripts, exclude external tables from any extent-size-related
ALTER TABLElogic.
Examples
The disallowed attempt
ALTER TABLE external_orders MODIFY NEXT SIZE 100;
-- -444: external_orders lives in an extspace; extent size
-- doesn't apply
Confirming a table is external before scripting ALTER TABLE logic
SELECT tabname, tabtype FROM systables WHERE tabname = 'external_orders';
-- external tables have a distinct tabtype; exclude them from
-- extent-size-related ALTER TABLE scripts
Diagnostic Checks
- Confirm whether the target table is external before attempting any extent-size-related
ALTER TABLEoperation. - Review generic schema-management scripts for logic that doesn't account for external tables' different storage model.
Related Errors / Related Topics
- -322 — "Cannot Alter view, Rename view or Create a trigger on a view." A related "this object type doesn't support this ALTER operation" restriction, for views instead of external tables.
- -370 — "Cannot drop last column." Another
ALTER TABLE-related structural restriction, in a different context.
External tables live outside Informix's own storage management (in an extspace) — extent size,
like several other physical-storage attributes, simply doesn't apply to them.