SQL Anywhere Mobile - Remote Transaction log problem

Author

Remote Transaction log problem

Rebecca Snyder

2005-03-30, 9:43 am

ASA 9.0.2
Pocket PC
Pocketbuilder app.

First off, I'm a newbie to the mobile development world, so forgive my lack
of understanding.
I was working fine on my PDA, syncing the db and running my app. I'm just
in test mode.
I made a couple of db changes (added table, changed a column). I copied the
new db and log to my PDA using explorer. I seem to think that I used
dblog -t to redirect the log file to the PDA, but that isn't working for me
now. I can see the db start and it wants to use the transaction log on my
desktop (c: drive).
How can I redirect the transaction log after I copy a new version of the
remote db to my PDA? I cannot find what I'm looking for in the docs.

Thanks,
Becky Snyder
Bradley University.

Greg Fenton

2005-03-30, 9:43 am

Rebecca Snyder wrote:
> dblog -t to redirect the log file to the PDA, but that isn't working for me
> now. I can see the db start and it wants to use the transaction log on my
> desktop (c: drive).

It is likely that when you used "dblog -t" you specified the full path
to the .log file on your desktop system, and this is what is stored in
the .db file. So when the .db is started, it is trying to find the .log
at the full path provided.

You can specify a relative path when using "dblog -t" and it is that
relative path that will be used (relative to the location of the .db
file). If you leave a directory off altogether, the .log will be
created in the same dir as the .db:

dblog -t mydatabase.log mydatabase.db

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

Rebecca Snyder

2005-03-30, 9:43 am

Perfect - thank-you for your suggestion. It worked!

Becky

"Greg Fenton" <greg. fenton_NOSPAM_@ianyw
here.com> wrote in message
news:424241c2$1@foru
ms-2-dub...
> Rebecca Snyder wrote:
>
> It is likely that when you used "dblog -t" you specified the full path to
> the .log file on your desktop system, and this is what is stored in the
> .db file. So when the .db is started, it is trying to find the .log at
> the full path provided.
>
> You can specify a relative path when using "dblog -t" and it is that
> relative path that will be used (relative to the location of the .db
> file). If you leave a directory off altogether, the .log will be created
> in the same dir as the .db:
>
> dblog -t mydatabase.log mydatabase.db
>
> Hope this helps,
> 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