Not logged in : Login |
Database reports Broken index RDF_QUAD_XXXX on startup If on startup the Virtuoso database fails to start reporting Broken index RDF_QUAD_XXXX: 11:14:55 built-in procedure "WS.WS.SYS_DAV_RES_RES_CONTENT_HOOK" overruled by the RDBMS 11:14:55 built-in procedure "WS.WS.SYS_DAV_RES_RES_CONTENT_INDEX_HOOK" overruled by the RDBMS 11:14:59 Roll forward started 11:15:03 353 transactions, 3698455 bytes replayed (100 %) 11:15:03 Roll forward complete 11:15:05 Broken index RDF_QUAD_POGS 11:15:05 GPF: colsearch.c:1757 less ces in seg than indicated in leaf col ref GPF: colsearch.c:1757 less ces in seg than indicated in leaf col ref This can be recovered by as follows: Ensure a full backup or copy of the database is made Remove or rename the virtuoso.trx transaction log file Start the database again which should not start successfully and run the command to drop the broken RDF index: _INTERNAL_DROP_INDEX ('DB.DBA.RDF_QUAD', 'RDF_QUAD_POGS'); Perform a database crash dump of the database with the +crash-dump command: virtuoso-iodbc-t +configfile virtuoso.ini +crash-dump On completion the database can be restored with the +restore-crash-dump command: virtuoso-iodbc-t +configfile virtuoso.ini +restore-crash-dump The missing index can then be recreated as detailed in the RDF Performance Tuning guide, thus is the case of the RDF_QUAD_POGS index the command would be: DROP INDEX RDF_QUAD_POGS ; CREATE COLUMN INDEX RDF_QUAD_POGS ON DB.DBA.RDF_QUAD (P, O, G, S) PARTITION (O varchar (-1, 0hexffff));
Attributes | Values |
---|---|
type | |
described by | |
name |
|
description |
|
schema:nextItem | |
position |
|
is topic of | |
is schema:nextItem of | |
is schema:step of |