DBAsupport.com Forums - Powered by vBulletin
Results 1 to 6 of 6

Thread: Multi-Character Set Support

  1. #1
    Join Date
    Nov 2000
    Posts
    245

    Multi-Character Set Support


    I need to set up a instance which support English and Chinese data BOTH.
    How I implement it, what I need?
    1. create a new instance
    2. convert a existing instance with NLS_CHARACTERSET = WE8ISO8859P1

    I know I need to setup up NLS_lang, NLS_character set...
    I understand I have 2 options, UTF8 and simple/traditional chinese. which one I should use?

    thanks in advance

  2. #2
    Join Date
    Mar 2001
    Location
    Ireland/Dublin
    Posts
    688
    It is up to you which Charset would you use. I don't know much about chinese charset, but I use UTF8, as I know it support a lot of languages. If you sure that you need only chinese and english in future you may use chinese charset, but if you expect european language, you should use UTF8.
    You have to create new Instance for that.
    Best wishes.

  3. #3
    Join Date
    Nov 2000
    Posts
    245

    THANKS KGB.

    in init.ora I use:
    character set "UTB8"
    national character set "UTB8"
    NLS_LANGUAGE=??
    NLS_TERRITORY=??

    how about NLS_LANGUAGE and NLS_TERRITORY
    do I have to set up any value or use default (american)
    or use CHINA and SIMPLE CHINESE

    thanks again



  4. #4
    Join Date
    Mar 2001
    Location
    Ireland/Dublin
    Posts
    688
    I use database parameters:

    CHARACTER SET UTF8
    NATIONAL CHARACTER SET UTF8
    NLS_LANG=AMERICAN_AMERICA.UTF8
    NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS'

    NLS_LANGUAGE AMERICAN
    NLS_TERRITORY AMERICA
    NLS_CURRENCY $
    NLS_ISO_CURRENCY AMERICA
    NLS_NUMERIC_CHARACTERS .,
    NLS_CALENDAR GREGORIAN
    NLS_DATE_FORMAT Mon DD YYYY HH24:MI:SS
    NLS_DATE_LANGUAGE AMERICAN
    NLS_CHARACTERSET UTF8
    NLS_SORT BINARY
    NLS_TIME_FORMAT HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT DD-MON-YY HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZH:TZM
    NLS_TIMESTAMP_TZ_FORMAT DD-MON-YY HH.MI.SSXFF AM TZH:TZM
    NLS_DUAL_CURRENCY $
    NLS_NCHAR_CHARACTERSET UTF8
    NLS_COMP

    NLS_TERRITORY doesn't effect on data saving.

    Originally posted by jm

    THANKS KGB.
    in init.ora I use:
    character set "UTB8"
    national character set "UTB8"
    NLS_LANGUAGE=??
    NLS_TERRITORY=??
    how about NLS_LANGUAGE and NLS_TERRITORY
    do I have to set up any value or use default (american)
    or use CHINA and SIMPLE CHINESE
    thanks again
    [Edited by kgb on 06-26-2001 at 01:51 PM]

  5. #5
    Join Date
    Nov 2000
    Posts
    245

    It makes sense, all I need is use UTF8 to store the data.

    thanks kgb,

  6. #6
    Join Date
    Feb 2000
    Posts
    3

    Unhappy

    Hello,

    I will be setting up a UTF8 database, and I need to migrate a WE8ISO8859P1 database onto this one. I'm trying with export/import, but I'm not sure how the client settings are supposed to be (NLS_LANG...). I have CLOBs in a table, and it seems that the data gets garbled in the import... can anyone help me with this?

    Thanks in advance!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width