Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 11.0.1 » SQL Anywhere 11 - Changes and Upgrading » What's new in version 8.0.1 » Behavior changes in version 8.0.1


MobiLink behavior changes

  • Timestamp mismatch notification   When the timestamps between consolidated and remote databases are at variance, the MobiLink server will log a warning with each synchronization.

  • GLOBAL AUTOINCREMENT   The default value has been changed from 0 to 2147483647. global_database_id can now be set to 0 and will cause values to be generated starting at 1.

    It is still the case that if global_database_id is not set, or is set to the default value, attempts to cause a global autoincrement value to be generated result in a NULL. This commonly gives an error when attempting to insert the value into a non-nullable primary key column and is the indication that the global_database_id option has not been set.

    Disallowing a setting of 0 for global_database_id prevented generation of values starting at 1. Instead, values would start at the partition size specified for the column.

    For more information, see global_database_id option [database].

  • dbmlstop performs soft shutdown   By default (if none of -w, -f, -h or -t are specified), dbmlstop does a soft shutdown. This means that it stops accepting new connections and exits when the current synchronizations are complete.

    For more information, see MobiLink stop utility (mlstop).