Oninit
Talk to an expert →

Informix Error -253

-253 Identifier length exceeds the maximum allowed by this version

of the server.

An SQL identifier exceeded the maximum number of characters. In IBM Informix Dynamic Server 9.2x or later, the maximum length for identifiers in SQL statements is 128 characters. In other Informix database servers, the maximum length for identifiers in SQL statements is 18 characters.

Check that no identifier in the statement is longer than the maximum length and that no punctuation error, such as a missing space or comma, combines two identifiers into one.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-253 is functionally the same condition as -200 — the official explanatory text is nearly word-for-word identical. An SQL identifier exceeded the version-specific maximum: 128 characters on IBM Informix Dynamic Server 9.2x or later, 18 characters on other Informix database servers. Which specific code (-200 or -253) you see for this condition appears to depend on the exact code path or version involved, but the causes and fixes are the same.

  1. A genuinely long identifier exceeding the version-specific maximum.
  2. A punctuation error combining two identifiers into one — a missing space or comma merging two ordinary, correctly-sized identifiers into what the parser reads as a single, much longer one. The official text calls this out explicitly, exactly as it does for -200.
  3. Auto-generated identifiers growing beyond the limit over time, or SQL ported from a system with a more generous identifier length limit.
  4. Version confusion about which limit (128 vs. 18) actually applies.
Solutions / Resolution

See -200 for the full treatment — it applies here without modification:

  1. Check that no identifier exceeds the maximum length for the server version in use.
  2. Check for a missing space, comma, or other punctuation combining two identifiers into one — often the actual cause even when the statement looks like it has only reasonably-sized names.
  3. Confirm the server version/product if there's doubt about which limit applies.
Examples

See -200's examples — the punctuation-error case (a missing comma merging two column names) and the genuinely-long-identifier case both apply identically here.

Diagnostic Checks
  1. Count identifier lengths against the applicable limit.
  2. Review the statement for missing punctuation between identifiers.
  3. Confirm the server version/product in use.
Related Errors / Related Topics
  • -200 — "Identifier is too long." The functionally identical sibling — same official explanatory text, same causes, same fixes. See that entry for the fuller treatment.

This is the same condition as -200 under a different code number — refer there for the complete guidance rather than duplicating it here.