Informix Error -84501: Connection between secondary and primary has been lost

Reasons / Common Causes

-84501 is a duplicate-title code: the live official page's text is identical to -7351's — per the official guidance, the connection between the secondary and primary has been lost, preventing updates on the secondary until connectivity is reestablished.

1. The connection between secondary and primary being lost, per the official guidance — the direct, only cause.

Solutions / Resolution

1. Reestablish connectivity between the secondary and primary, per the official guidance, before further updates on the secondary can proceed.

Examples

N/A

No specific triggering statement is documented beyond a lost primary/secondary connection.

Diagnostic Checks

1. Check network connectivity and replication status between the secondary and primary, and reestablish the connection.

Related Errors / Related Topics

• -7351 — "Connection between secondary and primary has been lost" 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.
• -84500 — "Attempt to update a stale version of a row" A related replication error, on a stale row on an otherwise-connected secondary rather than a lost connection.
• -84502 — "XA transactions are not supported on read-only secondary servers" A related secondary-server restriction, on XA transactions specifically rather than connectivity loss.

The connection between secondary and primary was lost, blocking secondary updates until reestablished. This is a duplicate of -7351's official text under a different code number.