|
Home > Archive > SQL Anywhere Mobile > March 2005 > dbmlsyncactivex.log
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
dbmlsyncactivex.log
|
|
| Dan Jablonski 2005-03-30, 9:43 am |
| TeamSybase,
We've recently upgraded to ASA 9.0.2 build(3044) and are surprised by a file
(dbmlsynactivex.log) that is showing up on our client machines in the root
directory named dbmlsynactivex.log. It is growing without bound. Almost 2G
on the client machine. It appends status information from subsequent
syncronizations. How do we turn this off?
Our server parameters are: -ps 20 -os 1M -o ml.log -tcpip
Our client dbmlsync9 parameters are -n pub_initialize,pub_s
tandard -u
CAS_142 -e sa=off; DBS=500K; st=off
Data within this file is referring to the Mobilink Server that is on another
machine. Here's a sample...
Thanks,
Dan
15:21:31 - Message callback 0 (Begin synchronizing
'pub_initialize,pub_
standard' for MobiLink user 'CAS_101')
15:21:31 - COMServer::Call opcode 200 datasize 0
15:21:31 - Status callback 101 (size 384)
15:21:31 - COMServer::Call opcode 200 datasize 0
15:21:31 - Message callback 5 (Processing remote transaction log ...)
15:21:31 - COMServer::Call opcode 200 datasize 0
15:21:31 - Status callback 102 (size 4)
15:21:31 - COMServer::Call opcode 200 datasize 0
15:21:31 - Message callback 1 (Log scan starting at offset 0067762168)
15:21:31 - COMServer::Call opcode 200 datasize 0
15:21:32 - Message callback 1 (Processing transaction logs from directory
"C:\Runtime\3.01\db\Field\")
15:21:32 - COMServer::Call opcode 200 datasize 0
15:21:32 - Message callback 1 (Deleted old log file
"C:\Runtime\3. 01\db\Field\050323AA
.LOG")
15:21:32 - COMServer::Call opcode 200 datasize 0
15:21:32 - Message callback 1 (Deleted old log file
"C:\Runtime\3. 01\db\Field\050323AB
.LOG")
15:21:32 - COMServer::Call opcode 200 datasize 0
15:21:32 - Message callback 1 (Deleted old log file
"C:\Runtime\3. 01\db\Field\050323AC
.LOG")
15:21:32 - COMServer::Call opcode 200 datasize 0
15:21:32 - Message callback 1 (Transaction log
"C:\Runtime\3. 01\db\Field\050323AD
.LOG" starts at offset 0067749770)
15:21:32 - COMServer::Call opcode 200 datasize 0
15:21:32 - Message callback 1 (Processing transactions from transaction log
"C:\Runtime\3. 01\db\Field\050323AD
.LOG")
15:21:32 - COMServer::Call opcode 200 datasize 0
15:21:32 - COMServer::Call opcode 200 datasize 0
15:21:32 - COMServer::Call opcode 200 datasize 0
| |
| Reg Domaratzki \(iAnywhere Solutions\) 2005-03-30, 9:43 am |
| Do I assume correctly that you are using the DBMLSync Integration Component
to launch dbmlsync?
It looks to me like this file should only be created when you are running
the debug version of the DBMLSync Integration Component. Did you download
v902.3044 from the Sybase download web site?
--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup
iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL
"Dan Jablonski" <djablonski@diginsp.com> wrote in message
news:42488611$1@foru
ms-1-dub...
> TeamSybase,
>
> We've recently upgraded to ASA 9.0.2 build(3044) and are surprised by a
file
> (dbmlsynactivex.log) that is showing up on our client machines in the
root
> directory named dbmlsynactivex.log. It is growing without bound. Almost
2G
> on the client machine. It appends status information from subsequent
> syncronizations. How do we turn this off?
>
> Our server parameters are: -ps 20 -os 1M -o ml.log -tcpip
>
> Our client dbmlsync9 parameters are -n pub_initialize,pub_s
tandard -u
> CAS_142 -e sa=off; DBS=500K; st=off
>
> Data within this file is referring to the Mobilink Server that is on
another
> machine. Here's a sample...
>
> Thanks,
> Dan
>
> 15:21:31 - Message callback 0 (Begin synchronizing
> 'pub_initialize,pub_
standard' for MobiLink user 'CAS_101')
> 15:21:31 - COMServer::Call opcode 200 datasize 0
> 15:21:31 - Status callback 101 (size 384)
> 15:21:31 - COMServer::Call opcode 200 datasize 0
> 15:21:31 - Message callback 5 (Processing remote transaction log ...)
> 15:21:31 - COMServer::Call opcode 200 datasize 0
> 15:21:31 - Status callback 102 (size 4)
> 15:21:31 - COMServer::Call opcode 200 datasize 0
> 15:21:31 - Message callback 1 (Log scan starting at offset 0067762168)
> 15:21:31 - COMServer::Call opcode 200 datasize 0
> 15:21:32 - Message callback 1 (Processing transaction logs from directory
> "C:\Runtime\3.01\db\Field\")
> 15:21:32 - COMServer::Call opcode 200 datasize 0
> 15:21:32 - Message callback 1 (Deleted old log file
> "C:\Runtime\3. 01\db\Field\050323AA
.LOG")
> 15:21:32 - COMServer::Call opcode 200 datasize 0
> 15:21:32 - Message callback 1 (Deleted old log file
> "C:\Runtime\3. 01\db\Field\050323AB
.LOG")
> 15:21:32 - COMServer::Call opcode 200 datasize 0
> 15:21:32 - Message callback 1 (Deleted old log file
> "C:\Runtime\3. 01\db\Field\050323AC
.LOG")
> 15:21:32 - COMServer::Call opcode 200 datasize 0
> 15:21:32 - Message callback 1 (Transaction log
> "C:\Runtime\3. 01\db\Field\050323AD
.LOG" starts at offset 0067749770)
> 15:21:32 - COMServer::Call opcode 200 datasize 0
> 15:21:32 - Message callback 1 (Processing transactions from transaction
log
> "C:\Runtime\3. 01\db\Field\050323AD
.LOG")
> 15:21:32 - COMServer::Call opcode 200 datasize 0
> 15:21:32 - COMServer::Call opcode 200 datasize 0
> 15:21:32 - COMServer::Call opcode 200 datasize 0
>
>
>
| |
| Dan Jablonski 2005-03-30, 9:43 am |
| Reg,
We are using the visual integration component version to launch dbmlsync.
We downloaded the 3044-EBF from the Sybase web site.
Could the build that's on the web site be set to the debug mode?
Thanks,
Dan
"Reg Domaratzki (iAnywhere Solutions)" < Spam_bad_rdomarat@ia
nywhere.com>
wrote in message news:4249692a$1@foru
ms-1-dub...
> Do I assume correctly that you are using the DBMLSync Integration
> Component
> to launch dbmlsync?
> It looks to me like this file should only be created when you are running
> the debug version of the DBMLSync Integration Component. Did you download
> v902.3044 from the Sybase download web site?
>
> --
> Reg Domaratzki, Sybase iAnywhere Solutions
> Sybase Certified Professional - Sybase ASA Developer Version 8
> Please reply only to the newsgroup
>
> iAnywhere Developer Community : http://www.ianywhere.com/developer
> iAnywhere Documentation :
> http://www.ianywhere.com/developer/product_manuals
> ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
> -> Choose SQL Anywhere Studio
> -> Set "Platform Preview" and "Time Frame" to ALL
>
> "Dan Jablonski" <djablonski@diginsp.com> wrote in message
> news:42488611$1@foru
ms-1-dub...
> file
> root
> 2G
> another
> log
>
>
| |
| Reg Domaratzki \(iAnywhere Solutions\) 2005-03-30, 9:43 am |
| I'll look into that possibility.
--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup
iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL
"Dan Jablonski" <djablonski@diginsp.com> wrote in message
news:42498336$1@foru
ms-1-dub...
> Reg,
>
> We are using the visual integration component version to launch dbmlsync.
>
> We downloaded the 3044-EBF from the Sybase web site.
>
> Could the build that's on the web site be set to the debug mode?
>
> Thanks,
> Dan
>
> "Reg Domaratzki (iAnywhere Solutions)" < Spam_bad_rdomarat@ia
nywhere.com>
> wrote in message news:4249692a$1@foru
ms-1-dub...
running[color=darkre
d]
download[color=darkr
ed]
Almost[color=darkred
]
directory[color=dark
red]
>
>
| |
| Reg Domaratzki \(iAnywhere Solutions\) 2005-03-30, 9:43 am |
| Yeah, the debug flag looks to be active in the production versions of
dbmlsynccom.dll and dbmlsynccomg.dll from our website. For now, it's OK to
delete the file, then create a new (empty if you want) file at the root of
the C: drive (or at \\ on CE devices) called dbmlsynactivex.log with the
read-only attribute set. I'll fix this up for the next EBF.
--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup
iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL
"Dan Jablonski" <djablonski@diginsp.com> wrote in message
news:42498336$1@foru
ms-1-dub...
> Reg,
>
> We are using the visual integration component version to launch dbmlsync.
>
> We downloaded the 3044-EBF from the Sybase web site.
>
> Could the build that's on the web site be set to the debug mode?
>
> Thanks,
> Dan
>
> "Reg Domaratzki (iAnywhere Solutions)" < Spam_bad_rdomarat@ia
nywhere.com>
> wrote in message news:4249692a$1@foru
ms-1-dub...
running[color=darkre
d]
download[color=darkr
ed]
Almost[color=darkred
]
directory[color=dark
red]
>
>
| |
| Reg Domaratzki \(iAnywhere Solutions\) 2005-03-30, 9:43 am |
| Dan, did you just start using the dbmlsync integration component after
upgrading to v902? From what I can see, we've always been creating this log
since v901 GA, which is when the feature was introduced.
--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup
iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL
"Dan Jablonski" <djablonski@diginsp.com> wrote in message
news:42498336$1@foru
ms-1-dub...
> Reg,
>
> We are using the visual integration component version to launch dbmlsync.
>
> We downloaded the 3044-EBF from the Sybase web site.
>
> Could the build that's on the web site be set to the debug mode?
>
> Thanks,
> Dan
>
> "Reg Domaratzki (iAnywhere Solutions)" < Spam_bad_rdomarat@ia
nywhere.com>
> wrote in message news:4249692a$1@foru
ms-1-dub...
running[color=darkre
d]
download[color=darkr
ed]
Almost[color=darkred
]
directory[color=dark
red]
>
>
| |
| Dan Jablonski 2005-03-30, 9:43 am |
| How much does writting this log effect performance?
When can we expect the next EBF?
"Reg Domaratzki (iAnywhere Solutions)" < Spam_bad_rdomarat@ia
nywhere.com>
wrote in message news:4249a155$1@foru
ms-1-dub...
> Yeah, the debug flag looks to be active in the production versions of
> dbmlsynccom.dll and dbmlsynccomg.dll from our website. For now, it's OK
> to
> delete the file, then create a new (empty if you want) file at the root of
> the C: drive (or at \\ on CE devices) called dbmlsynactivex.log with the
> read-only attribute set. I'll fix this up for the next EBF.
>
> --
> Reg Domaratzki, Sybase iAnywhere Solutions
> Sybase Certified Professional - Sybase ASA Developer Version 8
> Please reply only to the newsgroup
>
> iAnywhere Developer Community : http://www.ianywhere.com/developer
> iAnywhere Documentation :
> http://www.ianywhere.com/developer/product_manuals
> ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
> -> Choose SQL Anywhere Studio
> -> Set "Platform Preview" and "Time Frame" to ALL
>
> "Dan Jablonski" <djablonski@diginsp.com> wrote in message
> news:42498336$1@foru
ms-1-dub...
> running
> download
> Almost
> directory
>
>
| |
| Dan Jablonski 2005-03-30, 9:43 am |
| Since writting you, we went back to the 9.0.1 implementation and saw it
there also also. But the log isn't something that we see as valuable and it
may cause problems in some remote sites that try to lock down their root
directory.
"Reg Domaratzki (iAnywhere Solutions)" < Spam_bad_rdomarat@ia
nywhere.com>
wrote in message news:4249b3b2$1@foru
ms-1-dub...
> Dan, did you just start using the dbmlsync integration component after
> upgrading to v902? From what I can see, we've always been creating this
> log
> since v901 GA, which is when the feature was introduced.
>
> --
> Reg Domaratzki, Sybase iAnywhere Solutions
> Sybase Certified Professional - Sybase ASA Developer Version 8
> Please reply only to the newsgroup
>
> iAnywhere Developer Community : http://www.ianywhere.com/developer
> iAnywhere Documentation :
> http://www.ianywhere.com/developer/product_manuals
> ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
> -> Choose SQL Anywhere Studio
> -> Set "Platform Preview" and "Time Frame" to ALL
>
> "Dan Jablonski" <djablonski@diginsp.com> wrote in message
> news:42498336$1@foru
ms-1-dub...
> running
> download
> Almost
> directory
>
>
| |
| Reg Domaratzki \(iAnywhere Solutions\) 2005-03-30, 7:05 pm |
| The creation of the log is definitely a bug. It should only be created when
a developer compiles the debug version of the dbmlsync integration component
on their own machine and uses that version. I figured out why the log is
being created and will check in the change today or tomorrow. The "feature"
I'm talking about in my last post was the dbmlsync integration component,
not the log.
--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup
iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL
"Dan Jablonski" <djablonski@diginsp.com> wrote in message
news:4249c873$1@foru
ms-1-dub...
> Since writting you, we went back to the 9.0.1 implementation and saw it
> there also also. But the log isn't something that we see as valuable and
it
> may cause problems in some remote sites that try to lock down their root
> directory.
>
> "Reg Domaratzki (iAnywhere Solutions)" < Spam_bad_rdomarat@ia
nywhere.com>
> wrote in message news:4249b3b2$1@foru
ms-1-dub...
dbmlsync.[color=darkred]
< Spam_bad_rdomarat@ia
nywhere.com>[color=darkred]
by[color=darkred]
the[color=darkred]
pub_initialize,pub_s
tandard -u[color=darkred]
....)[color=darkred]
0067762168)[color=da
rkred]
>
>
| |
| Reg Domaratzki \(iAnywhere Solutions\) 2005-03-30, 7:05 pm |
| The effect on performance is simply how long it would take that machine to
write that amount of data to the disk. That will be different on every
single machine, and will be different for each synch.
There are too many variables involved in the QA process to give an estimate
on when a 902 EBF will be available. I'll post back to this thread with the
build number you should be looking for when I check in the change.
--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup
iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL
"Dan Jablonski" <djablonski@diginsp.com> wrote in message
news:4249c768$1@foru
ms-1-dub...
> How much does writting this log effect performance?
>
> When can we expect the next EBF?
>
> "Reg Domaratzki (iAnywhere Solutions)" < Spam_bad_rdomarat@ia
nywhere.com>
> wrote in message news:4249a155$1@foru
ms-1-dub...
of[color=darkred]
dbmlsync.[color=darkred]
< Spam_bad_rdomarat@ia
nywhere.com>[color=darkred]
by[color=darkred]
the[color=darkred]
pub_initialize,pub_s
tandard -u[color=darkred]
....)[color=darkred]
0067762168)[color=da
rkred]
>
>
| |
| Reg Domaratzki \(iAnywhere Solutions\) 2005-03-30, 7:05 pm |
| Fixed in v901.2007 and v902.3105. The file will no longer be created.
--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup
iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL
"Reg Domaratzki (iAnywhere Solutions)" < Spam_bad_rdomarat@ia
nywhere.com>
wrote in message news:424b0416$1@foru
ms-2-dub...
> The effect on performance is simply how long it would take that machine to
> write that amount of data to the disk. That will be different on every
> single machine, and will be different for each synch.
>
> There are too many variables involved in the QA process to give an
estimate
> on when a 902 EBF will be available. I'll post back to this thread with
the
> build number you should be looking for when I check in the change.
>
> --
> Reg Domaratzki, Sybase iAnywhere Solutions
> Sybase Certified Professional - Sybase ASA Developer Version 8
> Please reply only to the newsgroup
>
> iAnywhere Developer Community : http://www.ianywhere.com/developer
> iAnywhere Documentation :
http://www.ianywhere.com/developer/product_manuals
> ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
> -> Choose SQL Anywhere Studio
> -> Set "Platform Preview" and "Time Frame" to ALL
>
> "Dan Jablonski" <djablonski@diginsp.com> wrote in message
> news:4249c768$1@foru
ms-1-dub...
OK[color=darkred]
root[color=darkred]
> of
the[color=darkred]
> dbmlsync.
> < Spam_bad_rdomarat@ia
nywhere.com>
> by
> the
subsequent[color=dar
kred]
> pub_initialize,pub_s
tandard -u
on[color=darkred]
> ...)
> 0067762168)
0067749770)[color=da
rkred]
>
>
| |
| Dan Jablonski 2005-03-30, 7:05 pm |
| Thanks for the explanation Reg.
Dan
"Reg Domaratzki (iAnywhere Solutions)" < Spam_bad_rdomarat@ia
nywhere.com>
wrote in message news:424b0344$1@foru
ms-2-dub...
> The creation of the log is definitely a bug. It should only be created
> when
> a developer compiles the debug version of the dbmlsync integration
> component
> on their own machine and uses that version. I figured out why the log is
> being created and will check in the change today or tomorrow. The
> "feature"
> I'm talking about in my last post was the dbmlsync integration component,
> not the log.
>
> --
> Reg Domaratzki, Sybase iAnywhere Solutions
> Sybase Certified Professional - Sybase ASA Developer Version 8
> Please reply only to the newsgroup
>
> iAnywhere Developer Community : http://www.ianywhere.com/developer
> iAnywhere Documentation :
> http://www.ianywhere.com/developer/product_manuals
> ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
> -> Choose SQL Anywhere Studio
> -> Set "Platform Preview" and "Time Frame" to ALL
>
> "Dan Jablonski" <djablonski@diginsp.com> wrote in message
> news:4249c873$1@foru
ms-1-dub...
> it
> dbmlsync.
> < Spam_bad_rdomarat@ia
nywhere.com>
> by
> the
> pub_initialize,pub_s
tandard -u
> ...)
> 0067762168)
>
>
|
|
|
|
|