Duration of Repository repair-checks

[Markus Blaurock <bl...@dig.de>]

Hello,

we are using Jackrabbit (v1.6.1) with a fairly large number of nodes
(around 5,5 million), all in one default workspace.
Sometimes there are inconsistencies within the workspace we don't know
why. We  
*repair* the  *repository* with the instructions described in:
http://wiki.gxdeveloperweb.com/confluence/display/GXDEV/How+to+*repair*+a+'corrupt'+JCR
<http://wiki.gxdeveloperweb.com/confluence/display/GXDEV/How+to+repair+a+%27corrupt%27+JCR>
Unfortunately this takes a lot of time, about 6 hours.
Is there any way we can reduce the amount of time used for repairing?
(aside from reducing the size of the workspace? ;)

        <PersistenceManager
class="org.apache.jackrabbit.core.persistence.bundle.OraclePersistenceManager">
          <param name="url"
value="jdbc:oracle:thin:@10.xx.xx.xx:1522:xxxx"/>
          <param name="user" value="xxxx"/>
          <param name="password" value="xxxx"/>
          <param name="schemaObjectPrefix" value="version_"/>
          <param name="externalBLOBs" value="false"/>
        </PersistenceManager>

       <DataStore class="org.apache.jackrabbit.core.data.FileDataStore"/>

<Cluster id="xyxyxyxy" syncDelay="2000">
  <Journal class="org.apache.jackrabbit.core.journal.OracleDatabaseJournal">
    <param name="revision" value="${rep.home}/revision.log" />
    <param name="driver" value="oracle.jdbc.driver.OracleDriver" />
    <param name="url" value="jdbc:oracle:thin:@xx.xx.xx.xx:1522:xxxxx" />
    <param name="user" value="xxxxxx"/>
    <param name="password" value="xxxxx"/>
  </Journal>
</Cluster>

thanks in advance,
markus