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
Hi Piret,
> As the quad dump failed I went with an option to select list of named graphs
> we needed to save from corrupted database and I am making dumps of those
> graphs one by one using procedure specified here
>
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.
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
Hi Piret,
If you build a debug binary with symbols in place you will get a more
meaningful gdb back trace ie “?”’s will resolve, as follows:
1. Configure using the —with debug option:
./configure —with-debug
2. In the Makefile, check to ensure CFLAGS has the “-g” option set which
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 :
Hi Piret,
Have you attempted a "Crash Recovery When The Normal Crash Recovery Fails”
which rebuild schema and system keys etc as detailed in section 6.1.5.4.3. of
the docs at:
http://docs.openlinksw.com/virtuoso/databaseadmsrv.html#backup
Also, do you have "Log Audit Trail" an
