Informix Error -1237
-1237 Bad era name.
The date format requires an era name, but no name that matches the era names in the GLS locale could be found in the input string. Check that you are using the correct locale and that you entered the era name correctly.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-1237 fires when a date format requires an era name, but no name matching the era names in the active GLS locale could be found in the input string — per the official guidance, this is a more specific case than -1236's general bad-era-date condition.
- The input string missing an era name entirely, per the official guidance — the direct, common cause.
- The wrong GLS locale active, per the official guidance — the era name given doesn't match any era defined in the locale actually in effect.
- A misspelled or mistranslated era name, per the official guidance's other named possibility.
Solutions / Resolution
- Check that you are using the correct locale, per the official guidance.
- Check that the era name was entered correctly, per the official guidance, matching the spelling defined for that locale.
Examples
N/A
No specific triggering statement is documented — check the active GLS locale and the era name's exact spelling against it.
Diagnostic Checks
- Confirm the active GLS locale, and check the era name in the input string against the era names that locale actually defines.
Related Errors / Related Topics
- -1236 — "Bad era date." The general form of an era-format problem, covering both name and offset issues.
- -1238 — "Bad era initialization." A related, internal era-configuration error.
No matching era name was found in the input string for the active GLS locale — check the locale and the era name's exact spelling.