My Oracle Support Banner

Questions Regarding NLS Parameters Related To Agile 9.3.6 Upgrade (Doc ID 2528256.1)

Last updated on JULY 15, 2019

Applies to:

Oracle Agile PLM Framework - Version 9.3.6.0 and later
Information in this document applies to any platform.

Goal

Questions regarding NLS parameters related to Agile 9.3.6 upgrade


Few questions about building a new Oracle database when upgrading Agile from 9.3.3 to Agile 9.3.6.

1) In the pfile produced by running the agile9database.sh script,  noticed that it set nls_length_semantics='CHAR', which the documentation says is the default for Agile (even though it's not the default for the Oracle database). Looking in existing Agile databases, using BYTE everywhere instead of CHAR. Assume there is nothing wrong with setting it to BYTE, since that is currently the way its being used?

2)  Is there any reason Agile chose CHAR as their default for nls_length_semantics, when the default for an Oracle database appears to be BYTE for nls_length_semantics?

3) Are the default character sets (AL32UTF8 for NLS_CHARACTERSET and AL16UTF16 for NLS_NCHAR_CHARACTERSET) a good choice when upgrading to 9.3.6? currently have UTF8 for both the NLS_CHARACTERSET and NLS_NCHAR_CHARACTERSET, and have seen in some Oracle tools like the DBCA (Database Configuration Assistant) that it is on a list of fonts no longer recommended by Oracle. thinking it should be OK to change it, because assume that AL32UTF8 is a superset of UTF8, and when creating a new database is the time to do it. On the other hand if most Agile customers still use UTF8 for both the NLS_CHARACTERSET and NLS_NCHAR_CHARACTERSET then can keep it the same. Is this correct?
 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.