Oracle 10g db character set issue

I have a database 10g with database character set western
european "WE8ISO8859P1" and we are receiving data from source
database with database character set as "UTF8" during data load
for one of the tables we receive the following error "ORA-29275:
partial multibyte character" I understand this might be due to
the fact western european character set is not a subset/superset
of UTF8 .Am i right ? What would be the way around this ?

It is certainly possible that the issue is that your database characterset is a subset of UTF8.
How are you getting the data? Are we talking about a flat file? A query over a database link? Something else?
Does the data you're getting contain characters that cannot be represented in the ISO-8859 1 character set? It is quite common to send UTF-8 encoded files even when the underlying data is representable in other 8-bit character sets (like ISO-8859 1).
What are you trying to do with the data? Are you trying to load it into a CHAR/ VARCHAR2 column? A CLOB? A BLOB? An NCHAR/ NVARCHAR2? Something else?
Justin

Similar Messages

Oracle to Mysql character set conversion problem!!! PLZ HELP

Hi Experts,
I have created a database link from Oracle 10g to Mysql 5.
I have installed Oracle Gateway 11g for this purpose.
When i retreive the data from sql plus the text is displayed as question marks.
Oracle 10g Database character set is WE8MSWIN1252
Mysql character set --->latin1
Character set of ODBC connector for mysql is latin7
Character set in the parameter file of HS folder is WE8MSWIN1252When i retrieve data from sql developer the text is fine(as i think it directly takes the character set of target) but
when i login from sqlplus i get question marks!
Appreciate your help,
regards

thank you for replying damorgan,
my previous two threads in the "heterogeneous Connectivity" forum were for different issues, one was to enquire as to how i could connect from oracle to mysql(which i have marked as answered), the other is for error when i get when i tried accessing data(which i am still facing on my office machine ).
I followed the steps from these two threads and was able to successfully connect to mysql on my personal PC at home, but faced some problem with text not displayed so i created this thread.
I had created another thread similar to this in the globalisation support as i was facing issue with the character sets in a heterogenous setup, so wasen't clear as to which forum would be suitable for this issue.
My apologies to everyone if this has offended you.

Oracle to Mysql character set conversion problem!!! PLZ IGNORE

Hi Experts,
I have created a database link from Oracle 10g to Mysql 5.
I have installed Oracle Gateway 11g for this purpose.
When i retreive the data from sql plus the text is displayed as question marks.
Oracle 10g Database character set is WE8MSWIN1252
Mysql character set --->latin1
Character set of ODBC connector for mysql is latin7
Character set in the parameter file of HS folder is WE8MSWIN1252When i retrieve data from sql developer the text is fine(as i think it directly takes the character set of target) but
when i login from sqlplus i get question marks!
I have another post in Heterogeneous Connectivity forum
Re: Oracle to Mysql character set conversion problem!!! PLZ HELP
Kindly update your comments there,
@@@@@@@@@@@@@@2
Appreciate your help,
regards
Edited by: user10243788 on Apr 21, 2010 3:25 AM

It is OK to post a globalization-related question in this forum in addition to the forum pertaining to the main technology. Not all experts follow all possible forums on OTN. Of course, you should cross-link the posts to let people merge the answers.
Regarding the problem itself, make sure that SQL*Plus has the right NLS_LANG setting in the environment. On Windows, in the Command Prompt:
C:\> set NLS_LANG=.WE8PC850
C:\> sqlplus ...On Unix:
$ setenv NLS_LANG .WE8ISO8859P1 (or NLS_LANG=.WE8ISO8859P1; export NLS_LANG)
$ sqlplus ...-- Sergiusz

Oracle XE and character set

