Any time we do something during start up we should do everything we can to prevent an error from blowing it up. If the DB was corrupt but working (small chance, I know) this would break the startup process and leave someone with a dead installation.

Seems like a pretty good candidate for a migration, otherwise the solution is to manually update the DB, or start from scratch, both of which will very likely result in a forum post and time spent troubleshooting.