Forum DB error...

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Blairwarlock
    Senior Member
    • Nov 2001
    • 199

    Forum DB error...

    Server ran out of disk space again and corrupted the DB. I freed up disk space, but here's the error I get...

    <!-- Database error in vBulletin 2.2.9:
    Invalid SQL: SELECT user.*,userfield.* FROM user LEFT JOIN userfield ON userfield.userid=user.userid WHERE user.userid='1'
    mysql error: Can't open file: 'userfield.MYD'. (errno: 145)


    I tried running the repair.php, but it just gives me a blank page. I ran phpMyAdmin and from the SQL tab, I ran "REPAIR TABLE user;". The results were db.user repair status OK.

    However, the error is still there. Please advise! TIA.
    Last edited by Blairwarlock; Sun 12 Jan '03, 9:38am.
  • Steve Machol
    Former Customer Support Manager
    • Jul 2000
    • 154488

    #2
    It's the userfield table that's corrupted, not user. Run this query in phpMyAdmin:

    REPAIR TABLE userfield;
    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

    • Blairwarlock
      Senior Member
      • Nov 2001
      • 199

      #3
      i knew that

      any idea why running repair.php would generate a BLANK page?

      Comment

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

        #4
        The only reason I can think of is that it was not uploaded in ASCII or it was just taking a very long time to process.

        P.S. Repair.php will not fix the user and userfield tables.
        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

        • inetd
          Senior Member
          • Jan 2001
          • 1179
          • 3.0.0 Release Candidate 2

          #5
          Why this message in vB3 Troubleshooting forum?
          Sorry for my bad English! :)

          Comment

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

            #6
            I tried to move it but there were some parse errors. This should be fixed now so I'll try it again.
            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

            • Blairwarlock
              Senior Member
              • Nov 2001
              • 199

              #7
              All good now...my dumb mistake. Still looking into why repair.php is not working right...I know for a fact it's NOT in ASCII format. So maybe it is taking a long time. Anyway to verify that IS the case other than waiting?

              Comment

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

                #8
                Originally posted by Blairwarlock
                Still looking into why repair.php is not working right...I know for a fact it's NOT in ASCII format.
                Is this a typo? Repair.php needs to be uploaded in ASCII.
                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

                widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
                Working...