Informix Error -84500: 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 a optimistic concurrancy failure.
This error can occur when using updates on secondary and the current verstion of the row has not yet been replicated to the secondary on which the client application is connected.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-84500 is a duplicate-title code: the live official page's text is identical to -7350's — per the official guidance, an attempt was made to update a stale copy of a row, causing an optimistic-concurrency failure.
- 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 named cause, occurring when updates are made on a secondary.
Solutions / Resolution
- Retry the update, if the cause is replication lag — the row should catch up shortly.
Examples
N/A
No specific triggering statement is documented beyond replication lag between primary and secondary.
Diagnostic Checks
- Check replication lag between the primary and the secondary the client is connected to.
Related Errors / Related Topics
- -7350 — "Attempt to update a stale version of a row" This project's original entry for the same official title/text — confirmed the site genuinely lists this text twice, under two different codes; not a fabrication, documented per this project's established duplicate-content precedent.
- -84501 — "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.
An update targeted a stale row copy on an updatable secondary, likely due to replication lag — retry the update. This is a duplicate of -7350's official text under a different code number.