Regarding sync issue in mobilink sever

upload_fetch_column_conflict is only getting called, if there is a line updated. Therefore an insert will not trigger that function.

If inserting a new line which might conflict with a recent change on consolidated database, the conflict needs to be caught during upload workflow -- so e.g. inside processing of upload_insert.

Mobilink can also pass schemachanges to it's replicated databases. For this, there exists the start synchronization schema change statement

This looks like this:

START SYNCHRONIZATION SCHEMA CHANGE
  FOR TABLES DBA.Sales, DBA.Products
  SET SCRIPT VERSION = 'version_2';
ALTER TABLE DBA.Sales ADD SUBTOTAL NUMERIC (10,2);
ALTER TABLE DBA.Products ALTER QUANTITY BIGINT;
STOP SYNCHRONIZATION SCHEMA CHANGE;