What to set in order to select UTF8 character set in sqlplus?

We are using 9.0.1.
select * from nls_database_parameters;
NLS_CHARACTERSET = UTF8
LANGUAGE = AMERICAN
TERRITORY = AMERICA
Web page encoding is UTF8.
We can see traditional and simplied chinese characters on web page without problem.
When we want to select thru sqlplus, the problem comes.
At first, I set the default win2000 language to traditional chinese.
locales is Chinese (Hong Kong).
Ansi Code page becomes 950. reboot the machine
set NLS_LANG=TRADITIONAL CHINESE.HONG KONG=ZHT16MSWIN950 in registry
web page can show traditonal and simplied chinese characters, but sqlplus fails.
Then I set the default win2000 language to simplied chinese, set the locales
to Chinese (PRC). reboot the machine
set NLS_LANG to simplied chinese character set.
web page can show traditonal and simplied chinese characters, but sqlplus still fails.
I have even set the NLS_LANG to _.UTF8. sqlplus still cannot show proper character set. Only the web page is okay.
I have referenced Oracle globalization web pages. I follow everything. What should I try?

The good news is that according to the iSQL*Plus FAQ on OTN, iSQL*Plus is available with 9.0.1.1 on Windows, and you can also download it directly from OTN. The bad news is that it does not support the SPOOL command
Since your requirement is to generate text reports with both Traditional and Simplified Chinese characters only, and that you don't need these characters to be able to display correctly inside a SQL*Plus session. You can set your NLS_LANG to TRADITIONAL CHINESE_HONG KONG.UTF8, launch SQL*Plus and spool out the content of the SELECT statement into a text file. This file will be encoded in UTF-8 and your Chinese data should show up in a Unicode UTF-8 viewer correctly.
I am not sure if Notepad in Windows 2000 can display UTF-8 text, if not you can open the text file up in a browser, and then set the page encoding to UTF-8 to view it.

