Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Characterset / conversion problem

Re: Characterset / conversion problem

From: Lou Fangxin <anysql_at_gmail.com>
Date: Thu, 15 Sep 2005 17:44:48 +0800
Message-ID: <ea5907d305091502445bf1f9f7@mail.gmail.com>


Oracle's upgrade script will detect this issue, since there is only two sets for nls_charactersets above 9i.
 On 9/15/05, Marco Gralike <Marco.Gralike_at_amis.nl> wrote:  

> Maybe not Lou, but as I said to Berhard…
>
> Great to hear :-)
>
> What I meant is:go for UTF char.sets. It will provide you for every
> possibility in the future.
>
> Downsize is that it consumes more space
>
> By the way, be also aware that if you encounter charset conversion it
> also always will consume CPU time (on every level where it occurs) and there
> are a lot off bugs reported during charset conversion.
>
> That's why among others, that I said "check at regular intervals if all
> client, database, middletier have the same characterset".
>
> ...
>
> Mit freundlichen grüßen,
>
> ;-)
>
> Marco
>
> ------------------------------
>
> *From:* Lou Fangxin [mailto:anysql_at_gmail.com]
> *Sent:* donderdag 15 september 2005 11:34
> *To:* nora.bernhard_at_stgkk.sozvers.at
> *Cc:* Marco Gralike; oracle-l_at_freelists.org
> *Subject:* Re: Characterset / conversion problem
>
> If you did not use NCHAR/NVARCHAR/NCLOB, then you can ignore the
> NLS_CHARACTERSET.
>
>
> On 9/15/05, *BERNHARD Nora* <nora.bernhard_at_stgkk.sozvers.at> wrote:
>
> > NLS_LANG = .WE8ISO8859P15
> > In other words set your NLS_LANG environment setting the same as the
> NLS
> > settings in your database.
>
> Oh, thanks for the great hint! The parameter NLS_LANG was not at all set
> for the (os) oracle user I set it according to your example, and
> everything is fine now, the import worked and I still have all my
> special characters *yippie*.
>
> > Go at the end for UTF16, it will cost you more database space but you
> > have everything checked for the future (only check at regular
> intervals
> > if all client, database, middletier have the same characterset)
>
> This isn't possible. According to metalink note 276914.1, " From 9i
> onwards the NLS_NCHAR_CHARACTERSET can have only 2 values: UTF8 or
> AL16UTF16 who are Unicode charactersets."
>
> Thanks a lot!
>
> Nora
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
>
> --
> Welcome, Fangxin.Lou from China
> MYDUL, alternative to DUL !!!
> Home: http://www.anysql.net/en/
> Mydul: http://www.anysql.net/en/mydul.html
>

-- 
Welcome, Fangxin.Lou from China
MYDUL, alternative to DUL !!!
Home: http://www.anysql.net/en/
Mydul: http://www.anysql.net/en/mydul.html
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Sep 15 2005 - 04:46:59 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US