Change db2 encoding to utf in String field

Hi Gurus,
We need to retrieve a field from db2 and send it to Siebel via Web Service in order to insert that data. We are having trouble with the encoding and we were wondering if there is any function to change encoding from db2 to utf so we can add it to our xml.
We believe that changing the encoding will insert it propperly in Siebel.
Thank you very much,
Alvaro

Hi Alvaro,
What is the technology of your staging area ?
In Oracle, you have a function to do that kind of change : http://docs.oracle.com/cd/B28359_01/server.111/b28286/functions027.htm .
If your staging is not Oracle, you can probably find something similar.
You can apply it to all your string mappings. If you always use that function for string data with these technology, you can also edit your KM and put the function in it.
Regards,
JeromeFr

Similar Messages

Change character encoding from UTF-8 to EUC-KR

We are receiving data in UTF-8 in the querystring from a partner formatted as:
%EA%B3%A0%EB%AF%BC%ED%95%98%EC%9E%90%21
Our site uses EUC-KR so using this text for search/display/etc is not possible. Does anyone know how we can convert this to the proper Korean EUC encoding so it can be displayed properly using JSP? Basically it should be:
%B0%ED%B9%CE%C7%CF%C0%DA%21
Thanks in advance.

I'm not sure where you are getting %xx encoded UTF-8.... Is it cuz you have it in a GET method form and that's what you are seeing in the browser's location bar? ...
Let's assume you have a form on a page, and the page's charset is set to UTF-8, and you want to generate a URL encoded string (%xx format, although URLEncoder will not encode ASCII chars that way...).
In the page processing the form, you need to do this:
request.setCharacterEncoding("UTF-8"); // makes bytes read as UTF-8 strings(assumes that the form page was properly set to the UTF-8 charset)
String fieldValue = request.getParameter("fieldName"); // get value
// the value is now a Unicode String in Java, generated from reading the bytes submitted from the form as UTF-8 encoded text...
String utf8EncString = URLEncoder.encode(fieldValue, "UTF-8");
// now utf8EncString is a URL encoded (%xx) string of UTF-8 values
String euckrEncString = URLEncoder.encode(fieldValue, "EUC-KR");
// now euckrEncString is a URL encoded (%xx) string of EUC-KR valuesWhat is probably screwing things up for you mostly is this:
euckrValue = new String(utf8Value.getBytes(), "EUC-KR");
What this does is takes the bytes of the string utf8Value (which is not really UTF-8... see below) in the local encoding (possibly Cp1252 (Windows) or ISO8895-1 (Linux), or EUC-KR if it's Korean Windows), and then reads them as if they were EUC-KR... which they aren't.
The key here is that Strings in Java are not of any encoding. They are pure Unicode values. Encodings only matter when converting to or from bytes. The strings stored in a file or sent over the net have to convert to bytes since that's what is stored/sent, just bytes. The encoding defines how the characters can be encoded into 1 or more bytes, and thus reconstructed.

Change XML Encoding to UTF-8

Dear SDNers:
Hello!
I face an issue of sending some XML documents from SAP to a non SAP System. This non SAP System stores XML documents in UTF-8 encoding format. When I create an XML document using CALL TRANSFORMATION in ABAP, the XML code generated has encoding as "ISO-...". Could anyone of you please guide me on how to have this changed to UTF-8?
In case of no solution, I would eventually have to pick the XML generated code and replace the "ISO-..." thing with "UTF-8" at runtime within the program. However, I feel that's not a quality method.
So, if anyone of you can suggest/opine of something better, it would be truly appreciated and rewarded.
Have a Nice Day!
Vivek.

Hello Uwe:
Currently we are on 6.20. But an upgrade is very near and I should expect these Classes to be handy then. I will explore them individually and post back. However, regarding my issue: the XML code generated by program is something like:
<?xml version="1.0" encoding="iso-8859-1"?>#<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0"><asx:values><SOURCE>42</SOURCE>
<?xml version="1.0" encoding="iso-8859-1"?>#<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0"><asx:values><SOURCE>42</SOURCE>.......
My need here is to replace the - encoding="iso-8859-1" with "UTF-8". So if you suggest proper methods to do so then it will be a good step for me.
Thanks for the relevant information anyways.
Have a nice day!

HTTP adapter - change encoding from UTF-8 to ISO-8859-1

Hi,
I am trying to change the encoding used by the HTTP sender adapter in a scenario.
However, when I enter ISO-8859-1 in the XML Code under XI Payload Manipulation on the comms channel it has no effect - the paylad still shows as UTF-8 in SXI_MONITOR.
Am I missing a step or entering the field incorrectly ??
Thanks
Colin.

Hi,
From help
Enhancing the Payload
Some external systems, for example, Web servers in marketplaces, can only process data if it is sent as an HTML form using HTTP.
A typical HTML form comprises named fields. When transferring a completed form to the server or a CGI program, the data must be transferred in such a way that the CGI script can recognize the fields that make up the form, and which data was entered in which field.
The plain HTTP adapter constructs this format using a prolog and an epilog. Therefore, there is a particular code method that separates form fields and their data from each other. This code method uses the following rules:
     Individual form elements, including their data, are separated from each other by the character &.
     The name and data of a form element are separated from each other by an equals sign (=).
     Blanks in the entered data (for example, in multiple words) are replaced by a plus sign (+).
    All characters with the (enhanced) ASCII values 128 to 255 (hexadecimal 80 to FF) are transcribed using a hexadecimal sequence, beginning with a percentage sign (%) followed by the hexadecimal value of the character (for example, the German umlaut ö in the character set ISO-8859-1 is transcribed as %F6).
   All characters that occur in these rules as control characters (&, +, =, and %) are also transcribed hexadecimally in the same way as high value ASCII characters
http://help.sap.com/saphelp_nw2004s/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
Regards
Chilla

Changing character encoding in ps xml pub. from utf-8 to iso-8859-1

I am using xml publisher to generate a report in a pdf format, now my problem is user has entered a comment which is not supported by utf but in iso-8559-1 its working fine,
I tried to change the encoding in people code, xml doc file ,schema and xliff file but still the old formatting exist,should I change somewhere else.
Following the error i get when trying to generate pdf:"Error generating report output: (235,2309)Error occurred during the process of generating the output file from template file, XML data file, and translation XLIFF file.".The parser is not able to recognise with utf-8 encoding.

I had the same issue. I created the xml through rowset and used string substitute function and its working.
Sample:
&inXMLDoc = CreateXmlDoc("");
&ret = &inXMLDoc.CopyRowset(&rsHdr);
&sXMLString = &inXMLDoc.GenFormattedXmlString();
&sXMLString = Substitute(&sXMLString, "<?xml version=""1.0""?>", "<?xml version=""1.0"" encoding=""ISO-8859-1""?>");
hope this helps!
GN.

Changing the xml encoding from UTF-8 to ISO-8859-1

Hi,
I have created an xml file in xMII transaction that I feed into a webservice as input. As of now, the data in the xml file is entirely english text (it would be changing to have European text soon). I gave the encoding as UTF-8.
I get an error on the webservice side(not xMII code) that the its not able to parse. The error is 'SaxParseException: Invalid 1 of 1-byte UTF-8 sequence). I know that an easy fix is if tI change the encoding to iso-8859-1.
But the reference document doesnot let me put anythign other than UTF-8. Even if I put <?xml version="1.0" encoding="iso-8859-1"?> as the first line, when I save it and open it back, i see <?xml version="1.0" encoding="UTF-8"?>
Is there any way to change the encoding? Or better still, anyway idea why this invalid sequence is coming from?
Thanks,
Ravi.

Hi Ravi,
We have encountered scenarios where we needed to take the <?xml version="1.0" encoding="UTF-8"?> out completely. As xMII was providing the Web Service, it needed a workaround.
In your case, it seems that you wish to pass it from xMII to an external Web Service provider. One option might be to pass the XML document as string.
Once you convert it to a string, it may escape all XMl characters (i.e. '<' into '<'). You could perform a string manipulation and remove the <?xml version="1.0" encoding="UTF-8"?> from the string. You may also need to play around with xmlDecode( string ) function in the Link Editor.
I would suggest that before you try this option, create a string variable will the contents, but without the <?xml version="1.0" encoding="UTF-8"?> and try assigning it to the input.
You may also wish to try a string variable that has <?xml version="1.0" encoding="iso-8859-1"?> as the first line. If this works, you should be able to perform string manipulations to convert your XML document into this modified string.
Cheers,
Jai.

Change encoding from utf-8 to ISO-8859-1

Hi
I have a problem with changeing the encoding of a text. The text is in utf-8, but when I try to send the text as mail with javax.mail and "text/html", Outlook doesn't want to display the right characters. Can somebody help me?

Hi,
String s = java.net.URLEncoder.encode(myText, newencoding)
http://galileo.spaceports.com/~ibidris/

Encoding from UTF-8 encoded String to Microsoft Project default encode

Hi Expert ...
I have a problem with encoding a String from UTF-8 String in order to write a MPX (Microsoft Project) file. I used UTF-8 on my Database encoding, and I want to write a MPX file using MPXJ library, but the result is (?) character. I think it's because I didn't encode yet to Shift JIS (a Microsoft Product default encoding). And after that I try to encode the String with Shift_JIS encoding, but the same result is appeared. I try to looking another way, but there is no result.
I hope some expert would help me to solve this problem.
Thank you,
Alfian B.

Totally wrong. A String doesn't have an encoding.
Now if you had an array of bytes, which were encoded using one charset, and you wanted to convert that to an array of bytes encoded using a second charset, you would use code like this:byte[] bytes = // the bytes encoded in UTF-8, let's say
String s = new String(bytes, "UTF-8"); // make that into a String
byte[] newbytes = s.getBytes("windows-31j"); // encode the String into windows-31j

How to change the Encoding type of a XML

Hi all,
I'm having a XML(generated at run time) with UTF-8 Encoding. If I'm going to parse it, getting an error saying "*Document root element is missing*".
If I change the encoding to ANSI, it parses without error.
How can I change the encoding type of a documnet ?
Any comment welcome.
Kaushalya

There's no such thing as the "encoding of a String". If you produced a String from a sequence of bytes using the wrong encoding, you may not be able to repair that problem by hacking about in your code. You're better off to produce the String using the correct encoding in the first place. Read this for more information about XML and encodings as you appear to be misunderstanding basic concepts:
[http://skew.org/xml/tutorial/]

Converting encoding of a Stream/String

Hi,
I am wondering if there is a way we can convert encoding of a Stream/String. For example, I have an Stream/String having iso-8859-1 encoding and I want to convert it to utf-8 encoding. Is there any way to do that conversion?
I figured out a way, but that is expensive to do. I build a JDOM document out of that InpuStream, and use Outputter to output the document into an OutputStream/String setting the encoding. The resultant OutputStream/String has the new encoding. Here is what I do for this:
Document doc = getDocumentFromStream(inputStream);
XMLOutputter outputter = new XMLOutputter();
//default encoding in JDOM is "UTF-8", if no encoding is specified, encoding
//is not set and thus defaults to "UTF-8"
if(StringUtils.isNotEmpty(encoding)){
     outputter.setEncoding(encoding);
outputter.setTextTrim(true);
outputter.output(doc, out);
I am wondering if there is any way we can do it without using JDOM thing, which is expensive.
I will appreciate any help on this issue.
Thanks in advance,
Pramodh.

Hi,
Thanks for the reply!
The reason, I want to convert the encoding of a Stream is: Our application supports UTF-8 very well. So, incoming data in non-UTF-8 encoding may most probably fail. There are characters like �, TM, copyright, etc which are supported by UTF and also ISO-8859-1. So, if I change the incoming ISO-8859-1 Stream into UTF-8, then the application will like resultant UTF-8 data.
I tried what u suuggested, but stil can't get it work. Following is what i did:
reader = new InputStreamReader(inStream, "ISO-8859-1");
writer = new OutputStreamWriter(outStream, "UTF-8");
int n;
while ((n = reader.read(c)) > 0) {
writer.write(c, 0, n);
Any other suggestions?
Thanks.

Errors when calling OCIStmtExecute w/ query encoded as UTF-16

Environment: Oracle 11.2.0.1.0 on Fedora Core 12, gcc 4.4.4. Server and client are running on the same machine.
I'm trying to use OCI to establish a UTF-16 encoded connection to a database where the character set is UTF-8:
SQL> SELECT parameter, value FROM nls_database_parameters WHERE parameter LIKE 'NLS%CHARACTERSET';
PARAMETER VALUE
NLS_CHARACTERSET AL32UTF8
NLS_NCHAR_CHARACTERSET AL16UTF16
int status = OCIEnvNlsCreate(&pEnv,
OCI_THREADED | OCI_OBJECT,
(dvoid *)0,
(dvoid * (*)(dvoid *, size_t))0,
(dvoid * (*)(dvoid *, dvoid *, size_t))0,
(void (*)(dvoid *, dvoid *))0,
(size_t)0,
(dvoid **)0,
OCI_UTF16ID,
OCI_UTF16ID);
/* Intermediate code omitted. See below for full code. */
table definition is: CREATE TABLE foo (val1 INTEGER, val2 INTEGER);
// Use the UnicodeString class from the ICU project (icu-project.org) to construct a UTF-16 string
UnicodeString stmt1_ins(UNICODE_STRING_SIMPLE("INSERT INTO foo (val1) VALUES (1);"));
status = OCIStmtPrepare(pStmt1,
pError,
(const text *) stmt1_ins.getTerminatedBuffer(), // returns NULL terminated buffer
(ub4) ((stmt1_ins.length() + 1) * 2), // NULL term plus 2 bytes per char
OCI_NTV_SYNTAX,
OCI_DEFAULT);
status = OCIStmtExecute(pSvcCtx,
pStmt1,
pError,
(ub4) 1,
(ub4)0,
(OCISnapshot*)NULL,
(OCISnapshot*)NULL,
OCI_DEFAULT);
The preparation succeeds, but OCIStmtExecute return ORA-00911, "invalid character".
I dumped stmt1_ins as hex and verified that it's UTF-16 encoded with a two byte NULL at the end. The characters are all correct, so the string is being correctly constructed by UnicodeString. I copied the literal query and pasted it into sqlplus via the terminal and was able to execute it successfully, so there are no typos in the query.
Does OCI have an endianness requirement with UTF-16? I would expect that to be transparent since they're on the same OS, or handled by the TCP/IP stack if they weren't.
If endianness isn't the problem, does anyone have an idea what might be? Full code below. FYI, UChar is defined as a 16 bit int.
// Declare output handles
OCIEnv* pEnv = NULL;
OCIError* pError = NULL;
OCISvcCtx* pSvcCtx = NULL;
OCIServer* pServer = NULL;
OCISession* pSession = NULL;
OCIStmt* pStmt1 = NULL;
// Create the environment with UTF charset and ncharset
int status = OCIEnvNlsCreate(&pEnv,
OCI_THREADED | OCI_OBJECT,
(dvoid *)0,
(dvoid * (*)(dvoid *, size_t))0,
(dvoid * (*)(dvoid *, dvoid *, size_t))0,
(void (*)(dvoid *, dvoid *))0,
(size_t)0,
(dvoid **)0,
OCI_UTF16ID,
OCI_UTF16ID);
// Init our error struct
status = OCIHandleAlloc((dvoid *) pEnv,
(dvoid **) &pError,
OCI_HTYPE_ERROR,
0,
(dvoid **)0);
// Init our context
status = OCIHandleAlloc((dvoid *) pEnv,
(dvoid **) &pSvcCtx,
OCI_HTYPE_SVCCTX,
0,
(dvoid **)0);
// Init our server
status = OCIHandleAlloc((dvoid *) pEnv,
(dvoid **) &pServer,
OCI_HTYPE_SERVER,
0,
(dvoid **)0);
// Attach to it
static const UChar db_name[] = {0x75, 0x6E, 0x69, 0x63, 0x6F, 0x64, 0x65, 0}; // "unicode"
sb4 db_name_len = 14;
status = OCIServerAttach(pServer,
pError,
reinterpret_cast<const OraText *>(db_name),
db_name_len,
OCI_DEFAULT);
// Set the server as an attribute of the context
OCIAttrSet((dvoid *) pSvcCtx,
OCI_HTYPE_SVCCTX,
(dvoid *) pServer,
0,
OCI_ATTR_SERVER,
pError);
// Init our session
status = OCIHandleAlloc((dvoid *) pEnv,
(dvoid **) &pSession,
OCI_HTYPE_SESSION,
0,
(dvoid **)0);
// Set the username
static const UChar username[] = {0x77, 0x68, 0x73, 0x65}; // "whse"
ub4 username_len = 8;
status = OCIAttrSet((dvoid *) pSession,
OCI_HTYPE_SESSION,
(dvoid *) username,
username_len,
OCI_ATTR_USERNAME,
pError);
// Set the password
static const UChar password[] = {0x77, 0x68, 0x73, 0x65}; // "whse"
ub4 password_len = 8;
status = OCIAttrSet((dvoid *) pSession,
OCI_HTYPE_SESSION,
(dvoid *) password,
password_len,
OCI_ATTR_PASSWORD,
pError);
// Begin the session
status = OCISessionBegin(pSvcCtx,
pError,
pSession,
OCI_CRED_RDBMS,
OCI_DEFAULT);
// Add the session to the context
status = OCIAttrSet((dvoid *) pSvcCtx,
(ub4) OCI_HTYPE_SVCCTX,
(dvoid *) pSession,
(ub4) 0,
(ub4) OCI_ATTR_SESSION,
pError);
// Allocate a statement handle
status = OCIHandleAlloc((dvoid *) pEnv,
(dvoid **) &pStmt1,
OCI_HTYPE_STMT,
0,
(dvoid **)0);
UnicodeString stmt1_ins(UNICODE_STRING_SIMPLE("INSERT INTO foo (val1) VALUES (1);"));
status = OCIStmtPrepare(pStmt1,
pError,
(const text *) stmt1_ins.getTerminatedBuffer(), // returns NULL terminated buffer
(ub4) ((stmt1_ins.length() + 1) * 2), / NULL term plus 2 bytes per char
OCI_NTV_SYNTAX,
OCI_DEFAULT);
status = OCIStmtExecute(pSvcCtx,
pStmt1,
pError,
(ub4) 1,
(ub4)0,
(OCISnapshot*)NULL,
(OCISnapshot*)NULL,
OCI_DEFAULT);

I ran across this thread, which suggested removing the semicolon from the end of the statement: Procedure calling..Error if Call interface changed from ODBC 3.5 . Now I'm getting ORA-24374, "define not done before fetch or execute and fetch". That makes a lot more sense, as I didn't define any output variables (figuring that they wouldn't be needed for a statement that doesn't return records).
Edited by: 854879 on Apr 27, 2011 1:22 PM

How do I supress the encoding of UTF-8 characters in a f:param element

Hello,
I have a keyboard displayed on my page, which won't work properly because of the used german characters.
I have an icon for every button embedded in a link, which adds the selected character to the searchstring.
For example adding an a works like this:
from keyboard.xhtml:
<s:link><f:param name="#{keyname}" value="#{keyword}a"/><h:graphicImage value="key_a.png"/></s:link>keyname and keyword are parameters submitted by the including form:
from myform.xhtml:
<ui:param name="keyword" value="#{end}"/>
<ui:param name="keyname" value="end"/>This works great as long as the character is a standard one, but on as soon as I have a german umlaut in the string, the umlaut gets encoded/escaped with every single character that i add to the searchstring:
The string makes it's way correctly to the keyboard-template, I can use a h:outputText to show it on the page and it doesn't get escaped.
So, how can I prevent the escaping of my characters in the f:params elements?
I really need to get this to work. so any hint or even solution would be fabulous.
Thanks in advance, Peter
PS: maybe my web server is doing something nasty, so it would be nice, if someone can check this code:
<s:link><f:param name="test" value="�"/>INIT</s:link> 
<s:link><f:param name="test" value="#{test}"/>REPEAT</s:link> 
INFO: <h:outputText value="#{test}" /> here is the same one with h:outputLink
<h:outputLink><f:param name="test" value="�"/>INIT</h:outputLink> 
<h:outputLink><f:param name="test" value="#{test}"/>REPEAT</h:outputLink> 
INFO: <h:outputText value="#{test}" /> EDIT: I found the solution, it was my beloved jboss application server, after adding a parameter to the server.xml, everything worked as expected:
use page settings:
<Connector port="8080" .....
useBodyEncodingForURI="true" ..../>hardcoded:
<Connector port="8080" .....
URIEncoding="UTF-8" ..../> Edited by: pete007 on Mar 12, 2008 1:47 PM

"Encoding" refers to the charset used to convert the Unicode data into bytes. But since you're writing to a String, you aren't converting the data to bytes and therefore UTF-16 is the appropriate encoding. It doesn't make sense to ask for your data to be encoded in UTF-8 when you aren't producing bytes.
You could read this tutorial about XML and Unicode and encodings for more information:
http://skew.org/xml/tutorial/

How to set File Encoding to UTF-8 On Save action in JDeveloper 11G R2?

Hello,
I am facing issue when I am modifying a File using JDeveloper 11G R2. JDeveloper is changing the Encoding of the File to System default Encoding (ANSI) instead of UTF-8. I have updated the Encoding to UTF-8 in "Tools | Preferences | Environment | Encoding" option and restarted the JDeveloper. I have also updated "Project Properties | Compiler | Character Encoding" option to UTF-8. None of them are working.
I am using below version of JDeveloper,
Oracle JDeveloper 11g Release 2 11.1.2.3.0
Studio Edition Version 11.1.2.3.0
Product Version: 11.1.2.3.39.62.76.1
I created a file in UTF-8 Encoding. I opened it, do some changes and Save it.
When I open the "Properties" tab using "Help | About" Menu, I can see that the Properties of JDeveloper are showing encoding as Cp1252. Is it related?
Properties
sun.jnu.encoding
Cp1252
file.encoding
Cp1252
Any idea how to make sure JDeveloper saves the File in UTF-8 always?
- Sujay

I have already done that. That is the first thing I did as mentioned in my Thread. I have also added below 2 options in jdev.conf and restarted JDeveloper, but that also did not work.
AddVMOption -Dfile.encoding=UTF-8
AddVMOption -Dsun.jnu.encoding=UTF-8
- Sujay

Change of Encoding in Sender JMS Adapter

Hi,
My scenario is like that:-
FTP->MQ Queue->JMS Queue->XI->R/3
From JMS Queue IDOC xml is coming in UTF-8 encoding to XI. In that IDOC xml certain special characters are there, say, some Latin or European character. But for the scenario XI->R/3, data are not getting posted to R/3. In XI side, it is not giving any error, but it is giving a flag (in QRFC Monitor) which is Error between two Character Sets.
I am unable to rectify this error. One solution I have guessed that is, it will be possible to resolve this issue if I can change the encoding in XI to ISO-8859-1. But I dont know how to change the encoding in Sender JMS Adapter in XI. Could you please help me to resolve this issue?
BR
Soumya B

Hi,
Check following:
1. In SXMB_MONI, what is the XML structure generated for inbound and outbound message. Check the encoding used in both. This could be checked by looking at the first line of XML generated. For UTF encoding, usually, the first line should look as follows:
<?xml version="1.0" encoding="UTF-8" ?>
2. If the encoding for both is different, try to figure out which encoding is used for Message Type in XI. For matching the encodings, you could change the XSD used for creating message type in XI. This way, the character encoding could be changed. And this solution should suffice if the problem has occured between XI to R3 scenario.
Also, for learning more about character encodings, you could visit following link:
http://www.cs.tut.fi/~jkorpela/chars.html
Hope it helps.
Bhavish.
Reward points if comments found useful:-)

A record selection problem with a string field when UNICODE database

We used report files made by Crystal Reports 9 which access string fields
(char / varchar2 type) of NON-UNICODE database tables.
Now, our new product needs to deal with UNICODE database, therefore,
we created another database schema changing table definition as below.
(The table name and column name are not changed.)
    char type -> nchar type
    varchar2 type -> nvarchar2 type
When we tried to access the above table, and output a report,
the SQL statement created from the report seemed to be wrong.
We confirmed the SQL statement using Oracle trace function.
    SELECT (abbr.) WHERE "XXXVIEW"."YYY"='123'.
We think the above '123' should be N'123' because UNICODE string
is stored in nchar / nvarchar2 type field.
Question:
How can we obtain the correct SQL statement in this case?
Is there any option setting?
FYI:
The environment are as follows.
    Oracle version: 11.2.0
    ODBC version: 11.2.0.1
    National character set: AL16UTF16

With further investigating, we found patterns that worked well.
Worked well patters:
    Oracle version: 11.2.0
    ODBC version: 11.2.0.1
    National character set: AL16UTF16
    Report file made by Crystal Reports 2011
    Crystal Reports XI
Not worked patters:
    Oracle version: 11.2.0 (same above)
    ODBC version: 11.2.0.1 (same above)
    National character set: AL16UTF16 (same above)
    Report file made by Crystal Reports 2011 (same above)
    Crystal Reports 2008 / 2011
We think this phenomenon is degraded behavior of Crystal Reports 2008 / 2011.
But we have to use the not worked patters.
Anything wrong with us? Pls help.
-Nobuhiko

Change db2 encoding to utf in String field

Similar Messages

Maybe you are looking for