Differences

This shows you the differences between two versions of the page.

Link to this comparison view

knowledge-base:database-migration:setup-and-troubleshooting:oracle:non-ansi-symbols [2019/05/28 11:48]
 knowledge-base:database-migration:setup-and-troubleshooting:oracle:non-ansi-symbols [2023/10/27 14:28] (current)
uliana.philippova created
Line 1: Line 1:
 +\\
 +[[https://​www.ispirer.com|Ispirer Website]]
 +[[https://​www.ispirer.com/​products/​oracle-migration|Ispirer Capabilities:​ Oracle Migration]]
 +[[https://​www.ispirer.com/​download/​download-demo|Free Trial]]
 +====== Preserving Non-Ansi Symbols in Business Logic and Data ======
  
 +**Symptoms**
 +
 +For example when running a conversion in SQLWays Wizard on Japanese locale, it doesn'​t extract Shift-JIS encoding properly, it corrupts all Japanese characters instead.
 + 
 +**Cause**
 +
 +The Oracle option to extract Japanese characters from the source database and to display correctly the Japanese locale has not been set.
 +
 +**Solution**
 +
 +In order to extract all Japanese characters correctly from Oracle database working with Japanese locale, Oracle environment needs to be configured as follows:
 +In the following path HKEY_LOCAL_MACHINE -> SOFTWARE -> Wow6432Node -> ORACLE -> KEY_OraDb11g_home1 please set NLS_LANG parameter in Japanese_Japan.JA16SJIS
 +
 +{{:​knowledge-base:​database-migration:​setup-and-troubleshooting:​oracle:​ora_non_ansi_symb.png?​nolink|}}
 +
 +__**Ispirer Note:**__
 +
 +   For Japanese characters you can try to use the NLS_LANG parameter provided in the article. For Korean characters you can try to set NLS_LANG parameter to KOREAN_KOREA.KO16MSWIN949.
 +   For other types of characters we recommend to check the appropriate value of NLS_LANG parameters in the Oracle documentation. ​
 +\\
 +
 +If you have any other questions, please contact us: [[[email protected]]]