dbTalk Databases Forums  

Cannot close the database in WinCE

sybase.public.sqlanywhere.mobilink sybase.public.sqlanywhere.mobilink


Discuss Cannot close the database in WinCE in the sybase.public.sqlanywhere.mobilink forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Ailin Org
 
Posts: n/a

Default Cannot close the database in WinCE - 01-16-2009 , 04:43 AM






Hi,

I am using SQL Anywhere 10.0.1.3415. When there is a error in the
synchronization, say wrong userid for synchronization, the database still
exists in the tray even if the program is terminated. Would you please
kindly advise how to shutdown the database ? And, I have accidentially
deleted the Log file and RID file of the database. Now, the mobilsync
complained that it could not synchronize the records. Please advise how I
can recover it. Thanks in advance.

Thanks!



Reply With Quote
  #2  
Old   
Reg Domaratzki (Sybase iAnywhere)
 
Posts: n/a

Default Re: Cannot close the database in WinCE - 01-16-2009 , 08:35 AM






"Ailin Org" <AilinOrg85322 (AT) yahoo (DOT) com> wrote in
news:497064bd$1@forums-1-dub:

Quote:
Hi,

I am using SQL Anywhere 10.0.1.3415. When there is a error in the
synchronization, say wrong userid for synchronization, the database
still exists in the tray even if the program is terminated. Would you
please kindly advise how to shutdown the database ?
There are two SQL Anywhere processes that run on the remote device. When
you say "the database still exists" do you mean dbmlsync or dbsrv10?

If it's dbmlsync that is still running, you can add the -k switch to the
dbmlsync start line to tell dbmlsync to shut down on completion, but if
an error occurs during the synchronization, the windows will not close
unless you have also redirected the dbmlsync output to a text file using
the -o or -ot switch. We refuse to shut down if the output is not
written to a text file since the open window is the only place you will
be able to see the error.

If it's dbsrv10 that is still running, then you should look into the
autostop connection parameter, so a shutdown of the DB Server will occur
when there are no more connections to the remote database. I suspect
you're actually talking about dbmlsync though.

Quote:
And, I have
accidentially deleted the Log file and RID file of the database. Now,
the mobilsync complained that it could not synchronize the records.
Please advise how I can recover it.
The RID file will be re-created, but dbmlsync relies on the transaction
log to determine what operations to send to the MobiLink server. If you
have deleted a transaction log that contained operations that had not
yet been sent to the MobiLink Server, you will NEVER be able to send
those
operations. If you are just in a test environment and those operations
are not important, you can drop and re-create the synchronization
subscription at the remote database, and dbmlsync will start to send
again
from the current log offset.


--
Reg Domaratzki, Sybase iAnywhere Solutions
Please reply only to the newsgroup

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Docs : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swd/base.do
-> Choose SQL Anywhere Studio
-> Set filter to "Display ALL platforms IN ALL MONTHS"



Reply With Quote
  #3  
Old   
David Fishburn
 
Posts: n/a

Default Re: Cannot close the database in WinCE - 01-16-2009 , 08:40 AM



"Ailin Org" <AilinOrg85322 (AT) yahoo (DOT) com> wrote in
news:497064bd$1@forums-1-dub of sybase.public.sqlanywhere.mobilink:

AO> I am using SQL Anywhere 10.0.1.3415. When there is a error in the
AO> synchronization, say wrong userid for synchronization, the database
AO> still exists in the tray even if the program is terminated. Would
you
AO> please kindly advise how to shutdown the database ?

Much of that depends on your dbmlsync command line.
Was the database already running before you started dbmlsync?
Or did dbmlsync autostart the database?
How does your application connect to the database.

AO> And, I have accidentially deleted the Log file and RID file of the
AO> database. Now, the mobilsync complained that it could not
AO> synchronize the records.
AO> Please advise how I can recover it.

Recover what exactly?

The database is still good, you can connect to it and perform
operations on it.

By deleting the LOG file, you have broken synchronization.
You can no longer synchronize any data in the remote.
The _only_ thing you can do now is:
1. Drop the SYNC SUBSCRIPTION
2. Create the SYNC SUBSCRIPTION

This of course means data will begin synchronizing from _this point_
forward. Any previous changes made to data will _not_ be uploaded.

You must never get rid of the SQL Anywhere transaction log manually.

If you do want to control the _size_ of those logs, then you should be
reading up on the Delete_old_logs database option. That is the only
safe way to manage the size of your remote database transaction logs.

--
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 (dbeng11 -v).

EBFs and Maintenance Releases
http://downloads.sybase.com/

Developer Community / Whitepapers
http://www.ianywhere.com/developer

Case-Express - to report bugs
http://case-express.sybase.com

CodeXchange - Free samples
http://ianywhere.codexchange.sybase....ctDocumentList

Documentation
http://dcx.sybase.com/


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.