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

Reasons / Common Causes

-7351 fires when the connection between a secondary and its primary server is lost — per the official guidance, this prevents updates on the secondary until connectivity is reestablished.

1. A network or server-level interruption between the secondary and primary, per the official guidance — the direct, only cause.

Solutions / Resolution

1. Reestablish connectivity between the secondary and the primary, per the official guidance — updates on the secondary are blocked until this happens.

Examples

N/A

No specific triggering statement is documented beyond a network/server-level connectivity loss.

Diagnostic Checks

1. Check network connectivity and both servers' status between the secondary and primary, and reestablish the connection.

Related Errors / Related Topics

• -7350 — "Attempt to update a stale version of a row" A related replication error, about a stale row on an otherwise-connected secondary rather than connectivity loss itself.
• -7353 — "The transaction cannot continue on the new primary server." A related replication error, about a primary failover mid-transaction rather than a simple connectivity loss.
• -84501 — "Connection between secondary and primary has been lost" 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.

The connection between a secondary and its primary was lost — updates on the secondary are blocked until connectivity is reestablished.