Informix Error -361

Reasons / Common Causes

-361 is explicitly documented as an internal error reflecting a communications problem between the database server and the client application, rather than an ordinary SQL-level mistake a developer would trigger through normal query writing. The official guidance is direct: this shouldn't normally occur in practice.

1. A client/driver-level communication protocol mismatch or bug, where the size information exchanged between the application and server becomes corrupted or misinterpreted.
2. A driver or client library bug, particularly in older or less common client libraries, miscalculating or mis-encoding a column size value sent to the server.
3. Network-level corruption affecting the data exchanged between client and server in rare cases.

Solutions / Resolution

1. Don't expect to encounter this under normal usage, per the official guidance — this is an internal-level error, not a query-design issue to fix in SQL.
2. If it recurs, document the exact circumstances (client driver and version, statement being executed, connection details) as thoroughly as possible.
3. Contact IBM Informix Technical Support with that documentation, per the official guidance, rather than attempting to work around it at the application level.
4. Check for a client driver/library update if the error recurs consistently with a specific client, since a driver bug is a plausible root cause.

Examples

Documenting the circumstances for a support case

- Client driver and version in use
- Exact statement being executed
- Server version
- Frequency: one-off or reproducible?
- Any other errors or anomalies around the same time

Diagnostic Checks

1. Confirm whether the error is a one-off or reproducible with a specific client driver/version combination.
2. Check for available updates to the client driver/library in use.

Related Errors / Related Topics

• -306 — "Subscript out of range." An unrelated, ordinary application-level size/bounds error, useful as a contrast — -361 is explicitly an internal/communications-level issue instead.

This is documented as an internal error, not a query-writing mistake — if it recurs, gather detailed reproduction information and escalate to IBM Informix Technical Support rather than searching for a SQL-level fix.