Re: [Virtuoso-users] Odd behavior in Virtuoso 7.0.0

2013-09-23 Thread Erich Bremer
That last isql "lockup" completed and correctly but it took a long time: SQL> SQL> DB.DBA.SPARQL_SELECT_KNOWN_GRAPHS(); GRAPH_IRI VARCHAR ___ http://www.openlinksw.com/schemas/virtrdf# http://localhost:8890/sparql http://l

Re: [Virtuoso-users] Odd behavior in Virtuoso 7.0.0

2013-09-23 Thread Erich Bremer
My original "locked" isql session just spit out the rest of the named graphs including the geonames graph: http://localhost:8890/DAV/ http://www.w3.org/2002/07/owl# http://www.geonames.org 5 Rows. -- 644278 msec. SQL> SQL> DB.DBA.SPARQL_SELECT_KNOWN_GRAPHS(); Running DB.DBA.SPARQL_SELECT_KNOWN_G

Re: [Virtuoso-users] Odd behavior in Virtuoso 7.0.0

2013-09-23 Thread Erich Bremer
Hi Hugh, The dataset is geonames.org's ~120million triple data set. I converted the quasi-RDF/XML dump they have (URI, RDF/XML. URI, RDF/XML, URI, RDF/XML ...) and split the triples over 50 turtle files. I repeated the same experiement again for the third time (with what I thought wa

Re: [Virtuoso-users] Odd behavior in Virtuoso 7.0.0

2013-09-23 Thread Hugh Williams
Hi Erich, What does the DB.DBA.SPARQL_SELECT_KNOWN_GRAPHS() function return if run as this point: http://docs.openlinksw.com/virtuoso/fn_sparql_select_known_graphs.html What datasets are you loading when this issue occurs as if they can be provided we would like to attempt to recreate