The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

crashed innodb tables

Discussion in 'Database Discussions' started by persianwhois, Jun 10, 2015.

  1. persianwhois

    persianwhois Well-Known Member

    Joined:
    Apr 18, 2007
    Messages:
    117
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Mahallat
    cPanel Access Level:
    Root Administrator
    Our mysql server crashed and for resolve problem we have removed "ibdata1" from /var/lib/mysql and restart mysql service.
    Now its start, but some website have problem to read database details.
    We have checked mysql log and we see many error like this:

    2015-06-10 21:31:31 14939 [Warning] InnoDB: Cannot open table humble_tipsdb/qat_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/...eshooting.html

    How we should resolve this problem?
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
  3. cPanelRyanR

    cPanelRyanR Member
    Staff Member

    Joined:
    Jul 17, 2014
    Messages:
    9
    Likes Received:
    9
    Trophy Points:
    3
    cPanel Access Level:
    Root Administrator
    Just to add to what Michael stated, I wanted to reiterate that removing ibdata1 is essentially the same as removing all of the data stored on InnoDB tables. You will not be able to access any of it, which is why I always recommend troubleshooting the InnoDB crash/corruption scenario in preference to re-generating a new ibdata1 file, unless you've got backups, in which case restoring from backups is always best.

    This seems to be a common misstep. One of the aspects that confuses people is that, after removing the ibdata1 file, they see that MySQL is again able to start. That's because it's not loading any of your InnoDB data. So if the crash was occurring due to an issue in one of the InnoDB tables, of course a clean slate ibdata1 file allow MySQL to start. It will not, however, load any of your existing InnoDB tables in that state. The InnoDB table files, unlike MyISAM table files, are not portable. They rely on the existence of metadata in the "data dictionary" (stored in the ibdata1 file) to correspond with them, in order to properly load them and verify their integrity.

    With that in mind, if you still have a copy of the original ibdata1 file, I would advise restoring that back into its place in /var/lib/mysql (or wherever you have your MySQL data directory configured), and troubleshooting the original crash issue from that point.
     
  4. James Bowlin

    James Bowlin Registered

    Joined:
    Jun 18, 2015
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Kansas
    cPanel Access Level:
    Root Administrator
    Wait so your software update of WHM/CPanel screws up MySQL and corrupts my databases and it's outside of the scope of your organization to provide support for that? Ok guess I will just cancel my WHM/CPanel licenses and contact a Web Host Panel Provider that is willing to support their products.
     
  5. dalem

    dalem Well-Known Member
    PartnerNOC

    Joined:
    Oct 24, 2003
    Messages:
    2,577
    Likes Received:
    40
    Trophy Points:
    48
    Location:
    SLC
    cPanel Access Level:
    DataCenter Provider
  6. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    I sent a response to the following quote:

    The cPanel update process should not cause InnoDB corruption. Did this happen on one of your servers?

    Thank you.
     
Loading...

Share This Page