Question Re: [-10100] The synchronization server system table 'ml_user' is missing in Technology Q&A

[-10100] The synchronization server system table 'ml_user' is missing

Former Member — Wed, 22 Aug 2018 12:03:59 GMT

Hi Experts.

We are currently having trouble running the Mobilink service on Mobilink 17 due to the error [-10100]. We have already upgraded our consolidated database using the oracle upgrade scripts found on the Mobilink directories. We have also checked and found that the ml_user system table exists on the consolidated database, but still we keep on getting this error. Could anyone advise on how we can move forward?

Thanks and regards,

Pau

Re: [-10100] The synchronization server system table 'ml_user' is missing

chris_keating — Wed, 22 Aug 2018 18:55:51 GMT

What script did you use to upgrade? And from what version of MobiLink did you upgrade? Did you run the scripts with same user that MobiLink server is using for its connection?

This is likely nothing to do with MobiLink. I suspect you will need to troubleshoot why a query like

select * from ml_user

is not successful when run using the ODBC based connection that is used by MobiLink server.

Re: [-10100] The synchronization server system table 'ml_user' is missing

Former Member — Thu, 23 Aug 2018 04:51:30 GMT

Hi Chris.

We ran all the scripts found on the Mobilink>Upgrade>9.0.2>upgrade_ora.sql

We previously had a Mobilink 9.0.2 server on a Windows 2003 Server and we upgraded to Mobilink 17 installed on a Windows 2016 Server. The current consolidated database is cloned and we created a new user which we used to run the upgrade scripts.

Re: [-10100] The synchronization server system table 'ml_user' is missing

chris_keating — Thu, 23 Aug 2018 14:43:38 GMT

And the results of testing the simply query with that user (assuming it is that user that the MobiLink server connection to that database is using)?

Re: [-10100] The synchronization server system table 'ml_user' is missing

Former Member — Thu, 23 Aug 2018 20:03:05 GMT

I think what Chris is asking is this: Did you use the SAME consolidated database user id to run the consolidated upgrade, as you use to connect from mlsrv17.exe to the consolidated?

There is a design [cough] inadequacy in MobiLink that makes it [cough] difficult and [cough] inconvenient to use different user ids for different purposes. This is ESPECIALLY TRUE in large mature Oracle shops where there are strict rules and regulations about what user id is used for which purpose; e.g., DDL changes like upgrades versus DML processes like mlsrv17.exe.