|
Home > Archive > SQL Anywhere Mobile > August 2005 > mobilink log sent, progress and currentredopos
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
mobilink log sent, progress and currentredopos
|
|
| Eric Verhorstert 2005-07-15, 7:24 am |
| After synchonization the values are:
SYS.SYSSYNC
created 1270966
sent 1272127
progress 1272127
db_property(CurrentR
edoPos) returns 11697539
Looking with db_log it return 11697560. This is probably different from
CurrentRedoPos because I closed the database.
I had expected that in the sys.syssync table I would find the value
11697539 or something nearby. In this way I can see if all information
is synchronized.
How can I see if the user has sent the last input to the consolidated
database?
Thanks
Eric
| |
| Reg Domaratzki \(iAnywhere Solutions\) 2005-07-15, 7:24 am |
| Did you rebuild this database? There's no way that the values you point out
in the SYSYSYNC table should be larger than the current log offset.
--
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
"Eric Verhorstert" <ontsnapt@hotmail.com> wrote in message
news:42d7a442@forums
-2-dub...
> After synchonization the values are:
>
> SYS.SYSSYNC
> created 1270966
> sent 1272127
> progress 1272127
>
> db_property(CurrentR
edoPos) returns 11697539
>
> Looking with db_log it return 11697560. This is probably different from
> CurrentRedoPos because I closed the database.
>
> I had expected that in the sys.syssync table I would find the value
> 11697539 or something nearby. In this way I can see if all information
> is synchronized.
>
> How can I see if the user has sent the last input to the consolidated
> database?
>
> Thanks
> Eric
| |
| Reg Domaratzki \(iAnywhere Solutions\) 2005-07-15, 9:23 am |
| Crap, ignore my last post, since I responded before my first coffee and
thought that your current log offset was in the 1.1 million byte range, and
not 11 million.
Here's a slightly more intelligent response :
There are always at least two rows in the SYSSYNC table, you need to make
sure you're looking at the row where publication_id and site_name and both
not NULL.
--
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
"Eric Verhorstert" <ontsnapt@hotmail.com> wrote in message
news:42d7a442@forums
-2-dub...
> After synchonization the values are:
>
> SYS.SYSSYNC
> created 1270966
> sent 1272127
> progress 1272127
>
> db_property(CurrentR
edoPos) returns 11697539
>
> Looking with db_log it return 11697560. This is probably different from
> CurrentRedoPos because I closed the database.
>
> I had expected that in the sys.syssync table I would find the value
> 11697539 or something nearby. In this way I can see if all information
> is synchronized.
>
> How can I see if the user has sent the last input to the consolidated
> database?
>
> Thanks
> Eric
| |
| Breck Carter [TeamSybase] 2005-07-15, 11:24 am |
| On 15 Jul 2005 07:00:16 -0700, "Reg Domaratzki \(iAnywhere
Solutions\)" <FirstName.LastName@ianywhere.com> wrote:
>I responded before my first coffee
Ohhhh, man, I've made *that* mistake before, I feel your pain :)
Breck
--
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
| |
| Eric Verhorstert 2005-07-18, 3:23 am |
| Yes, I looked at that row in the syssync table.
But I forgot that this was the first synchonization. During this
synchonization I upload nothing and download about 10 Mb. I think the
column "mobilink log sent" is filled before the download starts.
After the second synchronization log sent, log progress and
currentredopos are allmost the same.
Now I wonder if mobilink knows which records it received from the
consolidated. Since the value in log send is before the download and the
downloaded rows are not uploaded again accept when they are changed.
Thanks
Eric
Reg Domaratzki (iAnywhere Solutions) wrote:
> Crap, ignore my last post, since I responded before my first coffee and
> thought that your current log offset was in the 1.1 million byte range, and
> not 11 million.
>
> Here's a slightly more intelligent response :
>
> There are always at least two rows in the SYSSYNC table, you need to make
> sure you're looking at the row where publication_id and site_name and both
> not NULL.
>
| |
| Breck Carter [TeamSybase] 2005-07-18, 7:23 am |
| On 15 Jul 2005 07:00:16 -0700, "Reg Domaratzki \(iAnywhere
Solutions\)" <FirstName.LastName@ianywhere.com> wrote:
Eric asks a good question: How does dbmlsync avoid uploading rows that
were downloaded in the previous synchronization? These downloaded
changes could be intermingled in the log file, with changes made by
other remote database connections that *should* be uploaded.
Methinks there must be a magical relationship between dbmlsync.exe and
dbeng9.exe :)
Breck
--
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
| |
| David Fishburn 2005-08-18, 8:25 pm |
| "Breck Carter [TeamSybase]" < NOSPAM__bcarter@risi
ngroad.com> wrote in
news:4urmd1t4g2gi7al
779njsg0toqtsfsjnl1@
4ax.com of
sybase.public.sqlanywhere.mobilink:
BC> Eric asks a good question: How does dbmlsync avoid uploading rows
that
BC> were downloaded in the previous synchronization? These downloaded
BC> changes could be intermingled in the log file, with changes made by
BC> other remote database connections that *should* be uploaded.
BC>
BC> Methinks there must be a magical relationship between dbmlsync.exe
and
BC> dbeng9.exe :)
When dbmlsync is applying operations that were downloaded it places
additional information in the transaction log indicating this was part
of the download.
If you are using any of the sp_hook_dbmlsync procedures, this
information is removed while those execute (depending on the hook
possibly).
So yes, this is a magical relationship. This prevents circular
synchronization.
--
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]
|
|
|
|
|