Verifying Code Page Settings for Oracle

Release 9.2 requires that the national character set of an Oracle database be set to AL16UTF16. Make sure AL16UTF16 is chosen for a new Oracle database install. This setting cannot be changed after the database is created without potential data loss depending on what it's being changed to and from.

Note: While the AL16UTF16 character set is valid for the Release 9.2 Unicode database, for Upgrades you should not change the values so that the prior release non-Unicode database can still be accessed.

The correct code page parameters must be set in the Oracle database and on the operating systems; the setting is the same for Microsoft Windows or UNIX. These settings apply to the Oracle database and the Oracle client:

• NLS_NCHAR_CHARACTERSET

  This parameter must always be set to AL16UTF16 for all languages (the only alternative is AL32UTF8, which is not supported by JD Edwards EnterpriseOne).

  JD Edwards EnterpriseOne uses this parameter for columns such as NCHAR, NVARCHAR2, and NCLOB. JD Edwards EnterpriseOne requires that content stored in these columns is in fact in AL16UTF16.

• NLS_CHARACTERSET

  This setting defines the database character set. This setting is determined at database creation time. This setting depends on the language you want to use. For example, most Western European languages use the setting WE8MSWIN1252

  This setting only affects your specified language. If all your data sources have the Unicode box checked, this setting will never be used.

  JD Edwards EnterpriseOne uses this parameter for columns such as CHAR and VARCHAR2.

• NLS_LANG

  This sets the locale. The value can be changed by setting the NLS_LANG environment variable on UNIX and the registry on Microsoft Windows.

Caution: Set the NLS_ CHARACTERSET and NLS_NCHAR_CHARACTERSET parameters for the appropriate language before loading your central objects specification objects for Release 9.2.

To verify the code page settings for Oracle:

1. Verify the code page setting of the Oracle database by executing this single-line SQL command from SQL Plus:

   SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER = 'NLS_CHARACTERSET';

2. Verify the Unicode code page setting of the Oracle database by executing this single-line SQL command from SQL Plus:

   SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER = 'NLS_NCHAR_CHARACTERSET';

   If the setting is incorrect, set the NLS_NCHAR_CHARACTERSET value to AL16UTF16, using the Oracle documentation to change the setting.

3. Set up NLS_LANG parameter for Oracle.

   For JD Edwards EnterpriseOne environments with languages to function properly, the NLS_LANG parameter must be set correctly for Oracle. These settings must be set for your Oracle client Development Clients and Oracle database server.

   Caution: Remember to add a period before the NLS_LANG variable value for the given code page.

   See Also

   Refer to Language Process Overview for the National Language Support tables and other information related to multilingual installations.