Open Dental Forum

Tried to update from 6.8.32 to 6.9.50 this evening . Got error message. 'Incorrect information in file graphicsassembly.frm'

Checked the contents of the file. It seems to be empty.

Did I miss something in updating? Is there another file to download with this new release?

Thanks
drtmz

Could it be this?: http://www.opendental.com/manual/mysqls ... ables.html

Or maybe the database maint tool needs to be run.

I have been updating with no problem on my Windows XP pro machines since forever with no problem.
I use everything from OD nothing else.
I get a message that the conversion to 6.9.50 failed and OD never starts so I can't run the database maintenance tool.
I reinstall 6.8.32 and it works just fine.

drtmz

Can you run the db maint on 6.8 and then convert?

Jordan,

Ran the database maintenance tool and this is what I got
01/07/2010 10:42:24 AM------------------------------------------------------------------------------------------
Corrupt file found for table graphicassembly
Repair log:
colmar.graphicassembly,repair,error,Incorrect information in file: '.\colmar\graphicassembly.frm',
Corrupt file found for table graphicelement
Repair log:
colmar.graphicelement,repair,error,Incorrect information in file: '.\colmar\graphicelement.frm',
Corrupt file found for table graphicpoint
Repair log:
colmar.graphicpoint,repair,error,Incorrect information in file: '.\colmar\graphicpoint.frm',
Corrupt file found for table graphicshape
Repair log:
colmar.graphicshape,repair,error,Incorrect information in file: '.\colmar\graphicshape.frm',
Corrupt file found for table graphictype
Repair log:
colmar.graphictype,repair,error,Incorrect information in file: '.\colmar\graphictype.frm',
Corrupt file found for table proclicense
Repair log:
colmar.proclicense,repair,error,Incorrect information in file: '.\colmar\proclicense.frm',
Corrupt file found for table scheddefault
Repair log:
colmar.scheddefault,repair,error,Incorrect information in file: '.\colmar\scheddefault.frm',
Corrupted files probably fixed. Look closely at the log. Also, run again to be sure they were really fixed.

I then ran it a second time and got the same result so it looks like nothing is fixed.

Tom Zaccaria

You have a corrupted database. That's why it won't upgrade properly. The good news is that none of those tables are even used anymore. But you will have to get us involved in the fix unless you want to restore from a backup that's not corrupt.

It's curious to me that all of the corrupted tables are essentially empty tables. To me, that means that you might be using some backup software that ignores or changes files that are empty. Did you restore from a backup at any time? If you are doing this on your home computer, then you are restoring from a backup, and it could be the actual backup process that is faulty. Are you running the db maint tool at the office, or are you running it on a restored backup at home?

Kudos to Shannon and James. We somehow got some corrupt files which they had to remove. Then we were good to go.
drtmz