On Nov 2, 2011, at 2:23 PM, Patrick van Kleef wrote:

> Hi Cédric,
>> 
>> sometimes our Virtuoso server segfaults on a sparql query.
>> 
>> When we were using version 6.1.2, the error on the log was:
>> 09:24:48 GPF: bitmap.c:1552 next/prev of non-valid bit pos
>> 
>> With version 6.1.3, the error is now:
>> 12:35:34 Invalid bit position on index: RDF_QUAD_POGS
>> 12:35:34 GPF: bitmap.c:1606 next/prev of non-valid bit pos
>> 
>> Any idea of what the problem could be ?
> 
> I believe this issue is fixed in the 6.1.4 release we just announced earlier 
> this week.
> 
> I suggest you first upgrade to 6.1.4

Hi Patrick

Upgrade done, using a copy of the db directory.
I get a "No need to update DB.DBA.RDF_QUAD" message in the log.

> then you should run the following two statements on your database using the 
> isql tool:
> 
>  select count (*) from RDF_QUAD table option (index primary key)
>  select count (*) from RDF_QUAD table option (index RDF_QUAD_POGS)

These counts are matching.

> These counts should match, else you may need to drop the index and re-create 
> it:
> 
>  drop index RDF_QUAD_POGS;
> 
>  create bitmap index RDF_QUAD_POGS on RDF_QUAD (P, O, G, S) partition (O 
> varchar (-1, 0hexffff))
> Let me know if this solves your problem.


I'm think I'm going to try 6.1.4, and see if we get segfaults with this version.

Should I re-create the index if we get segfaults with the new version ?

Regards,

Cédric


Reply via email to