Error upgrading from 7.2 to 7.6

[pna]

Hi,

I am upgrading an OD 7.2 setup to 7.6. As a test, I ran upgrade process by running OD 7.6 on a copy of the production MySQL database. During the upgrade, the process fails with following error message:

Code: Select all

Field "PluginDIIName" doesn't have a default value
Conversion unsuccessful. your database is now corrupted & you can not use it. please contact us

As the message says, the database isn't usable after the process aborts. Since this is not the production database, I don't need to recover the corrupted database; I can always copy from the backup again. But, any ideas on what could be the issue and how to resolve this?

Thanks

[jordansparks]

Looks like you should turn off any plugins before upgrading. I think a plugin is to blame.

[pna]

Thanks for the suggestion. I received a new backup after all the plugins were disabled. That didn't help much -- I get the same error. If I am guessing correctly, just disabling the plugins probably didn't revert the mysql schema back to the vanilla state that open-dental expects (if it was indeed modified by a plugin) and hence the error still persists. Did you mean uninstalling the plugins when you said "turning-off plugins"?

Another possibility that comes to mind is: the error could be due to the fact that I am upgrading on a test computer that just has the OD 7.6 executable (without the plugins) using the production database which, a plugin could possibly have modified. So the question is, do plugins participate in the upgrade process? In other words, would the results be any different if I copied the plugins on top of fresh install of OD 7.6 just before upgrading?

Thanks again for your help.

[jordansparks]

Oh, wait a minute. I think I know what's wrong.
http://www.opendental.com/manual/mysqls ... ables.html

The only thing is, I thought we addressed that. You must have some extra clutter in your my.ini file that we didn't anticipate.

[pna]

Finally I got a chance to try your suggestion and you were spot on. I had a non-blank string for sql-mode in my.ini file that specified

sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

This isn't the default, but maybe when mySQL is installed separately (which I did), it sets this stricter and standard compliant mode for INSERT statements, which probably in turn tripped a new SQL in 7.6.

Thanks for your help.

PS A similar problem was addressed here http://bugkill.blogspot.com/2007/06/mys ... fault.html