Informix Error -79785: Unable to convert JDBC escape format date string to localized date string.

Cause and resolution

Unable to convert JDBC escape format date string to localized date string.

The JDBC escape format for date values must be specified in the format {d 'yyyy-mm-dd'}.

Verify that the JDBC escape date format specified is correct. Verify the DBDATE and GL_DATE settings for the correct date string format if either of these was set to a value in the connection database URL string or property list.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-79785 fires when a JDBC escape-format date string can't be converted to a localized date string — per the official guidance, the escape format for dates is {d 'yyyy-mm-dd'}.

A date string not in {d 'yyyy-mm-dd'} escape format, per the official guidance — the direct, only cause.

Solutions / Resolution

Verify the JDBC escape date format is correct, per the official guidance.
Verify the DBDATE/GL_DATE settings, per the official guidance, if either was set in the connection URL or property list.

Examples

N/A

No specific triggering statement is documented beyond a malformed escape-format date string.

Diagnostic Checks

Check the date string's escape-format syntax, and check DBDATE/GL_DATE settings if configured.

Related Errors / Related Topics

-79786 — "Unable to build a Date object based on localized date string representation." A related date-conversion error, on building a Date from a localized string in a CHAR/VARCHAR/LVARCHAR column rather than converting a JDBC escape-format string.

A JDBC escape-format date string couldn't be converted — verify its {d 'yyyy-mm-dd'} format and the DBDATE/GL_DATE settings.