RE: Change database character set
- From: Scott Canaan <srcdco@xxxxxxx>
- To: "christopherdtaylor1994@xxxxxxxxx" <christopherdtaylor1994@xxxxxxxxx>, "oracle.unknowns@xxxxxxxxx" <oracle.unknowns@xxxxxxxxx>
- Date: Thu, 23 Oct 2014 14:41:35 +0000
I already ran the csscan utility and it came up with 10 rows that wouldn’t
convert properly. One row is in SYS.REG$ and the other 9 are CLOBS in one
table in the application itself. This is the result:
Database Scan Individual Exception Report
[Database Scan Parameters]
Parameter Value
------------------------------ ------------------------------------------------
CSSCAN Version v2.1
Instance Name CAMPTEST
Database Version 11.2.0.3.0
Scan type Full database
Scan CHAR data? YES
Database character set US7ASCII
FROMCHAR US7ASCII
TOCHAR al32utf8
Scan NCHAR data? NO
Array fetch buffer size 1024000
Number of processes 3
Capture convertible data? NO
------------------------------ ------------------------------------------------
[Data Dictionary individual exceptions]
User : SYS
Table : REG$
Column: SESSION_KEY
Type : VARCHAR2(1024)
Number of Exceptions : 1
Max Post Conversion Data Size: 111
ROWID Exception Type Size Cell Data(first 30 bytes)
------------------ ------------------ ----- ------------------------------
AAABZBAABAAAC3hAAA lossy conversion ?·rÝÑEEf”‰cƒºÇÔ„.PÎßç«‹ôCÏÆÝ
------------------ ------------------ ----- ------------------------------
[Application data individual exceptions]
User : CAMPUS
Table : SCRIPT_GROUP
Column: SCRIPT_TEXT
Type : CLOB
Number of Exceptions : 9
Max Post Conversion Data Size: 3842
ROWID Exception Type Size Cell Data(first 30 bytes)
------------------ ------------------ ----- ------------------------------
AAAzpZAAFAAAAR0AAA lossy conversion <p class="MsoNormal" style="MA
AAAzpZAAFAAAAR0AAB lossy conversion <p class="MsoNormal" style="MA
AAAzpZAAFAAAAR0AAI lossy conversion <p>Hello this is ______ I am a
AAAzpZAAFAAAAR0AAJ lossy conversion <p>Hello, I'm calling from RIT
AAAzpZAAFAAAAR0AAK lossy conversion Hello, I'm calling from RIT.
AAAzpZAAFAAAAR1AAA lossy conversion <p class="MsoNormal" style="MA
AAAzpZAAFAAAARzAAC lossy conversion <p class="MsoNormal" style="MA
AAAzpZAAFAAAARzAAD lossy conversion <p class="MsoNormal" style="MA
AAAzpZAAFAAAARzAAF lossy conversion <p class="MsoNormal" style="MA
------------------ ------------------ ----- ------------------------------
Scott Canaan ’88 (srcdco@xxxxxxx<mailto:srcdco@xxxxxxx>)
(585) 475-7886 – work (585) 339-8659 – cell
“Life is like a sewer, what you get out of it depends on what you put into it.”
– Tom Lehrer
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Chris Taylor
Sent: Wednesday, October 22, 2014 2:29 PM
To: oracle.unknowns@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Change database character set
Check out:
Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8 (Unicode) in 8i, 9i , 10g and
11g (Doc ID 260192.1)
In the meantime, you probably have a couple of options. You can run the
character set checker utility and see if you have any data that wouldn't
convert cleanly. If everything would convert cleanly then you can convert
in-place.
To export the data, you would export it in P1 characterset, (set your NLS_LANG
variable to match the db), recreate the db, and import the data back in leaving
your NLS_LANG set to P1 and the database will convert the character information
to the appropriate code page (I think that's the way to do it but read over
that MOS document above to be sure).
Regards,
Chris Taylor
On Wed, Oct 22, 2014 at 1:20 PM, Chen Zhou
<oracle.unknowns@xxxxxxxxx<mailto:oracle.unknowns@xxxxxxxxx>> wrote:
Hi, Everyone,
We have a 11.2.0.3 database created with character set WE8ISO8859P1
(NLS_CHARACTERSET) and national character set UTF8 (NLS_NCHAR_CHARACTERSET).
Apparently it is causing problem for our European team and we need to change
the database character set to AL32UTF8 to fix the problem and match the other
databases. Can I export the whole database or the main schema data, recreate
the database with AL32UTF8 character set and import the data back?
Thank you,
Chen
Other related posts:
