SQL Anywhere Mobile - How do I reset a log file of my remote/consolidated?

Author

How do I reset a log file of my remote/consolidated?

Ignacio Mateos

2005-05-03, 1:24 pm

Hi to all:

My log files are getting huge in the consolidated and remote sides.

How do I reset them?

Also, I need to start with a clean slate from time to time (empty the recors
in the consolidated and remote, keep the structure and the publications,
reset the logs) to start a new function.

What is the best way to do this? (It seems that every time I touch something
the sync process fails).

Regards

David Fishburn

2005-05-03, 8:24 pm

"Ignacio Mateos" <imateos@telefonica.net> wrote in
news:4277b802$1@foru
ms-2-dub of sybase.public.sqlanywhere.mobilink:

IM> My log files are getting huge in the consolidated and remote sides.
IM> How do I reset them?

You can run with dbmlsrv9 -os 5m -o ml.txt
This will rename the file when it reaches 5M for you automatically.

This works for both the MobiLink server and the client (dbmlsync).

IM> Also, I need to start with a clean slate from time to time (empty the
IM> recors in the consolidated and remote, keep the structure and the
IM> publications, reset the logs) to start a new function.
IM>
IM> What is the best way to do this? (It seems that every time I touch
IM> something the sync process fails).

Easiest way is to:
1. Make sure you are using 9.0.2 and later (for the MobiLink server).
2. Drop the sync subscription, delete the records, create the sync
subscription and start synchronizing again.

That should work just fine.
In 9.0.1 and below, you would have received a progress mismatch error.
So if you are using 9.0.1 and below, after dropping the subscription you
would have to run dbmluser -d to drop that user from the ML server at
the consolidated database (to prevent the mismatch error).

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

Greg Fenton

2005-05-04, 3:25 am

Ignacio Mateos wrote:
>
> My log files are getting huge in the consolidated and remote sides.
>

Do you mean the logs created by the ML client (dbmlsync) and server
(dbmlsrv9) or by the ASA transaction logs (typically <dbname>.log) ?

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

Ignacio Mateos

2005-05-04, 7:24 am

I mean the asa logs...

"Greg Fenton" <greg. fenton_NOSPAM_@ianyw
here.com> escribió en el mensaje
news:42782a23$1@foru
ms-2-dub...
> Ignacio Mateos wrote:
>
> Do you mean the logs created by the ML client (dbmlsync) and server
> (dbmlsrv9) or by the ASA transaction logs (typically <dbname>.log) ?
>
> greg.fenton
> --
> Greg Fenton
> Consultant, Solution Services, iAnywhere Solutions
> --------
> Visit the iAnywhere Solutions Developer Community
> Whitepapers, TechDocs, Downloads
> http://www.ianywhere.com/developer/

David Fishburn

2005-05-04, 9:24 am

"Ignacio Mateos" <imateos@telefonica.net> wrote in news:42789659$1
@forums-1-dub
of sybase.public.sqlanywhere.mobilink:

IM> I mean the asa logs...

Ahh, that is different.

First, for the consolidated you must *always* have a proper backup and
recovery procedure in place. Make sure you read this section of the
documentation (I am referencing 9.0.2):

ASA Database Administration Guide
Backup and Data Recovery

The transaction log of the *CONSOLIDATED* database (if it is ASA) is not
used by the MobiLink server. Whereas the remote database transaction
logs ARE scanned by dbmlsync and are critical for synchronization to
succeed.

To control log growth in the *remote* databases, you can read this
section:
SQL Remote User's Guide
Administering SQL Remote for Adaptive Server Anywhere
Transaction log and backup management

SQL Remote and MobiLink (for the remotes) both scan the transaction log.
So the concepts listed here are identical for both.

In the simpliest case you can do this:
1. In all the remotes:
SET OPTION PUBLIC.DELETE_OLD_LOGS = 'ON'
2. dbmlsync -x 5m

This will rename the ASA transaction log when it gets larger than 5M.
With the DELETE_OLD_LOGS option set, dbmlsync will automatically delete
the renamed transaction logs (and thus freeing the space) when the
consolidated have *verified* receipt of all the transactions.

Depending on your situation, you may want to get more complicated, but
we would need more information to make any recommendations.

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

Ignacio Mateos

2005-05-04, 9:24 am

Thanks very much, that sounds like a good starting point.

