Client-side greek character set problem

hi everyone,
i am a .net developer and absolutelly new to oracle, its my first project that i have make oracle and .net co-operate and it's proving to be a nightmare!
i ll try and provide as much info as possible to you
we have a unix sap server with oracle 10.something on it (i can check exactly what version if that's of importance) and i am writting a .net app which accesses the oracle db and retrieve some data we need
the locale settings of the db are american_america.we8dec and i cannot temper with that machine, it is out of the question
i have made the connection to the db using just connection string info, not tns and stuff, and i have set my dev machine's nls_lang to we8dec everywhere i could find it with a 'find' in the registry
however my app displays the data (which is in greek) showing random symbols that obviously make to sense
furthermore when i connect to the db via sql developer or navicat i still get the same symbols
i understand it is something to do with my client system's settings but i cant work it out
i would really appreciate your help i am sorry if it is something very simple but i just cant find it
thanks

user9084006 wrote:
i am a .net developer and absolutelly new to oracle, its my first project that i have make oracle and .net co-operate and it's proving to be a nightmare!Welcome. It's a brand new universe, but if you take it step by step I'm sure you'll do fine. Get someone near with Oracle dev and dba background to guide you, so you don't get stuck or go down broken roads.
we have a unix sap server with oracle 10.something on it (i can check exactly what version if that's of importance)It is of importance most of the time. Down to at least 4 positions (for example, "10g" is just a marketing label and mostly useless in a techincal context - 10.2.0.5 is more like it).
Also mention platform (unix OS) details.
and i am writting a .net app which accesses the oracle db and retrieve some data we needHow is the to-be retrieved data loaded or entered to begin?
>
the locale settings of the db are american_america.we8dec and i cannot temper with that machine, it is out of the question Please post output from:
SQL> select * from nls_database_parameters where parameter like '%CHARACTERSET';
and i have set my dev machine's nls_lang to we8dec everywhere i could find it with a 'find' in the registryDoes your dev (client) machine use a "we8dec" character set? Likely, as you seem to be on Windows, you should have set nls_lang client char set part to match win-1252 or whatever client char set (code page) is in use.
however my app displays the data (which is in greek) showing random symbols that obviously make to senseNo surprise since DEC character set does not have a greek character in its repertoire. If I'm not all mistaken DEC MCS (or similar) is the charcter set to which WE8DEC corresponds. You could check against mapping table in Locale builder, but available characters should be per following link or close enough.
http://czyborra.com/charsets/iso8859.html#ISO-8859-1 (second chart is DEC-MCS)
Please provide a sample of those "random symbols".
furthermore when i connect to the db via sql developer or navicat i still get the same symbolsIf that's Oracle SQL Developer it should give a true picture of what's actually stored - which, unfortuantely, seem to be invalid character data.
i understand it is something to do with my client system's settings but i cant work it out See above. But even if you correctly setup client environment, the db won't be able to store the data if databas character set is in fact WE8DEC.
>
i would really appreciate your help i am sorry if it is something very simple but i just cant find it I'm not sure, but it would seem as you have been given unfeasible conditions to work from. So maybe it's not up to you, until a character set migration has been taken place.
In general, the Database character set should be a suitable superset (repertoire) that covers all current (and hopefully future) language alphabets requirements.
You might want to search forum for 'we8dec' to find previous related discussions.
Edit:
- Added url with DEC MCS.
- platform info
Edited by: orafad on Jan 26, 2012 12:28 PM
Edited by: orafad on Jan 26, 2012 12:43 PM

Similar Messages

Greek Character Set Problem

Dear All,
We are currently working on Oracle 8i to 9i migration and unicode implementation of an application SampleDB. We encountered an issue (described below) while the data migration.
Issue:
We have a database in oracle8i with
NLS_LANGUAGE AMERICAN
NLS_CHARACTERSET WE8ISO8859P1
NLS_NCHAR_CHARACTERSET WE8ISO8859P1
The character set WE8ISO8859P1 does not support GREEK language. The user inserts/modifies records in this database from the front-end. The front end installed in the client machine has the following setting:
Control Panel->Regional settings ->Advanced ->Language for non-unicode programs = Greek
Oracle client installed in English
Greek characters have been inserted/ updated into this database and retrieved and displayed correctly by the GUI.
Note: Greek data has been inserted into WE8ISO8859P1 database which does not support Greek characters.
Hence the actual data that is stored in the database are not Greek. Only while displaying, they are getting converted into Greek characters due to the settings in the client machine.
Requirement: Migrate the database to Oracle 9i - Unicode.
While migration, we need to eliminate any data discrepancy and make sure the data in the Unicode database is in Greek.
Can any one suggest us a method to do the migration to avoid the above mentioned problem?
Further, can any one tell us a way to verify what characters get stored in the database and help us identify if they are real Greek characters

The character set WE8ISO8859P1 does not support GREEK language.If you want to support Greek characters (or 'math' symbols), look at the EL8... char sets.
Control Panel->Regional settings ->Advanced
->Language for non-unicode programs = Greek
Oracle client installed in EnglishThis is dependent on the app and Windows. What is the NLS_LANG value in this Oracle home? NLS_LANG should be adjusted to fit the application.
Note: Greek data has been inserted into WE8ISO8859P1
database which does not support Greek characters.
Hence the actual data that is stored in the database
are not Greek. Only while displaying, they are
getting converted into Greek characters due to the
settings in the client machine.Maybe character data does not get converted, but still shown as greek.
Further, can any one tell us a way to verify what
characters get stored in the database and help us
identify if they are real Greek charactersIn the case of character data, what you really store depends on the db and the character values. You can use dump or some other PL function to look at the values.
There's a Database Globalization Support Guide for 9.2 that might be useful.

Oracle 8i us7ascii character set problem - help required urgent.

Hi frnds,
I have a oracle 8i database server installed on sun solaris os. The database character set is us7ascii. In one of the tables TIFF images are stored in a long column. I m trying to fetch these images using oracle 9i client and visual basic(oracle ODBC drivers). But i m unable to do so. I can not fetch special characters.
Is it because of the character set problem? but when i run my code on the server itself, i m able to fetch the images. I tried to fetch the images using oracle 8 i client on windows XP machine but could not do so. Are there any special settings that i have to do on the client side?

Indeed, it's an ODBC issue. Read this statement from Oracle:
From ODBC 8.1.7.2.0 drivers onwards it's NOT possible any more to
"disable" Characterset conversion by specifying for the NLS_LANG
the same characterset as the database characterset. There is now
ALWAYS a check to see if a codepoint is valid for that characterset.
Typically you will encounter problems if you upgrade an environment
that has NO NLS_LANG set on the client (or US7ASCII) and the database
was also US7ASCII. This incorrect setup allowed you to store characters
like èçàé in an US7ASCII database, with the new 8i drivers this is not possible
any more.
Basic problem is the 'wrong' characterset US7ASCII in the database. As long as no characterset conversion happens (that's the case on the unix server), special characters are no problem.
Werner

Oracle character set problem - help reqed urgent !!

Hello frnds,
I have a oracle 8i database server installed on sun solaris os. The database character set is us7ascii. In one of the tables TIFF images are stored in a long column. I m trying to fetch these images using oracle 9i client and visual basic(oracle ODBC drivers). But i m unable to do so. I can not fetch special characters.
Is it because of the character set problem? but when i run my code on the server itself, i m able to fetch the images. I tried to fetch the images using oracle 8 i client on windows XP machine but could not do so. Are there any special settings that i have to do on the client side?

i run my code on the server itself, i m able to fetch
the images. I tried to fetch the images using oracle
8 i client on windows XP machine but could not do so.You able to fetch the image , So it is not because of the character set.
First thing you need to consider is that use certified combination of OS , client and database server only. Check Certify - Oracle's Certification Matrices
Virag

Backup failure due to Character set problem

Hi,
I am manually running a COLD backup script in Windows NT environment and all the logs has been captured below:
Recovery Manager: Release 8.1.6.0.0 - Production
RMAN-06005: connected to target database: db1 (DBID=754030292)
RMAN-06009: using target database controlfile instead of recovery catalog
RMAN> shutdown immediate;
2> startup mount;
3> RUN {
4> ALLOCATE CHANNEL disk1 TYPE disk;
5> BACKUP DATABASE TAG 'db1_db_full' FORMAT 'e:\backup\db1\db1_backup';
6> copy current controlfile to 'e:\backup\db1\Control_db1.ctl';
7> }
8>
RMAN-06405: database closed
RMAN-06404: database dismounted
RMAN-06402: Oracle instance shut down
RMAN-06193: connected to target database (not started)
RMAN-06196: Oracle instance started
RMAN-06199: database mounted
Total System Global Area 934143244 bytes
Fixed Size 70924 bytes
Variable Size 260554752 bytes
Database Buffers 673439744 bytes
Redo Buffers 77824 bytes
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: disk1
RMAN-08500: channel disk1: sid=13 devtype=DISK
RMAN-03022: compiling command: backup
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: backup
RMAN-06003: ORACLE error from target database: ORA-06550: line 1, column 166:
PLS-00553: character set name is not recognized
ORA-06550: line 0, column 0:
PL/SQL: Compilation unit analysis terminated
RMAN-06031: could not translate database keyword
Recovery Manager complete.
As the above log shown, I cannot do any backup command in the RUN bracket and it complains that the character set is not recognized.
This set of error happens when I have create six other Oracle databases in my NT box. Before that, I can manually run the backup with no problem and a backupset has been generated.
If you have come across this problem and have solutions of it. That will be great.
Thanks !!
null

kk001 wrote:
Hi ,
The export Backup failing due to character set problem
. . exporting table ravidlx
EXP-00008: ORACLE error 6552 encountered
ORA-06552: PL/SQL: Compilation unit analysis terminated
ORA-06553: PLS-553: character set name is not recognized
P
Please suggest how to set character set
I don't know what you have.
I don't know what you do.
I don't know what you see.
It is really, Really, REALLY difficult to fix a problem that can not be seen.
use COPY & PASTE so we can see what you do & how Oracle responds.
do as below so we can know complete Oracle version & OS name.
Post via COPY & PASTE complete results of
SELECT * from v$version;

Using translate function to correct character set problem....

I have a table(TBL_STOCK) on Oracle XE.
Rows come from sql server 2005 with a trigger on sql server table via the linked server.
But there is a character set problem with some character like İ,Ş,Ğ.
They change to Ý,Þ,Ð. in Oracle.
How can i correct these ? Do you suggest the TRANSLATE function ?
What do u think, if i create an After Insert trigger on Oracle table(TBL_STOCK) and convert these character using the Translate function when they inserted from sql server.
Anyone have any other ideas that can be more efficient. Any thoughts appreciated.
Thanks in advance.
Adam
PS:The NLS_CHARACTERSET of Oracle is AL32UTF8.

It is sql server 2005 and Collation is SQL_Latin1_General_CP1_CI_AS

Agent control character set problem

Hi,
here's my problem :
i've got the grid that's running on a RHES4 with an agent. On another RHES4, i've got 10g databases that run and another agent.
The repository database is configured like this :
nsl_language = AMERICAN
nls_territory = AMERICA
character set = AL32UTF8
all the uploads from the agent on the RHES4 where the grid is installed are ok.
On the other server, as soon as there's an UTF8 character in a xml file (like " é " ou " ' "), the upload fails and the agent stops.
in the logs, it s clear it comes from this. I've deleted all the occurences of UTF8 characters in the xml file and restarted the upload and it's ok...
I've tested different configurations but without success.
Any clue ?
Alivetu

Thanks for the reply,
NLS LANG is set on the 2 machines with FRENCHFRANCE.WE8ISO8859P15
I've added the line '<?xml version="1.0" encoding="ISO-8859-1"?>' at the beginning of the xml file that doesn't work and made a 'emctl upload'....it has passed and the agent has stopped arrived to another UTF8 xml file...
So, it really is a character set problem but where to set it ???
Alivetu

EXPORT Backup failing due to character set problem

Hi ,
The export Backup failing due to character set problem
. . exporting table ravidlx
EXP-00008: ORACLE error 6552 encountered
ORA-06552: PL/SQL: Compilation unit analysis terminated
ORA-06553: PLS-553: character set name is not recognized
P
Please suggest how to set character set
Regards,
kk
Edited by: kk001 on Aug 29, 2011 7:22 PM

kk001 wrote:
Hi ,
The export Backup failing due to character set problem
. . exporting table ravidlx
EXP-00008: ORACLE error 6552 encountered
ORA-06552: PL/SQL: Compilation unit analysis terminated
ORA-06553: PLS-553: character set name is not recognized
P
Please suggest how to set character set
I don't know what you have.
I don't know what you do.
I don't know what you see.
It is really, Really, REALLY difficult to fix a problem that can not be seen.
use COPY & PASTE so we can see what you do & how Oracle responds.
do as below so we can know complete Oracle version & OS name.
Post via COPY & PASTE complete results of
SELECT * from v$version;

Database client character set problem

Hello
My database oracle 11gR1 database at Linux platform
Database NLS_LANG settings
SQL> Select * from nls_session_parameters;
PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
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
SQL> SELECT * from NLS_DATABASE_PARAMETERS WHERE parameter IN ( 'NLS_LANGUAGE', 'NLS_TERRITORY', 'NLS_CHARACTERSET');
PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CHARACTERSET WE8ISO8859P9
SQL> Select * from v$nls_parameters ;
NLS_LANGUAGE
AMERICAN
NLS_TERRITORY
AMERICA
NLS_CURRENCY
$
NLS_ISO_CURRENCY
AMERICA
NLS_NUMERIC_CHARACTERS
NLS_CALENDAR
GREGORIAN
NLS_DATE_FORMAT
DD-MON-RR
NLS_DATE_LANGUAGE
AMERICAN
NLS_CHARACTERSET
WE8ISO8859P9
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_NCHAR_CHARACTERSET
UTF8
NLS_COMP
BINARY
NLS_LENGTH_SEMANTICS
BYTE
NLS_NCHAR_CONV_EXCP
FALSE
And Client informations: Windows 7 oracle forms 10gr2 forms installation NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P9
When i insert Turkish special characters from client,everything seems okey from client side
http://img.photobucket.com/albums/v346/satanix/moz-screenshot-1.png
But when i select from database it seems like this.
http://img.photobucket.com/albums/v346/satanix/moz-screenshot-2.png
And i update this row from Linux side and select from client
http://img.photobucket.com/albums/v346/satanix/moz-screenshot-4.png
NLS_LANGS which i tried at windows platforms
AMERICAN_AMERICA.WE8ISO8859P9
AMERICAN_AMERICA.UTF8
AMERICAN_AMERICA.TR8PC857 (Best result but still lots of problem)
AMERICAN_AMERICA.TR8MSWIN1254
Thanks

Hi,
sorry missed that picture. What I now think is that you missing the possibility to display turkish characters on Linux. Is there a Turkish pack to install for Linux "(I'm no a Linux expert). Or are you using a lettertype which cannot display Turkish letters?
Herald ten Dam
http://htendam.wordpress.com

Greek Character Display Problem

Hi
Server Side : We are using Oracle 8i . Database Character Set = UTF8.
Client Side: Windows XP. Modified Control Panel->Regional Settings -> Advanced->Language for non-unicode program = Greek.
Changed Alter session set NLS_Language = GREEK
When we opened the oracle connection in our VB application.
From our Visual Basic application
Now I am able to input greek chars, Retrieve it back and displayed correctly.
But When we copy a particular string and paste it in a field, one particular
character is always showing as ?. As we don't have a greek keyboard, I don't
know what combination of keys to press to key-in that particular character.
This is the Word I have copied from Editor and pasted it in the VB field.
Ονοµα επιßάτη .
Except the Character which looks like B, all other greek characters are getting displayed properly and inserted correctly in the database. Only that particular letter is displayed as ? (question mark)
Any idea what is wrong !!.
Thanks in advance.
Regards
Murali

Check this out.
http://www.oracle.com/technology/tech/globalization/htdocs/nls_lang%20faq.htm

Character set Problem (From WE8ISO8859P1 to EL8MSWIN1253)

Hi there,
I would like to describe a problem that I face with import, export and Greek characters.
I have two databases with the following characteristics
Source database:
O/S version Windows
Database version à 10GR2
NLS_CHARACTERSET à WE8ISO8859P1
NLS_NCHAR_CJARACTERSET à AL16UTF16
NLS_LANGUAGE à GREEK
NLS_TERRITORY à GREECE
Target database:
O/S version Windows
Database version à 10GR2
NLS_CHARACTERSET à EL8MSWIN1253
NLS_NCHAR_CJARACTERSET à AL16UTF16
NLS_LANGUAGE à GREEK
NLS_TERRITORY à GREECE
From the source database, using the export tool I am exporting a table (TABLE_A) which contains Greek records. At this point I want to mention that the from the source database I am able to read the Greek characters from TABLE_A by using sqlplus i.e (select * from table_a;)
On the target database by using import I load the table TABLE_A into the database.
When I select the newly imported TABLE_A on the target database I am not able to read the Greek characters.
I have tested various scenarios by using different values for the NLS_LANG variable regarding export and import clients but I did not manage to read the Greek characters on the target database.
If anyone faced the same or a similar problem please I am asking for assistance.
Thank you in advance

Please, review this thread:
Re: Arabic Character set conversion-help needed
The thread describes a similar issue for Arabic data. Therefore, when reading the thread, substitute 'WE8ISO8859P1' for 'AR8ISO8859P6', 'EL8MSWIN1253' for 'AR8MSWIN1256', and 'Greek' for 'Arabic'.
-- Sergiusz

Turkish character set problem in Windows

Hi;
I am developing an application in VB.net 2005 using an oracle database on the Linux server.
I have Oracle Client installed on my windows machine.
I installed ODT.NET and ODP.Net by executing ODTwithODAC10202.exe on the client side.
I am using Turkish character set in Windows.
I have couples of problems I couldn't manage..
1. I cannot use 'i' character in database password since it leads to error: 'Invalid user ıd or password'
2. I cannot use Pooling parameter in my oracle connection string, since it leads to error 'Pooling is invalid attribute of connetion string'
3. I cannot store Turkish characters to the database.
--SELECT * from NLS_SESSION_PARAMETERS results in following:
NLS_LANGUAGE TURKISH
NLS_TERRITORY TURKEY
NLS_CURRENCY TL
NLS_ISO_CURRENCY TURKEY
NLS_NUMERIC_CHARACTERS ,.
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD/MM/RRRR
NLS_DATE_LANGUAGE TURKISH
NLS_SORT TURKISH
NLS_TIME_FORMAT HH24:MI:SSXFF
NLS_TIMESTAMP_FORMAT DD/MM/RRRR HH24:MI:SSXFF
NLS_TIME_TZ_FORMAT HH24:MI:SSXFF TZR
NLS_TIMESTAMP_TZ_FORMAT DD/MM/RRRR HH24:MI:SSXFF TZR
NLS_DUAL_CURRENCY YTL
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
--SELECT * from NLS_DATABASE_PARAMETERS results in following:
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET WE8ISO8859P1
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
How should I configure the NLS settings to be able to store Turkish characters?
Thanks in advance..
Melike

meraba ankara yasiyorum.Sizinle mail araciliyla görüsmemiz mumkun mu?
e_mail: [email protected]
Bilgisayırıma 10g express edition yükledim .Bi de ODT for 10gXE (ADD-in) yükledim.Ama
connect e basınca veritabanına .net den baglanamıyorum username yada password yanlis diyor.string name express edition icin nedir..net 2003 bilgisayarima yüklü.
.net ve oracle kullanarak bir proje yapmak istiyorum.Yardimci olabilirmisiniz
saygilar..

DIR7 Character Set Problem / Foreign Language

Hi there,
I am working on an app built using Director 7 that until now
has used the standard English (latin-1) character set.
However, I am required to deliver a new version including
some elements displayed in a second language, in this case Welsh,
which uses characters outside of the normal set. I believe those
required are included in Latin-1 Extended, otherwise in Unicode as
a whole, obviously.
I am having specific problems with two characters that appear
to be missing from Latin-1, which are: ŵ and ŷ
(w-circumflex, and y-circumflex [i think!]).
In a standard text box I create using Director, I am unable
either to paste either character in, or enter it using its
ALT+combination, let alone save to the associated database.
I have read that Dir 11 is the first version with full
Unicode support - which surprises me - however I would assume that
someone would likely have hit this, or a similar issue before the
release of this version and was wondering if there is a possible
solution without upgrade.
My possible thinking is either a declaration that allows
change of a Charset, as I might do in XHTML for example, or
deployment of an Xtra that allows me to use a different character
set.
If anyone could shed some light on the matter, it would be
very helpful! Thanks in advance!
Rich.

Yes, this was always a problem for years. Back when I was
**** this, we had
some projects that needed text displayed in various
languages. Each
language presented its own challenges. Things like Greek
weren't too bad,
because the Symbol font works for most Greek text. (Only
problem was the
's' version of Sigma, which had to switch back to Times New
Roman.) Various
eastern European languages (Polish, Czech, Hungarian, etc.)
posed a problem
with some of the accents that were not available in standard
font sets. We
were forced to live without some of the more exotic accents,
but were told
that it would still be readable without them, if not exactly
correct. This
would probably be the closest to your situation, from what
little I know
about Welsh. It could be worse, though. Hebrew and Arabic
were challenging
as they are written right-to-left, and thus had to have code
written to
input them backwards. Russian was also tough, as the Cyrillic
alphabet has
more characters than the others, but I was able to find a
font to fake it.
(It replaced some of the lesser-used standard characters in
order to fill in
all the letters, which unfortunately meant that in the rare
cases where
those characters *were* needed, we had to improvise.) The
hardest by far
were any east Asian languages. In that case, I gave up on
trying to display
any of the text in text form, and just converted it all to
bitmaps. Without
Unicode, trying to display Mandarin or Japanese or Korean
correctly as text
is pretty much impossible.

Problems with LPX-00245 (character set problem?)

Hi all,
I've got a problam with ORA-19202 and LPX-00245 (extra data after end of document) when querying my xmltype table. The table contains one large xml document. This xml document is valid, I've checked it against the corresponding XSD (using JDeveloper and also Notepad++, no validation errors).
I gues it has something to do with the encoding of the document. The original encoding is ISO-8859-1 (<?xml version="1.0" encoding="ISO-8859-1"?>). When I load the document to the database it is autoamtically changed to UTF-8 (<?xml version="1.0" encoding="UTF-8"?>) maybe because the character setting of my database is AL32UTF8.
I use the following statement to store my XML:
      insert into my_table
      values( my_seq_spp.nextval,
           r_get_files.file_name,
              xmltype(
              bfilename(p_directory, r_get_files.file_name) -- p_directory is the name of an oracle dircetory
              , nls_charset_id('WE8ISO8859P1')
Nevertheless the retrieved charset id 31 is ignored. Also if II use csid = 0, it doesn't work...
Any idea how to enforce using ISO-8859-1 instead UTF-8 as character set?
Best regards
Matthias

Hi Marco,
I don't think it has anything to do with encoding (client-side or not).
I'd be more inclined to say it's related to XML fragments manipulation.
@Matthias :
Does this work better :
select m.version
     , sp.Betriebsstelle
     , spa.Betriebsstellenfahrwege
from imp_spurplan t
   , xmltable('/XmlIssDaten'
       passing t.xml_document
       COLUMNS
         Version                  varchar2(6) path 'Version/Name'
       , Spurplanbetriebsstellen xmltype     path 'Spurplanbetriebsstellen'
     ) m
   , xmltable('/Spurplanbetriebsstellen/Spurplanbetriebsstelle'
       passing m.Spurplanbetriebsstellen
       COLUMNS
         Betriebsstellenfahrwege_xml xmltype      path 'Betriebsstellenfahrwege'
       , Betriebsstelle              varchar2(6) path 'Betriebsstelle'
     ) sp
   , xmltable('/Betriebsstellenfahrwege'
       passing sp.Betriebsstellenfahrwege_xml
       COLUMNS
         Betriebsstellenfahrwege xmltype path '.'
     ) spa
where sp.Betriebsstelle = 'NWH'

DB Creation(character set Problem)

HI,
I am in the process of creating new database from the full export dump file which i got from client. In the export logfile i can see,
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
I am creating the database manually at my site and planning to import that full export dumpfile from the client.
Do i need to create the DB with national character set WE8MSWIN1252 or can i also use character set as AL32UTF8
I want to se the correct character set so that my import doesn't fails because of charactor set problem.
Please help me.
Oracle Version At client site:9.2.0.1
OS :Windows
Oracle Version at my site:9.2.0.1
OS:LINUX
Thank You..

I can't answer your question because of several things.
The first is that all versions of 9i are currently in desupport and it has been years since I've seen one.
But if I was forced to work with 9i I certainly wouldn't do anything at all until I had patched to 9.2.0.8.
My recommendation would be, unless someone else can help you, to try it and see what happens.
Nothing ventured nothing gained.

Client-side greek character set problem

Similar Messages

Maybe you are looking for