This content has been marked as final. Show 4 replies
Pl indicate how you are planning to upgrade. If you going to directly upgrade in-place using DBUA or migration scripts, then the characterset will not change as part of the upgrade. The characterset can be changed if you are creating a new empty 18.104.22.168 database and then performing an upgrade via export/import.
Oracle recommends using the AL32UTF8 characterset (http://docs.oracle.com/cd/E11882_01/server.112/e25494/create001.htm#ADMIN13343), but if your application does not expect to ever use any characters that are not included in US7ASCII, you can continue to use this characterset.
Yes, I am creating a new empty 22.214.171.124 database and then performing an upgrade via export/import... Next as far as I know, my application team is supporting inhouse only and they are expecting low or zero impact to their inhouse apps when I do the upgrade/migration to new database... On top of that, they seems happy with what they are doing now and cannot be bother with CHARACTERSET or whatsoever. With this and your input, I will continue to use US7ASCII as my characterset.
A trival question, may I know what NLS_CHARACTERSET US7ASCII and NLS_NCHAR_CHARACTERSET AL16UTF16 mean and in what way are they different?
Thanks for your answer.. It helps..
Is there a reason you are not using DBUA for the upgrade ?1 person found this helpful
Pl see these MOS Docs for an explanation of NLS_CHARACTERSET and NLS_NCHAR_CHARACTERSET
Changing the Database Character Set ( NLS_CHARACTERSET ) [ID 225912.1]
The National Character Set ( NLS_NCHAR_CHARACTERSET ) in Oracle 9i, 10g and 11g [ID 276914.1]
I'm not using DBUA because the new 11g will be on a separate new server.. Somewhere in Oracle doc, i saw:
Databases must be on the same system (in-place upgrade where the new version of Oracle Database is installed on the same server as the existing version).
Thanks for the MOS docs..