"David Fishburn" <fishburn_spam@off.ianywhere.com> escribió en el mensaje
news:Xns964C67923282
0fishburnsybasecom@1
27.0.0.1...
> "Ignacio Mateos" <imateos@telefonica.net> wrote in news:42789659$1
> @forums-1-dub
> of sybase.public.sqlanywhere.mobilink:
>
> IM> I mean the asa logs...
>
> Ahh, that is different.
>
> First, for the consolidated you must *always* have a proper backup and
> recovery procedure in place. Make sure you read this section of the
> documentation (I am referencing 9.0.2):
>
> ASA Database Administration Guide
> Backup and Data Recovery
>
> The transaction log of the *CONSOLIDATED* database (if it is ASA) is not
> used by the MobiLink server. Whereas the remote database transaction
> logs ARE scanned by dbmlsync and are critical for synchronization to
> succeed.
>
> To control log growth in the *remote* databases, you can read this
> section:
> SQL Remote User's Guide
> Administering SQL Remote for Adaptive Server Anywhere
> Transaction log and backup management
>
> SQL Remote and MobiLink (for the remotes) both scan the transaction log.
> So the concepts listed here are identical for both.
>
> In the simpliest case you can do this:
> 1. In all the remotes:
> SET OPTION PUBLIC.DELETE_OLD_LOGS = 'ON'
> 2. dbmlsync -x 5m
>
> This will rename the ASA transaction log when it gets larger than 5M.
> With the DELETE_OLD_LOGS option set, dbmlsync will automatically delete
> the renamed transaction logs (and thus freeing the space) when the
> consolidated have *verified* receipt of all the transactions.
>
>
> Depending on your situation, you may want to get more complicated, but
> we would need more information to make any recommendations.
>
>
> --
> 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]
>

RAY

2005-05-05, 11:24 am

I have two consolidates and one remote, one of the consolidate uses
tradational replication from Sybase ASA (consolidate -1) to Sybase ASA
(Remote -1) and the other one uses Mobilink Synchronization from Sybase ASA
(Remote -1) to Oracle 9i (Consolidate - 2). Can I still use the folloing
logic to Rename and/or to delete the log files?

RAY.

"David Fishburn" <fishburn_spam@off.ianywhere.com> wrote in message
news:Xns964C67923282
0fishburnsybasecom@1
27.0.0.1...
> "Ignacio Mateos" <imateos@telefonica.net> wrote in news:42789659$1
> @forums-1-dub
> of sybase.public.sqlanywhere.mobilink:
>
> IM> I mean the asa logs...
>
> Ahh, that is different.
>
> First, for the consolidated you must *always* have a proper backup and
> recovery procedure in place. Make sure you read this section of the
> documentation (I am referencing 9.0.2):
>
> ASA Database Administration Guide
> Backup and Data Recovery
>
> The transaction log of the *CONSOLIDATED* database (if it is ASA) is not
> used by the MobiLink server. Whereas the remote database transaction
> logs ARE scanned by dbmlsync and are critical for synchronization to
> succeed.
>
> To control log growth in the *remote* databases, you can read this
> section:
> SQL Remote User's Guide
> Administering SQL Remote for Adaptive Server Anywhere
> Transaction log and backup management
>
> SQL Remote and MobiLink (for the remotes) both scan the transaction log.
> So the concepts listed here are identical for both.
>
> In the simpliest case you can do this:
> 1. In all the remotes:
> SET OPTION PUBLIC.DELETE_OLD_LOGS = 'ON'
> 2. dbmlsync -x 5m
>
> This will rename the ASA transaction log when it gets larger than 5M.
> With the DELETE_OLD_LOGS option set, dbmlsync will automatically delete
> the renamed transaction logs (and thus freeing the space) when the
> consolidated have *verified* receipt of all the transactions.
>
>
> Depending on your situation, you may want to get more complicated, but
> we would need more information to make any recommendations.
>
>
> --
> 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]
>

David Fishburn

2005-05-05, 11:24 am

"RAY" <s. rayala@stanleyassoci
ates.com> wrote in
news:427a3b11$1@foru
ms-1-dub of sybase.public.sqlanywhere.mobilink:

R> I have two consolidates and one remote, one of the consolidate uses
R> tradational replication from Sybase ASA (consolidate -1) to Sybase ASA
R> (Remote -1) and the other one uses Mobilink Synchronization from
R> Sybase ASA (Remote -1) to Oracle 9i (Consolidate - 2). Can I still use
R> the folloing logic to Rename and/or to delete the log files?

Yes.

dbmlsync, dbremote and dbltm all work together to determine if the log
can in fact be deleted.

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

Sponsored Links