> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-admin/troubleshooting-overview-cp/pentaho-repository-issues.md). # Pentaho Repository issues Common issues associated with the Pentaho Repository. ## Debugging a corrupted Pentaho Server repository A corrupted Pentaho Repository will become unresponsive resulting in missing content, inaccessibility, and the following error message that appears in the `/pentaho-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 error occurs, shut down the Pentaho 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. Enable debug logging by adding the following XML snippet above the `` element in the `/WEB-INF/classes/log4j2.xml` inside your deployed `pentaho.war`: ```xml ``` Restart the Pentaho Server and retry the action that caused the original error. If it occurs again, shut down the Pentaho Server and open the `catalina.out` log file in Tomcat. The last line that appears before the error usually contains the name of the file that has been damaged. When you have finished investigating, remove the extra logging capabilities so that your Pentaho Server log files do not become large and unmanageable. ### Using the H2 database recovery tool The Pentaho Server includes a third-party H2 database recovery tool that enables you to extract raw data from your Pentaho Repository. This recovery tool is primarily useful in situations where the repository has become corrupt and you do not have any relevant backups. {% hint style="info" %} **Note:** If the database has become corrupt, the corrupted rows will not be exported. Any information contained in corrupted rows is unrecoverable through this method. {% endhint %} The recovery tool is a JAR you run via the Java command. The output is a SQL dump that you can then attempt to import after you have re-initialized your Pentaho Server database. Read more about the recovery tool on the H2 Web site: . Follow these directions to use the recovery tool: 1. Open a terminal on (or establish an SSH connection to) your Pentaho Server. 2. Navigate to the `/pentaho-solutions/system/jackrabbit/repository/version/` folder. ``` cd pentaho-server/pentaho-solutions/system/jackrabbit/repository/version/ ``` 3. Run the `h2-1.2.131.jar` H2 database JAR with the recovery tool option. ```java java -cp h2-1.2.131.jar org.h2.tools.Recover ``` 4. Create a directory to move your old database files. ``` mkdir old ``` 5. Move the old database files to the directory created in the previous step. ``` mv db.h2.db db.trace.db old ``` 6. Re-initialize the repository with the **RunScript** option using the salvaged SQL dump as the source. 
java -cp h2-1.2.131.jar org.h2.tools.RunScript -url jdbc:h2:./db -user sa -script db.h2.sql
7. The backup directory you created earlier (`old` in the above example) can be removed after you are sure that you no longer need the corrupted database files. 8. Start the Pentaho Server and check for further errors. If repository errors persist, contact Pentaho support. ## Unable to get list of repositories When you are working with a repository and trying to execute a job or transformation remotely on a Carte server, the following error message may appear: ``` There was an error posting the transformation on the remote server: org.pentaho.di.core.exception.KettleException: Unable to get a list of repositories to locate repository 'repo' ``` To execute a job or transformation remotely on a Carte server, you first need to copy the local `repositories.xml` from the user's `.kettle` directory to the Carte server's `$HOME/.kettle` directory. The Carte service also looks for the `repositories.xml` file in the directory where Carte was started. ## Importing and exporting PDI content with Pentaho 8.0 and earlier When you export the contents of the repository from Pentaho version 8.0 or earlier and import them into a later version, an error occurs. This error may occur because you are attempting to export/import the entire repository, which may include items from repository locations that have restricted access in later versions of Pentaho. Here's how you can resolve this error: To import or export PDI content that was created in Pentaho 8.0 or earlier, select specific content and not the entire repository. If you are working with multiple selections, export each one separately. Also note that you do not need to export your Ops Mart content because it is automatically included and updated for each new version of Pentaho. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.pentaho.com/pdia-admin/troubleshooting-overview-cp/pentaho-repository-issues.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.