Hello all,
I installed Oracle XE on RHEL 4 Linux and I found out that database character set is AL32UTF8. Does anyone know why oracle choose this character set? Maybe because of NLS_LANG env variable? Is it possible to change it to EE8ISO8859P2? Since database is still empty I can drop it and crate new database.
Do you think it is possible to set some env variables and do new oracle xe instalation including database with iso charset?
I want to have EE8ISO8859P2 charset because of doing exp/imp from another oracle iso db to oracle xe and it is much easier to do this without charset conversion.
Any help will be appreciated.
regards,
Miha

When you download XE, you have a choice - take the 'western european' character set download, or the 'unicode' download.
No other choices.
Join us over in the XE forum where people have discussed this and found workarounds. Info about finding that forum at Re: Oracle XE Installation failed

How to Import Database user in oracle which have character set AL32UTF8?

Hello All,
I want export one database user which have character set in WE8MSWIN1252 and I want to Import that Database user in oracle which have character set AL32UTF8 without changing character set.
is there any argument in import command??
thanks

There's no problem, export and import will take care of character set conversions, the only problem is AL32UTF8 is a variable size character set, if 'ñ' uses 1 byte in WE8MSWIN1252, in AL32UTF8 it will use 2 bytes, so it's recommended to pre-create the tables with "char" instead of "byte": create table xxx ( col1 varchar2(100 char), ... )
Enrique

9i Character Set Issues

Hi All,
I have a done a search through the forums on this topic, and revealed many answers to my question, however I need some more information to help me resolve an Issue.
Here goes...
Our company has a French/Canadian client that has installed 9i with the characterset of WE8DEC. The software that we wrote and provided them with does not support this characterset, and in turn they are seeing inverted question marks in place of some characters (Usually accented characters).
Basically, I want to understand the options that our client has in terms of possible solutions.
I understand that the characterset can only be altered in the database to a superset of the current characterset, so this affords us no option in this regard.
My suggestions so far, is to create a new database and transfer the data accross, however will this actually cure the issue? Will the data transfer accross and convert into it's correct character? or will it just transfer as an inverted "?".
Would an upgrade to 10g help them? Or would the issue remain?
Is there anything that can be done on the O/S or Client level to rectify this?
All help greatly appreciated!
Thanks.

user10498503 wrote:
Hi All,
I have a done a search through the forums on this topic, and revealed many answers to my question, however I need some more information to help me resolve an Issue.
Here goes...
Our company has a French/Canadian client that has installed 9i with the characterset of WE8DEC. The software that we wrote and provided them with does not support this characterset, and in turn they are seeing inverted question marks in place of some characters (Usually accented characters).
Basically, I want to understand the options that our client has in terms of possible solutions.
I understand that the characterset can only be altered in the database to a superset of the current characterset, so this affords us no option in this regard.
My suggestions so far, is to create a new database and transfer the data accross, however will this actually cure the issue? Will the data transfer accross and convert into it's correct character? or will it just transfer as an inverted "?".Your issue has a client side component (the NLS_LANG setting already mentioned here) and a potential server side component (corrupted/invalid data in the database), depending on what happened so far.
The client side issue could lead to corrupted data in the database, and there is no way of "correcting" this automatically, even if you move to a new database using a different character set on 9i, or upgrade to 10g.
If a client that writes into the database uses a wrong NLS_LANG setting, you're potentially ending up with corrupted data in the database.
If a client that reads data from the database uses a wrong NLS_LANG setting, you're potentially ending up with corrupted data on the front end application (the typical "?" question mark).
All this has nothing to do yet if your database character set is actually capable of storing the characters you attempt to store from the client side.
So I think you first need to determine if your database contains invalid data using the "CSSCAN" utility. For more information, check the manuals and MetaLink:
http://download.oracle.com/docs/cd/B10501_01/server.920/a96529/ch11.htm
Depending on your findings you'll find the possible actions on MetaLink.
Then you should determine if your client NLS_LANG is appropriate. There is a very good FAQ available here how to check the current setting and determine the correct setting:
http://www.oracle.com/technology/tech/globalization/htdocs/nls_lang%20faq.htm
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

Oracle to MySql character set problem

