Comments on: Oracle Lite Part 1, how to get started

By: Sacramento Apartments

Sacramento Apartments — Tue, 07 Feb 2006 15:43:57 +0000

Do you provide a blog feed subscription for this blog so
I can get it via email?

By: rekounas

rekounas — Thu, 02 Feb 2006 00:27:13 +0000

The just nature of oracle lite and database replication has many locks and at times blocking locks. Have you identified what tables/user sessions are causing the blocks? Is it Mobileadmin or something else? Do you have an application that is directly connected to the database server that is also performing insert/update/deletes?

By: Leonardo Ortega

Leonardo Ortega — Fri, 27 Jan 2006 18:52:01 +0000

We are using WebToGo version 2.0.3.4.0 and we are having DB lock issues, we suspec that DB locks are happening during data synchronization, has anybody experienced this? is it a version issue that is resolved in a newer version?

I will appreciate your thoughts.

By: rekounas

rekounas — Sat, 03 Dec 2005 13:32:25 +0000

Ensure you have a Primary Key on all your base tables. I have not read any bugs on creating replication for large dataset. There are some known bugs and patches for replicating large sets, but not on creating them.

By: devendra

devendra — Wed, 16 Nov 2005 06:21:36 +0000

Hi,
I guess u r master in Oracle Lite.
One thing i wanted to add is that when u try to pubilsh through packaging waizard it gives Internal Server error when i have a large data.So what i do i create a jar file through packaging wizard and the import the application through mobile administrator.

Also the samples that they have provided on palm using codewarrior never run.
They have not clearly mentioned which library file to include.

If have developed any small application on Palm please help me………

Thanx
Devendra Sutar,
Palm OS developer.
Oracle Lite Admin.

By: Phil Stephenson

Phil Stephenson — Mon, 22 Aug 2005 15:15:52 +0000

Andre – We apreciate your comments on Database Lite and welcome your suggestion for product imporvements or please contact me if you have additinoal unanswered questions about the product. We look forward to additional installments. – Phil

By: rekounas

rekounas — Mon, 22 Aug 2005 11:46:19 +0000

Oracle Lite actually creates 5 tables per snapshot, 3 in the application schema, 2 in the MOBILEADMIN schema. The application schema has the Error Queue, Log Tables, and Version Tables. The MOBILEADMIN Schema has the In and Out Queues.

This is the first I have heard of not being able to sync large tables. Our application uses 9i Lite and we are able to sync tables with 500,000+ records.

WTGPACK gives the In and Out queue a sequenced number when you publish an application. To get around this, use the Java API provided with the application. This is for more advanced users but it will save time in identifying what tables the In and Out queues are associated with.

By: rekounas

rekounas — Mon, 22 Aug 2005 00:48:13 +0000

I totally agree with you enthusiasm for the application. Once you get everything working, it's a joy, but to get to that point can be very frustrating. One thing that Oracle did wrong with this product is the gave it the name "Lite." There is nothing light weight about this application. The sync server and the MGP process are complete hogs of the resources. You want to have a knowledgable DBA to help out with the fine tuning. Oracle Lite actually create 5 tables for each base table you publish. 3 tables in the application schema CEQ$, CLG$, CVR$. 2 Tables in the MOBILEADMIN schema, CFM$. The tables in the application schema are your Version Table, Log Table, and Error Queue. While the tables in the MOBILEADMIN schema are your IN and OUT queues. I will have to look at the documentation, but I don't believe Oracle mentions anything about large recordsets. In fact, we have an application that has large volume users that get about 1GB of data, and most of that data resides in one of 2 tables. Both tables having about 500,000+ records. I would also think that you can set the POLITE.INI on the server side somehow. Maybe using the WSH utility or the Java API. One thing to consided if you do have large tables to sync, is to use an Java API (Consolidator in 9i Lite) to Partition your Out Queue. If you do not like the random numbers that are associated with the snapshots and publications, I would recommend using the Java API. More advanced users will prefer the use of the Java API over the WTGPACK. I usually use WTGPACK to create small applications for testing/debugging purposes.