Hi Alexander,
When the Virtuoso hang occurred, how did you stop server was this a graceful
shutdown or did you have to forcibly shut it down ? For the query(s) failing
can provide the output of running the "explain" function which compiles a query
and returns a description of that compilation as a result set, return value or
parse tree, as detailed at:
http://docs.openlinksw.com/virtuoso/fn_explain.html
It would also be useful to have a copy of your virtuoso.log file to see it
their may been any errors reported in this log that might be associated with
the failure to the clear the graph. Running the RDF_AUDIT_METADATA function
also seems prudent as this can detect and clean up any Metsdata corruption in
the RDF data, as detailed at:
http://docs.openlinksw.com/virtuoso/fn_rdf_audit_metadata.html
Should these locks still be encountered then please run the Virtuoso "status()"
command from isql which will provide details of any locks in the system.
Best Regards
Hugh Williams
Professional Services
OpenLink Software
Web: http://www.openlinksw.com
Support: http://support.openlinksw.com
Forums: http://boards.openlinksw.com/support
Twitter: http://twitter.com/OpenLink
On 16 May 2010, at 13:44, Alexander Sidorov wrote:
> Hello!
>
> Virtuoso hanged during large graph clearing. I stopped Virtuoso, removed
> virtuoso.lck and started again. I am not sure whether graph was cleared or
> not but now all queries from this graph result in "S1T00 Error SR171:
> Transaction timed out". I need to reload dataset to this graph. Is there any
> way to remove transaction lock?
>
> Regards,
> Alexander
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Virtuoso-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
