RE: Converting WE8ISO8859P1 TO UTF8
- From: "Ankur Godambe" <agodambe@xxxxxxxxxx>
- To: "Mark Brinsmead" <pythianbrinsmead@xxxxxxxxx>
- Date: Wed, 7 May 2008 00:09:44 -0700
To move from WE8ISO8859P1 to UTF8, it's an intermediate step to move
character set to WE8MSWIN1252 to take care of lossy data. I have raised
a service request with Oracle couple of weeks back but they are going
round and round pointing me to note: 555823.1 and Note:260192.1 but not
answering the question.
Thanks,
Ankur
________________________________
From: Mark Brinsmead [mailto:pythianbrinsmead@xxxxxxxxx]
Sent: Wednesday, May 07, 2008 7:32 AM
To: Ankur Godambe
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Converting WE8ISO8859P1 TO UTF8
Actually, I would expect the command should read TOCHAR=UTF8 ...
I presume the goal of this check is to see whether the data can be
converted cleanly to UTF8 with the assumption that the original
characterset had been WE8MSWIN1512.
But then, the note is provided by Oracle Support. Why don't you ask
them?
On Tue, May 6, 2008 at 5:45 AM, Ankur Godambe <agodambe@xxxxxxxxxx>
wrote:
Hello All,
I want to change character set of our existing databases from
WE8ISO8859P1 to UTF8 for which I am following steps mentioned on
Metalink Note:260192.1.
Point #2 of the note checks invalid code points in current character set
and suggests way to clear up "Lossy" data. On running csscan with
FROMCHAR=WE8ISO8859P1 and TOCHAR=WE8ISO8859P1 I see lot of tables as
"lossy". The way to recover from this situation, as suggested in note,
is changing the character set to WE8MSWIN1252 if the following command
has all data reported as changeless:
csscan FULL=Y FROMCHAR=WE8MSWIN1252 TOCHAR=WE8MSWIN1252 LOG=1252check
CAPTURE=Y ARRAY=1000000 PROCESS=2
Question:
1. Shouldn't the command be FROMCHAR=WE8ISO8859P1 and
TOCHAR=WE8MSWIN1252 instead of same FROMCHAR and TOCHAR both =
WE8MSWIN1252?
Thanks,
Ankur
--
Cheers,
-- Mark Brinsmead
Senior DBA,
The Pythian Group
http://www.pythian.com/blogs
Other related posts:
