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 a SELECT privilege on MASTER..SYSTRANSACTIONS.
The MobiLink server login ID must have the dtm_tm_role role, if the -cs option for mlsrv16 is used.
You must use the sp_dboption option to set the SELECT INTO option to true. For example, run the following script in Interactive
SQL to set the SELECT INTO privilege to true on your-database-name:
sp_dboption your-database-name, "SELECT INTO", true
To set up Adaptive Server Enterprise 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 syncase.sql setup script, located in %SQLANY16%\MobiLink\Setup.
Enable functionality group configuration parameter
When the enable functionality group configuration parameter is enabled on the ASE 15.7 server, the MobiLink server uses the "select ... for update" feature to
lock remote IDs to prevent redundant synchronizations for the same remote ID simultaneously. If you turn off the enable functionality group parameter, you must restart any MobiLink servers currently connected to the ASE server to avoid failure of synchronization
In Adaptive Server Enterprise, CHAR data types are fixed length and blank-padded to the full length of the string. In
MobiLink remote databases (SQL Anywhere or UltraLite), CHAR is the same as VARCHAR: values are not blank-padded to a fixed
width. It is strongly recommended that you use VARCHAR in the consolidated database rather than CHAR. If you must use CHAR,
the mlsrv16 -b command line option can be used to remove trailing blanks from strings during synchronization. This option
is important for string comparisons used to detect conflicts.
To download BLOB data with a data size greater than 32 KB (the default), do the following:
On Windows, set Text Size on the Advanced page of the Adaptive Server Enterprise ODBC Driver Configuration window to be greater than the largest expected BLOB.
On Linux, set the TextSize entry in the .obdc.ini file to be greater than the largest expected BLOB.
Restrictions on VARBIT
MobiLink does not support synchronizing 0 length (empty) VARBIT or LONG VARBIT values to an Adaptive Server Enterprise
consolidated database. Adaptive Server Enterprise does not support a VARBIT type so these types would normally be synchronized
to a VARCHAR or TEXT column in the Adaptive Server Enterprise database. On Adaptive Server Enterprise, empty string values
are converted into a single space. A space is not allowed in a VARBIT column on SQL Anywhere, so an attempt to download these
values causes an error on the remote database.