Dear Gurus,
My database is Oracle 11g R2 (11.2.0.1.0) on Sun Solaris 10. To get data from mysql database for reporting purpose, I used DG4ODBC and followed strictly the OMSC note "Detailed Overview of Connecting Oracle to MySQL Using DG4ODBC Database Link [ID 1320645.1]. Here are main configuration steps:
- Check DG4ODBC 32/64-bit
- Install and configure ODBC Driver Manager unixodbc-2.2.14
- Install and configure MyODBC 5.1.8
- Configure tnsnames.ora and listener.ora
- Create db links
Oracle character set is AL32UTF8
MySQL charactoer set is uft8
$ODBC_HOME/etc/odbc.ini
[ODBC Data Sources]
myodbc5 = MyODBC 5.1 Driver DSN
[myodbc5]
Driver = /opt/mysql/myodbc5/lib/libmyodbc5.so
Description = Connector/ODBC 5.1 Driver DSN
SERVER = <mysql server ip>
PORT = 3306
USER = <mysql_user>
PASSWORD = ****
DATABASE = <mysql db name>
OPTION = 0
TRACE = OFF
$ORACLE_HOME/hs/admin/initmyodbc5.ora
# HS init parameters
HS_FDS_CONNECT_INFO=myodbc5 # Data source name in odbc.ini
HS_FDS_TRACE_LEVEL=OFF
HS_FDS_SHAREABLE_NAME=/opt/unixodbc-2.2.14/lib/libodbc.so
HS_FDS_SUPPORT_STATISTICS=FALSE
HS_LANGUAGE=AMERICAN_AMERICA.WE8ISO8859P1
# ODBC env variables
set ODBCINI=$ODBC_HOME/etc/odbc.ini
My issue is I can query data from mysql database tables but the output is incorrect in character type columns (VARCHAR columns). It just shows the first character in such columns. I tried to read through some OMSC notes but none is useful. If you experienced on such issues, please share your idea / help me resolve it.
Thanks much in advance,
Hieu

S. Wolicki, Oracle wrote:
I have little experience with MySQL and ODBC Gateway, but this setting looks weird to me: HS_LANGUAGE=AMERICAN_AMERICA.WE8ISO8859P1. Why do you configure WE8ISO8859P1 when both databases are Unicode UTF-8. Shouldn't the setting be AMERICAN_AMERICA.AL32UTF8 instead?
-- SergiuszIf I set HS_LANGUAGE=AMERICAN_AMERICA.AL32UTF8 or without the HS_LANGUAGE setting, the following error will happen.
SQL> select count(*) from "nicenum_reserve"@ussd;
select count(*) from "nicenum_reserve"@ussd
ERROR at line 1:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
I followed the metalink note "Error Ora-28500 and Sqlstate I Issuing Selects From a Unicode Oracle RDBMS With Dg4odbc To Mysql or SQL*Server [ID 756186.1]" to resolve the above error. The note guides to set HS_LANGUAGE=AMERICAN_AMERICA.WE8ISO8859P1 and resolved the above error.
The following are the output from original database (MySql) and Oracle via SQLPLUS and TOAD.
On MySQL database (Sorry because of the output format)
SQL> select ID, source_msisdn, target_msisdn, comment from nicenum_reserve where ID=91;
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| ID | source_msisdn | target_msisdn | comment |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 91 | 841998444408 | 84996444188 | Close reservation becasue of swap activity |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
SQLRowCount returns 1
1 rows fetched
Via Sqlplus on Oracle server:
SQL> select "ID","source_msisdn","target_msisdn","comment" from "nicenum_reserve"@ussd where "ID"=91;
ID
source_msisdn
target_msisdn
comment
91
8 4 1 9 9 8 4 4 4 4 0 8
8 4 9 9 6 4 4 4 1 8 8
C l o s e r e s e r v a t i o n b e c a s u e o f s w a p a c t i v i
t y
Via TOAD connected to Oracle server:
ID source_msisdn target_msisdn comment
91 8 8 C
It's likely this issue related to character set settings but I don't know how to set it properly.
Brgds,
Hieu

