- Existing databases that were created using previous requirements do not require a character set change as part of an upgrade.
- NCHAR database settings are not applicable to JDA Allocation
- In order to use the integration with the JDA Enterprise Knowledge Base for the collection of plan data, the Allocation database server machine requires a TNS entry for connection to the EKB database
(See JDA Allocation Installation Guide)
- AL32UTF8 is a Unicode, variable-width, multibyte encoding scheme (recommended by Oracle for all new systems), allowing Oracle to store, process, and retrieve data for almost all contemporary languages, i.e.:
- Phonetic writing systems (e.g. Greek, Latin, Cyrillic, Devanagari), typically encoded in one byte to represent languages (e.g. Spanish, English, Russian, Ukrainian).
- Ideographic writing systems (e.g. Chinese, Japanese), typically encoded in more than one byte.
- Non-Unicode character sets allows only for restricted multilingual support of related languages within one writing system.
E.g. WE8ISO8859P1 would support the languages French, English, Spanish, Swedish etc. but not Polish.
(see Oracle Database Globalization Support Guide)
