Oninit
Talk to an expert →

Informix Error -1378: SQL non-ANSI extension warning.

Cause and resolution

SQL non-ANSI extension warning.

A database operation was performed that is not part of ANSI SQL, although the current database is ANSI compliant. This message is informational only.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-1378 fires when a database operation outside ANSI SQL is performed against a database that is itself ANSI-compliant — per the official guidance, this message is purely informational.

  1. A non-ANSI SQL extension used against an ANSI-compliant database, per the official guidance — the direct, only cause, and not itself a problem.
Solutions / Resolution
  1. No action is required, per the official guidance's own framing — this message is informational only.
  2. If WHENEVER WARNING STOP is causing this to interrupt the program unexpectedly, review whether that setting is appropriate for a purely informational warning like this one.
Examples
N/A

No specific triggering statement is documented — this is a routine, informational notice about using a non-ANSI extension on an ANSI-compliant database.

Diagnostic Checks
  1. Confirm the message is purely informational in context, per the official guidance, before treating it as an actionable problem.
Related Errors / Related Topics
  • -1374 — "SQL character truncation or transaction warning." A related WHENEVER WARNING STOP warning, in the same family of database-related notices.
  • -1375 — "SQL NULL value in aggregate or mode ANSI database warning." Another related WHENEVER WARNING STOP warning.
  • -1376 — "SQL, database server, or program variable mismatch warning." Another related WHENEVER WARNING STOP warning.
  • -1377 — "SQL float-to-decimal conversion warning." Another related WHENEVER WARNING STOP warning.

A non-ANSI SQL extension was used on an ANSI-compliant database — informational only, no action required.