I am having the same issue.
Yes, it did not have any impact. We are able to delete any new distribution package and even a copy of an older one, but are unable to delete any older distribution packages without getting the error stated above.
do you have any solutions about this...? Is this problem fixed? and when how?
Chances are that there's some database-side problems.
First off - here's an article on how to detect & deal with orphaned data that I've written up - Detecting and handling orphaned data in your databases / how to delete items that re-appear constantly. - which may help (Warning - this will require full SQL Server admin access & you may need to lean on a DBA for help).
Secondly - "database checking" can be done via "DBCC" (assuming you're on SQL Server). That's the "DataBase Consistency Checker".
If you need to, you can contact LD support (chances are they'll need a full backup of your database) to help you out with this & see what's broken & how to fix it (for obvious reasons, I'd strongly be against such "fiddling" on live systems, as it should be deemed "high risk" at all times).
If there is orphaned data / problems with the database, it'd be "regular SQL Server process" to get those fixed (since we just throw commands at the DB, it's SQL Server that handles it).
Hope that helps?
"Coredbutil" is not likely to have much of an effect here, since that only (re-)creates missing tables & such. It can't fix things such as orphaned data, because that's something that SQL Server itself messed up with.