Oninit
Talk to an expert →

Informix Error -23107: DBLANG and CLIENT_LOCALE environment variables are incompatible.

Cause and resolution

DBLANG and CLIENT_LOCALE environment variables are incompatible.

DBLANG is the environment variable that points to the location where the message files are stored. Usually, the value of DBLANG corresponds with that of CLIENT_LOCALE. The value of DBLANG could be en_US.8859-1 or a value set according to X/Open standards for locale definitions. The locale is a set of files that defines the characteristics of a particular language (for example, French or Japanese), a particular territory (for example, France or Japan) and a particular code set (for example, MS Windows Code Page 1251 or ISO 8859-1). An example of a locale name for the French language in Canada that is encoded using ISO 8859-1 would be fr_CA.8859-1, and a locale name for the Japanese language that is encoded using EUC (Extended Unix Code) would be ja_JP.ujis.

Reexamine the value of the environment variables, DBLANG and CLIENT_LOCALE.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-23107 fires when DBLANG and CLIENT_LOCALE don't correspond — per the official guidance. DBLANG points to where message files are stored and usually matches CLIENT_LOCALE's value (e.g. en_US.8859-1, or an X/Open-standard locale like fr_CA.8859-1 for Canadian French in ISO 8859-1, or ja_JP.ujis for Japanese in EUC).

  1. DBLANG and CLIENT_LOCALE set to incompatible locale values, per the official guidance — the direct, only cause.
Solutions / Resolution
  1. Re-examine the values of DBLANG and CLIENT_LOCALE, per the official guidance, and correct them so they correspond.
Examples
Checking DBLANG and CLIENT_LOCALE
$ env | grep -E 'DBLANG|CLIENT_LOCALE'
Diagnostic Checks
  1. Compare DBLANG and CLIENT_LOCALE's locale values, and correct whichever doesn't match the intended language/territory/code-set combination.
Related Errors / Related Topics
  • -23101 — "Unable to load locale categories." The general locale-loading error this is a specific case of, for a DBLANG/CLIENT_LOCALE mismatch.

DBLANG and CLIENT_LOCALE were incompatible — check that both name the same language/territory/code-set combination.