Sybase 9.0.2.3534

How do I truncate a transaction log for a database involved
in Mobilink Replication? I need to know this for the
consolidated database and the publishing database.

Thanks

Herman,

There are two considerations here. For the consolidated database, there is no dependency on the
transaction log for MobiLink synchronization. Maintaining the transaction log size can be done using
an appropriate backup and recovery method. If you're going to truncate the consolidated database
transaction log, then you should make a backup of the transaction log for recovery purposes.

For the remote database, NEVER EVER truncate a transaction log. Truncating the transaction log will
break MobiLink synchronization. The transaction log is used to scan and generate the uploads. For
transaction log management you should rename and restart the transaction log. However, you may still
require the old transaction log as there may be operations that have yet to be synchronized. This
may require you to specify the location of old transaction log on the dbmlsync command line.

One option for managing the transaction log size for the remote database is by using dbmlsync -x
[size [K|M|G]] and then setting DELETE_OLD_LOGS option to ON. Each time dbmlsync runs, provided the
size of the transaction log meets the criteria, the transaction log will be renamed and restarted.
With the DELETE_OLD_LOGS option set to ON, when the transaction log is no longer required for
MobiLink synchronization, the log is removed automatically.

http://www.ianywhere.com/developer/p...9/00000169.htm

--
Joshua Savill
Sybase Inc. - Product Manager


Herman wrote:

We use Mobilink to send certain transaction down from the
consolidated database to the clients. Can we still truncate
the transaction log with no effect on Mobilink?

Thanks

MobiLink has no dependency on the transaction log with the consolidated database. So, you can
truncate the transaction log on the consolidated database. However, you should be truncating the
transaction log as part of your Backup and Recovery strategy because the transaction log is still
require for recovery.

--
Joshua Savill
Sybase Inc. - Product Manager


Herman Miller wrote:

If I understand your point regarding the consolidated db not
using the transaction log then the following statement will
send all rows from the consolidated db down to the remote db
regardless when the transaction occurred:

select * from table where ? IS NOT NULL And user_id= ?

is this correct?

Thanks

Correct.

--
Joshua Savill
Sybase Inc. - Product Manager


Herman Miller wrote:

Well correct in the sense that any row meeting the criteria of the SELECT statement will be sent to
the remote database.

--
Joshua Savill
Sybase Inc. - Product Manager


Josh Savill [Sybase] wrote: