This topic has been updated for build 1823.
Before running the setup script, you should be aware of the following requirements:
The database user who runs the setup script is expected to be the same one used to update the MobiLink system tables during synchronization. This user must be used to start the MobiLink server and to configure MobiLink applications. See Required privileges.
The RDBMS user that the MobiLink server uses to connect to the consolidated database must be able to use the MobiLink system tables, procedures, and so on, without any qualifiers (for example, SELECT * from ml_user). See MobiLink server system tables.
The MobiLink server login ID must have EXECUTE privilege on the SP_IQTRANSACTION system procedure for SAP Sybase IQ.
To set up SAP Sybase IQ to work as a MobiLink consolidated database, you must run a setup procedure that adds MobiLink system tables, stored procedures, triggers, and views that are required for MobiLink synchronization. There are multiple ways you can do this:
Run the synciq.sql setup script, located in %SQLANY16%\MobiLink\Setup.
Check and update the MobiLink system setup from Sybase Central. See MobiLink system setup.
You must set up an ODBC DSN for your SAP Sybase IQ consolidated database. The ODBC driver for SAP Sybase IQ is installed with Sybase IQ.
For information about the ODBC driver for SAP Sybase IQ, see the SAP Sybase IQ documentation.
With row-level versioning
With the SAP Sybase IQ 16 row-level versioning (RLV) feature more than one user can modify the same table concurrently, users can wait for transaction locks instead of having to retry, and a hybrid storage model optimizes data write-access, without sacrificing read-access performance. In order to get better upload performance, we recommend that all synchronization tables be RLV enabled.
Without row-level versioning or if you are using SAP Sybase IQ 15.4
If uploads contain upload data that modifies any synchronization tables that were defined on the SAP Sybase IQ store, and if the MobiLink server is running with more than one concurrent database worker thread, all the uploads must be serialized because SAP Sybase IQ server allows only a single connection to modify a given table on the SAP Sybase IQ store at any given time.
This requirement can be achieved, if the begin_upload connection script is written to include or to use the following SQL statement:
LOCK TABLE table_name IN WRITE MODE WAIT time_string
where table_name is the name of a table that is defined on the SAP Sybase IQ store and the time_string gives the maximum time period to lock the table. The table can be as simple as one defined as follows:
create table coordinate_upload ( c1 int )
The table is not required to have any data.
All transactions that modify SAP Sybase IQ tables must be serialized, whether they occur on MobiLink server connections or on other connections to the SAP Sybase IQ database. For MobiLink server transactions, the same logic outlined above can be used. This technique is more efficient than having the MobiLink server automatically retry on each transaction and results in better performance.
When creating a synchronization model for an SAP Sybase IQ consolidated database, the table mappings default to download-only for SAP Sybase IQ tables. If you change any mappings to bi-directional or upload-only, you must ensure that changes to those SAP Sybase IQ tables are serialized. For example, by adding a begin_upload event as described above.
Discuss this page in DocCommentXchange.
|Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0|