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

Thread: language and character set of a database

  1. #1
    Join Date
    Jan 2001
    Posts
    32

    Question

    hi all

    I have a problem with the caracters in a database, i have oracle 8.1.6 with solaris 8 os, two days ago, we reconfigure of database with a imp/exp commands to avoid partitioning, but now, there are son problems with son characters into de database.

    the character set of the database is

    WE8ISO8859P1

    and the log in the import command send me the next message

    Export file created by EXPORT:V08.01.06 via conventional path
    import done in US7ASCII character set and WE8ISO8859P15 NCHAR character set
    import server uses WE8ISO8859P15 character set (possible charset conversion)
    export server uses WE8ISO8859P1 NCHAR character set (possible ncharset conversio
    n)


  2. #2
    Join Date
    Mar 2001
    Location
    Ireland/Dublin
    Posts
    688
    of, cours it will be broblem as you didn't seted up environment on a sun, I mean you have default NLS_LANG is US7ASCII.

    export LANG=en_US.iso-8859-1
    export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
    export ORACLE_HOME=/oracle/oracle/OraHome1
    export ORACLE_BASE=/oracle/oracle
    export ORACLE_DOC=/oracle/oracle/oradoc
    export ORACLE_SID=nuance
    export PATH=$PATH:$ORACLE_HOME/bin
    export LD_LIBRARY_PATH=$ORACLE_HOME/lib
    export NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS'

    You have to set up the same charset on both servers

  3. #3
    Join Date
    Apr 2001
    Posts
    107
    Hi,

    Your "problem" comes from OS:
    Under UNIX OS, you must specify in the command line the character set you wish to use (at the export time).
    It must be done BEFORE exporting, because the default language of your server is certainly american & US7ASCII. Under UNIX OS, the character set is environment dependant....

    the command line type is:
    $export ORACLE_SID=SID
    $export NLS_LANG=AMERICAN.AMERICA.WE8ISO8859P1 (for example)

    Consider the 1st export you made to be "corrupted", as it is encoded on a 7bits basis...
    The only way out is to make another export file with the above command line entered BEFORE the export command line.

    Good luck

    cheers
    Fabien

  4. #4
    Join Date
    Jan 2001
    Posts
    32
    ok, I understand, and to solve the problema tha we have, i have to run the export command again?


  5. #5
    Join Date
    Oct 2000
    Location
    Saskatoon, SK, Canada
    Posts
    3,925
    Yes set your environment variables correctly and do the export again

    Sam
    Thanx
    Sam



    Life is a journey, not a destination!


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