Announcement

Collapse
No announcement yet.

fetch_table_info Error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • fetch_table_info Error

    I did a search for this problem and couldn't find any info on it. I'm updating from vB 3.5.6 to vB 3.6 and encountered this on step 9 (Paid Subscriptions updates):

    Originally posted by My screwed up update
    Step 9) Paid Subscription Updates
    • Altering profilefield Table (1 of 1)
    • Updating profilefield table
    • Altering adminhelp Table (1 of 1)
    • Altering session Table (1 of 1)
    • Altering phrase Table (1 of 3)
    • Altering phrase Table (2 of 3)
    • Altering phrase Table (3 of 3)
    • Creating subscriptionpermission table
    • Altering paymentinfo Table (1 of 1)
    • Altering paymenttransaction Table (1 of 7)vB_Database_Alter: fetch_table_info() has not been called successfully.

  • #2
    Any help guys? I've got a forum that's not working.

    Comment


    • #3
      The first thing you need to do is reupload all the original 3.6.0 non-image files (except install.php). Make sure you upload these in ASCII format and overwrite the ones on the server.
      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


      • #4
        I re-uploaded everything and it still does the same thing when I'm trying to upgrade to 3.6.0b1 on step 9.

        Comment


        • #5
          The error indicates that MySQL can not retrieve information on the current table. You could try running repair tables a few times, and then retry the upgrade.
          Want to take your board beyond the standard vBulletin features?
          Visit the official Member to Member support site for vBulletin Modifications: www.vbulletin.org

          Comment


          • #6
            Originally posted by Marco van Herwaarden View Post
            The error indicates that MySQL can not retrieve information on the current table. You could try running repair tables a few times, and then retry the upgrade.
            I just ran repair & optimize tables twice and it still gives me the same thing. This isn't looking good.

            This is the information I'm given on my forum index page:

            Originally posted by My Forum Index page SQL error
            Database error in vBulletin 3.5.5:

            Invalid SQL:

            SELECT
            user.username, (user.options & 512) AS invisible, user.usergroupid,
            session.userid, session.inforum, session.lastactivity,
            IF(displaygroupid=0, user.usergroupid, displaygroupid) AS displaygroupid, infractiongroupid
            FROM session AS session
            LEFT JOIN user AS user ON(user.userid = session.userid)
            WHERE session.lastactivity > 1154723552
            ORDER BY username ASC;

            MySQL Error : Unknown column 'infractiongroupid' in 'field list'
            Error Number : 1054
            Date : Friday, August 4th 2006 @ 01:47:32 PM
            Script : http://*pathto*/forums/
            Referrer :
            IP Address : *deleted*
            Username : *deleted*
            Classname : vb_database
            Last edited by Weirdwolf; Fri 4th Aug '06, 1:50pm.

            Comment


            • #7
              *bump*

              I hate to seem pushy, but I really would like to get my forums back up and running. I am recieving IM's and emails about the status of my board and it's getting annoying typing "I'm working on it". Thanks.

              Comment


              • #8
                It would help if you posted the complete error, including the script info.
                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


                • #9
                  I'm not sure what you mean? Above I've copied and pasted both entire errors (the latter with sensitive info deleted).

                  Screencap 1
                  Screencap 2

                  Comment


                  • #10
                    The error above is caused by the upgrade script not being run until the end. Unless you are able to repair the database (might need to ask your host for support) and finish the upgrade, you will not be able to get your board running without errors.

                    If you have a backup from before the upgrade, i would suggest you try to restore the database, make sure there is no corruption (run repair a few times), and then retry to upgrade process.
                    Want to take your board beyond the standard vBulletin features?
                    Visit the official Member to Member support site for vBulletin Modifications: www.vbulletin.org

                    Comment


                    • #11
                      PS you just added the screenshots, they are too small to read, but they look like the errors you posted in here, so it should not make much of a difference as to the solution.
                      Want to take your board beyond the standard vBulletin features?
                      Visit the official Member to Member support site for vBulletin Modifications: www.vbulletin.org

                      Comment


                      • #12
                        If all else fails you could delete the paymenttransaction table and then recreate it, like this ;

                        Run;

                        Code:
                        DROP TABLE paymenttransaction
                        Then ;

                        Code:
                        CREATE TABLE paymenttransaction (
                        	paymenttransactionid INT UNSIGNED NOT NULL AUTO_INCREMENT,
                        	paymentinfoid INT UNSIGNED NOT NULL DEFAULT '0',
                        	transactionid VARCHAR(250) NOT NULL DEFAULT '',
                        	state SMALLINT UNSIGNED NOT NULL DEFAULT '0',
                        	amount DOUBLE UNSIGNED NOT NULL DEFAULT '0',
                        	currency VARCHAR(5) NOT NULL DEFAULT '',
                        	dateline INT UNSIGNED NOT NULL DEFAULT '0',
                        	paymentapiid INT UNSIGNED NOT NULL DEFAULT '0',
                        	request MEDIUMTEXT,
                        	reversed INT UNSIGNED NOT NULL DEFAULT '0',
                        	PRIMARY KEY (paymenttransactionid),
                        	KEY dateline (dateline),
                        	KEY transactionid (transactionid),
                        	KEY paymentapiid (paymentapiid)
                        )
                        Baby, I was born this way

                        Comment


                        • #13
                          Originally posted by Paul M View Post
                          If all else fails you could delete the paymenttransaction table and then recreate it, like this ;

                          Run;

                          Code:
                          DROP TABLE paymenttransaction
                          Then ;

                          Code:
                          CREATE TABLE paymenttransaction (
                              paymenttransactionid INT UNSIGNED NOT NULL AUTO_INCREMENT,
                              paymentinfoid INT UNSIGNED NOT NULL DEFAULT '0',
                              transactionid VARCHAR(250) NOT NULL DEFAULT '',
                              state SMALLINT UNSIGNED NOT NULL DEFAULT '0',
                              amount DOUBLE UNSIGNED NOT NULL DEFAULT '0',
                              currency VARCHAR(5) NOT NULL DEFAULT '',
                              dateline INT UNSIGNED NOT NULL DEFAULT '0',
                              paymentapiid INT UNSIGNED NOT NULL DEFAULT '0',
                              request MEDIUMTEXT,
                              reversed INT UNSIGNED NOT NULL DEFAULT '0',
                              PRIMARY KEY (paymenttransactionid),
                              KEY dateline (dateline),
                              KEY transactionid (transactionid),
                              KEY paymentapiid (paymentapiid)
                          )
                          THANK YOU, THANK YOU, THANK YOU, ever so much. This fixed my problem, as for some reason the paymenttransaction table wasn't even in the database. I tried to drop it, but the SQL query couldn't because the table didn't exist. I inserted the table with the above query and it works perfectly now.

                          Comment


                          • #14
                            I have the same problem, except the table that doesn't exist in my db is "adminlog".

                            How would I go about creating that table, with all the proper entries?

                            EDIT: I found the mysql schema file, and successfully entered in this table. It looks like one of the previous upgrades I did neglected to add this table (I noticed quite a few others ran into this problem as well).
                            Last edited by lowlight; Fri 11th Aug '06, 3:58am.

                            Comment

                            Related Topics

                            Collapse

                            Working...
                            X