Adaptive Server Enterprise consolidated database

Setting up Adaptive Server Enterprise as a consolidated database

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 install-dir\MobiLink\setup.

  • In the MobiLink plug-in for Sybase Central, choose Mode » Admin and connect to your server database. Right-click the database name and choose Check MobiLink System Setup. If your database requires setup, you are prompted to continue.

  • When you use the Create Synchronization Model Wizard or Deploy Synchronization Model Wizard, system setup is checked when you connect to your server database. If your database requires setup, you are prompted to continue.

Note

The database user who runs the setup script is the only user who has permission to change the MobiLink system tables, which is required for configuring MobiLink applications. See Required permissions.

The RDBMS user that the MobiLink server uses to connect to the consolidated database must be able to 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.

ODBC driver

You must set up an ODBC DSN for your Adaptive Server Enterprise consolidated database using the ODBC driver that is provided with your Adaptive Server Enterprise database. See:

Adaptive Server Enterprise issues

  • BLOB sizes   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.

  • CHAR columns   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 mlsrv11 -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.

    For more information, see -b option.

  • Data type mapping   The data types of columns must map correctly between your consolidated and remote database. See Adaptive Server Enterprise data mapping.

  • Special considerations for version 11.5 and earlier   You cannot use MobiLink system procedures such as ml_add_connection_script to add scripts longer than 255 bytes to Adaptive Server Enterprise 11.5 or earlier. To define longer scripts, use Sybase Central or direct insertion.

  • 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 on 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.

Isolation level

See MobiLink isolation levels.

Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1