Database errors FROM vb3_infractionban

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Webber
    Senior Member
    • Aug 2004
    • 143
    • 4.1.x

    Database errors FROM vb3_infractionban

    I am getting this database error after upgrading to 3.6.2 and can't seem to overcome it:

    Database error in vBulletin 3.6.2:
    Invalid SQL:
    SELECT *
    FROM vb3_infractionban
    ORDER BY method, amount ASC;
    MySQL Error : Incorrect information in file: '****/vb3_infractionban.frm'
    Error Number : 1033
    Date : Tuesday, October 10th 2006 @ 05:25:23 PM
    Script : http://**********/admininfraction.php?do=modify
    Referrer : http://*********/admin/index.php?do=nav
    IP Address : ********
    Username : *****
    Classname : vB_Database

    I have uploaded clean copies of the vb 3.6.2; completed repair and optimize through vb AND through phpmyadmin but I can't get this fixed.

    It eventually crashes my mySQL server.

    I am running Windows 2003 Server.

    Any ideas on how to fix this would be greatly appreciated.
  • Steve Machol
    Former Customer Support Manager
    • Jul 2000
    • 154488

    #2
    I'm afraid the only way I know to fix this is to delete that table and recreate it. To do that, run these queries.

    1. DROP TABLE infractionban;

    2. CREATE TABLE infractionban (
    infractionbanid int unsigned NOT NULL auto_increment,
    usergroupid int NOT NULL DEFAULT '0',
    banusergroupid int unsigned NOT NULL DEFAULT '0',
    amount int unsigned NOT NULL DEFAULT '0',
    period char(5) NOT NULL DEFAULT '',
    method enum('points','infractions') NOT NULL default 'infractions',
    PRIMARY KEY (infractionbanid),
    KEY usergroupid (usergroupid)
    );
    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

    • Webber
      Senior Member
      • Aug 2004
      • 143
      • 4.1.x

      #3
      Thanks Steve I will try this. Ok I completed the queries:

      I succesfully dropped the table and created it again with the above queries but I still have the same exact error.

      I did notice that the ext was .frm does that matter with the above queries?

      Any other suggestions on how to fix this db error?

      Thanks in advance.
      Last edited by Webber; Wed 11 Oct '06, 9:41am.

      Comment

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

        #4
        Honestly the only thing I can think of is that your server is messing upo that file. A new table should not have that problem.

        I'll ask the Devs if they have any ideas.
        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

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

          #5
          My fault. I forgot to add your table prefix. Run these queries:

          1. DROP TABLE vb3_infractionban;

          2. CREATE TABLE vb3_infractionban (
          infractionbanid int unsigned NOT NULL auto_increment,
          usergroupid int NOT NULL DEFAULT '0',
          banusergroupid int unsigned NOT NULL DEFAULT '0',
          amount int unsigned NOT NULL DEFAULT '0',
          period char(5) NOT NULL DEFAULT '',
          method enum('points','infractions') NOT NULL default 'infractions',
          PRIMARY KEY (infractionbanid),
          KEY usergroupid (usergroupid)
          );
          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

          • Webber
            Senior Member
            • Aug 2004
            • 143
            • 4.1.x

            #6
            Awesome, thanks Steve --- that worked like a charm.

            Comment

            widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
            Working...
            😀
            😂
            🥰
            😘
            🤢
            😎
            😞
            😡
            👍
            👎