Hi Uldis,
Update intensive SPARQL update (SPARUL) operations should be performed with
Virtuoso transaction isolation level set to “Read Committed” (2), in the
Virtuoso INI file and restart, as detailed at;
http://wikis.openlinksw.com/dataspace/owiki/wiki/VirtuosoWikiWeb/ChangeVirtuos
Tried the following workaround and it worked (+ works reasonably fast):
- reconnect ODBC connection after each SPARQL update
Yet it would be good to solve the problem itself.
Best,
Uldis
On Sat, Nov 24, 2012 at 11:15 PM, Uldis Bojars wrote:
> Hi Hugh,
>
>> 1. The version of Virtuoso being used
Hi Hugh,
> 1. The version of Virtuoso being used as last we spoke you were using 6.1.4
> shipped with Ubuntu 12.04 and were going to attempt to rebuild for source to
> update to the latest 6.1.6 version ?
Still 6.1.4 shipped with Ubuntu. Will update, but did not get around
to it yet. However, t
HI Uldis,
Can you please confirm:
1. The version of Virtuoso being used as last we spoke you were using 6.1.4
shipped with Ubuntu 12.04 and were going to attempt to rebuild for source to
update to the latest 6.1.6 version ?
2. The version of the Virtuoso ODBC Driver on windows being used ie h
Hi,
The following error appears when doing ODBC [SPARQL] calls to Virtuoso:
GPF: \opl_port\pkg\virtuoso\libsrc\Dk\Dksestcp.c:1051 internal error
Unhandled Exception: System.AccessViolationException: Attempted to
read or write protected memory. This is often an indi
cation that other memory is co
