SQL Anywhere Mobile - MobiLink Monitor & Replicated tables

Author

MobiLink Monitor & Replicated tables

Alex van Denzel

2005-08-22, 11:24 am

Hello,

For redundancy purposes I have two servers, each with a mobilink server
and a database server (both from Studio 9.0.1.1989). The database
servers are replicated with repserver (12.6.12409).

The tables I replicate include the tables starting with "ml_", except
the tables starting with "ml_qa".

Now I want to use MobiLink Monitor to monitor both MobiLink servers, but
when I try to connect to the other server, I get a MobiLink Monitor
Error messagebox that tells me "The MobiLink server is already being
monitored from another location (auth_status=1000)", and the other
Monitor shows a yellow bar indicating a sort-of failed MobiLink session.
I know that there are no real MobiLink clients connecting yet.

I know I have to replicate the ml_user table but I'm not sure which
tables I can drop from the replication.

Update: I found out that, after a time (about half an hour), I can get a
MobiLink Monitor session connected to the other server, still don't know
why the first few times it didn't work.

Can anyone enlighten me on the dos and don'ts of replicating MobiLink
tables, and the issues with the MobiLink Monitor?

--
Alex.

Graham Hurst

2005-08-24, 8:25 pm

MobiLink is designed to work with a single consolidated database, so
you're in uncharted and unsupported territory if you are replicating
MobiLink's ml_* system tables.

Having said that, you might be alright if only 1 consolidated was
servicing sync requests at a time.

I think you must have inadvertently been connecting to the first ML
server when you got the error trying to connect a second Monitor. The
fact that a Monitor is connected is only saved in the memory of a given
ML server; it isn't saved in the ml_* tables. So the only way you could
get that error is if the ML server thought it was already being
monitored. The fact that you saw a yellow bar in the first Monitor when
trying to connect the second shows that you were actually trying to
connect to the ML server which was already being monitored, and the
error message was correct.

When you tried reconnecting later, it must have been to the different ML
server, or the first Monitor must have been disconnected.

Cheers,

Graham

Alex van Denzel wrote:
> Hello,
>
> For redundancy purposes I have two servers, each with a mobilink server
> and a database server (both from Studio 9.0.1.1989). The database
> servers are replicated with repserver (12.6.12409).
>
> The tables I replicate include the tables starting with "ml_", except
> the tables starting with "ml_qa".
>
> Now I want to use MobiLink Monitor to monitor both MobiLink servers, but
> when I try to connect to the other server, I get a MobiLink Monitor
> Error messagebox that tells me "The MobiLink server is already being
> monitored from another location (auth_status=1000)", and the other
> Monitor shows a yellow bar indicating a sort-of failed MobiLink session.
> I know that there are no real MobiLink clients connecting yet.
>
> I know I have to replicate the ml_user table but I'm not sure which
> tables I can drop from the replication.
>
> Update: I found out that, after a time (about half an hour), I can get a
> MobiLink Monitor session connected to the other server, still don't know
> why the first few times it didn't work.
>
> Can anyone enlighten me on the dos and don'ts of replicating MobiLink
> tables, and the issues with the MobiLink Monitor?
>
> --
> Alex.

David Fishburn

2005-08-27, 1:23 pm

Alex van Denzel <vandenzel@hotmail.com> wrote in news:4309f7c5$1@foru
ms-2-
dub
of sybase.public.sqlanywhere.mobilink:

AvD> For redundancy purposes I have two servers, each with a mobilink
server
AvD> and a database server (both from Studio 9.0.1.1989). The database
AvD> servers are replicated with repserver (12.6.12409).
AvD>
AvD> The tables I replicate include the tables starting with "ml_", except
AvD> the tables starting with "ml_qa".

Can you point out which tables you are replicating.
--
David Fishburn
Certified ASA Developer Version 8
iAnywhere Solutions - Sybase
Professional Services
Please only post to the newsgroup
Please ALWAYS include version and MORE importantly BUILD number with
EACH post (dbeng9 -v).

EBFs and Maintenance Releases
http://downloads.sybase.com/swx/sdmain.stm

Developer Community / Whitepapers
http://www.ianywhere.com/developer

CaseXpress - to report bugs
http://casexpress.sybase.com

CodeXchange - Free samples
[url]http://ianywhere.codexchange.sybase.com/servlets/ ProjectDocumentList[
/url]

Alex van Denzel

2005-08-28, 7:24 am

David Fishburn wrote:
> Alex van Denzel <vandenzel@hotmail.com> wrote in news:4309f7c5$1@foru
ms-2-
> dub
> of sybase.public.sqlanywhere.mobilink:
>
> AvD> For redundancy purposes I have two servers, each with a mobilink
> server
> AvD> and a database server (both from Studio 9.0.1.1989). The database
> AvD> servers are replicated with repserver (12.6.12409).
> AvD>
> AvD> The tables I replicate include the tables starting with "ml_", except
> AvD> the tables starting with "ml_qa".
>
> Can you point out which tables you are replicating.

Initially I replicated all of the following tables:

ml_connection_script
*
ml_device
ml_device_address
ml_listening
ml_property *
ml_script *
ml_script_version *
ml_scripts_modified *
ml_subscription *
ml_table *
ml_table_script *
ml_user *

I changed my replication definition to include only the tables marked
with * because the other are only used with push replication

Sponsored Links