Oninit
Talk to an expert →

Informix Error -1377: SQL float-to-decimal conversion warning.

Cause and resolution

SQL float-to-decimal conversion warning.

The program set WHENEVER WARNING STOP, and a warning condition arose. The condition is that in the database that was just opened, the database server will use the DECIMAL data type for FLOAT values.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-1377 fires when a program has WHENEVER WARNING STOP set, and the database server will use DECIMAL in place of FLOAT for the newly opened database — per the official guidance, this is a database-level type-handling notice, surfaced on the DATABASE/CREATE DATABASE statement.

  1. The newly opened database configured such that the server uses DECIMAL for FLOAT values, per the official guidance — the direct, only named cause.
Solutions / Resolution
  1. Confirm whether this float-to-decimal handling is expected for the database being opened, and adjust WHENEVER WARNING handling if it's not actually a problem.
Examples
N/A

No specific triggering statement is documented beyond the DATABASE/CREATE DATABASE context itself — this is an informational notice about the opened database's FLOAT handling.

Diagnostic Checks
  1. Confirm the database being opened is expected to use DECIMAL in place of FLOAT.
Related Errors / Related Topics
  • -1374 — "SQL character truncation or transaction warning." A related WHENEVER WARNING STOP warning, in the same family of database-open-time 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.

The newly opened database uses DECIMAL in place of FLOAT — confirm this is expected.