Upgrade 3.71 to latest 4.X release - LONG upgrade step 104

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Zachery
    Former vBulletin Support
    • Jul 2002
    • 59097

    #16
    I think it should be


    ALTER TABLE post DROP INDEX title
    ALTER TABLE thread DROP INDEX title

    If you dont get anything, you might not have those indecies.

    Comment

    • DiscussAnything
      Senior Member
      • Nov 2002
      • 166

      #17
      Thanks, that did seem to drop the index.

      However, I feel when I rerun the upgrade, I'm getting a different error, I believe earlier:

      An error has occurred with your database. Please contact vBulletin Support for assistance.
      Module: 400a1, Step 23 Database Error:1025
      Error on rename of './test/#sql-a1c_5c' to './test/tag' (errno: 121)
      Query:
      ALTER TABLE tag ENGINE=InnoDB
      www.discussanything.com

      Comment

      • Trevor Hannant
        vBulletin Support
        • Aug 2002
        • 24325
        • 5.7.X

        #18
        That's an issue with your database - you should speak to your host regarding this.
        Vote for:

        - Admin Settable Paid Subscription Reminder Timeframe (vB6)
        - Add Admin ability to auto-subscribe users to specific channel(s) (vB6)

        Comment

        • Zachery
          Former vBulletin Support
          • Jul 2002
          • 59097

          #19
          Originally posted by DiscussAnything
          Module: 400a1, Step 23 Database Error:1025
          Error on rename of './test/#sql-a1c_5c' to './test/tag' (errno: 121)
          Query:
          ALTER TABLE tag ENGINE=InnoDB
          OS error code 121: Remote I/O error
          MySQL error code 121: Duplicate key on write or update

          I would go with the OS error over the mysql error on this one.

          Comment

          • kontrabass
            Senior Member
            • Jul 2000
            • 302
            • 3.6.x

            #20
            Originally posted by Trevor Hannant
            That's an issue with your database - you should speak to your host regarding this.

            Ummm... Yeah... so why is this an issue that many people are having, that is a confirmed, reproducable bug with "MAJOR" status in the bug tracker? http://tracker.vbulletin.com/browse/VBIV-4353

            I cannot upgrade for the same reason. Nothing's wrong with my OS or database.

            Comment

            • Zachery
              Former vBulletin Support
              • Jul 2002
              • 59097

              #21
              You can remove that line of the upgrade and continue past it, though i still believe there is a fault here with mysql. Maybe I am wrong, but if that was a real issue wouldnt it effect every upgrade?

              Comment

              • Steve Machol
                Former Customer Support Manager
                • Jul 2000
                • 154488

                #22
                The problem is that this issue was never really confirmed to be a bug in vB, regardless of the status of that issue.
                Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
                Change CKEditor Colors to Match Style (for 4.1.4 and above)

                Steve Machol Photography


                Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


                Comment

                • kontrabass
                  Senior Member
                  • Jul 2000
                  • 302
                  • 3.6.x

                  #23
                  Originally posted by Zachery
                  You can remove that line of the upgrade and continue past it, though i still believe there is a fault here with mysql. Maybe I am wrong, but if that was a real issue wouldnt it effect every upgrade?
                  It seems like there are a good handful of us that have this error judging from the 2 threads I've found this afternoon. I can alter the table storage engines just fine in phpMyAdmin (I just changed table "tag" to InnoDB via phpMyAdmin), so I don't know why the vb console updater should fail?

                  Code:
                  Upgrading to 3.8.0
                  ----------------------------------
                  Upgrade Complete
                  
                  Upgrading to 4.0.0 Alpha 1
                  ----------------------------------
                  Step 1 - Altering reputation Table (1 of 4)
                  Step 2 - Altering reputation Table (2 of 4)
                  Step 3 - Altering reputation Table (3 of 4)
                  Step 4 - Altering reputation Table (4 of 4)
                  Step 5 - Altering subscribegroup Table (1 of 1)
                  Step 6 - Altering thread Table (1 of 1)
                  Step 7 - Altering reputation Table (1 of 2)
                  Step 8 - Altering reputation Table (2 of 2)
                  Step 9 - Altering subscribegroup Table (1 of 1)
                  Step 10 - Altering forum Table (1 of 1)
                  Step 11 - Altering thread Table (1 of 2)
                  Step 12 - Altering thread Table (2 of 2)
                  Step 13 - Altering tachyforumpost Table (1 of 1)
                  Step 14 - Altering tachythreadpost Table (1 of 1)
                  Step 15 - Altering style Table (1 of 1)
                  Step 16 - Altering template Table (1 of 1)
                  Step 17 - Creating templatemerge table
                  Step 18 - Updating adminmessage table
                  Step 19 - Updating adminmessage table
                  Step 20 - Updating adminmessage table
                  Step 21 - Altering tag Table (1 of 1)
                  Step 22 - Creating index canonicaltagid on tag
                  Step 23 - Updating phrasetype table
                  
                  ----------------------------------
                  Error on rename of './forum4test/#sql-1350_97606' to './forum4test/tag' (errno: 121)
                  ----------------------------------
                  ALTER TABLE tag ENGINE=InnoDB

                  Comment

                  • Paul M
                    Former Lead Developer
                    vB.Com & vB.Org
                    • Sep 2004
                    • 9886

                    #24
                    Error 121 is duplicate key.

                    Possibly the tablename already exists in the Innodb data dictionary, so when mysql tries to add it again, it fails.

                    Look in your mysql err log and you should see more details on whats actually failing.
                    Baby, I was born this way

                    Comment

                    • kontrabass
                      Senior Member
                      • Jul 2000
                      • 302
                      • 3.6.x

                      #25
                      You're right: The problem it turns out is that I did a test upgrade to vb4 back in 2010. I dumped the test db after deciding to stick to 3.6, but apparently innodb holds onto table names somewhere internally. Since I used the same test database name for both test upgrades (even though the first was 'dumped'), the recent test failed.

                      Would recommend getting rid of the issue in the bug tracker, as that's the first thing that came up when I google'd this error.
                      Last edited by kontrabass; Thu 24 Mar '11, 7:18am.

                      Comment

                      Related Topics

                      Collapse

                      Working...