MSSQL Dataserver logfile messages

disk0

New Member
Hi all,

I have an OE10.2B win client connecting to a MS SQL database (v08.00.2171) using the OE DataServer connection method.
Over the last couple of weeks the following messages are appearing in the dataserv.lg file and are filling up the log file at the rate of almost 100MB per day!

Here is just a small sample - there are literally thousands of these...
[10/10/12@20:05:26.783+1000] P-007712 T-007224 2 MSS CURSOR Pcurs=0x175a70c <7>[6] cli_cur#1
[10/10/12@20:05:26.799+1000] P-007712 T-007224 2 MSS CURSOR Pcurs=0x175aa9c <9>[8] cli_cur#1
[10/10/12@20:05:26.799+1000] P-007712 T-007224 2 MSS CURSOR Pcurs=0x175ae2c <11>[10] cli_cur#1
[10/10/12@20:05:26.799+1000] P-007712 T-007224 2 MSS CURSOR Pcurs=0x170aa14 <4>[3] cli_cur#1
[10/10/12@20:05:26.799+1000] P-007712 T-007224 2 MSS CURSOR Pcurs=0x175a70c <7>[6] cli_cur#1
[10/10/12@20:05:26.799+1000] P-007712 T-007224 2 MSS CURSOR Pcurs=0x175aa9c <9>[8] cli_cur#1
[10/10/12@20:05:26.799+1000] P-007712 T-007224 2 MSS CURSOR Pcurs=0x175ae2c <11>[10] cli_cur#1
[10/10/12@20:05:27.314+1000] P-007712 T-007224 2 MSS CURSOR Pcurs=0x170aa14 <4>[3] cli_cur#1
[10/10/12@20:05:27.314+1000] P-007712 T-007224 2 MSS CURSOR Pcurs=0x175a70c <7>[6] cli_cur#1
[10/10/12@20:05:27.314+1000] P-007712 T-007224 2 MSS CURSOR Pcurs=0x175aa9c <9>[8] cli_cur#1
[10/10/12@20:05:27.314+1000] P-007712 T-007224 2 MSS CURSOR Pcurs=0x175ae2c <11>[10] cli_cur#1
[10/10/12@20:05:27.314+1000] P-007712 T-007224 2 MSS CURSOR Pcurs=0x170aa14 <4>[3] cli_cur#1
[10/10/12@20:05:27.330+1000] P-007712 T-007224 2 MSS CURSOR Pcurs=0x175a70c <7>[6] cli_cur#1


As you can see a message is genereated every millisecond, and I am guessing i get one for every hit of the SQL db?

This has only started happening since moving from 10.1B to 10.2B client.
Does anyone know what these messages mean and how I can remove them?
The program itself does not seem to be affected other then the performace has degraded by about 50% - probably due to the sheer amount of logging going on.

Any help appreciated,
Cheers
Dave Prosser
Pulse Mining Systems
Australia
 
I have not seen this kind of behavior before. Could it be the result of a DataServer logging parameter? For example -DSrv qt_debug,cursor ?
 
Thanks Stefan, I have checked this already and I have no debug options set. As I understand the default is to have no debugging at all.
Perhaps I need to be explicit and set the qt_no_debug option?!
 
Back
Top