SQL Anywhere Mobile - synchronization question

Author

synchronization question

Dimitris Karistinos

2005-06-16, 7:24 am

Hello again,

I am making a lot of tests here so that is why I make so many postings.....

So I far I have done many things regarding scripts etc following the manuals
but I got into something that I cannot understand why it is happening.

I recently added a new table in my consolidated database. I want that table
to my remote db too and to be synchronized along with my other tables in the
publication..

What I did is the following

1.I used the Migrate database utility in order to bring that new table in
the already existing remote database.
2. I added a new article in the existing publication
3. Tried to synchronize.

The result was that every table was synchronized except the new one!!! Why
is that happening?

I can understand that maybe there are missing entries in the mobilink tables
but I don't exactly which ones should I alter. and how!! (maybe mobilink
stored procedures??)

Anyway I will need some guidance in that subject so if there is a standard
procedure for that please inform me.

Kind Regards
D

Reg Domaratzki $iAnywhere Solutions$

2005-06-16, 9:23 am

Did you add synchronization scripts for the new table on the consolidated?

My guess is that you had the synchronization scripts automatically generated
for you by MobiLink using the -za switch. The -za switch will only
automatically create scripts for you if there are no scripts that currently
exist in that script version, so when you added the new table on the
consolidated and synchronized, no synchronization scripts were created for
the new table.

If this is what's happening, you have two choices :

1) Manually add the synch script yourself for the new table using the
ml_add_table_script stored procedure.

2) After adding the table on the consolidated and remote (and adding the
table into the publication on the remote), also change the name of the
script version that you are using on the remote. This is a suggested step
anyway when schema changes are made. The next time you synchronize from the
remote with the new script version (make sure SendColumnNames='on'
as well),
if MobiLink has been started with the -za switch, new scripts will be
created for you by MobiLink using the new script version.

Note that a new script version for a different schema is a great idea.
Imagine you had a handful of remote all synchronizing using script verison
'TwoTables' that synchronized tables t1 and t2. Now, create a new table t3
on the consolidated, and create a new remote user that includes tables t1,t2
and t3. The new remotes will use a script version called 'ThreeTables'.
The remotes with two table and the remotes will three tables will both be
able to synchronize now since they are using two different script versions.

Finally, you should also know that automattically generated scripts download
every row to each remote on each synchronization. Once you're comfortable
with your setup, you should read up the section in the MobiLink
Administration Guide on Synchronization Techniques. The section on
timestamp-based synchronization shows you how to download only changed rows,
and the whole chapter is a good read.

--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL

"Dimitris Karistinos" <dkaris@relational.gr> wrote in message
news:42b16d5f@forums
-2-dub...
> Hello again,
>
> I am making a lot of tests here so that is why I make so many
postings.....
>
> So I far I have done many things regarding scripts etc following the
manuals
> but I got into something that I cannot understand why it is happening.
>
> I recently added a new table in my consolidated database. I want that
table

> to my remote db too and to be synchronized along with my other tables in
the
> publication..
>
> What I did is the following
>
> 1.I used the Migrate database utility in order to bring that new table in
> the already existing remote database.
> 2. I added a new article in the existing publication
> 3. Tried to synchronize.
>
> The result was that every table was synchronized except the new one!!!
Why
> is that happening?
>
> I can understand that maybe there are missing entries in the mobilink
tables
> but I don't exactly which ones should I alter. and how!! (maybe mobilink
> stored procedures??)
>
> Anyway I will need some guidance in that subject so if there is a standard
> procedure for that please inform me.
>
> Kind Regards
> D
>
>

Dimitris Karistinos

2005-06-17, 3:26 am

Thank you very much, that is exactly what I am doing here... I will do it
agian correctly this time.

