Re: [Virtuoso-users] Page set checksum error on backup_online.

2016-09-02 Thread Piret Lattikas
Hi, Hugh. Thank you for your response. Yesterday evening another virtuoso crashed during the backup set by virtuoso inner scheduler with the same error: 20:13:12 Backing up page 293 20:13:12 page set checksum ck=d368ab6a pck=5368ab6a xor = 8000 20:13:12 /usr/bin/virtuoso-t() [0xb074

[Virtuoso-users] Page set checksum error on backup_online.

2016-08-17 Thread Piret Lattikas
Hi all. We setup a separate location for virtuoso backup files on a different volume. First I did a full backup by stopping all processes writing to virtuoso and executed commands in ISQL terminal: SQL> checkpoint_interval(-1); SQL> backup_context_clear(); SQL> checkpoint; SQL> backup_online('v

Re: [Virtuoso-users] URGENT! Insert error in Virtuoso 7.2.2!

2016-02-01 Thread Piret Lattikas
Hi, all. Thank you, Patrick for your help. With your guidelines I was able to create a debian package with debug binary with symbols in place. I recreated the crash condition on corrupted database as follows: - executed "Crash Recovery When The Normal Crash Recovery Fails” first command 'vir

Re: [Virtuoso-users] URGENT! Insert error in Virtuoso 7.2.2!

2016-01-18 Thread Piret Lattikas
just fine. Connection with virtuoso is made with url "jdbc:virtuoso://:/CHARSET=UTF-8". I was not able to create a debian package with debug binary with symbols in place using debian/rules for compiling. Can someone maybe give me some guidance on where to correctly add option --wi

Re: [Virtuoso-users] URGENT! Insert error in Virtuoso 7.2.2!

2016-01-12 Thread Piret Lattikas
Hi Hugh, Started NQuad dump on the corrupted database and at some point it failed with the error: Connected to OpenLink Virtuoso Driver: 07.20.3215 OpenLink Virtuoso ODBC Driver OpenLink Interactive SQL (Virtuoso), version 0.9849b. Type HELP; for help and EXIT; to exit.

Re: [Virtuoso-users] URGENT! Insert error in Virtuoso 7.2.2!

2016-01-10 Thread Piret Lattikas
Hi Hugh, Unfortunately I am not able to provide test case for that condition. One thing I did notice about this error is that until we insert triples without plain literal object values there is no error. After a triple with object value as plain literal without type reference the error occurs

[Virtuoso-users] URGENT! Insert error in Virtuoso 7.2.2!

2016-01-08 Thread Piret Lattikas
Hi. I wrote about the same problem regarding version 7.2.1 and then I was told that this problem will be fixed with version 7.2.2 release. We switched to version 7.2.2 as soon as it came out and for a while everything was ok. Now we are experiencing the same error again: SQL Error: X :

Re: [Virtuoso-users] SQL Error on insert with virtuoso 7.2.1

2015-12-20 Thread Piret Lattikas
-2015 OpenLink Software Where can this error occur and why? Best regards. Piret On 08.12.15 14:43, Piret Lattikas wrote: > Hi, > > We recently upgraded our virtuoso to latest stable version 7.2.1. We > made a quad dump of the previous database and imported all the data to > new

Re: [Virtuoso-users] SQL Error on insert with virtuoso 7.2.1

2015-12-10 Thread Piret Lattikas
Hi, Hugh. Saw that new release verison 7.2.2 of virtuoso is available. But when I try to build debian packages I get an error: test -x debian/rules /usr/bin/make -C binsrc/VirtuosoClient.Net clean make[1]: Entering directory `/tmp/build/virtuoso-opensource/binsrc/VirtuosoClient.Net' make[1]:

Re: [Virtuoso-users] SQL Error on insert with virtuoso 7.2.1

2015-12-08 Thread Piret Lattikas
-- http://twitter.com/OpenLink Google+ -- http://plus.google.com/100570109519069333827/ Facebook -- http://www.facebook.com/OpenLinkSoftware Universal Data Access, Integration, and Management Technology Providers On 8 Dec 2015, at 12:43, Piret Lattikas <mailto:piret.latti...@zerotech.ee>&

[Virtuoso-users] SQL Error on insert with virtuoso 7.2.1

2015-12-08 Thread Piret Lattikas
Hi, We recently upgraded our virtuoso to latest stable version 7.2.1. We made a quad dump of the previous database and imported all the data to new virtuoso. When we started our process against the new database got an error on insert after about 1000 named graphs were added, with approximately

Re: [Virtuoso-users] Virtuoso 7.2.0 terminated with signal SIGSEGV, Segmentation fault.

2015-12-03 Thread Piret Lattikas
, Patrick van Kleef wrote: > Hi Piret, > >> On 24 Nov 2015, at 10:00, Piret Lattikas wrote: >> >> Hi Hugh. >> >> I have no additional settings set on my build. For building virtuoso debian >> packages from latest github develop/7 branch source I do the follo

Re: [Virtuoso-users] Virtuoso 7.2.0 terminated with signal SIGSEGV, Segmentation fault.

2015-11-24 Thread Piret Lattikas
m/ Weblog -- http://www.openlinksw.com/blogs/ LinkedIn -- http://www.linkedin.com/company/openlink-software/ Twitter -- http://twitter.com/OpenLink Google+ -- http://plus.google.com/100570109519069333827/ Facebook -- http://www.facebook.com/OpenLinkSoftware Universal Data Access,

Re: [Virtuoso-users] Virtuoso 7.2.0 terminated with signal SIGSEGV, Segmentation fault.

2015-11-23 Thread Piret Lattikas
Hi Hugh. I tried building the latest debian packages from branch develop/7 with latest changes up to today, 23rd of November. The build steps are based on this post accepted answer: http://serverfault.com/questions/631673/virtuoso-opensource-7-1-how-do-i-build-an-ubuntu-deb-package-from-github-

Re: [Virtuoso-users] Virtuoso 7.2.0 terminated with signal SIGSEGV, Segmentation fault.

2015-10-24 Thread Piret Lattikas
status(); output and noticed that with every run the used memory increased. Is there a way to flush the memory after we do a checkpoint, when running the script? Is there a way to execute some sort of garbage collection to free up unused memory? Best Regards. Piret Lattikas On 20.10.15 17:00,

Re: [Virtuoso-users] Virtuoso 7.2.0 terminated with signal SIGSEGV, Segmentation fault.

2015-10-20 Thread Piret Lattikas
ts. PID: 7440, OS: unix, Application: unknown, IP#: 127.0.0.1 Transaction status: PENDING, 1 threads. Locks: Running Statements: Time (msec) Text 868 status() Hash indexes Best Regards. Piret Lattikas On 20.10.15 15:59, Hugh Williams wrote: > Hi Piret, > > If you have

Re: [Virtuoso-users] Virtuoso 7.2.0 terminated with signal SIGSEGV, Segmentation fault.

2015-10-20 Thread Piret Lattikas
ce are down during that time. Best Regards. Piret Lattikas On 19.10.15 17:41, Hugh Williams wrote: Hi Piret, I note you are using an older Virtuoso 7.2.3212 build from Apr 2015 where as the current stable release build from git or source-forge is 7.2.3214, thus I would suggest updating to thi

[Virtuoso-users] Virtuoso 7.2.0 terminated with signal SIGSEGV, Segmentation fault.

2015-10-19 Thread Piret Lattikas
-pthreads as of Apr 8 2015 Compiled for Linux (x86_64-pc-linux-gnu) Copyright (C) 1998-2015 OpenLink Software Do you have any suggestions why this happened and how can it be fixed? Best regards, Piret Lattikas -- ___