hi there.
2 weeks ago I moved from one root server to a new one. during this move, I moved a couple of wordpress installations and oen wpmu isntallation from the old server to the new one.
It seemed everything had gone perfectly ok but now I find some odd behaviour. If I open the moved databases on the new server with phpmyadmin, I get warnings liek the ones below and after studying the wordpress database description it seems at least the wp_comments indexes are ok, but then why is phpmyadmin complaining?
Basically the problems I hit start already in the export phase:
mysql -h localhost -u root -pmyPass -c --add-drop-table --add-locks --all --quick --lock-tables web6db5 > /root/web6db5.sql
mysql: unknown option '-c'
ok, seems the -c switch is obsolete, so I tried the replacement --skip-auto-rehash:
mysql -h localhost -u root -pmyPass --skip-auto-rehash --add-drop-table --add-locks --all --quick --lock-tables web6db5 > /root/web6db5.sql
mysql: unknown option '--add-drop-table'
then I tried doing the whole thing via phpmyadmin and it seemed to have succeeded.
QUESTIONS:
- can anyone help me with those export commands? that would be the best I think, because then I would just export again.
- If I have manually fiddled with a database, is there an automatic way to have wordpress restore it, in terms of indexes, etc? maybe manually calling the DB upgrade that occurs sometimes during bigger wordpress updates? OR do ihave to manually go through: http://codex.wordpress.org/Database_Description#Table:_wp_comments and manually compare?
- what about these phpmyadmin warnings? what to do about them?
Problems with indexes of table
wp_pac_comments
PRIMARY and INDEX keys should not both be set for columncomment_ID
More than one INDEX key was created for columncomment_approved
More than one INDEX key was created for columncomment_post_ID
More than one INDEX key was created for columncomment_date_gmt
More than one INDEX key was created for columncomment_author_url
Problems with indexes of tablewp_pac_links
PRIMARY and INDEX keys should not both be set for columnlink_id
UNIQUE and INDEX keys should not both be set for columnlink_rel
UNIQUE and INDEX keys should not both be set for columnlink_rating
More than one UNIQUE key was created for columnlink_rating
UNIQUE and INDEX keys should not both be set for columnlink_name
UNIQUE and INDEX keys should not both be set for columnlink_target
UNIQUE and INDEX keys should not both be set for columnlink_updated
More than one INDEX key was created for columnlink_updated
UNIQUE and INDEX keys should not both be set for columnlink_rss
More than one INDEX key was created for columnlink_category
More than one INDEX key was created for columnlink_visible
More than one FULLTEXT key was created for columnlink_visible
More than one INDEX key was created for columnlink_image
More than one INDEX key was created for columnlink_description
Problems with indexes of tablewp_pac_movie_ratings
PRIMARY and INDEX keys should not both be set for columnid
UNIQUE and INDEX keys should not both be set for columnwatched_on
More than one INDEX key was created for columnwatched_on
UNIQUE and INDEX keys should not both be set for columntitle
More than one FULLTEXT key was created for columntitle
More than one FULLTEXT key was created for columnreview