Re: Problem in UTF8 migration from monolingual characterset

From: Laurenz Albe <invite_at_spam.to.invalid>
Date: 15 Feb 2006 12:54:49 GMT
Message-ID: <1140008087.946307@proxy.dienste.wien.at>

Venkatesh <venkatme198410_at_gmail.com> wrote:
> The table that i have specified are running in the production with
> corruption and we can't drop any table or increase the column size
> and the monolingual characterset used is german
> thanks in advance

In an earlier post you said:

> When the oracle database of monolingual character set was exported and
> imported in a UTF8 data base

Do you mean that the newly created UTF8 database is corrupt? Or do you mean that the 'monolingual' original database is corrupt?

If the latter is the case, you have no problem.

You drop the table in the UTF8 database (BTW, I would use AL16UTF8 instead of UTF8) and recreate it using character semantics for the columns. Then you can import the exported data into these newly created tables.

I would also change the initialization parameter NLS_LENGTH_SEMANTICS to CHAR and restart the instance.

Yours,
Laurenz Albe Received on Wed Feb 15 2006 - 06:54:49 CST