RE: NLS question
- From: Michael Schmitt <mschmitt@xxxxxxxxxxxx>
- To: "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 10 Mar 2011 22:02:57 -0600
Thanks Jimmy,
I was under the impression that the NLS_NCHAR_CHARACTERSET being set to
AL16UTF16 would allow us to store this data for columns of type NCHAR,
NVARCHAR2, and NCLOB
What is the purpose of the NLS_NCHAR_CHARACTERSET if that is not the case?
Thanks
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Jimmy Brock
Sent: Thursday, March 10, 2011 9:40 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: NLS question
NLS_CHARACTERSET=US7ASCII means 256 characters see http://www.asciitable.com/
If you need support beyond ASCII you may want to consider changing the
character set to WE8ISO8859P1. But before you do run the CSSCAN utility - it
checks to see if your current data can be migrated.
csscan fromchar=US7ASCII tochar=WE8ISO8859P1
It will report if character migration will be successful.
If you have a very large database running may take a while to complete.
--
Jimmy Brock
Other related posts:
