E-ORA: Why are the delivered PUM Images have Database National Character Set (NLS_NCHAR_CHARACTERSET) configured to UTF8 and not AL16UTF16?
(Doc ID 2453497.1)
Last updated on FEBRUARY 07, 2019
Applies to:
PeopleSoft Enterprise PT PeopleTools - Version 8.56 and laterInformation in this document applies to any platform.
Goal
For the national character set (NLS_NCHAR_CHARACTERSET), a database can only use UTF8 or AL16UTF16.
*** All the documentation from a database perspective "strongly recommends" AL16UTF16 for the national character set. For example:
SQL> select value,parameter from v$nls_parameters where parameter like '%CHARACTERSET';
VALUE
----------------------------------------------------------------
PARAMETER
----------------------------------------------------------------
AL32UTF8
NLS_CHARACTERSET
AL16UTF16
NLS_NCHAR_CHARACTERSET
*** However all the PeopleSoft deployment package databases come shipped with UTF8 for the national character set. For example:
CDBCS SQL> select value,parameter from v$nls_parameters where parameter like '%CHARACTERSET';
VALUE
----------------------------------------------------------------
PARAMETER
----------------------------------------------------------------
AL32UTF8
NLS_CHARACTERSET
UTF8
NLS_NCHAR_CHARACTERSET
Is there a reason/requirement PeopleSoft databases are shipped with UTF8 for the national character set rather than AL16UTF16?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |