This content has been marked as final. Show 14 replies
As you are aware Oracle Lite 10.3.0.3.0 does support the Android Client as well as your current Wm 6.1 Olite Client
Oracle Mobile Server 11g doe not support the Olite WM 6.1 Client anymore i.e. its desupported but there is a Sqlite & BerkeleyDB Client for Wm 6.1
I see the best option for you is as follows
1. Upgrade to 10.3.0.3.0 and run your current Clients (Olite WM 6.1) against the existing Application
2. Develop your Android Application in this Repository based on a Sqlite Publication
3. Deploy your Android Clients when timeframe suits you running exitsing Olite Clients in Parallell
4. When you have moved ALL your Clients over to Android upgrade the Mobile Server to 11G
Note that upgrading straight to 11G would mean you are unable to use your existing Olite Wm 6.1 Clients and they would need to be reinstalled with the Sqlite/Berkeley DB Client that is available in 11G.
Global Support Services
If we upgrade to 10.3.0.3, will there be a 'smooth' way to upgrade to 11g on the client side, or will we have to install the SQLite clients manually?
Our Android app will soon be ready for release, and since each update on WM has caused a lot of trouble (users without any computer skills and limited knowledge of English lang.) we are considering the option to just moving to the latest 11g version directly (have the users uninstalling the Olite client and installing the SQLite client manually).
In this way we (hopefully) only need one updgrade.
We would prefer the smooth upgrade, though :)
at least we do now upgrade from Oracle lite (10.3.0.3) to SQLite (but still in 10.3.0.3) and only way is to reinstall this application. There is no "smooth" way that upgrade will happen during sync process because of many things. Once we will migrate all to SQLite then we consider upgrade server.
I tried to install the Olite 10.3.0.3, but since our Oracle database is 11g, the install stopped with a "Migrate path not supported" message.
We do actually use Olite 10.3.0.2 with Oracle DB 11g in production now, we tested it for a while and it seemingly works with no issues.
Is it possible to get 10.3.0.3 to run with Oracle DB 11g, or is it definately not recommended?
Otherwise I guess we'll just have to go for Mobile server 11g right away.
i cannot help you with your main issue but i can verify that oracle 10.3.0.3 works fine with oracle database 11g. we use this setup in our windows mobile 6.1, 6.5 based clients with no problems on win 2003 systems.
the error your getting is probably an update from 10.3.0.2 to 10.3.0.3 migration issue(problem).
for information concerning the upgrade you could check
Good to know, Vasileios!
I actually got the error "Migration path not supported" the second time I tried to run the rep-wizard. The first time I got no such message, but the wizard just crashed.
We use Oracle RAC with ASM, and it looks like the repwizard cannot cope with ASM. It creates its datafile on one particular node instead of using ASM. We had to do some tidy-up and tried to create the SYNCSERVER tablespace manually on the ASM before running the repwiz again. We then got a bit further, but the repwizard crashed. (The java app "disappeared" in the midle of setup/installation, with nothing useful in the logs).
The second time I tried to run the repwizard, I got the "Migration path not supported" message along with references to supported Oracle database versions (!= 11g).
Maybe I should drop the mobileadmin schema and go for it again. Moving to 10.3.0.3 would be a lot easier and save me a lot of work this summer (no need to SQLiteyfy the Winmo olite terminals)
we installed a fresh new oracle 184.108.40.206.0 then we installed the 10.3.0.3 , our database expert set up the environment correctly on windows 2003 server with java version (java -version)
1.4.2_03-b02. then we started installing the patches as they came out (we installed a second java version for those but didnt change the java home so that olite still works with the 1.4.2 version) i think we installed like 5-6 patches (as they came along during the months). when we had to go to a client install or we needed to create a new testing/development server we just copied the entire server from the vmware and paste it into a new server then loggin change the ip manual and we had a new server. this way we could install a customer server in his environment in less than 4-5 hours (actually the copy paste takes like 4 -5 hours and then you need minor adjustments for his domain which take like 5 minutes).
our clients are windows mobile 6.1-6.5 our apps are .net 3.5 on intermec and motorola handheld devices(rugged). we had some problems with the unicode characters and the set up for our localized (greek) characters but our database expert set the database with the correct language page (i think it was 1253 for us) and then we set it also on the windows mobile-olite and we got passed that issue too.
i know this doesnt help you much but (im not an oracle expert, nor oracle rep) if i were you i wouldnt try to migrate from olite 10.3.0.2 to 10.3.0.3 . if i were you i would install a fresh 11g+10.3.0.3 and overwrite the entire server. the reason is that if you search this forum you will find many posts from people asking help about migrating from one version of olite to another. they report many problems. so why not make a fresh install? you can later migrate all the database tables your self.
but if you need to go from 10.3.0.2->10.3.0.3 the link i sent you gives some info, if your problem persists i guess you need to ask for help from oracle, perhaps open a service request,(or perhaps search for a similar post here, if your lucky:) ).
Oracle DB 11G should be fine with Oracle Lite 10.3.0.3.0
Note that when using ASM you must create the SYNCSERVER Tablespace in advance otherwise it will fail. Note 799544.1 covers this but basically you need to do the following
pre-create the SYNCSERVER Tablespace before installing Oracle Lite with a size of 200MB with Autoextend
Note there will be some DB file(s) created like mobile01.dbf and it may well be that if these still exists even if you created the Tablespace in ASM it still fails so i would suggest the following
1. Drop user Mobileadmin from your Repository DB
2. Drop the tablespace SYNCSERVER
3. Check and remove any/all mobile(nn).dbf files from Your database
4. Create the SYNCSERVER Tablespace in your ASM environment with size 200MB and Autoextend on
If you are still encountering issues after this please raise a Service request and we will be glad to help you further.
Thanks for the informative post, Vasileos. It's allways interesting to hear about other Olite users experiences. Especially since our use (clients) are pretty similar.
I actually did a clean install, but I think it was ASM-problems that was the reason the installation failed. I am not sure we managed to clean up properly after the first attempt.
I am waiting for a new Windows server and the database experts to clean up again. After this, I will try again, encouraged by your success :)
After a long and painfull period of trial and error with installing 10.3.0.3, we finally made it. The problem was the JDBC-URL. As long as we used load balancing, the installation just silently failed, sometimes with a "Got -1 from a read call" message. When we changed it to just use a single node, it alll went smoothly.
The problem probably has something to do with the setup/config of our Oracle test environment. In production, we have not had any problems with installation with a load balancing JDBC-URL.
We support the following JDBC URL format for RAC environment :
Is your JDBC URL format for RAC correct? Do you try your JDBC URL in a simple program to connect to your RAC environment?
Oracle Berkeley DB and Mobile Server Development
This is the URL we used:
jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = 10.10.10.10)(PORT = 1521))(ADDRESS = (PROTOCOL = TCP)(HOST = 10.10.10.11)(PORT = 1521))(LOAD_BALANCE = yes)(CONNECT_DATA =(SERVER = DEDICATED)(SERVICE_NAME = DB1.TEST.LOCAL)(FAILOVER_MODE =(TYPE = SELECT)(METHOD = BASIC)(RETRIES = 180)(DELAY = 5))))
I'll try the suggested format next time.