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

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.

Spring version with rest api of webcenter sites

Hi everyone!
I'm using the rest api of webcenter sites, with this libraries: com.fatwire.wem.api.rest 11.1.1.8.0, com.fatwire.wem-sso-api-cas-11.1.1.8.0, com.fatwire.wem-sso-api-11.1.1.8.0 in a spring application with version 3.2.10.RELEASE. And it's works fine! I'm getting a list of assets and all their attributes, but I need use this application with the spring version 4.0.6.RELEASE, then when I update the spring version the rest api this libraries do not work. This is the method that fails:
SSOSession ssoSession = SSO.getSSOSession(baseUri);
multiticket = ssoSession.getMultiTicket(username, password); -> ERROR LINE
baseResource = baseResource.queryParam("multiticket", multiticket);
this because the application cannot get a mutiticket. I'm using the same code and the same structure only changes the spring version. Oracle webcenter is updated with all the patches until this date.
How it's possible solve this?
Thx

SOLVED
private void authenticate() throws RestConnectionException {
   try {
SSOSession ssoSession = SSO.getSSOSession("CASConfig.xml");
   multiticket = ssoSession.getMultiTicket(username, password);
   baseResource = baseResource.queryParam("multiticket", multiticket);
} catch (SSOException e) {
   throw new RestConnectionException(e);
CASConfig.xml
<beans:beans xmlns="http://www.springframework.org/schema/mvc"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xmlns:beans="http://www.springframework.org/schema/beans"
   xmlns:jee="http://www.springframework.org/schema/jee" xmlns:tx="http://www.springframework.org/schema/tx"
   xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee.xsd http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx.xsd">
   <beans:bean id="ssoconfig" class="com.fatwire.wem.sso.cas.conf.CASConfig">
   <beans:property name="casUrl" value="http://server:port/cas" />
   <beans:property name="casInternalURL" value="http://server:port/cas"/>
   </beans:bean>
   <beans:bean id="ssoprovider" class="com.fatwire.wem.sso.cas.CASProvider">
   <beans:property name="config" ref="ssoconfig" />
   </beans:bean>
   
</beans:beans>
add the casconfig to the classpath in spring, set the server and port in xml and it works!

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.

How to get an offline version of the API documentation?

Well, thats the question. I want to have the API documetatio like in this link: http://java.sun.com/j2se/1.4/docs/api/overview-summary.html , but I want it all and offline. Is there a Help file I can download somewhere where the API is documented?
thanx

If you have Java installed you have the documentation on your harddrive.
%JDKDIR%\src.zip
in some versions src.jar
You can open that file with "zip"-applications such as WinZip and in there you got every class your installed version has...and ever source file is filled with comments for every method.
In this file you can alsow easeily look upp what methods a class has.

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 <b>available now</b> for customers. I would suggest that you start with this release.
Note: SAP BW 3.1 Content on unicode is <b>not</b> 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.

Compiling servet.error wrong version of servet-api.jar

hi,
I try to compile the following servlet
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
public class ServletTemplate extends HttpServlet
public void doGet(HttpServletRequest request,HttpServletResponse response) throws ServletException,IOException
PrintWriter out=response.getWriter();
But I got the follwing error.
D:\apache-tomcat-6.0.14\webapps\Raju\WEB-INF\classes>javac SevletTemplate.java
SevletTemplate.java:5: class ServletTemplate is public, should be declared in a
file named ServletTemplate.java
public class ServletTemplate extends HttpServlet
^
SevletTemplate.java:5: cannot access javax.servlet.http.HttpServlet
bad class file: D:\apache-tomcat-6.0.14\lib\servlet-api.jar(javax/servlet/http/H
ttpServlet.class)
class file has wrong version 49.0, should be 48.0
Please remove or make sure it appears in the correct subdirectory of the classpa
th.
public class ServletTemplate extends HttpServlet
^
2 errors
I have set CLASSPATH with servelt-api.jar.
Please help me

rajuchinu wrote:
class file has wrong version 49.0, should be 48.0You have compiled it with a newer javac version than the JRE version with which you're running it.
Check java -version and javac -version and align them both out to the same version.

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.

Any Windows 7 64bit version for bdb xml available?

Dear experts,
I received the following:
Exception in thread "main" java.lang.UnsatisfiedLinkError: C:\Program Files (x86)\Oracle\Berkeley DB XML 2.5.16\bin\libdb_java48.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
     at java.lang.ClassLoader$NativeLibrary.load(Native Method)
     at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1803)
     at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1728)
     at java.lang.Runtime.loadLibrary0(Runtime.java:823)
     at java.lang.System.loadLibrary(System.java:1028)
     at com.sleepycat.db.internal.db_javaJNI.<clinit>(db_javaJNI.java:38)
     at com.sleepycat.db.internal.DbEnv.<init>(DbEnv.java:264)
     at com.sleepycat.dbxml.XmlManager.<init>(XmlManager.java:77)
     at com.sleepycat.dbxml.XmlManager.<init>(XmlManager.java:101)
     at berkeleydbxml.BDBXML.createContainer(BDBXML.java:29)
     at berkeleydbxml.BDBXML.main(BDBXML.java:173)