Similar Messages

  • UTF8 character set conversion for chinese Language

    Hi friends,
    Would like to some basic explanation on UTF8 feature,what does it help while converting the data from chinese language.
    Would like to know what all characters this UTF8 will not support while converting from chinese language.
    Thanks & Regards
    Ramya Nomula

    Not exactly sure what you are looking for, but on MetaLink, there are numerous detailed papers on NLS character sets, conversions, etc.
    Bottom line is that for traditional Chinese characters (since they are more complicated), they require 4 bytes to store the characters (such as UTF-8, and AL32UTF8). Some mid-eastern characters sets also fall in this category.
    Do a google search on "utf8 al32utf8 difference", and you will get some good explanations.
    e.g., http://decipherinfosys.wordpress.com/2007/01/28/difference-between-utf8-and-al32utf8-character-sets-in-oracle/
    Recently, one of our clients had a question on the differences between these two character sets since they were in the process of making their application global. In an upcoming whitepaper, we will discuss in detail what it takes (from a RDBMS perspective) to address localization and globalization issues. As far as these two character sets go in Oracle, the only difference between AL32UTF8 and UTF8 character sets is that AL32UTF8 stores characters beyond U+FFFF as four bytes (exactly as Unicode defines UTF-8). Oracle’s “UTF8” stores these characters as a sequence of two UTF-16 surrogate characters encoded using UTF-8 (or six bytes per character). Besides this storage difference, another difference is better support for supplementary characters in AL32UTF8 character set.
    You may also consider posting your question on the Globalization Suport forum which pertains more to these types of questions.
    Globalization Support

  • Export using UTF8 character set

    Hi,
    My client is having a production database with default character set.
    While exporting I need to export the database to create a dump with UTF8 character set.
    Please let me know how to export with UTF8 option.
    Thanks....

    Hi, I am not sure if I got you correst. Here is what I think I have understood:
    - your client has a db which uses UTF8 as character set.
    - you want to export and make sure that there is no conversion taking place.
    for this you must set NLS_LANG variable in the shell from where you call exp, resp. expdp properly.
    NLS_LANG is composit and consists of:
    NLS_LANGUAGE_NLS_TERRITORY.NLS_CHARACTERSET
    In a bash this would look like this:
    $ export NLS_LANG=american_america.UTF8
    In other shells you might need to first define the varaible and then export:
    $ NLS_LANG=american_america.UTF8
    $ export NLS_LANG
    What you also need to know is that you influence the behavior for decimal separator and grand separator in numeric values and a few more settings by specifying NLS_TERRITORY.
    For instance NLS_TERRITORY uses a "." as decimal separator and a "," as grand separator for numeric values.
    This can be a pitfall! If you have the wrong territory specified then it might destroy all you numerics!
    Hope this helps,
    Lutz

  • Can I user Dot Matrix Printer under UTF8 character set ?

    Hi,
    We are using UTF8 character set. Somebody told me that I can only use the postscript printer. Is it necessary to set up a report server if I need to print on dot-matrix printer? Any workaround solution?
    Thanks and regards
    Toby

    Your printer emulation and the SAP device type for the output device must match.
    For example, if you use IBM Proprinter emulation, then use device type IBM4232.
    If you use Epson emulation, then you may have a look at note 1135053.
    What are your emulation and device type?

  • Cdrtools package, support for nls/utf8 character sets

    Hello ppl,
    I've been trying desperetly to burn a cd/dvd(k3b) with greek filenames and directory names. I ended up with file names like "???????????????????? (invalid unicode)"
    After a lot of searching, i managed to isolate and solve the problem. There has been a patch(http://bugs.gentoo.org/attachment.cgi?id=52097) for cdrtools to support nls/utf8 character sets.
    I guess that 90%+ of people using arch and burning cd's/dvd's, ignore the problem cause they just burn cd's/dvd's using standard english characters.
    For all others here it is     :
    # Patched cdrtools to support nls/utf8 character sets
    # Contributor: Akis Maziotis <[email protected]>
    pkgname=cdrtools-utf8support
    pkgver=2.01.01
    pkgrel=3
    pkgdesc="Tools for recording CDs patched for nls/utf8 support!"
    depends=('glibc')
    conflicts=('cdrtools')
    source=(ftp://ftp.berlios.de/pub/cdrecord/alpha/cdrtools-2.01.01a01.tar.gz http://bugs.gentoo.org/attachment.cgi?id=52097)
    md5sums=('fc085b5d287355f59ef85b7a3ccbb298' '1a596f5cae257e97c559716336b30e5b')
    build() {
    cd $startdir/src/cdrtools-2.01.01
    msg "Patching cdrtools ..."
    patch -p1 -i ../attachment.cgi?id=52097
    msg "Patching done "
    make || return 1
    make INS_BASE=$startdir/pkg/usr install
    It's a modified pkgbuild of the official arch cdrtools package (http://cvs.archlinux.org/cgi-bin/viewcv … cvs-markup) patched to support nls/utf8 character sets.
    Worked like a charm. 
    If u want to install it, u should uninstall the cdrtools package
    pacman -Rd cdrtools
    P.S.: I've issued this as a bug in http://bugs.archlinux.org/task/3830 but nobody seemed to care...    :cry:  :cry:  :cry:

    Hi Bharat,
    I have created a Oracle 8.1.7 database with UTF8 character set
    on WINDOWS 2000.
    Now , I want to store and retrieve information in other languages
    say Japanese or Hindi .
    I had set the NLS Language and NLS Terrritory to HINDI and INDIA
    in the SQL*PLUS session but could not see the information.You cannot view Hindi using SQL*Plus. You need iSQL*Plus.
    (Available as a download from OTN, and requiring the Oracle HTTP
    server).
    Then you need the fonts (either Mangal from Microsoft or
    Code2000).
    Have your NLS_LANG settings in your registry to
    AMERICAN_AMERICA.UTF8. (I have not tried with HINDI etc, because
    I need my solution to work with 806,817 and 901, and HINDI was
    not available with 806).
    Install the language pack for Devanagari/Indic languages
    (c_iscii.dll) on Windows NT/2000/XP.
    How can I use the Forms 6i to support this languages ?I am not sure about that.
    Do write back if this does not solve your problem.
    --Shirish

  • Oracle 11g Installation How to select Database Character Set

    Hi,
    I am Installing oracle 11g R2. After installation I had verified the character set it was AL16UTF16 but I wants to set AL32UTF8 charater set at the time of oracle installation only. I can't see the character set setting opetion at the time of installation because I am selecting the installation option " Install database softerware only" and after installation of oracle software manually I am creating the database. Please help me how can I set the character set at the time of oracle installation or at the time of database creation.
    My question is-
    How can I set the AL32UTF8 character set in above scenario?
    Why It is showing AL16UTF16 character set even I did not define any thing?

    But is there any choice to set the NLS_CHARACTERSET at the time of manually database creation. Actually For creating the database i am using one shell script for seting the parameter values in init.ora file so can I set the parameter at that level(at the time of creating init.ora using manually database creation). like
    ## Original init.ora file created by manual database creation tool on ${DATE}.
    *.aq_tm_processes=0
    *.background_dump_dest='$ORACLE_BASE/admin/$ORACLE_SID/bdump'
    *.compatible='10.2.0'
    *.control_files='/$db_file_loc/oradata/$ORACLE_SID/control01.ctl','/$db_file_loc/oradata/$ORACLE_SID/control02.ctl','/$db_file_loc/oradata/$ORACLE_SID/control03.ctl'
    *.core_dump_dest='$ORACLE_BASE/admin/$ORACLE_SID/cdump'
    *.db_block_size=8192
    *.db_cache_size=104857600
    *.db_domain='$server_name'
    *.db_file_multiblock_read_count=8
    *.db_name='$ORACLE_SID'
    *.fast_start_mttr_target=300
    *.instance_name='$ORACLE_SID'
    *.java_pool_size=16777216
    *.job_queue_processes=4
    *.large_pool_size=16777216
    *.log_archive_dest='/u05/oradata/$ORACLE_SID'
    *.log_archive_format='$ORACLE_SID_%s_%t_%r.arc'
    *.olap_page_pool_size=4194304
    *.open_cursors=500
    *.optimizer_index_cost_adj=50
    *.pga_aggregate_target=536870912
    *.processes=1500
    *.query_rewrite_enabled='TRUE'
    *.remote_login_passwordfile='EXCLUSIVE'
    *.shared_pool_size=83886080
    *.sort_area_size=1048576
    *.sga_max_size=1048576000
    *.sga_target=536870912
    *.star_transformation_enabled='TRUE'
    *.timed_statistics=TRUE
    *.undo_management='AUTO'
    *.undo_retention=10800
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='$ORACLE_BASE/admin/$ORACLE_SID/udump'
    *.utl_file_dir='/export/home/oracle/utlfiles'
    **.nls_characterset='AL32UTF8'*
    EOF
    Is it correct?

  • Change to UTF8 character set

    Hi,
    Currently the character set available is WE8MSWIN1252 and I need it
    to change to UTF8.
    When I tried to change then it throws an error saying that it should be superset of the current character set.
    Please let me know how to resolve this issue ?
    Thanks and Regards,
    A.Mohammed Rafi.

    This transformation is not possible using ALTER .... CHARACTERSET ..., you have to use export/import. Here's a list a possible combinations (up to 9.2),
    for example AL32UTF8 is a superset of UTF8 :
    8.1.6 Subset/Superset Pairs
    ===========================
    A. Current Char set B. New Char set (Superset of A.)
    US7ASCII WE8DEC
    US7ASCII US8PC437
    US7ASCII WE8PC850
    US7ASCII IN8ISCII
    US7ASCII WE8PC858
    US7ASCII WE8ISO8859P1
    US7ASCII EE8ISO8859P2
    US7ASCII SE8ISO8859P3
    US7ASCII NEE8ISO8859P4
    US7ASCII CL8ISO8859P5
    US7ASCII AR8ISO8859P6
    US7ASCII EL8ISO8859P7
    US7ASCII IW8ISO8859P8
    US7ASCII WE8ISO8859P9
    US7ASCII NE8ISO8859P10
    US7ASCII TH8TISASCII
    US7ASCII BN8BSCII
    US7ASCII VN8VN3
    US7ASCII VN8MSWIN1258
    US7ASCII WE8ISO8859P15
    US7ASCII WE8NEXTSTEP
    US7ASCII AR8ASMO708PLUS
    US7ASCII EL8DEC
    US7ASCII TR8DEC
    US7ASCII LA8PASSPORT
    US7ASCII BG8PC437S
    US7ASCII EE8PC852
    US7ASCII RU8PC866
    US7ASCII RU8BESTA
    US7ASCII IW8PC1507
    US7ASCII RU8PC855
    US7ASCII TR8PC857
    US7ASCII CL8MACCYRILLICS
    US7ASCII WE8PC860
    US7ASCII IS8PC861
    US7ASCII EE8MACCES
    US7ASCII EE8MACCROATIANS
    US7ASCII TR8MACTURKISHS
    US7ASCII EL8MACGREEKS
    US7ASCII IW8MACHEBREWS
    US7ASCII EE8MSWIN1250
    US7ASCII CL8MSWIN1251
    US7ASCII ET8MSWIN923
    US7ASCII BG8MSWIN
    US7ASCII EL8MSWIN1253
    US7ASCII IW8MSWIN1255
    US7ASCII LT8MSWIN921
    US7ASCII TR8MSWIN1254
    US7ASCII WE8MSWIN1252
    US7ASCII BLT8MSWIN1257
    US7ASCII N8PC865
    US7ASCII BLT8CP921
    US7ASCII LV8PC1117
    US7ASCII LV8PC8LR
    US7ASCII LV8RST104090
    US7ASCII CL8KOI8R
    US7ASCII BLT8PC775
    US7ASCII WE8DG
    US7ASCII WE8NCR4970
    US7ASCII WE8ROMAN8
    US7ASCII WE8MACROMAN8S
    US7ASCII TH8MACTHAIS
    US7ASCII HU8CWI2
    US7ASCII EL8PC437S
    US7ASCII LT8PC772
    US7ASCII LT8PC774
    US7ASCII EL8PC869
    US7ASCII EL8PC851
    US7ASCII CDN8PC863
    US7ASCII HU8ABMOD
    US7ASCII AR8ASMO8X
    US7ASCII AR8NAFITHA711T
    US7ASCII AR8SAKHR707T
    US7ASCII AR8MUSSAD768T
    US7ASCII AR8ADOS710T
    US7ASCII AR8ADOS720T
    US7ASCII AR8APTEC715T
    US7ASCII AR8NAFITHA721T
    US7ASCII AR8HPARABIC8T
    US7ASCII AR8NAFITHA711
    US7ASCII AR8SAKHR707
    US7ASCII AR8MUSSAD768
    US7ASCII AR8ADOS710
    US7ASCII AR8ADOS720
    US7ASCII AR8APTEC715
    US7ASCII AR8MSAWIN
    US7ASCII AR8NAFITHA721
    US7ASCII AR8SAKHR706
    US7ASCII AR8ARABICMACS
    US7ASCII LA8ISO6937
    US7ASCII JA16VMS
    US7ASCII JA16EUC
    US7ASCII JA16SJIS
    US7ASCII KO16KSC5601
    US7ASCII KO16KSCCS
    US7ASCII KO16MSWIN949
    US7ASCII ZHS16CGB231280
    US7ASCII ZHS16GBK
    US7ASCII ZHT32EUC
    US7ASCII ZHT32SOPS
    US7ASCII ZHT16DBT
    US7ASCII ZHT32TRIS
    US7ASCII ZHT16BIG5
    US7ASCII ZHT16CCDC
    US7ASCII ZHT16MSWIN950
    US7ASCII AL24UTFFSS
    US7ASCII UTF8
    US7ASCII JA16TSTSET2
    US7ASCII JA16TSTSET
    8.1.7 Additions
    ===============
    US7ASCII ZHT16HKSCS
    US7ASCII KO16TSTSET
    WE8DEC TR8DEC
    WE8DEC WE8NCR4970
    WE8PC850 WE8PC858
    D7DEC D7SIEMENS9780X
    I7DEC I7SIEMENS9780X
    WE8ISO8859P1 WE8MSWIN1252
    AR8ISO8859P6 AR8ASMO708PLUS
    AR8ISO8859P6 AR8ASMO8X
    IW8EBCDIC424 IW8EBCDIC1086
    IW8EBCDIC1086 IW8EBCDIC424
    LV8PC8LR LV8RST104090
    DK7SIEMENS9780X N7SIEMENS9780X
    N7SIEMENS9780X DK7SIEMENS9780X
    I7SIEMENS9780X I7DEC
    D7SIEMENS9780X D7DEC
    WE8NCR4970 WE8DEC
    WE8NCR4970 TR8DEC
    AR8SAKHR707T AR8SAKHR707
    AR8MUSSAD768T AR8MUSSAD768
    AR8ADOS720T AR8ADOS720
    AR8NAFITHA711 AR8NAFITHA711T
    AR8SAKHR707 AR8SAKHR707T
    AR8MUSSAD768 AR8MUSSAD768T
    AR8ADOS710 AR8ADOS710T
    AR8ADOS720 AR8ADOS720T
    AR8APTEC715 AR8APTEC715T
    AR8NAFITHA721 AR8NAFITHA721T
    AR8ARABICMAC AR8ARABICMACT
    AR8ARABICMACT AR8ARABICMAC
    KO16KSC5601 KO16MSWIN949
    WE16DECTST2 WE16DECTST
    WE16DECTST WE16DECTST2
    9.0.1 Additions
    ===============
    US7ASCII BLT8ISO8859P13
    US7ASCII CEL8ISO8859P14
    US7ASCII CL8ISOIR111
    US7ASCII CL8KOI8U
    US7ASCII AL32UTF8
    BLT8CP921 BLT8ISO8859P13
    US7ASCII AR8MSWIN1256
    UTF8 AL32UTF8 (added in patchset 9.0.1.2)
    Character Set Subset/Superset Pairs Obsolete from 9.0.1
    =======================================================
    US7ASCII AR8MSAWIN
    AR8ARABICMAC AR8ARABICMACT
    9.2.0 Additions
    ===============
    US7ASCII JA16EUCTILDE
    US7ASCII JA16SJISTILDE
    US7ASCII ZHS32GB18030
    US7ASCII ZHT32EUCTST
    WE8ISO8859P9 TR8MSWIN1254
    LT8MSWIN921 BLT8ISO8859P13
    LT8MSWIN921 BLT8CP921
    BLT8CP921 LT8MSWIN921
    AR8ARABICMAC AR8ARABICMACT
    ZHT32EUC ZHT32EUCTST
    UTF8 AL32UTF8
    Character Set Subset/Superset Pairs Obsolete from 9.2.0
    =======================================================
    LV8PC8LR LV8RST104090

  • Convert custom character set of nonunicode system to standard character set

    hi all,
    I'm a BI consultant and have the following problem:
    we want to load attribute data (products, customers,...) from R3 into BI via standard extractors.
    R3 is a non-unicode system, and some products (or customers) use a custom character set Z2.
    When we extract this data to BI (a unicode system) we get an error (tRFC) saying he can't confert certain values. SAP says that he can't convert character set Z2 to the standard character set 4102.
    Converting the R3 system to a unicode system would be the solution,but is not an option... unfortunatly...
    Please advice, give gidelines,... because this problem is really a showstopper for our project...
    Thx!!!
    Joke

    hi joke,
    i am providing some  links pls chk them . I think they will be help full for you.
    www.sap-press.de/katalog/buecher/htmlleseproben/gp/htmlprobID-149 - 69k
    www.sap-press.de/download/dateien/1240/sappress_unicode_in_sap_systems.pdf
    http://209.85.207.104/search?q=cache:y__bQrnsix0J:https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f5130af2-0a01-0010-c092-a6d44eadd153convertcustomcharactersetofnonunicodesystemtostandardcharacterset%2B+abap&hl=en&ct=clnk&cd=7&gl=us
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/efd1dd90-0201-0010-e1b0-8437c998cd79
    www.redbooks.ibm.com/redpapers/pdfs/redp4189.pdf
    thanks
    karthik

  • Database character set = UTF-8, but mismatch error on XML file upload

    Dear experts,
    I am having problems trying to upload an XML file into an XMLType table. The Database is 9.2.0.5.0, with the character set details:
    SELECT *
    FROM SYS.PROPS$
    WHERE name like '%CHA%';
    Query results:
    NLS_NCHAR_CHARACTERSET          UTF8     NCHAR Character set
    NLS_SAVED_NCHAR_CS          UTF8
    NLS_NUMERIC_CHARACTERS          .,     Numeric characters
    NLS_CHARACTERSET          UTF8     Character set
    NLS_NCHAR_CONV_EXCP          FALSE     NLS conversion exception
    To upload the XML file into the XMLType table, I am using the command:
    insert into XMLTABLE
    values(xmltype(getClobDocument('ServiceRequest.xml','UTF8')));
    However, I get the error:
    ORA-31011: XML parsing failed
    ORA-19202: Error occurred in XML processing
    LPX-00200: could not convert from encoding UTF-8 to UCS2
    Error at line 1
    ORA-06512: at "SYS.XMLTYPE", line 0
    ORA-06512: at line 1
    Why does it mention UCS2, as can't see that on the Database character set?
    Many thanks for your help,
    Mark

    USC2 is known as AL16UTF16(LE/BE) by Oracle...
    Try using AL32UTF8 as the character set name
    AFAIK The main difference between Oracle's UTF8 and AL32UTF8 character set is that is the UTF8 character set does not support those UTF-8 characteres that require 4 bytes..
    -Mark

  • What Determines the "File Character Set" on Export?

    When we Export a Page, for example, from APEX, the File Character Set is defaulted to some value (and not editable). On some of our instances, this defaults to "Western European Windows 1252" while on others it is "Unicode UTF-8." Specifically, what setting is being used to make this determination? This is kind of a pain because we have some environments wherein we are promoting changes from environment to environment and these settings differ. If, during import, the user neglects to set this to the same File Character Set in which the file was originally exported, we get issues (non-printable control characters and the like). Therefore, we'd love to make all of the environments match but, aren't sure how to do this.
    Thanks,
    -Joe
    Edited by: Joe Upshaw on Apr 10, 2013 3:25 PM

    Hello Joe,
    In your environment, the character set of the APEX exported files is set according to the DAD character set, and with your APEX version, it must be set to AL32UTF8 (regardless of the database character set).
    Re: Export - File Character Set list is read only (fixe UTF-8 value)
    You should check the DAD character set setting in the environments in which APEX is not exporting the files using UTF8.
    Regards,
    Arie.
    &diams; Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.
    &diams; Author of Oracle Application Express 3.2 – The Essentials and More

  • Oracle Character sets with PeopleSoft - AL32UTF8 vs. UTF8

    We currently have PeopleSoft FInancials v8.8 with PeopleTools 8.45 running on Oracle 9.2.0.8 with the UTF8 character set.
    We plan to upgrade to Oracle 10.2, and want to know if we can and should also convert the character set to AL32UTF8.
    Any issues?
    (A couple of years ago, we were told that AL32UTF8 was not yet supported in PeopleSoft).

    Right now, something strange, Oracle recommand do not use anymore UTF8, and Peoplesoft recommand do not use AL32UTF8 yet.
    You can read the solution id #719906, but anyway, AL32UTF8 on PT8.4x should works fine.
    Nicolas.

  • Using Set Break Order property

    Hi,
    I create a Break Group with one column in the Data Model
    Open the Property Palette for the column and the Set Break Order property does not appear. However the Break Order property does appear and its values is asending or descending.
    Here's the definition for this property in Report Bulder Help "The Set Break Order Property is whether to set the order in which to display the column's values, using the Break Order property". This implies that if the Break Order property is set to something other than NONE, the Set Break Order is Yes.
    Another reference I have states " A point to be noted is that all break groups must have at least one column with the Set Break Order set to the Yes value".
    My concern/question is in all of the documentation I have read both properties appear, but only one appears in my environment. Am I doing something wrong? Is there a setting to be change to make both properties appear? I am using Reports 6i, on Win2000 and connected to an Oracle 8i database.
    Thanks in advance,
    Audrey

    Hi,
    This looks to be a documentation mistake. From Reports 3.0.5 onwards, We have removed the Set Break Order Property for columns and just added
    a "None" item to the Break Order property poplist instead. For columns which cannot be break columns, we do not even give the option of changing the Break Order from None to anything else. So just go-on desiging your Report with just one break order property, that is sufficient.
    Thanks,
    Rohit

  • How to set or change character set for Oracle 10 XE

    Installing via RPM on Linux.
    I need to have my database set to use UTF8 and WE8ISO8859P15 as the character set and national character set. (Think those are in the right order. If not, it's the opposite.)
    If I do a standard "yum localinstall rpm-file-name," it installs Oracle. I then run the "/etc/init.d/oracle-xe configure" command to set my ports.
    Every time I do this, I end up with AL32/AL16 character sets.
    I finally hardcoded ISO-8859-15 as the Linux 'locale' character set and set this in the various bash profile config files. Now, I end up with WE8MSWIN1252 as the character set and AL16UTF16 as the national character set.
    I've tried editing the createdb.sh script to hard code the character set types and then copied that file over the original while the RPM is still installing. I've tried editing the nls_lang.sh script to hard code the settings there and copied over the original shell script while the RPM is still installing.
    Doesn't matter.
    HOW can I do this? If I wait until after the RPM is installed and try running the createdb.sh file, then it ends up creating a database but not doing everything properly. I end up missing pfiles or spfiles. Various errors crop up.
    If I try to change them from the sql command line, I am told that the new character set must be a superset of the old one. It fails.
    I'm new to Oracle, so I'm treading water that's uncharted. In short, I need community help. It's important to the app I'm running and attempting to migrate from to maintain these character sets.
    Thanks.

    I don't think you can change Oracle XE character set. When downloading Oracle XE you must choose to download:
    - either the Universal Edition using AL32UTF8
    - or the Western Euopean Edition using WE8MSWIN1252.
    See http://download.oracle.com/docs/cd/B25329_01/doc/install.102/b25144/toc.htm#BABJACJJ
    If you really need UTF8 instead of AL32UTF8 you need to use Oracle Standard Edition or Oracle Entreprise Edition:
    these editions allow to select database character set at database creation time which is not really possible with Oracle XE
    Note that changing environment variable NLS_LANG has nothing to do with changing database character set:
    http://download.oracle.com/docs/cd/B25329_01/doc/install.102/b25144/toc.htm#BABBGFIC

  • Character set in MDL export/import

    Hi,
    we are running OWB 10.1.0.2. In order to get version control, we perform MDL exports of collections from our development environment and then import them into our test and production environments. Each environment uses its own design repository, but all repositories are in the same database.
    When doing an export of a collection, we always specify the character set AL32UTF8 because that is what we are running in the repository database. When later doing an import using the graphical user interface, it is not possible to specify the character set (but this can be done when using the import utility). According to the documentation, the GUI import will then assume that the character set in the collection is the character set of the client, which usually is WE8MSWIN1252. (The documentation also says that it IS possible to specify the character set during GUI import, this is obviously a documentation error).
    My questions are: What is the point of specifying character set when doing exports and imports? Could an AL32UTF8 export followed by an WE8MSWIN1252 import cause problems? I assume that the character set used by export is specified in the collection file, so does the import then convert it to WE8MSWIN1252 (or the character set specified in the import utility)?
    Or, to be more general: What is actually happening with the character sets during MDL export/import?
    /Kjell Gullberg

    Dear ski123,
    I think you are not going to loose any data of yours when you migrate the database. You may proceed to the import.
    Please find below documentations;
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14196/install003.htm#sthref81
    For Database Character Set, select from one of the following options:
        *Use the Default—Select this option if you need to support only the language currently used by the operating system for all your database users and your database applications.
        *Use Unicode (AL32UTF8)—Select this option if you need to support multiple languages for your database users and your database applications.
        *Choose from the list of character sets—Select this option if you want the Oracle Database to use a character set other than the default character set used by the operating system.Choosing a Character Set;
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch2charset.htm#NLSPG002
    AL32UTF8;
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/glossary.htm#sthref2039
    Hope That Helps.
    Ogan

  • Error while running package ORA-06553: PLS-553 character set name is not re

    Hi all.
    I have a problem with a package, when I run it returns me code error:
    ORA-06552: PL/SQL: Compilation unit analysis terminated
    ORA-06553: PLS-553: character set name is not recognized
    The full context of the problem is this:
    Previously I had a developing data base, then was migrated to a new server. After that I started to receive the error, so I began to check for the solution.
    My first move was compare the “old database” with the “new database”, so I check the nls parameters, and this was the result:
    select * from nls_database_parameters;
    Result from the old
    NLS_LANGUAGE     AMERICAN
    NLS_TERRITORY     AMERICA
    NLS_CURRENCY     $
    NLS_ISO_CURRENCY     AMERICA
    NLS_NUMERIC_CHARACTERS     .,
    NLS_CHARACTERSET     US7ASCII
    NLS_CALENDAR     GREGORIAN
    NLS_DATE_FORMAT     DD-MON-RR
    NLS_DATE_LANGUAGE     AMERICAN
    NLS_SORT     BINARY
    NLS_TIME_FORMAT     HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT     DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT     HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT     DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY     $
    NLS_COMP     BINARY
    NLS_LENGTH_SEMANTICS     BYTE
    NLS_NCHAR_CONV_EXCP     FALSE
    NLS_NCHAR_CHARACTERSET     AL16UTF16
    NLS_RDBMS_VERSION     10.2.0.1.0
    Result from the new
    NLS_LANGUAGE     AMERICAN
    NLS_TERRITORY     AMERICA
    NLS_CURRENCY     $
    NLS_ISO_CURRENCY     AMERICA
    NLS_NUMERIC_CHARACTERS     .,
    NLS_CHARACTERSET     US7ASCII
    NLS_CALENDAR     GREGORIAN
    NLS_DATE_FORMAT     DD-MON-RR
    NLS_DATE_LANGUAGE     AMERICAN
    NLS_SORT     BINARY
    NLS_TIME_FORMAT     HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT     DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT     HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT     DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY     $
    NLS_COMP     BINARY
    NLS_LENGTH_SEMANTICS     BYTE
    NLS_NCHAR_CONV_EXCP     FALSE
    NLS_NCHAR_CHARACTERSET     AL16UTF16
    NLS_RDBMS_VERSION     10.2.0.1.0
    As the result was identical, I decided to look for more info in the log file of the new database. What I find was this:
    Database Characterset is US7ASCII
    Threshold validation cannot be done before catproc is loaded.
    Threshold validation cannot be done before catproc is loaded.
    alter database character set INTERNAL_CONVERT WE8MSWIN1252
    Updating character set in controlfile to WE8MSWIN1252
    Synchronizing connection with database character set information
    Refreshing type attributes with new character set information
    Completed: alter database character set INTERNAL_CONVERT WE8MSWIN1252
    alter database character set US7ASCII
    ORA-12712 signalled during: alter database character set US7ASCII...
    alter database character set US7ASCII
    ORA-12712 signalled during: alter database character set US7ASCII...
    Errors in file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_3132.trc:
    Regards

    Ohselotl wrote:
    Hi all.
    I have a problem with a package, when I run it returns me code error:
    ORA-06552: PL/SQL: Compilation unit analysis terminated
    ORA-06553: PLS-553: character set name is not recognized
    The full context of the problem is this:
    Previously I had a developing data base, then was migrated to a new server. After that I started to receive the error, so I began to check for the solution.
    My first move was compare the “old database” with the “new database”, so I check the nls parameters, and this was the result:
    select * from nls_database_parameters;
    Result from the old
    NLS_LANGUAGE     AMERICAN
    NLS_TERRITORY     AMERICA
    NLS_CURRENCY     $
    NLS_ISO_CURRENCY     AMERICA
    NLS_NUMERIC_CHARACTERS     .,
    NLS_CHARACTERSET     US7ASCII
    NLS_CALENDAR     GREGORIAN
    NLS_DATE_FORMAT     DD-MON-RR
    NLS_DATE_LANGUAGE     AMERICAN
    NLS_SORT     BINARY
    NLS_TIME_FORMAT     HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT     DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT     HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT     DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY     $
    NLS_COMP     BINARY
    NLS_LENGTH_SEMANTICS     BYTE
    NLS_NCHAR_CONV_EXCP     FALSE
    NLS_NCHAR_CHARACTERSET     AL16UTF16
    NLS_RDBMS_VERSION     10.2.0.1.0
    Result from the new
    NLS_LANGUAGE     AMERICAN
    NLS_TERRITORY     AMERICA
    NLS_CURRENCY     $
    NLS_ISO_CURRENCY     AMERICA
    NLS_NUMERIC_CHARACTERS     .,
    NLS_CHARACTERSET     US7ASCII
    NLS_CALENDAR     GREGORIAN
    NLS_DATE_FORMAT     DD-MON-RR
    NLS_DATE_LANGUAGE     AMERICAN
    NLS_SORT     BINARY
    NLS_TIME_FORMAT     HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT     DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT     HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT     DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY     $
    NLS_COMP     BINARY
    NLS_LENGTH_SEMANTICS     BYTE
    NLS_NCHAR_CONV_EXCP     FALSE
    NLS_NCHAR_CHARACTERSET     AL16UTF16
    NLS_RDBMS_VERSION     10.2.0.1.0
    As the result was identical, I decided to look for more info in the log file of the new database. What I find was this:
    Database Characterset is US7ASCII
    Threshold validation cannot be done before catproc is loaded.
    Threshold validation cannot be done before catproc is loaded.
    alter database character set INTERNAL_CONVERT WE8MSWIN1252
    Updating character set in controlfile to WE8MSWIN1252
    Synchronizing connection with database character set information
    Refreshing type attributes with new character set information
    Completed: alter database character set INTERNAL_CONVERT WE8MSWIN1252
    *********************************************************************This is an unsupported method to change the characterset of a database - it has caused the corruption of your database beyond repair. Hopefully you have a backup you can recover from. Whoever did this did not know what they were doing.
    alter database character set US7ASCII
    ORA-12712 signalled during: alter database character set US7ASCII...
    alter database character set US7ASCII
    ORA-12712 signalled during: alter database character set US7ASCII...
    Errors in file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_3132.trc:
    RegardsThe correct way to change the characterset of a database is documented - http://docs.oracle.com/cd/B19306_01/server.102/b14225/ch11charsetmig.htm#sthref1476
    HTH
    Srini

Maybe you are looking for