SQL Anywhere Mobile - MobiLink bad offset error

Author

MobiLink bad offset error

Doug

2005-06-22, 9:24 am

We are using MobiLink 7.0.313. We are consistently getting the following
error messages from some of our sites when attempting a synchronizatrion:
[color=darkred]

Upon further investigation we have discovered that our remote log file is
being truncated! And we have realized that our application has a menu option
that allows the user to backup the database using the 'BACKUP DATABASE'
command. The only parameter used for this command other than the backup
directory is 'TRANSACTION LOG RENAME MATCH'.

Does this option cause a truncation of the log file? Nothing I can find says
it does but I really need to eliminate it as a source of our log truncation
issue.

Reg Domaratzki $iAnywhere Solutions$

2005-06-22, 9:24 am

No, this command is renaming the log file, not truncating it.

What is your dbmlsync start line? You may need to specify the location of
the renamed logs on the dbmlsync command line.

--
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

"Doug" < doogie414removethis@
yahoo.com> wrote in message
news:42b96f80$1@foru
ms-1-dub...
> We are using MobiLink 7.0.313. We are consistently getting the following
> error messages from some of our sites when attempting a synchronizatrion:
>
>
> Upon further investigation we have discovered that our remote log file is
> being truncated! And we have realized that our application has a menu
option
> that allows the user to backup the database using the 'BACKUP DATABASE'
> command. The only parameter used for this command other than the backup
> directory is 'TRANSACTION LOG RENAME MATCH'.
>
> Does this option cause a truncation of the log file? Nothing I can find
says
> it does but I really need to eliminate it as a source of our log
truncation
> issue.
>
>
>

Doug

2005-06-22, 9:24 am

dbmlsync start line is as follows:

dbmlsync.exe -c " dbn=mydb;uid=dba;pwd
=sql99" -n "syncname" -v -k -e
"memory=16M" -os 2M -o d:\mobilink\logs\myd
b\synclog.txt -r

Looks like there is nothing there to specify the location of the renamed log
files. But why is the log starting over after a backup? Is that the default
behaviour? We are backing up other ASA 7 databases in the same engine with
'BACKUP DATABASE' and those logs aren't being 'reset'. I'm confused.

"Reg Domaratzki (iAnywhere Solutions)" <FirstName.LastName@ianywhere.com>
wrote in message news:42b9706c$1@foru
ms-1-dub...
> No, this command is renaming the log file, not truncating it.
>
> What is your dbmlsync start line? You may need to specify the location of
> the renamed logs on the dbmlsync command line.
>
> --
> 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
>
> "Doug" < doogie414removethis@
yahoo.com> wrote in message
> news:42b96f80$1@foru
ms-1-dub...
synchronizatrion:[co
lor=darkred]
is[color=darkred]
> option
> says
> truncation
>
>

Reg Domaratzki $iAnywhere Solutions$

2005-06-22, 9:24 am

This is the clause on the backup command that is renaming your current
transaction log :

'TRANSACTION LOG RENAME MATCH'

With this clause, the backup directory you specify ends up with a log file,
and the current active transaction log also gets a renamed copy. I suspect
that if you add the directory where the current transaction log resides to
the end of the dbmlsync command line, your problems will go away.

--
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

"Doug" < doogie414removethis@
yahoo.com> wrote in message
news:42b9725e@forums
-1-dub...
> dbmlsync start line is as follows:
>
> dbmlsync.exe -c " dbn=mydb;uid=dba;pwd
=sql99" -n "syncname" -v -k -e
> "memory=16M" -os 2M -o d:\mobilink\logs\myd
b\synclog.txt -r
>
> Looks like there is nothing there to specify the location of the renamed
log
> files. But why is the log starting over after a backup? Is that the
default
> behaviour? We are backing up other ASA 7 databases in the same engine with
> 'BACKUP DATABASE' and those logs aren't being 'reset'. I'm confused.
>
> "Reg Domaratzki (iAnywhere Solutions)" <FirstName.LastName@ianywhere.com>
> wrote in message news:42b9706c$1@foru
ms-1-dub...
of[color=darkred]
> http://www.ianywhere.com/developer/product_manuals
following[color=dark
red]
> synchronizatrion:
> is
DATABASE'[color=dark
red]
backup[color=darkred
]
find[color=darkred]
>
>

Sponsored Links