Foreign character set issue

Hi
This might sound a bit silly, but stay with me.
There's a database that decidedly supports UTF 8. I checked using this query
select * from nls_database_parameters where parameter like '%CHARACTERSET'
And got this result
NLS_CHARACTERSET UTF8
NLS_NCHAR_CHARACTERSET AL16UTF16
It's Oracle 10g.
In a particular table, some text is stored in multiple languages. There are seven languages (English, Mandarin, Japanese, German...). Every language has 2-3 rows to itself. There's a column where I have to get rid of the trailing few characters, the number of which depends on the content of the string.
But I cannot see any of the Eastern languages in TOAD. The column is in VARCHAR2.
My problem is twofold.
1. What functions do I use to ensure that only the last few bytes are truncated, and there's no data loss (which many websites gravely warn of when dealing with foreign language data) ?
2. How can I see this foreign language text in TOAD/SQLPlus?
(Yes, I'm kind of new to the whole multiple-language-game. Please let me know if I've left out any important detail!)

Do you have metalink access?
If so, please see the notes below, there's a lot of good information in them:
158577.1 - NLS_LANG explained
260893.1 - Unicode Character Sets in the Database
788156.1 - UTF8 implications
With any character set situation there are at least two and a bit sides to the equation.
First is whether you are storing the correct data.
You're best using the DUMP function to inspect the stored data, e.g.
SELECT DUMP(<column_name>) FROM <table_name> WHERE ....This function may help you with your truncation of the last few bytes - not sure why you need to do this?
The "second and a bit" bit is having the correct client settings - NLS_LANG - and using a client which supports the characters required.
SQL*Plus has it's limitations here. Toad I don't know well enough but it should support full UTF8 characters.
SQL*Developer and iSQL*Plus both should support the full UTF8 - I tend to use the former, particularly for UTF8.

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 10g RAC+ASM - Storage Issue

I’ve an issue related to Oracle 10g RAC.
I’ve 2 node cluster each being Dell 2850 Server with RHEL 4.0
I’ve EMC CX300 SAN storage with following partitions
/orasoft     10 Gb          OCFS2 File system
/oracrs          2 Gb          OCFS2 File system
/orabackup      100 Gb          OCFS2 File system
The datafiles are on ASM which is not directly visible in OS.
I’ve common Oracle Home installed in /orasoft/db_1 which is shared by both nodes in cluster.
I’ve faced an issue recently related to EMC storage.
The /orasoft partition displays 1.4 Gb space available using df command.
With both nodes sharing the common Oracle Home (/orasoft/db_1), when ever I try to touch a file I get an error as No Space left on device. I’m unable to start any service with the same reason.
Is this setup correct ??
Can anyone help me with this storage issue ??

Hi,
If you create a new diskgroup you may be to add the same diskgroup to parameter file or spfile and which will be needing down time.
sugestion: Instead of creating new diskgroup you should to add disk to existing group.if you add asm disk to existing group your all problem will be solved and Oracle itself will be managing all.And than i am sure no need to add entry in the parameter or spfile like +db_create_file_dest=.....
regards,
Sher khan

German character set issues on Solaris

Hi,
I am facing an issue with German character settings with my Java application on a solaris box.
When I run my application on the box, and I pass an input file with German special characters they get converted as ?. However, other normal English characters are formed properly.
When I run the same application on another Solaris box with a different JRE, the German characters are formed properly.
I understand that there is a difference in the archiecture between the 2 boxes ie.e
64 bit SPARC machine v/s 32 bit x86 machine
the JRE
1.4.2_03(64bit) v/s 1.4.1_01
I am tryinbg to evaludate further differences between the 2 environments to pinpoint the issue, and get this resolved on the 1st box.
Can anyone provide me any inputs?
Lavin

