Informix Error -1375: SQL NULL value in aggregate or mode ANSI database warning.

Reasons / Common Causes

-1375 fires when a program has WHENEVER WARNING STOP set and a warning condition arises — per the official guidance, on a DATABASE statement the warning means the opened database is ANSI-compliant; on any other statement, it means a NULL value was used in an aggregate computation.

1. The opened database being ANSI-compliant, per the official guidance's specific DATABASE-statement case — a warning, not necessarily a problem, but one WHENEVER WARNING STOP treats as an error.
2. A NULL value included in an aggregate computation, per the official guidance's general case for other statements — aggregates like SUM/AVG silently skip NULLs, and this warning flags that it happened.

Solutions / Resolution

1. If triggered by DATABASE, confirm whether ANSI mode is expected for that database, and adjust WHENEVER WARNING handling if it's not actually a problem.
2. If triggered by another statement, review whether NULL values in the aggregated column are expected, and decide whether that's acceptable or needs filtering.

Examples

Distinguishing the two cases

WHENEVER WARNING STOP
DATABASE stores7
-- -1375 here means: stores7 is an ANSI-compliant database

SELECT AVG(total) INTO v_avg FROM orders;
-- -1375 here (a different statement) means: some total values were NULL

Diagnostic Checks

1. Identify which statement triggered the warning — a DATABASE statement means ANSI mode; any other statement means a NULL in an aggregate.

Related Errors / Related Topics

• -1374 — "SQL character truncation or transaction warning." A related WHENEVER WARNING STOP warning, sharing the same DATABASE-statement-vs.-other-statement interpretation split.

Depends on which statement triggered it — DATABASE means ANSI mode; any other statement means a NULL in an aggregate.