# DBRepair development **URL:** \ **Category:** Apps & Creations\ **Created:** [December 14, 2022, 3:57am UTC](https://forums.plex.tv/t/dbrepair-development/822684 "2022-12-14T03:57:23Z")\ **Posts on this page:** 20\ **Page:** 64
**Author:** ![balthazarr1](https://avatars.discourse-cdn.com/v4/letter/b/a87d85/32.png) [@balthazarr1](https://forums.plex.tv/u/balthazarr1)\ **Post date:** [October 8, 2026, 10:00pm UTC](https://forums.plex.tv/t/dbrepair-development/822684/1361 "2026-10-08T22:00:36Z")
PM’d. Another issue - I thought I’d try restoring a DB backup - ![Screenshot 2026-10-09 at 08.26.56](https://global.discourse-cdn.com/plex/original/4X/3/3/f/33fb8e3de61d70a51455ee9de66184a2ac182a60.png) ![Screenshot 2026-10-09 at 08.27.46](https://global.discourse-cdn.com/plex/original/4X/9/4/0/9409b9a21e4cb305b9b52d900d9a89acf1300c89.png) No idea where those dates are coming from in DB Repair - it’s not Blobs backups, they have identical dates and very similar times. ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [October 8, 2026, 11:58pm UTC](https://forums.plex.tv/t/dbrepair-development/822684/1366 "2026-10-08T23:58:25Z")
### ALL: There will be another release before we go to Public. I fixed a few bugs today which I want to confirm are good. I also want to address the issues brought up today. I might have a solution to DBRepair opening and immediately closing. (not administrator problem) by changing what windows calls the ‘manifest’. I’ll check that out. Also will be addressing the UI requests. Another issue was raised today which needs investigating. I see the problem and want to track it out. It’s simple but detail rich. ON good news, I’d like to end the day by telling you that there was a big improvement in performance by fixing the bug presented by @Kgtree . Large databases are now as much as 2-3x faster than previous. ( No more sneaking out to the 'fridge for a cold one while it runs 😉 ) Heavy shakedown testing is going very very well. These “nits” and the ever-looming Wiki remain. ---
**Author:** ![Viralfrag](https://avatars.discourse-cdn.com/v4/letter/v/ecb155/32.png) [@Viralfrag](https://forums.plex.tv/u/Viralfrag)\ **Post date:** [October 9, 2026, 5:10am UTC](https://forums.plex.tv/t/dbrepair-development/822684/1367 "2026-10-09T05:10:37Z")
> [@ChuckPa](#): > > Large databases are now as much as 2-3x faster than previous. > ( No more sneaking out to the 'fridge for a cold one while it runs 😉 ) Moving forward, the application should display a dynamically generated excuse every time it is run. 🙂 ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [October 9, 2026, 6:04am UTC](https://forums.plex.tv/t/dbrepair-development/822684/1368 "2026-10-09T06:04:28Z")
Why should DBRepair generate a dynamic excuse because you can’t control your media collection habit ? 🤣 ---
**Author:** ![Viralfrag](https://avatars.discourse-cdn.com/v4/letter/v/ecb155/32.png) [@Viralfrag](https://forums.plex.tv/u/Viralfrag)\ **Post date:** [October 9, 2026, 6:14am UTC](https://forums.plex.tv/t/dbrepair-development/822684/1369 "2026-10-09T06:14:18Z")
haha. I mean generating excuses for grabbing a cold one from the fridge. ---
**Author:** ![hottif](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/hottif/32/81992_2.png) [@hottif](https://forums.plex.tv/u/hottif)\ **Post date:** [October 9, 2026, 6:18am UTC](https://forums.plex.tv/t/dbrepair-development/822684/1370 "2026-10-09T06:18:15Z")
@ChuckPa I’m not sure if I found an issue here. Could you please have a look: (Summary AI generated) **Title:** Butler DB backup silently stopped (Plex integrity check fails on FTS4 index `fts4_metadata_titles_icu`), but DBRepair `check` reports “OK” **Environment** - Plex Media Server 1.43.5.11029 (Windows 10, build 19045, x64), very large library - Main DB ~6.3 GB, blobs DB ~9.5 GB - Backup target: separate SSD with 400 GB free, path exists and is writable - “Backup database every 3 days” enabled, Butler window 01:00–08:00 **Problem** Scheduled database backups stopped working without any visible error. The last backup in the target folder is `com.plexapp.plugins.library.db-2026-08-23`. The next one should have followed within three days, but none was ever created. I updated to 1.43.4.10903 on Aug 24 and to 1.43.5.11029 on Oct 7, and no backup has been created since 23 Aug. I can’t prove the update caused it. **Analysis** The normal log did not cover the nightly Butler window ([debug logging](https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/#toc-1) rolls over a 10 MB file every 15–30 minutes). So I triggered the task manually (`POST /butler/BackupDatabase`) and read the log: ```auto [Database backup/com.plexapp.plugins.library.db] Activity: registered new activity ... "Database" ... (minutes later) ERROR - [Database backup/com.plexapp.plugins.library.db] The database failed its integrity check, not backing up. DEBUG - ... Push: Sending notification tv.plex.notification.admin.database.corrupted to 1 users. WARN - Butler: wasn't able to back up your database ``` This is not a DB-lock or disk problem. I had stopped the other writers (no “busy database” messages during the run), and the free space is plentiful. I then ran Plex’s own SQLite with Plex stopped: ```auto "C:\Program Files\Plex\Plex Media Server\Plex SQLite.exe" com.plexapp.plugins.library.db "PRAGMA integrity_check;" ``` Result (about 3–5 minutes): ```auto unable to validate the inverted index for FTS4 table main.fts4_metadata_titles_icu: SQL logic error ``` **The discrepancy** I ran DBRepair (current native Windows version, option 3 `check`) right before and after. It reports: ```auto Checking the PMS databases... Main DB is OK. Blobs DB is OK. ``` So the Butler integrity check (and a manual `PRAGMA integrity_check` with Plex SQLite) fails because of the FTS4 title index. DBRepair’s check passes. Because of that, Plex treats the DB as corrupt and refuses to back it up, while DBRepair tells the user everything is fine. ![image](https://global.discourse-cdn.com/plex/original/4X/5/8/f/58fa8b1f610673e9c9925ef590067aacd40e6c0b.png) After using the reindex feature of DBRepair the same error message is shown. ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [October 9, 2026, 6:32am UTC](https://forums.plex.tv/t/dbrepair-development/822684/1371 "2026-10-09T06:32:02Z")
@hottif Thanks to @Kgtree , I corrected that today. I wasn’t handling Unicode and special characters **exactly** as plex does. I have that fixed in 00.99.13 which I have here now. It is 2am here and about to sleep. When I wake tomorrow, I will post 00.99.13 for everyone to test. If this doesn’t fix it for you, Please send me the text logs and copy/paste of the console text? The screenshots you provided are very small and will not zoom in my browser. When did you upgrade to PMS 1.43.4 ? Was it about the time the backups stopped ? ---
**Author:** ![hottif](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/hottif/32/81992_2.png) [@hottif](https://forums.plex.tv/u/hottif)\ **Post date:** [October 9, 2026, 6:42am UTC](https://forums.plex.tv/t/dbrepair-development/822684/1372 "2026-10-09T06:42:33Z")
Thanks Chuck, please forget about the screenshot as the text is already in the message above 😃 The update to 1.43.4 happened around the time the backups stopped, yes. I’m looking forward to test the new version. But now have a good night 🙂 ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [October 9, 2026, 3:39pm UTC](https://forums.plex.tv/t/dbrepair-development/822684/1373 "2026-10-09T15:39:55Z")
# ALL: Being this close to release means I can no longer instantly respond to change requests. I must ask, from this point forward, you use my established GitHub “Issues” for feature changes / new feature requests. This will allow me to properly prioritize features, changes, and bug requests moving forward. As always, if an URGENT BUG, please report it here AND on GitHub. Thanks, Chuck > **[Issues · ChuckPa/DBRepair](https://github.com/ChuckPa/DBRepair/issues)** > > Database repair utility for Plex Media Server databases - Issues · ChuckPa/DBRepair ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [October 9, 2026, 8:51pm UTC](https://forums.plex.tv/t/dbrepair-development/822684/1377 "2026-10-09T20:51:43Z")
# ver 00.99.13 Testing ### Release Notes: - General - PMS version - Invalid ICU fail - Dropped rows - Windows ### For your consideration: - [MacOS - Arm64](https://drive.google.com/file/d/1FG_--R6EiqbZiDoqSw3X5OMuo6f2gxlh/view?usp=sharing) - [MacOS - x86\_64](https://drive.google.com/file/d/1T5fyAQiGnGIIJyRoW-6IdH6oRmYz8e7n/view?usp=sharing) - [Linux - Arm32 (Armv7)](https://drive.google.com/file/d/135c5u1g313omV1TMs1Z6NbCA2BgXXaqP/view?usp=sharing) - [Linux - Arm64 (Armv8)](https://drive.google.com/file/d/11GaRUN_EXGWmMZkFKgjbL489aogzzSSL/view?usp=sharing) - [Linux - X86\_64](https://drive.google.com/file/d/1Kbb581CfStlZpBGm2ULhn8j5_ikaQ8Tq/view?usp=sharing) - [Windows - X86\_64](https://drive.google.com/file/d/1QKqkhTRXwe4b6vsLqlJ8Ov1GkGIuamUo/view?usp=sharing). Please don’t hesitate to force a ‘repair’ to confirm everything works correctly for you ---
**Author:** ![napolij](https://avatars.discourse-cdn.com/v4/letter/n/a4c791/32.png) [@napolij](https://forums.plex.tv/u/napolij)\ **Post date:** [October 9, 2026, 9:38pm UTC](https://forums.plex.tv/t/dbrepair-development/822684/1378 "2026-10-09T21:38:12Z")
Did DBRepair auto. Saw it stop PMS, Did db checks, all ok, Restarted PMS Fedora 44 x86\_64 ---
**Author:** ![balthazarr1](https://avatars.discourse-cdn.com/v4/letter/b/a87d85/32.png) [@balthazarr1](https://forums.plex.tv/u/balthazarr1)\ **Post date:** [October 9, 2026, 10:49pm UTC](https://forums.plex.tv/t/dbrepair-development/822684/1379 "2026-10-09T22:49:31Z")
Ran it on auto QuTS Hero latest non-beta everything… Reported both DBs as okay, but then proceeded to rebuild both DBs, which checked okay after the rebuild. Is this intentional behaviour? ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [October 10, 2026, 12:44am UTC](https://forums.plex.tv/t/dbrepair-development/822684/1380 "2026-10-10T00:44:53Z")
Yes. that’s how it should be. Did PMS run ok or fail? ---
**Author:** ![balthazarr1](https://avatars.discourse-cdn.com/v4/letter/b/a87d85/32.png) [@balthazarr1](https://forums.plex.tv/u/balthazarr1)\ **Post date:** [October 10, 2026, 1:27am UTC](https://forums.plex.tv/t/dbrepair-development/822684/1381 "2026-10-10T01:27:40Z")
Fine both before and after. ---
**Author:** ![StephenH](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/stephenh/32/313798_2.png) [@StephenH](https://forums.plex.tv/u/StephenH)\ **Post date:** [October 10, 2026, 4:22am UTC](https://forums.plex.tv/t/dbrepair-development/822684/1382 "2026-10-10T04:22:12Z")
> [@ChuckPa](#): > > For your consideration: All looking good for me testing 00.99.13 on macOS Sequoia 15.8.1 with ARM64, thanks @ChuckPa ---
**Author:** ![AnonFawkes](https://avatars.discourse-cdn.com/v4/letter/a/5e9695/32.png) [@AnonFawkes](https://forums.plex.tv/u/AnonFawkes)\ **Post date:** [October 10, 2026, 7:09am UTC](https://forums.plex.tv/t/dbrepair-development/822684/1383 "2026-10-10T07:09:50Z")
```auto Stopping PMS. (60 second max delay) Stopped PMS. Checking the PMS databases... Database itself is fine however 1 tables/triggers/indexes are missing. Repair required. Main DB is damaged. Blobs DB is OK. --- Processing Main DB --- Rebuilding Main DB Transferring schema. Building FTS tables. Generating triggers. Transferring data records. Generating indexes. Warning: New index found (index_title_sort_naturalsort) in Main DB. Please inform '@ChuckPa'. Warning: New index found (index_taggings_on_created_at) in Main DB. Please inform '@ChuckPa'. 1 index missing from source, recreated from stored schema. Populating FTS tables. Checking Main DB after rebuild. Main DB rebuild and verification complete. --- Processing Blobs DB --- Rebuilding Blobs DB Transferring schema. Building FTS tables. Generating triggers. Transferring data records. Generating indexes. Populating FTS tables. Checking Blobs DB after rebuild. Blobs DB rebuild and verification complete. Making DB(s) active Swap complete. Live databases updated. Automatic repair successful. Starting PMS. Started PMS. ``` @ChuckPa Plex version 1.43.5.11029 on linux ---
**Author:** ![dokuro](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/dokuro/32/329926_2.png) [@dokuro](https://forums.plex.tv/u/dokuro)\ **Post date:** [October 10, 2026, 9:20am UTC](https://forums.plex.tv/t/dbrepair-development/822684/1384 "2026-10-10T09:20:25Z")
> [@napolij](#): > > Fedora 44 x86\_64 @napolij Hello fellow fedora admin 🙂 @ChuckPa Ran a number of tests today with the new updated tool, I’d not had a change to review any of your updates over the past few months. Gave it a good hour today trying various aspects and everything passed on my dbs. Thanks. ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [October 10, 2026, 4:30pm UTC](https://forums.plex.tv/t/dbrepair-development/822684/1385 "2026-10-10T16:30:41Z")
@AnonFawkes do you still have a copy of the databases before running DBRepair ? If so, could you zip them up for me and PM me a link to where I can download them from ? Something isn’t right (obviously) and I’d like to see what happened. Also , may I have the full DBRepair log file ? ---
**Author:** ![AnonFawkes](https://avatars.discourse-cdn.com/v4/letter/a/5e9695/32.png) [@AnonFawkes](https://forums.plex.tv/u/AnonFawkes)\ **Post date:** [October 10, 2026, 6:30pm UTC](https://forums.plex.tv/t/dbrepair-development/822684/1386 "2026-10-10T18:30:31Z")
@ChuckPa only if it backs up the db somewhere do I have a copy. I should of backed up beforehand and that’s my bad. As far as the full log, where would that be at? I’m running inside the hotio container ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [October 10, 2026, 6:35pm UTC](https://forums.plex.tv/t/dbrepair-development/822684/1387 "2026-10-10T18:35:36Z")
@AnonFawkes You can PM me the DBrepair.log file. Backups & intermediate files are kept for every database-modifying step during the session (how History & Revert work)., Once the session ends, the history and temp files are removed to avoid collecting junk [Previous page](https://forums.plex.tv/t/dbrepair-development/822684.md?page=63) [Next page](https://forums.plex.tv/t/dbrepair-development/822684.md?page=65)