When you read the file, please point out what character set using. For example:
FileInputStream fstream = new FileInputStream(url.getFile());
DataInputStream in = new DataInputStream(fstream);
BufferedReader br = new BufferedReader(new InputStreamReader(in, Charset.forName("ISO-8859-1")));
br.readLine();
This link possibly can help you.
http://www.velocityreviews.com/forums/t126128-jdk-14-character-set-change.html

Trouble with MSSQL Reporting Services and Oracle: PLS-00553: character set

First off, Oracle version is 8.1.7.4.0. SQL is 64bit 2005 on Windows 2003 with all the latest patches. We’re using the Oracle 10.2 client on the SQL box.
A few months ago queries against Oracle stopped working on our MSSQL reporting services server - after a service pack on this same system.
I ended up having to grant permissions on Oracle directories to eliminate the first error and then renamed the NLS_LANG registry entry (effectively deleting it) to get rid of the second error.
The second error was: ORA-12705: Cannot access NLS data files or invalid environment specified. I don’t have docs on the first error, but it was a reference to a file access problem. Looking at this error again makes me think that I still have some file access problems.
The old value for the NLS_LANG registry key was: AMERICAN_AMERICA.WE8MSWIN1252
Everything has been working fine since then.
Now we are moving some new reports into production which use Oracle stored procedures and they are getting this error:
--- End of inner exception stack trace ---
w3wp!processing!8!7/27/2009-09:26:09:: e ERROR: An exception has occurred in data source 'CSUD3_RPTAPL'. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'MYDATASET'. ---> System.Data.OracleClient.OracleException: ORA-06550: line 1, column 57:
PLS-00553: character set name is not recognized
ORA-06550: line 0, column 0:
PL/SQL: Compilation unit analysis terminated
I've created a test package as below, which has also gotten the same error.
create or replace
PACKAGE BODY SQLTEST AS
PROCEDURE OPEN_CURSOR (ResultCursor OUT T_CURSOR,
SQLTESTIN IN VARCHAR
AS
l_query varchar2(3000);
BEGIN
l_query := 'Hi there';
open ResultCursor for select l_query "field1" from dual;
END OPEN_CURSOR;
END SQLTEST;
I tried setting the NLS_Lang value back to its old value, but it did not fix this problem – and made all the regular oracle queries break again.
From what I've read, the client should be using the database default if the charset is not specified on the client.
Can anyone advise on what the problem might be?
Thanks!
Sam Greene

With all due respects I can not think of a worse reporting tool than MS Reporting Services.
Give serious consideration to getting a real report writing tool from Oracle or SAP (Business Objects / Crystal).
Reporting Services is one nightmare after another.

Oracle 10g Installation ./runInstaller Issue

I have RHEL 5 64 bit OS installed Oracle 10g Release 10.2.0.1.0
at end of oracle installation there is one error.
ERROR
OUI-10058: The OUI Inventory on this system does not exits or is not writable .
1-The /opt/oracle/oraInventory/orainstRoot.sh script was not executed with root privileges,
or an error occurred during execution;
2-You are not a member of the specified installer gourp
So i run
cd /u01/app/oracle/oraInventory/
./orainstRoot.sh
Changing permissions of /u01/app/oracle/oraInventory to 770.
Changing groupname of /u01/app/oracle/oraInventory to oinstall.
The execution of the script is complete
And i am running version upgrade package p6810189_10204_Linux-x86-64.
cd /u01/Disk1/
./runInstaller
Starting Oracle Universal Installer...
Checking installer requirements...
Checking operating system version: must be redhat-3, SuSE-9, SuSE-10, redhat-4, redhat-5, UnitedLinux-1.0, asianux-1, asianux-2 or asianux-3
Failed <<<<
Exiting Oracle Universal Installer, log for this session can be found at /u01/app/oracle/tmp/OraInstall2010-07-28_12-49-50PM/installActions2010-07-28_12-49-50PM.log
but it fail to install :)
Please export guide me to solve the issue.
Thanks for all your expertise ;o)
Edited by: Oracle DBA P on Jul 28, 2010 5:16 AM

