Hi Bharath,
I doubt the data is being loaded incorrectly but sounds as an index on the
RDF_QUAD table might be corrupt, which case you could try dropping and
recreating them as detailed at:
http://docs.openlinksw.com/virtuoso/rdfperformancetuning.html#rdfperfrdfscheme
Best Regards
Hi Robert,
Virtuoso extends SPARQL so it is possible to download RDF resource from a given
IRI, parse them and store the resulting triples in a graph, all three
operations will be performed during the SPARQL query execution as detailed in
[1]. The Virtuoso uriburner.com service at [2] is a
Hello Concetto,
On Mon, 2011-05-02 at 16:06 +0200, Concetto Bonafede wrote:
File size 46297088000, 5651500 pages, 128389 free.
200 buffers, 1824911 used, 6 dirty 0 wired down, repl age 0 0 w.
io 0 w/crsr.
Disk Usage: 10641382 reads avg 0 msec, 0% r 0% w last 12 s, 236840
writes,
Thanks Hugh for the reply i will check the virtuoso's index .
I have one more doubt when ever we use the delete query :
-- SPARQL DELETE FROM GRAPH http://examp.org { ?s ?p ?o } FROM
http://examp.org WHERE { ?s ?p ?o.})
the whole virtuoso crashes and there is no log also to know about the
Hi Bharath,
I would suggest rebuilding the index and then see if the delete from graph is
still causing a crash. Also do confirm you are running the latest 6.1.3 open
source release, use the “virtuoso-t -?” command to determine the version.
If a core file being produced when a crash occurs you
Hi Alexandre,
The backup files would get written the the master node database working
directory ie cluster_01 in your case or you can specify a directory for the
files to be written to with the optional 4th parameter of this function as
detailed in the function reference guide at:
On 03/05/2011 00:30, Alexandre Passant wrote:
Also, is there an easy way to create a full NQUAD archive from the content of
my RDF store ?
Should be pretty easy, I think.
a) devise a query that returns everything, for example
select distinct * where {
graph ?g { ?s ?p ?o . } }
limit 1000
b)
Hi.
Got the issue fixed myself. It was a java.sql.Date issue. Sorry for the
noise.
Br,
Timo Westkämper
On 05/03/2011 02:50 PM, Timo Westkämper wrote:
Hi.
As an update to the previous issue, xsd:dateTime literals work correctly.
Br,
Timo Westkämper
On 05/03/2011 12:00 PM, Timo Westkämper
Hi Everybody,
I am facing long read issue with one of my server (when sparqling). The
server runs:
(1) Virtuoso 5.12.3041
(2) PHP 5.3.2
(3) It uses the default unixodbc drivers that comes with ubuntu
(4) I am using DB.DBA.SPARQL_EVAL to wrap the sparql queries via the
PHP-ODBC API.
So,
