Oninit
Talk to an expert →

Informix Error -5012: CSM: received message of unexpected type.

Cause and resolution

CSM: received message of unexpected type.

A CSM (Communications Support Module), in the database server or in the client, received a message with a type that is inconsistent with the protocol formats and/or internal state. This message is more specific than message -5011 because in this case the protocol data unit that is internally consistent might be carrying a message type that the receiver cannot handle. This error can occur only if a CSM is used. It can be caused by a communications error, by the use of incompatible versions of the CSM in the client and the database server, or by inconsistent configurations of the client and database server CSMs.

If this error occurs during context setup (that is, at connection time), The connection establishment fails. If this error occurs after Establishment of the connection, the connection is dropped.

Make sure that the release versions of the CSMs types match, and the configurations of client and database server CSMs match. If the problem recurs, contact IBM Informix Technical Support or the CSM vendor and have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-5012 fires when a CSM (Communications Support Module) receives a message whose type is inconsistent with the protocol formats and/or internal state — per the official guidance, this is more specific than -5011: the protocol data unit is internally consistent, but carries a message type the receiver can't handle.

  1. A communications error, per the official guidance — the first named cause.
  2. Incompatible CSM versions between client and database server, per the official guidance — the second named cause.
  3. Inconsistent CSM configurations between client and database server, per the official guidance — the third named cause.
Solutions / Resolution
  1. Make sure the release versions of the CSM types match, per the official guidance.
  2. Make sure the configurations of client and database server CSMs match, per the official guidance.
  3. If the problem recurs, contact IBM Informix Technical Support or the CSM vendor, per the official guidance, with the CSS configuration files and sqlhosts information for both sides available.
Examples
N/A

No specific triggering statement is documented beyond a communications error or a CSM version/configuration mismatch.

Diagnostic Checks
  1. Compare CSM release versions and configurations on the client and database server, and align them.
Related Errors / Related Topics
  • -5011 — "CSM: protocol error." The general version of this same class of error, for a protocol data unit with an unknown format rather than an unhandled-but-consistent message type.

A CSM received a message of an unhandled type — match CSM release versions and configurations between the client and database server.