Menu: Repair

• REPAir - (Option 5): Repair/Optimize Databases

  • Overview: If the databases have not already been checked, performs an in-depth check and then repairs as needed. Creates new main and blobs databases and transfers the usable data from the existing databases into them (schema, search tables, triggers, data, indexes). Repair does all the 'heavy duty' work of repairing and optimizing your databases. No external ASCII (.sql) file is involved. In most cases Repair is the preferred option as the records extracted are only those SQLite deemed valid with those records transferred in perfect order.

  • Availability: Runs only when Plex Media Server is stopped. Requires enough free disk space for the new databases.

  • Technical quirks & behavior: 100% validity/usability by Plex is not guaranteed. DBRepair cannot validate each individual record's contents. It can only validate at the SQLite level. If a database has unrecoverable damage (SQLite internal data tables are unreadable), that database is skipped and DBRepair tells you to use Replace instead.

  • Safety status: Safe — The new databases are promoted to active only after both pass a full integrity check. If either fails, the new copies are discarded and your active databases are untouched. A successful promotion is recorded in History and can be undone with Revert at any time prior to exiting DBRepair.

---

Back