Process exited with exit code 1.
I do not have any visual studio version installed to rebuild the source.
Is there a way of having the bdb xml working with a 64bit jdk?
Is it possible to get a 64bit compatible version of dbxml-2.5.16.msi?
TIA!

I'm having a problem building for the x64 platform using a 64-bit Windows 7 Pro system with Visual Studio 8 and dbxml 2.5.16. Building for Win32 works just fine. When I switch to the x64 platform, the build skips every project:
========== Build: 0 succeeded or up-to-date, 0 failed, 52 skipped ==========
Looking in the Configuration Manager, every project shows the x64 platform; but selecting one of these platform menus reveals that x64 isn't an option in the menu and the platform for that project is automatically changed to Win32 (the only valid option).
The same problem occurs with dbxml 2.5.13 and Windows XP.
Any ideas?

How to detect exchange server version using EWS API?

Hello there,
I am new to this EWS area and I am looking for a way to detect exchange server version information whether user mailbox is exchange 2007 or 2010 or 2013 etc. Apologize if we already have such question posted earlier, I am posting it here as I could now find
any such forum.
1. Is it possible to fetch this information using EWS API? I am using EWS 2.0 libraries for now.
2. If yes, how can i get that information? can you please provide some sample?
Thanks in advance.
sureshh...

1. On 2010 and above you can use Autodiscover to get the EWS Schema version this is most accurate method to use. It's import to understand the EWS Schema version vs just the Server there is a good write up in
http://msdn.microsoft.com/en-us/library/office/dn741586%28v=exchg.150%29.aspx . Some EWS Managed API code to get the server version would look like
AutodiscoverService adAutoDiscoverService = new AutodiscoverService();
adAutoDiscoverService.Credentials = ncCred;
adAutoDiscoverService.EnableScpLookup = true;
adAutoDiscoverService.RedirectionUrlValidationCallback = adAutoDiscoCallBack;
adAutoDiscoverService.PreAuthenticate = true;
adAutoDiscoverService.TraceEnabled = true;
adAutoDiscoverService.KeepAlive = false;
GetUserSettingsResponse adResponse = adAutoDiscoverService.GetUserSettings("[email protected]", (new UserSettingName[1] { UserSettingName.EwsSupportedSchemas }));
This won't work on 2007 but the other method you can use is if you set the version to 2007_SP1 and make a call like binding to the Inbox folder and then check the result in ServerInfo http://msdn.microsoft.com/en-us/library/microsoft.exchange.webservices.data.exchangeservicebase.serverinfo(v=exchg.80).aspx
. (Note if your are going to use ServerInfo you do need to make a request like a FolderBind ).
Cheers
Glen

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.

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 ?

Regd OS versions supporting Essbase API and Essbase product suite.

Hi All,
Can some one clarify me whether there will be any change of Versions in Operating Systems supporting the Essbase API and Essbase product suite ( i.e Essbase Server,Client,AAS,EIS,APS).
Is it possible like some of the Operating System versions supporting Essbase Server or AAS will not support the Essbase API of the same product version(9.3.1).
If both of them support different versions of operating systems, can some body provide me with the supporting OS version documents for Essbase API 9.3.1 and Essbase API 7.1.
Thanks and Regards
Dheeraj

I installed Photoshop CS4 after installing snow leopard. PS is crashing when saving JPG files. It is completely repeatable.
I deleted the preferences files and I got it to save the file once. The second time it started to crash again.
The file is a PSD file with several layers it is 4267x1200 pixels.
I then flatten the file and save as .... JPG
As soon as I click on the JPG quality or OK button photoshop freezes. THIS IS REPEATABLE EVERY SINGLE TIME.
The big lie from Adobe is that they said that CS4 was certified to work with Snow Leopard, it DOES NOT.
I went and spent the $350 for the upgrade to find out that CS4 is just as unstable as CS3 (which actually can still save JPGs
but crashes usually while retouching an image with the brush tool).
My machine is a current iMac24 with plenty of free disk space and 4Gigs RAM
I ran disk tools too. no problems here either. Even if I restart and only run PS it still fails.
Adobe you have to fix this. It is completely unacceptable to tell customers to go buy CS4 and have it NOT WORK.
I have used PS for more than a decade and it has been quite good. you have concentrated on bloatware features, too frequent updates to get more money (greed) at the expense of quality.
I do not believe that you are honestly concerned about quality, just more money for overpriced upgrades.

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.

UNICODE version of BDB API

Similar Messages

Maybe you are looking for