Informix Error -912

Reasons / Common Causes

-912 fires when a genuine network failure prevents writing to the database server — per the official guidance, distinct from -911's internal-pipe framing, this is specifically a network problem.

1. A network failure between the client and the database server, per the official guidance — the direct, named cause.
2. Network congestion or instability severe enough to break an in-progress write, rather than merely slowing the initial connection (compare -908's congestion framing at connect time).

Solutions / Resolution

1. Look for OS-level error messages that might give more information, per the official guidance.
2. Restart the application, per the official guidance — the documented first step.
3. If the problem recurs, contact your system administrator and ask for network diagnostics to be run, per the official guidance — this points toward genuine infrastructure troubleshooting, not an application-level fix.

Examples

N/A

A genuine network failure — restart the application first; escalate to the system administrator for network diagnostics if it recurs.

Diagnostic Checks

1. Check OS-level error messages around the time of the failure.
2. Restart the application as the documented first response.
3. Escalate to the system administrator for network diagnostics if it recurs.

Related Errors / Related Topics

• -913 — "Network error - Could not read from database server." The read-side counterpart to this write-side network failure.
• -911 — "System error - Cannot read from pipe." A related-sounding but distinct error — a local IPC failure rather than a genuine network problem.
• -908 — "Attempt to connect to database server (servername) failed." A related network-connectivity error, at the initial connection stage rather than an in-progress write.

A genuine network failure, not a local IPC issue — escalate to the system administrator for network diagnostics if restarting doesn't resolve it.