Re: Database character set conversion.

From: David Mann <>
Date: Wed, 12 Aug 2009 11:20:14 -0400
Message-ID: <>

Fred Tilly wrote:
>We have two applications that use one database, and the database is
>with character set WE8ISO8859P1. One of the applications needs to handle
>multiple languages so the vendor wants us to convert ot a 16 bit character
>However the other application in the database has not been tested against a

>16bit database, and there are a lot of tables with fields defined as
>varchar2(4000) and clobs.
>Has anyone actually done such a conversion and is there anything we should
>looking out for.

My first stop for character set conversions is usually the CSSCAN utility. You can run it against your database and indicate the character set you would like to convert to and it will check all fields for any conversion anomalies and report them.

Here is a pointer to the documentation for 10g:

As far as application issues, an analysis of your technology stack would be in order. For projects such as this I usually lean on my developers to analyze their client apps and access methods for character set compatibility. If all else fails you can convert a test system and have QA give the data a once over.


Dave Mann - Database Stuff -

Received on Wed Aug 12 2009 - 10:20:14 CDT

Original text of this message