Best Regards
D.
"Reg Domaratzki (iAnywhere Solutions)" <FirstName.LastName@ianywhere.com>
wrote in message news:42b1801c$1@foru
ms-1-dub...
> Did you add synchronization scripts for the new table on the consolidated?
>
> My guess is that you had the synchronization scripts automatically
> generated
> for you by MobiLink using the -za switch. The -za switch will only
> automatically create scripts for you if there are no scripts that
> currently
> exist in that script version, so when you added the new table on the
> consolidated and synchronized, no synchronization scripts were created for
> the new table.
>
> If this is what's happening, you have two choices :
>
> 1) Manually add the synch script yourself for the new table using the
> ml_add_table_script stored procedure.
>
> 2) After adding the table on the consolidated and remote (and adding the
> table into the publication on the remote), also change the name of the
> script version that you are using on the remote. This is a suggested step
> anyway when schema changes are made. The next time you synchronize from
> the
> remote with the new script version (make sure SendColumnNames='on'
as
> well),
> if MobiLink has been started with the -za switch, new scripts will be
> created for you by MobiLink using the new script version.
>
> Note that a new script version for a different schema is a great idea.
> Imagine you had a handful of remote all synchronizing using script verison
> 'TwoTables' that synchronized tables t1 and t2. Now, create a new table
> t3
> on the consolidated, and create a new remote user that includes tables
> t1,t2
> and t3. The new remotes will use a script version called 'ThreeTables'.
> The remotes with two table and the remotes will three tables will both be
> able to synchronize now since they are using two different script
> versions.
>
> Finally, you should also know that automattically generated scripts
> download
> every row to each remote on each synchronization. Once you're comfortable
> with your setup, you should read up the section in the MobiLink
> Administration Guide on Synchronization Techniques. The section on
> timestamp-based synchronization shows you how to download only changed
> rows,
> and the whole chapter is a good read.
>
> --
> Reg Domaratzki, Sybase iAnywhere Solutions
> Sybase Certified Professional - Sybase ASA Developer Version 8
> Please reply only to the newsgroup
>
> iAnywhere Developer Community : http://www.ianywhere.com/developer
> iAnywhere Documentation :
> http://www.ianywhere.com/developer/product_manuals
> ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
> -> Choose SQL Anywhere Studio
> -> Set "Platform Preview" and "Time Frame" to ALL
>
> "Dimitris Karistinos" <dkaris@relational.gr> wrote in message
> news:42b16d5f@forums
-2-dub...
> postings.....
> manuals
> table
> the
> Why
> tables
>
>

Breck Carter [TeamSybase]

2005-06-17, 7:26 am

You are welcome to post as many questions as you want!

However, to ensure better service, please *start* your message with a
simple question of the form "How do I <do some thing or fix some
symptom>?"

After the question, you can put as much supporting material as you
want.

You can see more suggestions at http://www.sybase.com/detail?id=47613

Breck

On 16 Jun 2005 05:15:30 -0700, "Dimitris Karistinos"
<dkaris@relational.gr> wrote:

>Hello again,
>
>I am making a lot of tests here so that is why I make so many postings.....
>
>So I far I have done many things regarding scripts etc following the manuals
>but I got into something that I cannot understand why it is happening.
>
>I recently added a new table in my consolidated database. I want that table
>to my remote db too and to be synchronized along with my other tables in the
>publication..
>
>What I did is the following
>
>1.I used the Migrate database utility in order to bring that new table in
>the already existing remote database.
>2. I added a new article in the existing publication
>3. Tried to synchronize.
>
>The result was that every table was synchronized except the new one!!! Why
>is that happening?
>
>I can understand that maybe there are missing entries in the mobilink tables
>but I don't exactly which ones should I alter. and how!! (maybe mobilink
>stored procedures??)
>
>Anyway I will need some guidance in that subject so if there is a standard
>procedure for that please inform me.
>
>Kind Regards
>D
>

--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com

Greg Fenton

2005-06-17, 9:24 am

Breck Carter [TeamSybase] wrote:
>
> However, to ensure better service, please *start* your message with a
> simple question of the form "How do I <do some thing or fix some
> symptom>?"
>

Also, with every new thread please post the version and build number of
ML that you are using and where appropriate the type, version and build
number of your remotes and your consolidated.

greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/

Sponsored Links