Skip to main content
Hitachi Vantara Lumada and Pentaho Documentation

Troubleshooting a Corrupted DI Server Repository

If the DI Repository becomes corrupt, it will be unresponsive, content may be missing or inaccessible, and an error message similar to this will appear in the /data-integration-server/tomcat/logs/catalina.out log file:

ERROR [ConnectionRecoveryManager] could not execute statement, reason: File corrupted while reading record: "page[48970] data leaf table:8 entries:1 parent:49157 keys:[118547] offsets:[737]". Possible solution: use the recovery tool [90030-131], state/code: 90030/90030

If this happens, shut down the DI Server and restore your solution repository from a recent backup.

If you do not have a viable backup, you may be able to minimize data loss by identifying the exact file that is corrupt. To do this, enable debug logging by adding the following XML snippet above the <root> element in the /WEB-INF/classes/log4j.xml inside your deployed pentaho.war:

<category name="org.pentaho.platform">
     <priority value="DEBUG"/>

Restart the DI Server and retry the action that caused the original error. If it occurs again, shut down the DI Server and open the catalina.out log file in Tomcat. Look for the last line that appears before the error; it usually contains the name of the file that has been damaged. When you are finished investigating the data corruption, remove the extra logging capabilities so that your DI Server log files don't become large and unmanageable.

reading file with id 'xyz' and path '/public/a.txt'