Regd:UTF 8 Unicode Version

Hi Gurus,
How to find UTF-8 Version In Database? I need whether it is using version 1.0 or 2.0 like that.
Regards,
Simma...

jeneesh wrote:
Efficientoracle wrote:
hi,
s i need unicode version. How to find it in our database. Am using 11.2.0.3.
Regards,
Simma..It cannot change across databases.. As the documentation says, for 11g, it uses unicode version 3.0Oracle Database 11g, Release 1: 5.0
Cheers,
Manik.

Similar Messages

Windows API ANSI version and UNICODE version

Windows API have two version:
ANSI version and UNICODE.
I want to display chinese, so i use the UNICODE version. but i find it's some mistake.
and later, i change to ANSI version, it's correct.
why the ANSI version can display chinese, and UNICODE can't.
i use the api function
FindWindowA
GetWindowTextA
who can tell me?

I understand Vista is a 32 bit.
IE 8 is what I have but I would consider IE 9 if that would be necessary.
Just a bit more update. I just tried to download Adobe FP 10 again with the following results, again:
The Adobe Download Manager windows shows:
FP 10.3 Status as 100% "Installation Pending".
FP 10.2 Status as 100% " Instatlling Application"
and that will go one forever but never really actually installs anything and just keeps cycling through the "Add to Download" e.g. "Fanbase", "Times Reader"
and "Adobe Air" (none of which I want added to the download), and the download and installation shows as 100%.
Go figure!

Unicode version 3.2

Does Java support Unicode version 3.2? How to specify the unicode value of 5 digit long e.g. "\u29C73"? I have tried this but Java interpret is as "\u29C7" + "3".
Or what version of unicode Java supports?
Thanks!

See: http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Character.html
Java 1.5 supports Unicode Standard 4.0 through the Charactor class.

My ERP 2005 - Is it only UNICODE version ???

I heard that my ERP 2005 which is based on successor version of NW 04 and which is scheduled to release in Oct 2005 only supports Unicode installations ? I can't find any information on this on SAP website or SAP service market place to validate ? Only thing I know is that SAP will no longer support MDMP installations with mySAP ERP 2005.
Can someone from SAP answer this for us. If we have French, Spanish and English language used which are code page 1100, are we force to convert to unicode if we have to upgrade to mySAP ERP 2005.
Thanks,
Raja

