![]() ![]() output db-recovery.sqliteĮxit the SQLite command shell using. The below command will create a recovery file called db-recovery.sqlite. The first step is to generate a recovery file. ![]() If the above commands did not work, you can have Plex attempt to salvage as much information as possible, and then recreate the database from the salvaged data. If there are issues related to the database indexes, such as those that appear after running the integrity_check command, you can rebuild the indexes using the following command: REINDEX Low-level database recovery You can rebuild the database structure using the following command: VACUUM Rebuilding the indexes Some issues could be related to the database structure, including some issues that the integrity_check command couldn't detect. Once those commands run, you can re-run this command to see if the result has changed. If an error is returned, you can try to repair it using the additional commands outlined below. You can try additional commands to see if there is another underlying issue. While this command indicates there is no issue, there could be other issues that weren't detected. If the database structure is valid, you will see a result of ok. The following command can be used to check for database corruption: PRAGMA integrity_check If you exclude the semi-colon, the command will not run. Once both of the above things are done, you will need to know the location of the Plex database and then use the following command: "Plex SQLite" /.dbĮnsure you always add a semi-colon at the end of each diagnostic command. Creating a backup is always recommended, it should be done automatically on a regular schedule.Īlso, you should stop Plex Media Server to prevent more corruption and to ensure there is no issue with Plex SQLite from accessing and working with the database. var/packages/PlexMediaServer/target/Plex SQLiteīefore using the Plex SQLite tool with the Plex database, it is recommended that you first back up the Plex database. var/packages/Plex Media Server/target/Plex SQLite share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Plex SQLite Applications/Plex Media Server.app/Contents/MacOS/Plex SQLite The following table shows the location of the database for various systems: Location of the Plex SQLite Tool SystemĬ:\Program Files (x86)\Plex\Plex Media Server\Plex SQLite.exeĬ:\Program Files\Plex\Plex Media Server\Plex SQLite.exe The Plex SQLite tool is located in the same directory as the main Plex Media Server executable. The database includes some customizations, so the Plex team has included their command line interpreter to work with the database: Plex SQLite. If you do find that the database has been corrupted, this article will explain methods you can use to return the database to a functioning state.Īs mentioned earlier, the Plex database is an SQLite database. One way of corrupting the database could happen is if your server was turned off as Plex was writing to the database. There is a possibility that the Plex database could become corrupted, albeit, very rarely. Plex stores the metadata and other information for your media in an SQLite database that is located in the lex data directory on your server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |