Hi we are using sql anywhere 11.x and mobilink with -x option . it generates lot of log files while in sync whereas in sql ver 10.x renaming of the log files occurs only once until the mobilink remote restarted again... is there any behavioral change in ver 11.x? regards. |
I can't think of any behaviour change that would increase the frequency with which transaction logs are renamed from v10 to v11. When you changed versions, but you possibly change to running in continuous mode (i.e. specified a schedule in the extended options) ? You might consider adding a parameter to the -x switch. Instead of just saying "-x", which will rename and restart the transaction log after each send of data to the consolidated, consider using something like "-x 2M", which will only rename and restart the transaction log if the size is greater than 2 megabytes. answered 08 Jan '13, 08:45 Reg Domaratzki thanks Reg.. yes I am running in continuous mode by specifying schedule in extended option in both v10 and v11 with same switches and parameter. why v11 renames the logs in every sync whereas v10 only rename the logs on dbmlsync restart ?
(08 Jan '13, 20:53)
vhm
|
Please provide your full MobiLink start-line and exact version of MobiLink you are running. (e.g. 11.0.1.2913)
Do you mean "mobilink with -x option" or "dbmlsync with -x option"?
When you say "log files", are you referring to the transaction log associated with the database file, or the output logs generated by dbmlsync/mobilink?
version 11.0.1.2044
I am referring to dbmlsync with -x option rename the log files associated with database file .