characterset changes from WE8ISO8859P1 to UTF8
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: characterset changes from WE8ISO8859P1 to UTF8

  1. #1
    Join Date
    Aug 2000
    Location
    Chicago IL
    Posts
    586

    Question

    Hello
    We want to recreate our database to UTF8 characterset. I am planning on taking an export tomorow with WE8ISO8859P1 then recreating the database with UTF8 characterset. Will I run into any problems with the Import because of the characterset changes?

    Jigar
    "High Salaries = Happiness = Project Success."

  2. #2
    Join Date
    Feb 2001
    Posts
    290
    I strongly suggest you to call ORACLE SUPPORT before you do character conversion.

    And you may need to identify the data related recoveries...

    Thanks,
    Madhu

  3. #3
    Join Date
    Sep 2001
    Location
    NJ, USA
    Posts
    1,287
    U shouldn't any prombem with UNICODE, because:
    _________________________________________
    FROM ORACLE DOC:

    The Export utility always exports user data, including Unicode data, in the character sets of the Export server. The character sets are specified at database creation.

    The Import utility automatically converts the data to the character sets of the Import server.

    Some 8-bit characters can be lost (that is, converted to 7-bit equivalents) when you import an 8-bit character set export file. This occurs if the client system has a native 7-bit character set or if the NLS_LANG operating system environment variable is set to a 7-bit character set. Most often, you notice that accented characters lose their accent mark.

    Both Export and Import provide descriptions of any required character set conversion before exporting or importing the data.



  4. #4
    Join Date
    Feb 2001
    Posts
    290
    Pl find the following--

    http://metalink.oracle.com/metalink/...p_id=34596.996

    http://metalink.oracle.com/metalink/..._id=130358.996

    1. Set the environment variable
    NLS_LANG to "_.WE8ISO8859P1"
    2. Do a full export of the database
    3. Create a new database with the database character set UTF8
    4. Set the environment variable NLS_LANG to "_<
    TERRITORY>.UTF8"
    5. Import the export dump into the new database


    Thanks,
    Madhu

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