Oninit
Talk to an expert →

Informix Error -29033: Informix GLS locale could not be loaded: localename, errno, locale-file-name.

Cause and resolution

Informix GLS locale could not be loaded: localename, errno, locale-file-name.

localename The name of the IBM Informix GLS locale that could not be loaded. The value for localename must be of the format language_territory.codeset.

errno A number that indicates the specific reason that the IBM Informix GLS locale could not be loaded.

locale-file-name The subdirectory and filename (for example, /en_US/0333.lco) of the IBM Informix GLS locale file that could not be loaded.

language A two-letter lowercase abbreviation for the language name.

territory A two-letter uppercase abbreviation for the territory name.

codeset The name of the character code set for the locale.

Valid values for the codeset field are registered in the $INFORMIXDIR/gls/cm/REGISTRY file. The values are character strings that describe the code set. However, if a codeset field value is an integer in the range from 1 to 65,535, it is an acceptable value even if it is not in the REGISTRY file.

An attempt to load the IBM Informix GLS locale that localename specified failed for the reason that errno indicates, as follows:

6- The locale specification localename is in a bad format.

The Gateway administrator must correct this specification.

7- The locale file that locale-file-name specified does not exist.

If the appropriate directory (see the following paragraph) does not contain the locale file that the subdirectory and filename that locale-file-name specified, this IBM Informix GLS locale is not available. Read your IBM Informix product documentation to ensure that you specified the IBM Informix GLS localename correctly (using environment variables or other mechanisms that the documentation describes). The IBM Informix GLS localename might be incorrectly specified or might be equivalent to another IBM Informix GLS locale that is available.

If the subdirectory and filename that locale-file-name specified exist, verify that your product was installed correctly so that the IBM Informix GLS locale file can be located. Specifically, ensure that the GL_PATH environment variable is set (or not set) according to the Gateway installation instructions:

* If GL_PATH is not set, verify that the subdirectory and file that locale-file-name specifies are in the $INFORMIXDIR/gls/lc directory.

* If GL_PATH is set, verify that the subdirectory and filename that locale-file-name specifies are in one of the directories that the GL_PATH environment variable specifies.

10- The locale file that locale-file-name specified is not a locale file.

The locale file that locale-file-name specified is not an IBM Informix GLS locale file, or it has been corrupted. Check that you are using the locale file that your IBM Informix product supplier provided. Refresh the file from the original installation file if it has been corrupted.

11- The locale object is inconsistent.

The locale object is not consistent. For example, the same code set is not being used in each locale category. Contact your IBM Informix product supplier for assistance.

For any other errno value, contact your IBM Informix product supplier for assistance.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-29033 fires when the Gateway can't load an Informix GLS locale — per the official guidance, localename follows language_territory.codeset format, errno gives the specific failure reason, and locale-file-name is the subdirectory/filename that couldn't be loaded.

  1. errno 6 — the locale specification is badly formatted, per the official guidance — needs correction by the Gateway administrator.
  2. errno 7 — the locale file doesn't exist, per the official guidance — the GLS locale isn't available; verify the locale name and installation.
  3. Other documented errno values, per the official guidance, each indicating a different specific load failure.
Solutions / Resolution
  1. For a badly-formatted locale specification, correct it, per the official guidance — the Gateway administrator must fix this.
  2. For a missing locale file, verify the locale name and installation, per the official guidance, checking the product documentation for correct language_territory.codeset specification.
Examples
N/A

No specific triggering statement is documented beyond a locale-load failure, errno identifies the specific cause.

Diagnostic Checks
  1. Check the errno value returned, and follow its specific documented resolution (bad format vs. missing file, among others).
Related Errors / Related Topics
  • -29037 — "There is no CCSID or GLS locale set for the FE OS locale localename." A related GLS/locale error, on no locale being configured at all rather than a load failure.

An Informix GLS locale failed to load — check the returned errno for the specific cause (bad specification format, missing file, or another documented reason).