Re: WE8ISO8859P1 convert to AL32UTF8 unicode character set question

From: Laurenz Albe <invite_at_spam.to.invalid>
Date: Thu, 9 Apr 2009 11:44:40 +0200
Message-ID: <1239270303.675211_at_proxy.dienste.wien.at>



lsllcm wrote:
> After tested, csscan also report application data exception when
> prepare to change character set from WE8ISO8859P1 to WE8MSWIN1252, and
> we cannot use csalter.plb to change the database character set.
>
> Database character set
> WE8ISO8859P1
> FROMCHAR
> WE8ISO8859P1
> TOCHAR
> WE8MSWIN1252
> Scan NCHAR data?
> NO
> Array fetch buffer size
> 1024000
> Number of processes
> 1
> Capture convertible data?
> NO
> ------------------------------------------------------------------------------
>
> [Data Dictionary individual exceptions]
>
>
> [Application data individual exceptions]
>
> User : JACKY
> Table : AAA
> Column: C1
> Type : VARCHAR2(1000)
> Number of Exceptions : 1
> Max Post Conversion Data Size: 9
>
> ROWID Exception Type Size Cell Data(first 30
> bytes)
> ------------------ ------------------ -----------------------------------
> AAALaRAAEAAAAAQAAA lossy conversion sys.ůMed
> ------------------ ------------------ -----------------------------------

There's mot to changing the database character set, Metalink Note 555823.1 covers it in detail.

First, you have to be certain that all the non-ASCII characters in the database are WE8MSWIN1252.

Then you would have to run csscan with FROMCHAR=WE8MSWIN1252 TOCHAR=WE8MSWIN1252. There should be no errors.

Then you can convert the database.

Yours,
Laurenz Albe Received on Thu Apr 09 2009 - 04:44:40 CDT

Original text of this message