Database lost in migration

  • Resolved TiffanyBlitz

    (@tiffanyblitz)


    17 years, 4 months ago

    Okay, I think I’ve dug myself a deep hole this time…

    I am migrating my website to a new hosting company. Same URL, just changing the DNS to point to the new place.

    I have two instances of WP running, call them my main blog and my sales blog.

    I backed up everything… databases, files, got it all. Then I switched the DNS.

    Then I upload everything (FTP) onto the new server. Files are fine, main WP database “import” goes fine. But the sales database won’t import, it keeps generating SQL errors.

    My guess is that this may be because I never upgraded the WP on that blog (it’s still on 2.2-something?), since I never use it lately and didn’t think of it. So the database never got upgraded, so now it’s archaic… ??

    Now that the DNS is changed, I cannot get back to the old server via FTP to upgrade the WP and test my theory. I can still get to the databases via cPanel to the PHPMyAdmin, but don’t know what to do that might help. (I already had two copies of the backup, one straight and one zipped, so I assume it’s not just an error from a bad copy).

    I know I just said I don’t use this much, but there is a lot of time into putting the info together, and I do believe it will be needed in the future…

    Please – any thoughts?!

    Thank you!!

Viewing 5 replies - 1 through 5 (of 5 total)

  • You say:

    “But the sales database won’t import, it keeps generating SQL errors.“

    But you mention issues with upgrading WordPress. So are you getting these errors during the import of the database (where the version of WP you used for it would not be an issue), or after when trying to access the blog?

    If the latter, try running wp-admin/upgrade.php on your sales blog.

    Thread Starter TiffanyBlitz

    (@tiffanyblitz)

    I was saying I thought that might be an issue because of SQL versions or something. It happens during the import of the database – I haven’t even gotten as far as looking at the blog.

    I cannot go back update the blog on the old server, and try downloading the db again, because I can’t get to it now that the DNS points to the new server…

    So if the WP version updates don’t effect the SQL in any way, then that is NOT the issue, and I have no idea what is…

    Well, the actual SQL errors may help track down the problem. Can you post them here or — if too numerous — in a file uploaded somewhere you can link to here?

    Thread Starter TiffanyBlitz

    (@tiffanyblitz)

    When I try to import the uncompressed db file, I get this:

    SQL query:

    — phpMyAdmin SQL Dump
    — version 2.10.0.2
    — https://www.phpmyadmin.net
    —
    — Host: localhost
    — Generation Time: Nov 02, 2007 at 01:18 PM
    — Server version: 4.1.22
    — PHP Version: 4.4.4
    SET SQL_MODE = “NO_AUTO_VALUE_ON_ZERO”
    MySQL said:

    #1193 – Unknown system variable ‘SQL_MODE’

    When I try to import the zipped version of the db, I get this:

    Error
    There is a chance that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if the parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:
    —-BEGIN CUT—-
    eNodjjFvgzAUhJHSofLcH/CGjPjVNiQQbwhZaVQCFCfpTApqqFxCcVIlS3925zqVbjidTvedqqqi
    kpBySAVkKpcgIAAeEb1x8YSQdKclTFeNBPtlhnq07Yim2+NwGPxvEBjMQTA2e2Sxk7NSCMk5mPZz
    AeoywJSsr/olkxAiQxFRe6r7ph4bao7vZKsrKLQPyVLlGx92yjFfux5WCiJkpFwn7g/OMaSDCUj5
    VN4qfqFvawFyRh0a7dvBnPsGOWRdf76QLMmXEtqedvZI43i2oJz8PyifJ3cPnufde6ePfRT+/P4B
    +lhA4w==
    —-END CUT—-
    —-BEGIN RAW—-

    ERROR: C1 C2 LEN: 2 3 17
    STR: 

    CVS: $Id: sqlparser.lib.php,v 2.36 2005/08/08 20:22:11 lem9 Exp $
    MySQL: 4.0.27-standard-log
    USR OS, AGENT, VER: Win IE 7.0
    PMA: 2.6.4-pl3
    PHP VER,OS: 4.3.10-200.schlund.1 Linux
    LANG: en-iso-8859-1
    SQL: PKtjb74~?—-END RAW—-
    SQL query:

    PKtjb74~?
    MySQL said:

    #1064 – You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near ‘PK’ at line 1

    Hope that makes sense to someone else, because it’s all Greek to me! LOL

    The latter stuff is gibberish to me as well (I’m not geek in *all* things ;) ). But the former seems to denote a mismatch between the MySQL versions — which is not often a problem but it does crop up.

    I recommend locating that SET SQL_MODE line in your sql dump (i.e. the uncompressed db) file and edit it out. Or for safety’s sake, you can comment it out by placing a:

    #

    at the beginning of the line. Then try the import again.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Database lost in migration’ is closed to new replies.