Informix Error -794: One or more dbspaces for interval fragments do not exist.

Reasons / Common Causes

-794 fires when an interval-fragmented table/index's STORE IN clause names one or more dbspaces that don't actually exist — per the official guidance, the direct, only cause.

1. A misspelled dbspace name in the STORE IN clause — the most likely, direct cause.
2. A dbspace referenced that was planned but never actually created, or was later dropped.

Solutions / Resolution

1. Contact the database server administrator to have the dbspaces added, per the official guidance, if the named dbspaces were genuinely intended and just don't exist yet.
2. Or use ALTER FRAGMENT to modify the STORE IN clause, per the official guidance, listing dbspaces that actually exist:

   ALTER FRAGMENT ON TABLE orders MODIFY STORE IN (existing_dbspace1, existing_dbspace2);
   

3. Always confirm page-size compatibility too, per the official guidance's closing note — matching a dbspace's existence alone isn't sufficient; its page size must also match the table/index (see -793).
4. Check which dbspaces actually exist:

   onstat -d
   

Examples

Checking existing dbspaces before naming them in STORE IN

$ onstat -d
-- review the list of dbspaces currently configured on this instance,
-- and their page sizes

Correcting the STORE IN clause

ALTER FRAGMENT ON TABLE orders MODIFY STORE IN (interval_dbspace1, interval_dbspace2);

Diagnostic Checks

1. Run onstat -d to confirm which dbspaces actually exist, and check the STORE IN clause's named dbspaces against that list.
2. Check page-size compatibility for any dbspace confirmed to exist, per -793.

Related Errors / Related Topics

• -793 — "Page size of the dbspace does not match page size of the table or index." A related STORE IN clause error, about page-size mismatch once the dbspace is confirmed to exist, rather than nonexistence.

Confirm the dbspace exists first (onstat -d), then confirm its page size matches, per -793.