Hi Nicola,
The log_enable() setting should not matter for the index rebuild.
Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc. // http://www.openlinksw.com/
Weblog -- http://www.openlinksw.com/blogs/
LinkedIn -- http://www.linkedin.com/company/openlink-s
Hi Hugh,
here is the result of the status command on the running instance:
--
Database Status:
File size 168789278720, 20604160 pages, 6944022 free.
545 buffers, 4813858 used, 530 dirty 0 wired down, repl age
26906401 0 w. io 0 w/crsr.
Disk Usage: 14012379 reads avg 0 msec, 0% r
Hi Nicola,
You can delete and recreate the indexes, which should not be an issue provided
there is sufficient memory available which will determine how long the index
recreation will take. How much memory is available on the server hosting
Virtuoso and what does the "status('');" command return
Hi Hugh,
I needed it because I updated quite a lot of data and for doing so I
disabled the triggers, so now a search with bif:contains returns too few
results. What about deleting the index and recreating it? Would it be
feasible with ~2B triples?
Anyway, when is the update being scheduled? I mig
Hi Nicola,
Are you having a specific problem with FT indexes in v7 ? As the
DB.DBA.RDF_OBJ_FT_RECOVER() function issue is known and thus you need the
update to get this fix, there is also a known issue with incremental FT Indexes
which will be in the updated git archive being prepared ...
Bes
Hi all,
I saw that a call to DB.DBA.RDF_OBJ_FT_RECOVER() returns a known error
as explained here:
http://boards.openlinksw.com/phpBB3/viewtopic.php?f=12&t=6015
My question is: what is the best alternative to rebuild the full text
index in the meanwhile?
Thanks,
Nicola
