That was my question about the old DB, so apparently something killed 3838716.
Because File is a view, I “think” that delete is by by DELETE FROM “FileLookup”.
I see four of those in the source, and am wishing there was a profiling log to help.
Maybe first show “Verify files” button complains now. It likely will, but we know why.
Make a manual copy of the database to reduce risk if fix attempt makes this worse.
You could then either try an ambitious fix by inserting the File row that was missing
(which may break if it’s missing because something it needs for that file is missing),
or just make FilesetEntry forget it knows about that log file that sounds unessential.
I don’t see anything in Fileset table that says how many FilesetEntry rows it has, so
deleting a row will probably be tolerated. You can then see if Verify files gets happy.
That’s not quite the end of it (but a great start), as a dlist file is a fileset, with its info.
Database and destination internals but dlist files can be recreated if DB is correct…