ClickHouse/docs/en/faq/integration/oracle-odbc.md

---
title: What if I have a problem with encodings when using Oracle via ODBC?
toc_hidden: true
toc_priority: 20
---

# What If I Have a Problem with Encodings When Using Oracle Via ODBC? {#oracle-odbc-encodings}

If you use Oracle as a source of ClickHouse external dictionaries via Oracle ODBC driver, you need to set the correct value for the `NLS_LANG` environment variable in `/etc/default/clickhouse`. For more information, see the [Oracle NLS\_LANG FAQ](https://www.oracle.com/technetwork/products/globalization/nls-lang-099431.html).

**Example**

``` sql
NLS_LANG=RUSSIAN_RUSSIA.UTF8
```
[docs] reorganized F.A.Q. 2020-06-22 13:35:41 +00:00			`---`
[docs] extra F.A.Q. content (#11898) * more content for F.A.Q. * more content * normalize * more content * maybe fix the docs check * absolute img urls * fix tests 2020-06-24 12:59:19 +00:00			`title: What if I have a problem with encodings when using Oracle via ODBC?`
[docs] reorganized F.A.Q. 2020-06-22 13:35:41 +00:00			`toc_hidden: true`
normalize markdown 2020-06-22 13:39:48 +00:00			`toc_priority: 20`
[docs] reorganized F.A.Q. 2020-06-22 13:35:41 +00:00			`---`

normalize markdown 2020-06-22 13:39:48 +00:00			`# What If I Have a Problem with Encodings When Using Oracle Via ODBC? {#oracle-odbc-encodings}`
[docs] reorganized F.A.Q. 2020-06-22 13:35:41 +00:00
			If you use Oracle as a source of ClickHouse external dictionaries via Oracle ODBC driver, you need to set the correct value for the `NLS_LANG` environment variable in `/etc/default/clickhouse`. For more information, see the [Oracle NLS\_LANG FAQ](https://www.oracle.com/technetwork/products/globalization/nls-lang-099431.html).

			`Example`

			``` sql
			`NLS_LANG=RUSSIAN_RUSSIA.UTF8`
			```