Mobilink - converting from ASA11 to ASA16

[t1950]

If I convert a consolidated database from ASA11 to ASA16 and leave the Mobilink db's ASA11, will the ML db's do a full sync or will the ASA16 db know where to "start" syncing from?

What is the proper ML client to use if the ML db is ASA11 and the consolidated is ASA16?

Thanks,

Tom Mangano

[jeff_albion]

If I convert a consolidated database from ASA11 to ASA16 and leave the Mobilink db's ASA11, will the ML db's do a full sync or will the ASA16 db know where to "start" syncing from?

All of the MobiLink system data are kept in the system tables, so rebuilding the database should keep the MobiLink system data. If/when you upgrade the MobiLink server to version 16, that is when you will want run the 'upgrade' SQL scripts against the MobiLink system tables to bring them up to version 16.

See: http://dcx.sybase.com/index.html#sa160/en/sachanges/consol-upgrading-upgrade.html

What is the proper ML client to use if the ML db is ASA11 and the consolidated is ASA16?

The version of dbmlsync should match the version of the remote database, and the remote version needs to be compatible with the MobiLink server. MobiLink 16 is compatible with version 11 or later remotes.

See: http://dcx.sybase.com/index.html#sa160/en/sachanges/upgrade-what-s-ml-intro.html

[t1950]

I was planning an unload of the ASA11 db and a reload into an empty ASA16. Does the upgrade of the ASA11 db give me all of the features of a new ASA16? Should I upgrade the ASA11 db, unload the upgraded db and then reload into the ASA16 db?

[Breck_Carter]

The step-by-step instructions are here: http://dcx.sybase.com/index.html#sa160/en/sachanges/upgrade-what-s-ml-intro.html