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