Questions Regarding NLS Parameters Related To Agile 9.3.6 Upgrade
(Doc ID 2528256.1)
Last updated on APRIL 08, 2019
Applies to:Oracle Agile PLM Framework - Version 188.8.131.52 and later
Information in this document applies to any platform.
Questions regarding NLS parameters related to Agile 9.3.6 upgrade
Few questions about building a new Oracle database when we eventually upgrade Agile from 9.3.3 to Agile 9.3.6.
1) In the pfile produced by running the agile9database.sh script, we 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 our existing Agile databases, we are using BYTE everywhere instead of CHAR. I assume there is nothing wrong with setting it to BYTE, since that is currently the way we are using it at Harris?
2) I was curious though if there was 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 we upgrade to 9.3.6? We currently have UTF8 for both the NLS_CHARACTERSET and NLS_NCHAR_CHARACTERSET, and we 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. I was thinking it should be OK to change it, because I assume that AL32UTF8 is a superset of UTF8, and when we're creating a new database is the time to do it. On the other hand if you think most Agile customers still use UTF8 for both the NLS_CHARACTERSET and NLS_NCHAR_CHARACTERSET then we can keep it the same. What do you think?
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