Forums

migrated to a new server, hit some problems (2 posts)

  1. Ovidiu
    Member
    Posted 6 months ago #

    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 column comment_ID
    More than one INDEX key was created for column comment_approved
    More than one INDEX key was created for column comment_post_ID
    More than one INDEX key was created for column comment_date_gmt
    More than one INDEX key was created for column comment_author_url
    Problems with indexes of table wp_pac_links
    PRIMARY and INDEX keys should not both be set for column link_id
    UNIQUE and INDEX keys should not both be set for column link_rel
    UNIQUE and INDEX keys should not both be set for column link_rating
    More than one UNIQUE key was created for column link_rating
    UNIQUE and INDEX keys should not both be set for column link_name
    UNIQUE and INDEX keys should not both be set for column link_target
    UNIQUE and INDEX keys should not both be set for column link_updated
    More than one INDEX key was created for column link_updated
    UNIQUE and INDEX keys should not both be set for column link_rss
    More than one INDEX key was created for column link_category
    More than one INDEX key was created for column link_visible
    More than one FULLTEXT key was created for column link_visible
    More than one INDEX key was created for column link_image
    More than one INDEX key was created for column link_description
    Problems with indexes of table wp_pac_movie_ratings
    PRIMARY and INDEX keys should not both be set for column id
    UNIQUE and INDEX keys should not both be set for column watched_on
    More than one INDEX key was created for column watched_on
    UNIQUE and INDEX keys should not both be set for column title
    More than one FULLTEXT key was created for column title
    More than one FULLTEXT key was created for column review

  2. sql server hosting
    Member
    Posted 3 months ago #

    if you have an old installation of wordpress , you can copy do following

    1. first export the comments (or any table that needs to be repaired) -> export to .sql file

    2. open up your new installation and using phpmyadmin import the above file

    your old table will get restored this way

Reply

You must log in to post.

About this Topic