SQL Anywhere database replication - DBUnload.exe with Mobilink

Author

DBUnload.exe with Mobilink

Walt Tallman

2005-08-26, 1:23 pm

We are storing a significant number of BLOBS in ASA remote
database. The log files get renamed after reaching 1 gig.
When using dbunload to reduce filesize of database, in some
cases upto 500 megabytes, the renamed log files point to an
offset the no longer exist in the rebuilt database.

command lines as follows:

dbunload -c "dsn=[dsn name]" - ar 'rebuild and replace
database

the application can still use the database, but the end user
can no longer sync because of offset issue.

Is there a way to rebuild a database, to reduce file size,
and retain log offsets?

Reg Domaratzki \(iAnywhere Solutions\)

2005-08-29, 9:23 am

You need to specify a location for old log files when running dbunload -ar
on a replicating or synchronizing database.

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

<Walt Tallman> wrote in message news:430f5b91.29f9.1681692777@sybase.com...
> We are storing a significant number of BLOBS in ASA remote
> database. The log files get renamed after reaching 1 gig.
> When using dbunload to reduce filesize of database, in some
> cases upto 500 megabytes, the renamed log files point to an
> offset the no longer exist in the rebuilt database.
>
> command lines as follows:
>
> dbunload -c "dsn=[dsn name]" - ar 'rebuild and replace
> database
>
> the application can still use the database, but the end user
> can no longer sync because of offset issue.
>
> Is there a way to rebuild a database, to reduce file size,
> and retain log offsets?

Sponsored Links