Oninit
Talk to an expert →

Informix Error -7350: Attempt to update a stale version of a row

Cause and resolution

Attempt to update a stale version of a row

An attempt was made to update a stale copy of a row. This caused an optimistic concurrancy failure.

This error can occur when using updatable secondary and the current version of the row has not yet been replicated to the secondary on which the client application is connected.

This error code is also returned when table schema at secondary server doesn't match with the table schema at primary server.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-7350 fires when an update targets a stale copy of a row — per the official guidance, an optimistic-concurrency failure.

  1. The current version of the row hasn't yet been replicated to the (updatable) secondary the client is connected to, per the official guidance — the first named cause.
  2. The table schema on the secondary doesn't match the table schema on the primary, per the official guidance — the second named cause.
Solutions / Resolution
  1. Retry the update, if the cause is replication lag — the row should catch up shortly.
  2. Check that the secondary's table schema matches the primary's, per the official guidance, and reconcile any drift if the error persists.
Examples
N/A

No specific triggering statement is documented beyond replication lag or a schema mismatch between primary and secondary.

Diagnostic Checks
  1. Check replication lag between the primary and the secondary the client is connected to.
  2. Compare the table's schema on the primary and the secondary for a mismatch.
Related Errors / Related Topics
  • -7351 — "Connection between secondary and primary has been lost" A related replication error, about connectivity loss rather than a stale row on an otherwise-connected secondary.
  • -84500 — "Attempt to update a stale version of a row" A duplicate-title code — the live site lists this exact official text a second time under a different code number; confirmed as a genuine site-side duplication, not a fabrication.

An update targeted a stale row copy on an updatable secondary — likely replication lag or a primary/secondary schema mismatch.