Informix Error -197

Reasons / Common Causes

-197 is part of the same family as -169 and -178: newly added logged storage needs a backup baseline before it can be fully used. Here specifically, a partition was recently appended to a logged table or database, and a level-0 backup hasn't been performed yet to establish that baseline.

1. A partition (table or fragment) was recently added to a logged database or table, and a level-0 backup hasn't been performed since — the direct cause.
2. Logging was just enabled on a database (per -122/-128/-178), and an attempt to write to newly-logged partitions happened before completing the required level-0 archive.
3. A new fragment or partition added to an already-logged table without following through with a level-0 backup before writing to it.
4. Confusion about scope — the level-0 backup requirement applies to each newly-added logged partition or appended structure specifically, not just once for the whole database's lifetime. Having backed up the database previously doesn't cover a partition added afterward.

Solutions / Resolution

1. Perform a level-0 backup covering the target database, including the newly appended partition, before attempting to write to it — the direct fix per the official guidance.
2. Sequence work properly going forward: after adding a new partition to a logged table or database, follow immediately with a level-0 backup before resuming writes to it.
3. If this recurs even after a level-0 backup, treat it as a genuine anomaly — the official guidance explicitly says to note all circumstances and contact IBM Informix Technical Support in that case, rather than continuing to retry backups.

Examples

The required sequence

ALTER TABLE orders ADD FRAGMENT ...;
-- new partition appended to a logged table

ontape -s -L 0
-- level-0 backup covering the target database, including the new partition

INSERT INTO orders VALUES (...);
-- now succeeds against the newly appended partition

The scope mistake

-- Database was backed up last week
-- A new partition was added to a table in that database today
-- Writing to the new partition immediately fails with -197,
-- even though "a backup was done recently" for the database overall

The existing backup doesn't cover the newly appended partition specifically — a fresh level-0 backup is needed after this kind of structural change, not just periodically in general.

Diagnostic Checks

1. Confirm whether a level-0 backup has been performed since the partition was appended.
2. Review recent DDL history (partition/fragment additions) for the affected table or database.
3. If this recurs after a proper level-0 backup, gather full circumstances for escalation rather than continuing to attempt more backups.

Related Errors / Related Topics

• -169 — "ISAM error: Pages for TEXT or BYTE data can't be allocated from a chunk until chunk add is logged." The closest sibling in theme — newly added logged storage needing a step (there, forcing log rollover; here, a level-0 backup) before full use.
• -178 — "ISAM error: Database is locked; pending change to logging mode." Another member of the same family — a level-0 archive requirement tied to a logging-related change.

Perform a level-0 backup immediately after any structural change (a new partition, a new fragment) to a logged table or database — this is the standard follow-up step, not an occasional troubleshooting fix.