Database need to be upgraded loop

Yes, I am able to use the admin area just fine. The message is just an annoyance.

I tried upgrading again with a local version. Upgrading from MU 2.7 to 2.8.1, I got several of these errors in the php error log:

[16-Jul-2009 09:58:37] WordPress database error Duplicate key name ‘taxonomy’ for query ALTER TABLE wp_21_term_taxonomy ADD KEY taxonomy (taxonomy) made by wp_upgrade, make_db_current_silent, dbDelta

The upgrade said it completed successfully, but I am still seeing the “WordPress MU 2.8.1 is available! Please update.” message.

Any thoughts?

Something about your databases are hosed. My advice would be:
1. Restore from your backup.
2. Export the blog using the WP export functionality.
3. Create a new fresh blog with 2.8.1 (possibly in a subdirectory).
4. Import the data from your previous export.
5. Copy your themes, plugins, etc. Reconfigure your blog to make it work again and look the way it did.
6. Move the new working blog over the old one.

When you have a broken database, then you need to get a fresh one and eliminate that old broken one. An Export/Import process will keep your data but eliminate the database as the source of the problem (since you’re starting fresh). This is the only way to be sure, any manual attempts to fix the database is just going to be way more of a pain.

WP export funtionality? Possible without accessing wp-admin?

I already did use fresh version and just configured DB, doen’t work either. So how can an export/import be done?

You missed step 1: Restore from your backup. Whatever you had before which was working, put that back on there.

Before you can fix anything, you need to get the site working again, at minimum.

Well there you got me now…. No working copy left….

I remember having that problem on last upgrade too and was able to fix it. But I’m not sure what the problem was, may differing db_version, which isn’t the case now.

So…. Got lost now? ??

Well, then, you’re kinda screwed.

Best I can say is to make a fresh new blog and then manually copy your posts and such into new ones.

Never do an upgrade without a working backup.

Isn’t there a way to override that check and just tell WP to use DB as it is?

So I finally found a .sql before upgrade…. Tried to put into new DB, configured WP to use that one. db_version wasn’t the one of the actual version. Agreed to upgrade at wp_admin, version was raised but ended up in the loop again….