Can a corrupt database be fixed?

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:
BBCode is ON
[img] is ON
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: Can a corrupt database be fixed?

Re: Can a corrupt database be fixed?

by nynaevelan » Tue Feb 02, 2010 6:54 pm

nohitter151 wrote: There is also a script floating around somewhere which you can use to import playcounts from an old DB in the event that you have to create a new one for some reason. Similar add-ons for playlists, etc. are available.

That same script does playlists and added dates also: http://www.mediamonkey.com/forum/viewto ... =2&t=42085

Re: Can a corrupt database be fixed?

by nohitter151 » Tue Feb 02, 2010 6:39 pm

cali wrote:Yes, I did optimize the DB. The complete option.
There is also a script floating around somewhere which you can use to import playcounts from an old DB in the event that you have to create a new one for some reason. Similar add-ons for playlists, etc. are available.

Re: Can a corrupt database be fixed?

by nynaevelan » Tue Feb 02, 2010 8:28 am

Try these tools to see if they help: http://www.mediamonkey.com/forum/viewto ... it=+schema

Re: Can a corrupt database be fixed?

by cali » Mon Feb 01, 2010 8:04 pm

Yes, I did optimize the DB. The complete option.

Re: Can a corrupt database be fixed?

by nohitter151 » Mon Feb 01, 2010 7:53 pm

cali wrote:I'd been having some problems with MM for a few weeks, MM freezes or takes forever to start playing the first track, but not always. I finally narrowed it down to the database, it might be corrupt or it's too large (128MB).

Is there a way to fix it? Even if it's manually; I don't wanna lose my DB.

BTW, I'm using mm 3.2.0.1294 in a Win 7 64-bit system.
Did you try File > Maintain library (optimize database complete)

Can a corrupt database be fixed?

by cali » Mon Feb 01, 2010 7:47 pm

I'd been having some problems with MM for a few weeks, MM freezes or takes forever to start playing the first track, but not always. I finally narrowed it down to the database, it might be corrupt or it's too large (128MB).

Is there a way to fix it? Even if it's manually; I don't wanna lose my DB.

BTW, I'm using mm 3.2.0.1294 in a Win 7 64-bit system.

Top