Informix Error -7211: Cannot reference an external NLS database.
Cause and resolution
Cannot reference an external NLS database.
If your current database is not an NLS database, you cannot access an NLS database on another database server or on the same database server. However, if the NLS environment variables are set correctly, you can drop an external NLS database even if your current database is not an NLS database.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-7211 fires when the current database isn't an NLS database and an NLS database on another (or the same) database server is referenced — per the official guidance.
- The current database isn't NLS-enabled, and an external NLS database was referenced, per the official guidance — the direct, only cause.
Solutions / Resolution
- Connect to (or create) an NLS-enabled current database before referencing an external NLS database, per the official guidance.
- Dropping an external NLS database is still possible from a non-NLS current database, per the official guidance, as long as the NLS environment variables are set correctly — this specific operation is an exception to the general restriction.
Examples
N/A
No specific triggering statement is documented beyond referencing an NLS database from a non-NLS current database.
Diagnostic Checks
- Check whether the current database is NLS-enabled, and connect to an NLS database first if an external NLS database needs to be referenced (other than dropping it).
Related Errors / Related Topics
- -7210 — "This server does not have NLS capability." A related NLS restriction, about the server itself lacking NLS support entirely, rather than the current database not being NLS-enabled.
- -7202 — "Database was created without NLS functionality." A related NLS restriction,
about
NCHAR/NVARCHARusage in a non-NLS database, rather than referencing an external NLS database.
The current database isn't NLS-enabled, so an external NLS database can't be referenced (except to drop it) — connect to an NLS database first.