On Nov 4, 2011, at 7:15 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.
>> 
> 
> Ok that means that your database did not have an issue with certain types of 
> XML fragments that could cause a problem with ordering.
> 
>>> 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.
>> 
> 
> This means that there was no permanent damage to your index and your data is 
> structurally ok.
> 
> 
>>> 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 ?
>> 
> 
> The underlying cause of this GPF was fixed so I am expecting you should not 
> have similar GPF. However if it does occur please contact me before 
> recreating index.

Hello,

we still have the bug. Here is the log:

                Sat Nov 05 2011
00:00:21 Checkpoint started
00:00:22 Checkpoint finished, log reused
01:00:25 Checkpoint started
01:00:26 transact while cpt atomic, trx no 110, cpt trx no 106
01:00:26 transact while cpt atomic, trx no 112, cpt trx no 106
01:00:27 Checkpoint finished, log reused
02:00:30 Checkpoint started
02:00:31 transact while cpt atomic, trx no 110, cpt trx no 106
02:00:31 Checkpoint finished, log reused
03:00:34 Checkpoint started
03:00:35 transact while cpt atomic, trx no 112, cpt trx no 106
03:00:36 Checkpoint finished, log reused
04:00:38 Checkpoint started
04:00:38 transact while cpt atomic, trx no 122, cpt trx no 106
04:00:39 Checkpoint finished, log reused
05:00:41 Checkpoint started
05:00:42 transact while cpt atomic, trx no 126, cpt trx no 106
05:00:42 Checkpoint finished, log reused
06:00:46 Checkpoint started
06:00:47 Checkpoint finished, log reused
07:00:48 Checkpoint started
07:00:49 Checkpoint finished, log reused
08:00:50 Checkpoint started
08:00:51 Checkpoint finished, log reused
09:00:54 Checkpoint started
09:00:54 transact while cpt atomic, trx no 122, cpt trx no 106
09:00:55 Checkpoint finished, log reused
10:00:58 Checkpoint started
10:01:01 Checkpoint finished, log reused
11:01:04 Checkpoint started
11:01:04 transact while cpt atomic, trx no 110, cpt trx no 106
11:01:05 Checkpoint finished, log reused
12:01:08 Checkpoint started
12:01:08 transact while cpt atomic, trx no 122, cpt trx no 106
12:01:09 Checkpoint finished, log reused
13:01:11 Checkpoint started
13:01:12 transact while cpt atomic, trx no 122, cpt trx no 106
13:01:12 transact while cpt atomic, trx no 112, cpt trx no 106
13:01:12 transact while cpt atomic, trx no 132, cpt trx no 106
13:01:12 transact while cpt atomic, trx no 144, cpt trx no 106
13:01:12 transact while cpt atomic, trx no 114, cpt trx no 106
13:01:12 transact while cpt atomic, trx no 110, cpt trx no 106
13:01:12 transact while cpt atomic, trx no 126, cpt trx no 106
13:01:12 Checkpoint finished, log reused
14:01:15 Checkpoint started
14:01:16 transact while cpt atomic, trx no 110, cpt trx no 106
14:01:17 Checkpoint finished, log reused
14:58:47 Invalid bit position on index: RDF_QUAD_POGS

What should I do ?

Regards,

Cédric


Reply via email to