Informix Error -22648: Line is too long.
Cause and resolution
Line is too long.
This message indicates an IBM Informix ESQL/FORTRAN preprocessor error. The SQL statement is too long (greater than 32 kilobytes). In standard FORTRAN format, any nonblank character, except for zero, in column 6 is a continuation symbol. In UNIX-style FORTRAN format, an ampersand in column 1 is the continuation symbol. Shorten the SQL statement and try again.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-22648 fires when an embedded SQL statement exceeds 32 kilobytes — per the official guidance. In standard FORTRAN format, any nonblank, non-zero character in column 6 is a continuation symbol; in UNIX-style FORTRAN format, an ampersand in column 1 is the continuation symbol.
- An SQL statement larger than 32 kilobytes, per the official guidance — the direct, only cause.
Solutions / Resolution
- Shorten the SQL statement and try again, per the official guidance — use the appropriate continuation symbol (column-6 nonblank/non-zero for standard format, or a column-1 ampersand for UNIX-style format) to split it across lines if needed.
Examples
N/A
No specific triggering statement is documented beyond an SQL statement over 32 KB.
Diagnostic Checks
- Check the flagged SQL statement's total length, and shorten it below 32 KB, splitting across continuation lines if necessary.
Related Errors / Related Topics
- -22635 — "INTERNAL ERROR. Temporary buffer length has been exceeded." A related buffer-size error, on an internal temporary buffer rather than the SQL statement's own source-line length.
An embedded SQL statement exceeded 32 kilobytes — shorten it, using continuation lines if needed.