Informix Error -793: Page size of the dbspace does not match page size of the table or index.

Reasons / Common Causes

-793 fires when a fragment (or, for interval fragmentation, a STORE IN dbspace) has a different page size than the table/index's other fragments — per the official guidance, every fragment of a table or index must share the same page size.

1. A new fragment/dbspace added with a different page size than the table/index's existing fragments — the direct, common cause.
2. For interval fragmentation specifically, a STORE IN clause listing dbspaces with page sizes that don't all match each other, or don't match the initial fragments' page size, per the official guidance's specific note about this case.

Solutions / Resolution

1. Ensure all dbspaces in the STORE IN clause share the same page size, per the official guidance, and that it matches the initial fragment dbspaces' page size, for interval fragmentation.
2. Check each dbspace's page size before adding it as a fragment/STORE IN target:

   onstat -d
   

   review the page-size column for each dbspace involved.
3. Use a dbspace with matching page size, or create a new dbspace with the correct page size, rather than trying to change an existing dbspace's page size (which isn't itself supported — page size is fixed at dbspace creation).

Examples

Checking dbspace page sizes

$ onstat -d
-- review page size for each dbspace involved in the table/index's
-- fragmentation scheme, including any new STORE IN targets

Diagnostic Checks

1. Compare the page size of every dbspace involved — existing fragments, and any new fragment or STORE IN target — confirming they all match.

Related Errors / Related Topics

• -794 — "One or more dbspaces for interval fragments do not exist." A related STORE IN clause error, about a referenced dbspace not existing at all, rather than existing with a mismatched page size.

Every fragment must share the same page size — check each dbspace's page size via onstat -d before adding it.