thanks buddy
./runInstaller -ignoreSysPrereqs
Starting Oracle Universal Installer...
Checking installer requirements...
Checking operating system version: must be redhat-3, SuSE-9, SuSE-10, redhat-4, redhat-5, UnitedLinux-1.0, asianux-1, asianux-2 or asianux-3
Failed <<<<
Ignoring required pre-requisite failures. Continuing...Preparing to launch Oracle Universal Installer from /u01/app/oracle/tmp/OraInstall2010-07-28_01-40-35PM. Please wait ...
installer started and it installing now but still it through Failed <<<< error
Edited by: Oracle DBA P on Jul 28, 2010 5:45 AM
Edited by: Oracle DBA P on Jul 28, 2010 5:45 AM

Oracle 11gr2 - change character set from utf-8 to weiso8859p15

Hi guys,
I've a new and empty oracle 11gr2 database for my test environment, during the installation i've choosed the UTF-8 character's set but now i've see that in the production environment there is the WEISO8859 character's set.
I have a dump of the prod. env. (done with Exp function).
How can I change the character set from utf-8 to weiso8859p15 ?
I found this procedure:
SHUTDOWN IMMEDIATE or a SHUTDOWN NORMAL;
STARTUP MOUNT;
ALTER SYSTEM ENABLE RESTRICTED SESSION;
ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
ALTER SYSTEM SET AQ_TM_PROCESSES=0;
ALTER DATABASE OPEN;
ALTER DATABASE NATIONAL CHARACTER SET new_character_set;
SHUTDOWN IMMEDIATE; -- or SHUTDOWN NORMAL;
STARTUP;
is it correct ?
Thx.
Kind Regards,
Stefano.

evil.stefano wrote:
Hi guys,
I've a new and empty oracle 11gr2 database for my test environment, during the installation i've choosed the UTF-8 character's set but now i've see that in the production environment there is the WEISO8859 character's set.
I have a dump of the prod. env. (done with Exp function).
How can I change the character set from utf-8 to weiso8859p15 ?
I found this procedure:
SHUTDOWN IMMEDIATE or a SHUTDOWN NORMAL;
STARTUP MOUNT;
ALTER SYSTEM ENABLE RESTRICTED SESSION;
ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
ALTER SYSTEM SET AQ_TM_PROCESSES=0;
ALTER DATABASE OPEN;
ALTER DATABASE NATIONAL CHARACTER SET new_character_set;
SHUTDOWN IMMEDIATE; -- or SHUTDOWN NORMAL;
STARTUP;
is it correct ?NO
leave the character set alone.
UTF-8 will not be a problem.

PL/SQL XML generation: Character set issues

Hi,
I am using the PL/SQL DOM (wrappers to the Java DOM), to generate XML from bits of database information. (On Oracle 8i).
The output XML must be in UTF-8, and the database character set must be anything I want it to be. So I call
setCharset(doc, 'UTF8')
at the beginning, and I call
writeToClob(doc, xmllob, 'UTF8')
at the end, just to cover all eventualities.
However, any character outside ASCII gets
replaced with the character string "\xBF\xBF", which is rather tedious.
If, instead, we go via
writeToBuffer(doc, xmlbuf, 'UTF8')
and then dump the buffer contents into a clob, the UTF8 encoding is preserved, and everything works.
(This latter method is not good enough for my needs; I need more than 32K of data...)
So I was wondering if any kind soul could tell me what I am doing wrong.
Thanks,
<< Mike Alexander >>
null

I have the same problem. Is there any solution found?
only xslprocessor.valueOf returns values of xml document not loosing special symbols.

Oracle 10g db character set issue

Similar Messages

Maybe you are looking for