Informix Error -949

Reasons / Common Causes

-949 fires when ALTER FRAGMENT is attempted on a table that currently has disabled indexes — per the official guidance, this isn't allowed, and the action is aborted outright.

1. ALTER FRAGMENT attempted while one or more of the table's indexes are in DISABLED mode, per the official guidance — the direct, only cause.
2. An index disabled for a bulk load or maintenance operation, left disabled when a fragmentation change was also attempted during the same maintenance window.

Solutions / Resolution

1. Re-enable the table's indexes first, using the same SET INDEXES FOR tablename ENABLED mechanism discussed for -892/-893:

   SET INDEXES FOR orders ENABLED;
   

2. Then perform the ALTER FRAGMENT operation, once indexes are enabled.
3. Re-disable the indexes afterward, if the original reason for disabling them (a bulk load still in progress, for instance) is still in effect.

Examples

Re-enabling indexes before altering fragmentation

SET INDEXES FOR orders ENABLED;
ALTER FRAGMENT ON TABLE orders ADD new_west_dbspace (region = 'west');

Diagnostic Checks

1. Check whether any of the table's indexes are currently disabled before attempting ALTER FRAGMENT:

   SELECT idxname FROM sysindexes WHERE tabid =
     (SELECT tabid FROM systables WHERE tabname = 'orders');
   -- cross-reference with sysconstraints/object-mode state for disabled indexes
   

Related Errors / Related Topics

• -892 — "Cannot disable object object-name due to other active objects using it." A related object-mode restriction, about disable-ordering dependencies.
• -893 — "Cannot activate/create object object-name because of its dependencies." A related object-mode restriction, about enable-ordering dependencies.

Re-enable the table's indexes first (SET INDEXES FOR tablename ENABLED), then perform the fragmentation change.