Sebastian, On 28 Feb 2011, at 07:34, Sebastian Trüg wrote:
> Hi Hugh, > > On 02/26/2011 03:02 PM, Hugh Williams wrote: >> Hi Sebastian, >> >> This is because the insert operation are being performed in transaction >> mode, which you can turn off and force the auto-committing of the the >> transactions to avoid the log limit being exceeded and is generally >> recommended for SPARUL operations as detailed at: >> >> http://docs.openlinksw.com/virtuoso/sparqlextensions.html#rdfsparul >> >> Alternatively, the "TransactionAfterImageLimit" parameter can be set in the >> virtuoso.ini config file to a higher value than its 50MB default as detailed >> at: >> >> >> http://docs.openlinksw.com/virtuoso/databaseadmsrv.html#ex_threadcleanupinterval > > I see. Thanks a lot for pointing that out. > In general is there a problem with disabling the transaction mode in > general? I mean as long as I do not really make use of transactions > (which I sadly do not). [Hugh] No, there is not you can simple disable the whilst performing the insert operation and then reenable when done using the log_enable() function ... Best Regards Hugh Williams OpenLink Software > > Cheers, > Sebastian > >> >> 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 26 Feb 2011, at 10:12, Sebastian Trüg wrote: >> >>> Hello list, >>> >>> I get the following error when running an insert command which touches >>> quite a lot of triples: >>> >>> iODBC Error: [OpenLink][Virtuoso iODBC Driver][Virtuoso Server]SR325: >>> Transaction aborted because it's log after image size went above the limit >>> >>> The insert query in question is this (probably not important but just to >>> be sure): >>> sparql insert into graph <urn:crappyinference2:inferredtriples> { >>> ?r a rdfs:Resource . >>> ?r a nrl:Graph . >>> ?r a nrl:Data . >>> ?r a nrl:InstanceBase . >>> } where { >>> graph ?g { >>> ?r a nrl:DiscardableInstanceBase . >>> } . >>> FILTER(?g!=<urn:crappyinference2:inferredtriples>) . >>> } >>> >>> Is it possible to allow the max transaction log size to be exceeded for >>> single queries? >>> >>> Cheers, >>> Sebastian >>> >>> ------------------------------------------------------------------------------ >>> Free Software Download: Index, Search & Analyze Logs and other IT data in >>> Real-Time with Splunk. Collect, index and harness all the fast moving IT >>> data >>> generated by your applications, servers and devices whether physical, >>> virtual >>> or in the cloud. Deliver compliance at lower cost and gain new business >>> insights. http://p.sf.net/sfu/splunk-dev2dev >>> _______________________________________________ >>> Virtuoso-users mailing list >>> Virtuoso-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users >> >> > > ------------------------------------------------------------------------------ > Free Software Download: Index, Search & Analyze Logs and other IT data in > Real-Time with Splunk. Collect, index and harness all the fast moving IT data > generated by your applications, servers and devices whether physical, virtual > or in the cloud. Deliver compliance at lower cost and gain new business > insights. http://p.sf.net/sfu/splunk-dev2dev > _______________________________________________ > Virtuoso-users mailing list > Virtuoso-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/virtuoso-users
