cancel
Showing results for 
Search instead for 
Did you mean: 

Database server does not support InnoDB storage engine

   Did you know you can see the translated content as per your choice?

Translation is in progress. Please check again after few minutes.

Database server does not support InnoDB storage engine

Hi,

 

i know this seems to be a well known bug, but i cant find a solution for Ver 1.9.X . I ran the magento checker, https://www.plusvitalis.de/shop/magento-check.php everything is fine. Hoster says its a problem of the installer script, the variable "have_innodb" doesnt exist anymore in mysql 5.6.1. Do you have a new installer script or a solution how i can fix this? i got the installer from official magento website.  thanks a lot

daniel

 

 

5 REPLIES 5

Re: Database server does not support InnoDB storage engine

Hello,

 

has anyone a solution for that? 

 

Thanks

Daniel

Re: Database server does not support InnoDB storage engine

Re: Database server does not support InnoDB storage engine

@danjesch did you find a solution to your problem or did you use one of the solutions in the  link provided by @Pronto ? Looking farward to hear if this problem was solved and how.

Re: Database server does not support InnoDB storage engine

I'm having the same problem and the solution posted above doesn't work for me. Running out of ideas now.

Re: Database server does not support InnoDB storage engine

Hello, you can fix this error by:
Open Mysql4.php file located in app/code/core/Mage/Install/Model/Installer/Db/Mysql4.php and find:
 
public function supportEngine()
    {
        $variables  = $this->_getConnection()
            ->fetchPairs('SHOW VARIABLES');
        return (!isset($variables['have_innodb']) || $variables['have_innodb'] != 'YES') ? false : true;
    }
Then replace with 
public function supportEngine()
    {
        $variables  = $this->_getConnection()
            ->fetchPairs('SHOW ENGINES');
        return (isset($variables['InnoDB']) && $variables['InnoDB'] != 'NO');
    }
I did this for my Magento website and the error is gone. << Snipped >>