I am using an Oracle 12C as my consolidated DB and SQLAnywhere 16 as my remote db for syncing some of the data through Mobilink 1. Once the data is synced, I am using the same remote SQLAnywhere16 db as a consolidated DB and I am creating a UDB through Mobilink 2. The architecture is as follows :
Oracle Staging Area (Materialized Views, Stored Procedures, Tables) <-> Mobilink1 <-> SQLAnywhere16 DB <-> Mobilink2 <-> UDB
I am able to do the sync between Oracle and Sybase but when I am trying to create an UDB, I am getting only a partial success. The errors are as follows :
Is there a easier / neat way to do the sync rather than this double mobilink solution ?
Software version Used :
Oracle : 12C SqlAnywhere : 16.0.0 Mobilink : 16.0.0 Ultralite DB : 16.0.0 OS : RedHat Linux 6.5 Oracle and SQLAnywhere are running on different machines. SQLAnywhere and Mobilink are running on same machine. Apache relay is not yet configured. All these are running in an intranet.
asked 26 Jun '14, 13:05
18.104.22.1681 is very old and suffers from the Heartbleed flaw. Build 1915 is recommended.
The error message "Expecting 15 columns and found 17" signifies a flaw in the MobiLink setup, not a bug in SQL Anywhere or the MobiLink server... but if you are trying to use the Sybase Central MobiLink wizard to generate your scripts the problem may originate there (the wizard has many limitations, especially when life gets "interesting" as it does with three-tier synchronizing.)
High load should not cause a database server to crash. 3500 remote users is not (by itself) a reason to introduce three-tier synchronization... it may be a reason to build a MobiLink server farm, and enforcing limits on the number of simultaneous syncs (which mlsrv16 does quite well).
A three-tier setup is generally used when there is a need for a group of remote databases to pass data between themselves via a local consolidated database, when the local network is not connected to the top-level Oracle database... as in a team of workers in a remote location who are out of touch with head office but need to communicate with one another.
If all the data uploaded from the remotes must eventually be sent to Oracle, and all the data downloaded to the remotes originally comes from Oracle, I don't see how a three-tier architecture is going to solve performance and reliability problems. If the middle layer filters or hides or summarizes data, sure, but not if all the data is passed through.
A three-tier setup WILL introduce several new points of possible failure, as well as making development and administration harder.
answered 27 Jun '14, 08:39