Hi Greg,
Was the data reloaded using this updated 6.1.3 binary or was the existing
database file used ie that was loaded with the 6.1.2 binary ? As I would
suggest reloading the data into a new empty database using the 6.1.3 binary,
then try to dump the graphs.
Best Regards
Hugh Williams
On Aug 22, 2011, at 8:58 PM, Hugh Williams wrote:
Hi Greg,
Was the data reloaded using this updated 6.1.3 binary or was the existing
database file used ie that was loaded with the 6.1.2 binary ? As I would
suggest reloading the data into a new empty database using the 6.1.3 binary,
then
Hi Greg,
True, bit of a catch 22 situation then ...
What is the triple count in the Virtuoso Quad Store you are seeking to dump and
how was this data loaded originally ?
If the data cannot readily be reloaded from its original sources, then maybe a
full database dump to log and restore
Hi Greg,
Please make sure the 'env' variable in dump_one_graph procedure is initialized
as :
env := vector (dict_new (16000), 0, '', '', '', 0, 0, 0, 0);
Also you can take the procedure from attached script.
Best Regards,
Mitko
dg.sql
Description: Binary data
On Aug 23, 2011, at 12:10
On Aug 23, 2011, at 3:49 AM, Mitko Iliev wrote:
Hi Greg,
Please make sure the 'env' variable in dump_one_graph procedure is
initialized as :
env := vector (dict_new (16000), 0, '', '', '', 0, 0, 0, 0);
Also you can take the procedure from attached script.
Hi Mitko,
After recovering
On Aug 23, 2011, at 4:05 PM, Mitko Iliev wrote:
Hi Greg,
Please enable the CallstackOnException = 1 in the virtuoso.ini [Parameters]
section , then execute the dump_graphs () and send me the call-stack included
in the error string.
Hi Mitko,
Perhaps this isn't bad data but a heisenbug?
Hi Greg,
Please enable the CallstackOnException = 1 in the virtuoso.ini [Parameters]
section , then execute the dump_graphs () and send me the call-stack included
in the error string.
Best Regards,
Mitko
On Aug 23, 2011, at 11:00 PM, Gregory Williams wrote:
On Aug 23, 2011, at 3:49 AM,
On Aug 21, 2011, at 8:46 AM, Hugh Williams wrote:
Looking at the version 6.1.2 you report as being used and based on Ivan's
(who wrote these procedures) comment I would suggest you database be upgraded
to the latest 6.1.3 release to use these procedures. The latest 6.1.3
snapshot can be
Hi Greg,
The error implies that there is a bad triple in one of the graphs being
dumped, can you please check the “virtuoso.log” file to see if any errors are
reported there. The Virtuoso trace_on() function can also being enabled to
write more detailed information to the log file that might
Hugh,
Thanks for the response.
On Aug 20, 2011, at 8:02 PM, Hugh Williams wrote:
The error implies that there is a bad triple in one of the graphs being
dumped, can you please check the “virtuoso.log” file to see if any errors are
reported there. The Virtuoso trace_on() function can also
Hi Greg,
Checking the log I see the following query appearing to result in the error:
20:37:25 COMP_2 SPARQL 128.113.106.176 Internal Compile text: sparqlprefix
vann: http://purl.org/vocab/vann/
SELECT distinct ?namespace ?prefix
WHERE {
GRAPH
I've been trying to use the dump_graphs() function from
http://ods.openlinksw.com/wiki/main/Main/VirtDumpLoadRdfGraphs to dump the
RDF contents of my virtuoso database, and I've been getting the following error:
[willig4@sam db]$ cat /tmp/dump.txt
dump_graphs('/tmp/dump', 1);
12 matches
Mail list logo
