James Marsh wrote:
Hi Hugh,
On Tue, Oct 27, 2009 at 15:33, Hugh Williams <[email protected]
<mailto:[email protected]>> wrote:
Can you please provide a copy of your Virtuoso Configuration file
(virtuoso.ini) and Virtuoso log file (virtuoso.log) for review.
The log shows nothing unusual - the usual startup/roll forward and then
nothing but checkpoints. I've included the ini at the end if this email.
I've not had tracing turned on before the point the problems occur yet.
Which trace_on arguments are most helpful in debugging? I could perhaps
leave them enabled in the ini file for a while.
From http://docs.openlinksw.com/virtuoso/fn_trace_on.html, you could leave
trace_on('errors') ticking away happily. It's useful, but verbose, to use
trace_on('exec') as well - may be best for interactive debugging. As for
other parameters, either you'll know you want them (maybe client_sql?) or
they pertain to the VDB layer.
[]
Should anymore deadlocks start occurring can you provide the output
of running the following query from the isql prompt:
select top 10 * from sys_l_stat order by deadlocks desc;
Will do.
And another trick to bear in mind: isql -D.
[]
Regards,
~Tim
--
Tim Haynes
Product Development Consultant, OpenLink Software
<http://www.openlinksw.com/> <http://twitter.com/openlink>