Hi Max,
The growth varies based on the DB used. Oracle is based on UTF-8 so it has a variable length for fields. As the field length is variable the size of the DB depends on the characters stored.
Will you have a large numbers of data using exotic characters (like master data) or will you have minimal use of exotic characters and use more ASCII 7 characters? This has a different impact on DB size.
This is different for each customer so it hard to give an exact answer. The numbers you see from SAP about DB size are conservative estimates.
With regard to the size of your DB directly after the conversion.
The conversion process does a full DB reorg so the actual size maybe reduced. If you have a fully reorged DB before the conversion, then expect the DB growth mentioned in the presentations you have mentioned.
With regard to runtime of the conversion, there are a number of options available to you to speed the conversion. They are wholly dependent on your downtime needs and the hardware you have available. The optimization options are all based on optimizing data I/O and processing speed.
For the latest info, check out the TechEd 2005 presentations on the SAP service marketplace (http://service.sap.com/unicode@SAP).
I hope this helps,
Mike.

UNICODE version of BDB API

Hi
I wonder why Oracle does not give UINICODE version of BDB APIs.
Regards
Nisam

How do you mean? The BDB API is not aware of the encoding of the data it is storing. It returns exactly what you put in. The only times you need to worry about text encodings are with older code that assumes the most significant bit of each byte is unused for text (rare these days) or with code that does locale-aware text processing, such as collation or letter ranges (in regexps) and the like. BDB does none of that.
So as long as you know what text encoding you put in (UTF-8, -16) you shouldn't have to worry about Unicode. You can safely assume that BDB will not mangle your text. However, if you expect the btree access method to sort your Unicode keys (or duplicate values) according to a language-specific collation, then you'll need to write your own comparison function based on one of the collation algorithms available on unicode.org.
Hope this helps!
Dan

Poratl Unicode version

Hi All,
Is there any way to check whether portal version i have is unicode or Non-unicode.
Poratl version : Ep6.0 with support-stack 18.
How to convert Ep 6.0 to unicode enabled.
Any suggestions plz..
Thanks in advance.
Subhash.G

Just an idea, do a view source on a portal page anywhere. Do a search in the HTML file for "charset=utf-8" . If you find that as a meta tag, then you know the portal is producing pages that are trying to tell the browser to interprete the page as unicode.
I thought SAP were trying to make all installations unicode going forward? Did they even release a non-unicode SP18 ?

UTF-8 Unicode in JEditorPane doesn't work

I do hope this is the correct forum for this question so that some forum nazi doesn't give me grief...here goes.
I have a JEditorPane with the contentType set to "text/html; charset=UTF-8"
I do a .setText method with this text:
<HTML><body>
Followed by some text extracted from an RSS feed (just the contents of the <description> tag)
and then </body></html> to finish it off.
It displays fine apart from a unicode character, it looks like one of those 'fancy' apostrophes so that in the word "We've" the appostrophe shows as an accented a and two squares as shown in this screenshot : Screenshot
So does that mean that 'Arial Unicode MS' cannot display Unicode as the name would suggest, or am I doing something else wrong?

When you specify the charset in the contentType setting, you're telling the JEditorPane how to convert raw bytes that it reads from a URL into a Java string. That's assuming you use one of the setPage() methods to populate the component--but you're using setText(), which takes a String. That means the text was corrupted before you put it in the JEditorPane; you need to look at how it's getting brought in from the RSS feed. It's obviously encoded as UTF-8, but being decoded as if it were a single-byte encoding like ISO-8859-1 or windows-1252 (the default for English-locale Windows systems).

Convert UTF-8 (Unicode) Hex to Hex Byte Sequence while reading file

Hi all,
When java reads a utf-8 character, it does so in hex e.g \x12AB format. How can we read the utf-8 chaacter as a corresponding byte stream (e.g \x0905 is hex for some hindi character (an Indic language) and it's corresponding byte sequence is \xE0\x45\x96).
can the method to read UTF-8 character byte sequence be used to read any other (other than Utf 8, say some proprietary font) character set's byte sequence?

First, there's no such thing as a "UTF-8 character". UTF-8 is a character encoding that can be used to encode any character in the Unicode database.
If you want to read the raw bytes, use an InputStream. If you want to read text that's encoded as UTF-8, wrap the InputStream in an InputStreamReader and specify UTF-8 as the encoding. If the text is in some other encoding, specify that instead of UTF-8 when you construct the InputStreamReader. import java.io.*;
public class Test
// DEVANAGARI LETTER A (अ) in UTF-8 encoding (U+0905)
static final byte[] source = { (byte)0xE0, (byte)0xA4, (byte)0x85 };
public static void main(String[] args) throws Exception
    // print raw bytes
    InputStream is = new ByteArrayInputStream(source);
    int read = -1;
    while ((read = is.read()) != -1)
      System.out.printf("0x%02X ", read);
    System.out.println();
    is.reset();
    // print character as Unicode escape
    Reader r = new InputStreamReader(is, "UTF-8");
    while ((read = r.read()) != -1)
      System.out.printf("\\u%04X ", read);
    System.out.println();
    r.close();
} Does that answer your question?

UTF-8 Unicode output

Hi all,
I'm at the end of my resources (and those are very limited when speaking of character sets).
Specifically, I'm having trouble with unicode character 2628 (http://www.fileformat.info/info/unicode/char/2628/index.htm)
The SOAPMessage response I'm receiving is fine.
SOAPMessage response = getResponse();
response.writeTo(System.out); // Works fine. Outputs it correctlyWhere I'm having trouble is reading the data from the attachment itself. I've tried a few hundred different things to no avail.
Iterator attItr = response.getAttachments();
AttachmentPart attPart = (AttachmentPart)attItr.next();
String content = new String(attPart.getRawContentBytes(), "UTF-8"); // Doesn't work. Giberish.
String contentTo = attPart.getContent(); // Doesn't work either. Giberish as wellI've tried a few other things ... but I'm really stuck.
Any help would be greatly appreciated.
Thanks.

You may be able to find a text editor that can do the conversion. Alternatively, I have converted from one encoding to the another programmatically using Java as well.
Tim Tow
Applied OLAP, Inc

XDK support for UTF-16 Unicode

Hi,
Does the Oracle Java XDK, specifically the XSQL servlet and api,
support UTF16-Unicode.
Presumably, .xsql files have to be stored, read and queries
executed in a Unicode compliant format for this to work. Is this
possible currently???
Thanks,
- Manish

If you are using XDK 9.0.1 or later, and you are using JDK 1.3,
this combination supports UTF-16. XSQL inherits the support
for "free" in this case.

Conversion utf-16 unicode - ASCII

Hello,
i read a utf-16 file. The read text is diplayed like this string:
yp<#?#x#m#l# #v#e#r#s#i#o#n#=#"#1#.#0#"
How can I convert the text? I haven't found functions to do that.

Here's a QDAC (Quick & Dirty ABAP code) to convert UTF-16 file on app server to sap default codepage file.
Tested on a non-unicode 640 system.
data: gt_line type string occurs 0 with header line,
 gv_bin type xstring,
 conv_obj type ref to cl_abap_conv_in_ce.
parameters: in_file type rlgrap-filename,
 out_file type rlgrap-filename.
start-of-selection.
check not in_file is initial.
open dataset in_file for input in binary mode.
do.
 read dataset in_file into gv_bin.
 if sy-subrc ne 0.
 close dataset in_file.
 exit.
 endif.
 if sy-index eq 1.
 perform create_conv_obj.
 endif.
 try.
 call method conv_obj->convert
 exporting
 input = gv_bin
 n = -1
 importing
 data = gt_line.
 catch cx_sy_conversion_codepage .
 catch cx_sy_codepage_converter_init .
 catch cx_parameter_invalid_type .
 endtry.
 append gt_line.
enddo.
check not out_file is initial.
open dataset out_file for output in binary mode.
loop at gt_line.
 transfer gt_line to out_file.
endloop.
close dataset out_file.
*& Form create_conv_obj
form create_conv_obj.
data: lv_bom(2) type x,
 lv_encoding type abap_encod,
 lv_endian type abap_endia.
lv_bom = gv_bin.
if lv_bom eq 'FFFE'.
 lv_encoding = '4103'. "code page for UTF-16LE
 lv_endian = 'L'.
 shift gv_bin left by 2 places in byte mode.
elseif lv_bom eq 'FEFF'.
 lv_encoding = '4102'. "code page for UTF-16BE
 lv_endian = 'B'.
 shift gv_bin left by 2 places in byte mode.
else.
 message 'Byte order mark not found at the begining of the file'
 type 'E'.
endif.
try.
 call method cl_abap_conv_in_ce=>create
 exporting
 encoding = lv_encoding
 endian = lv_endian
 replacement = '#'
 receiving
 conv = conv_obj.
 catch cx_parameter_invalid_range .
 catch cx_sy_codepage_converter_init .
endtry.
endform. "create_conv_obj
Regards
Sridhar

BW Unicode & Versioning

Hi,
We are in the process of starting our Global BW project. Initially we thought of using 3.1 Unicode system by upgrading our 3.1 Non-unicode system. But I believe SAP are not going to support 3.1 Unicode from 2006 and asking all customer to go for the new installation of BW 3.5 or higher.
Now about some points which I would like to have help,
1. Our go-live time will be sometimes around 2007. In that case, what is your recommendations for the BW version ? Should we go for 3.5 or something higher. Like if we go live on 2007 March and then start our upgradation project to 4.0 - really we should then implement 4.0 now.
2. We are using R/3 4.7 Unicode as our source system. So if we go for BW 3.5 Unicode or higher version, do we need to tweak our R/3 source system a lot ? Like we are not willing to change a lot in R/3. Now we are using the R/3 system with our present Non-unicode BW 3.1 system.
3. Are there any different system as 3.5 Unicode and 3.5 Non-unicode or all the BW 3.5 is Unicode system.
Thanks for your time and appreciate your help and guidance.
Good Day !
Regards,
Arpan

Hi Arpan,
I'll try an address all the questions you entered!
1. SAP BW on unicode is only available as of SAP NetWeaver '04 (SAP BW 3.5). SAP NetWeaver '04 (SAP BW 3.5) is supported until March 2013. As SAP NetWeaver '04 is the latest release and it is available now for customers. I would suggest that you start with this release.
Note: SAP BW 3.1 Content on unicode is not available. You can't order SAP BW 3.1 Content on unicode.
2. I would recommend that you start with SAP BW on unicode.
- If you went with a non-unicode SAP BW there is only minimal impact (non on SAP R/3 Enterprise). The minor impact is ensuring you only extract language texts that you support on your SAP BW system.
It would be simplier to have a unicode SAP BW system to start with because I expect at some time in the future someone will want BW developments to cover language in mulitple code-page.
3. The major difference between a unicode and a non-unicode is that you hvae a fully unicode database and the underlying SAP Web AS kernel can communicate with the unicode database.
- From a SAP BW functionality perspective they are the same.
I hope this helps,
Mike.

When i try to run Firefox i get a error message "cannot run unicode version of ATL80.dll install ANSI" this only happens with firefox,internet explorer, Opera and everything else run fine, have re-installed firefox but still the same. run fine.

unicode ATL80.dll error message when trying to run firefox
== This happened ==
Every time Firefox opened
== User Agent ==
Opera/9.80 (Windows NT 5.1; U; en) Presto/2.6.30 Version/10.60

I had this problem as well. I found that somehow the firefox.exe file had been set to run in compatibility mode for Windows 95.
To check this on your system Browse to the firefox folder (C:\Program Files\Mozilla Firefox\) and right click on the file "firefox.exe".
Select "Properties" and then the "Compatibility" tab. Make sure the option "Run this program in compatibility mode for" is UNCHECKED.
Then try running Firefox as normal. Worked for me.
Best of Luck.

Error in installing SAP Web AS ABAP (Unicode Version)

I have SAP Web AS Java in my machine already, but in order to install XI, I need to install also ABAP unicode. During the installation, I got the following error. I can't interpret it what it is or what I have done wrong. Can anybody give me a hand?
Here is the error message:
ERROR 2005-12-16 01:51:17
MOS-01082 File system node E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE with type NODE does not exist.
ERROR 2005-12-16 01:51:17
MOS-01105 Processing of one or more file system node operations of table   Content of table: t_SAPComponent_Filesystem_Action_SHARED with condition WHERE WapsSystemName='J2E' AND WapsInstanceName='DVEBMGS00' AND WapsInstanceHost='vm-w3k-pck' AND OpMode NOT IN('CHECKFREESPACE', 'CHECKIF') Row[0]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/prfclog" FollowLinks="TRUE" NodeName="C:\usr\sap/prfclog" NodeType="DIRECTORY" OpMode="CREATE"   Row[1]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E" NodeType="DIRECTORY" OpMode="CREATE"   Row[2]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00" NodeType="DIRECTORY" OpMode="CREATE"   Row[3]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/data" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/data" NodeType="DIRECTORY" OpMode="CREATE"   Row[4]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/data/cache" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/data/cache" NodeType="DIRECTORY" OpMode="CREATE"   Row[5]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/exe" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/exe" NodeType="DIRECTORY" OpMode="CREATE"   Row[6]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/log" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/log" NodeType="DIRECTORY" OpMode="CREATE"   Row[7]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/sec" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/sec" NodeType="DIRECTORY" OpMode="CREATE"   Row[8]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/work" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/work" NodeType="DIRECTORY" OpMode="CREATE"   Row[9]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS" NodeType="DIRECTORY" OpMode="CREATE"   Row[10]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/exe" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/exe" NodeType="DIRECTORY" OpMode="CREATE"   Row[11]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/exe/opt" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/exe/opt" NodeType="DIRECTORY" OpMode="CREATE"   Row[12]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/exe/dbg" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/exe/dbg" NodeType="DIRECTORY" OpMode="CREATE"   Row[13]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/exe/run" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/exe/run" NodeType="DIRECTORY" OpMode="CREATE"   Row[14]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/gen" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/gen" NodeType="DIRECTORY" OpMode="CREATE"   Row[15]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/gen/dbg" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/gen/dbg" NodeType="DIRECTORY" OpMode="CREATE"   Row[16]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/gen/opt" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/gen/opt" NodeType="DIRECTORY" OpMode="CREATE"   Row[17]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/global" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/global" NodeType="DIRECTORY" OpMode="CREATE"   Row[18]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/profile" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/profile" NodeType="DIRECTORY" OpMode="CREATE"   Row[19]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/src" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/src" NodeType="DIRECTORY" OpMode="CREATE"   Row[20]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/tmp" FollowLinks="TRUE" NodeName="C:\usr\sap/tmp" NodeType="DIRECTORY" OpMode="CREATE"   Row[21]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans" FollowLinks="TRUE" NodeName="C:\usr\sap\trans" NodeType="DIRECTORY" OpMode="CREATE"   Row[22]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/tmp" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/tmp" NodeType="DIRECTORY" OpMode="CREATE"   Row[23]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS" NodeType="DIRECTORY" OpMode="CREATE"   Row[24]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/in" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/in" NodeType="DIRECTORY" OpMode="CREATE"   Row[25]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/out" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/out" NodeType="DIRECTORY" OpMode="CREATE"   Row[26]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/log" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/log" NodeType="DIRECTORY" OpMode="CREATE"   Row[27]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/bin" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/bin" NodeType="DIRECTORY" OpMode="CREATE"   Row[28]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/buffer" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/buffer" NodeType="DIRECTORY" OpMode="CREATE"   Row[29]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/cofiles" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/cofiles" NodeType="DIRECTORY" OpMode="CREATE"   Row[30]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/data" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/data" NodeType="DIRECTORY" OpMode="CREATE"   Row[31]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/etc" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/etc" NodeType="DIRECTORY" OpMode="CREATE"   Row[32]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/log" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/log" NodeType="DIRECTORY" OpMode="CREATE"   Row[33]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/sapnames" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/sapnames" NodeType="DIRECTORY" OpMode="CREATE"   Row[34]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="WAPS_COPY_E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE_C:\usr\sap\J2E\SYS\exe\run\..\UNINSTSAP.EXE" NodeName="E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE" NodeTarget="C:\usr\sap\J2E\SYS\exe\run\..\UNINSTSAP.EXE" OpMode="COPY" failed.

Still have the same error message.
When I look at the log, it fails at some step that tried to copy UNINSAP.EXE to my local drive. It is looking at directory IM01_NT_I386/SAPINST/NT/I386/UNISAP.EXE. This is a path in the "Installation Master" DVD. However, during the intsallation, the installation wizard asked me to insert the RDBMS DVD. I don't know exactly what it means. Anyway, following is a stack trace. See the last line:
MOS-01105 Processing of one or more file system node operations of table
Content of table: t_SAPComponent_Filesystem_Action_SHARED with condition WHERE WapsSystemName='ABP' AND WapsInstanceName='DVEBMGS00' AND WapsInstanceHost='vm-w3k-pck' AND OpMode NOT IN('CHECKFREESPACE', 'CHECKIF')
Row[0]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/prfclog" FollowLinks="TRUE" NodeName="C:\usr\sap/prfclog" NodeType="DIRECTORY" OpMode="CREATE"
Row[1]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP" NodeType="DIRECTORY" OpMode="CREATE"
Row[2]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00" NodeType="DIRECTORY" OpMode="CREATE"
Row[3]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/data" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/data" NodeType="DIRECTORY" OpMode="CREATE"
Row[4]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/data/cache" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/data/cache" NodeType="DIRECTORY" OpMode="CREATE"
Row[5]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/exe" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/exe" NodeType="DIRECTORY" OpMode="CREATE"
Row[6]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/log" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/log" NodeType="DIRECTORY" OpMode="CREATE"
Row[7]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/sec" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/sec" NodeType="DIRECTORY" OpMode="CREATE"
Row[8]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/work" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/work" NodeType="DIRECTORY" OpMode="CREATE"
Row[9]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS" NodeType="DIRECTORY" OpMode="CREATE"
Row[10]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/exe" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/exe" NodeType="DIRECTORY" OpMode="CREATE"
Row[11]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/exe/opt" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/exe/opt" NodeType="DIRECTORY" OpMode="CREATE"
Row[12]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/exe/dbg" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/exe/dbg" NodeType="DIRECTORY" OpMode="CREATE"
Row[13]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/exe/run" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/exe/run" NodeType="DIRECTORY" OpMode="CREATE"
Row[14]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/gen" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/gen" NodeType="DIRECTORY" OpMode="CREATE"
Row[15]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/gen/dbg" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/gen/dbg" NodeType="DIRECTORY" OpMode="CREATE"
Row[16]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/gen/opt" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/gen/opt" NodeType="DIRECTORY" OpMode="CREATE"
Row[17]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/global" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/global" NodeType="DIRECTORY" OpMode="CREATE"
Row[18]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/profile" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/profile" NodeType="DIRECTORY" OpMode="CREATE"
Row[19]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/src" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/src" NodeType="DIRECTORY" OpMode="CREATE"
Row[20]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/tmp" FollowLinks="TRUE" NodeName="C:\usr\sap/tmp" NodeType="DIRECTORY" OpMode="CREATE"
Row[21]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans" FollowLinks="TRUE" NodeName="C:\usr\sap\trans" NodeType="DIRECTORY" OpMode="CREATE"
Row[22]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/tmp" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/tmp" NodeType="DIRECTORY" OpMode="CREATE"
Row[23]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS" NodeType="DIRECTORY" OpMode="CREATE"
Row[24]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/in" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/in" NodeType="DIRECTORY" OpMode="CREATE"
Row[25]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/out" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/out" NodeType="DIRECTORY" OpMode="CREATE"
Row[26]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/log" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/log" NodeType="DIRECTORY" OpMode="CREATE"
Row[27]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/bin" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/bin" NodeType="DIRECTORY" OpMode="CREATE"
Row[28]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/buffer" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/buffer" NodeType="DIRECTORY" OpMode="CREATE"
Row[29]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/cofiles" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/cofiles" NodeType="DIRECTORY" OpMode="CREATE"
Row[30]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/data" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/data" NodeType="DIRECTORY" OpMode="CREATE"
Row[31]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/etc" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/etc" NodeType="DIRECTORY" OpMode="CREATE"
Row[32]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/log" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/log" NodeType="DIRECTORY" OpMode="CREATE"
Row[33]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/sapnames" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/sapnames" NodeType="DIRECTORY" OpMode="CREATE"
Row[34]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="WAPS_COPY_E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE_C:\usr\sap\ABP\SYS\exe\run\..\UNINSTSAP.EXE" NodeName="E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE" NodeTarget="C:\usr\sap\ABP\SYS\exe\run\..\UNINSTSAP.EXE" OpMode="COPY"
failed.

UTF-8, Unicode, XML and windows problems

Hi there,
I'm developing an application which uses a lot of russian text.
This russian text is stored in XML and can be sent to a server remotly
I use the standard javax.xml libaries to parse the xml files and DBunits XMLWriter to write generate XML strings.
The XML returned by the DBunit stuff is UTF-8, but its inside a UTF-16 string.
So when I generate xml and print it out I get something that looks like the following:
�� ?��Thats ok, beacause I can stick that streight into a file when writing files and it works.
But the problem comes when sending the XML over the server.
The sending implentation I use must be able to send java generated utf-16 and xml read utf-8.
So I convert the XML from utf-8 to utf-16, using the following:
byte[] stringBytesISO = isoString.getBytes("ISO-8859-1");
utf8String = new String(stringBytesISO, "UTF-8");And that works perfectly on my linux system.
However when I run it on windows, it only seems to convert some of the characters
Привычным �?ном за�?нут дороги до ве�?ны,Does anyone know whats going wrong here?

jammers1987 wrote:
I use the standard javax.xml libaries to parse the xml files and DBunits XMLWriter to write generate XML strings.DbUnit is a testing tool; are you saying you're using it in a production system? Ideally, you should use the same library to write the XML as you do to read it, but you definitely shouldn't be using DbUnit in this context.
The XML returned by the DBunit stuff is UTF-8, but its inside a UTF-16 string. That should never happen. XML is just text, and text can either be in the form of a Java string, or it can be stored externally using a text encoding like UTF-8. Never mind that Java strings use the UTF-16 encoding; you don't need to know or mention that. Encodings only come into play when you're communicating with something outside your program, like a file system or a database.
When you generate the XML, you specify that the encoding is UTF-8. When you read the XML, you specify that the encoding is UTF-8. That's all.

Regd:UTF 8 Unicode Version

Similar Messages

Maybe you are looking for