On Thu, 22 May 2014, Mauricio Acebal wrote:
> 2014-05-22 08:51:49 --> idxWORD08F adding records #3001-#4000 started
> 2014-05-22 08:51:52 --> Exception caught: (1062, "Duplicate entry
> '3001-FUTURE' for key 'PRIMARY'")
This happens when the indexer died for a reason or another during
indexing process. If automatic repair (that you tried) does not work,
then the situation is not fully lost: the `FUTURE` terms can be safely
discarded, since they will be reproduced at a later run. So you could
do something like:
$ echo "DELETE FROM idxWORD01R WHERE type='TEMPORARY' or type='FUTURE';" | \
/opt/invenio/bin/dbexec
see section 4.2 of the BibIndex Admin Guide:
http://invenio-demo.cern.ch/help/admin/bibindex-admin-guide#4.2
> Last thing we did was clearing global indexes idxWORD01F/R tables and
> started bibindex again which will certainly take more than a day
Yes, that's the waterproof solution, and always OK to do; its only
disadvantage is that reindexing from scratch takes time.
(Note that instead of truncating tables, you can trigger reindexing of
say global index by running `bibindex -w global -R`.)
Best regards
--
Tibor Simko
