innoDB not enabled by default?

[cpanelkenneth]

i am facing the same problem, how i will enable the InnDB from Phpmyadmin , i have checked the my.cnd file but it does not exist. then i checked the my.cnf file but it does not allow me to open it , it shows permission denied.

kindly show me the way how it will check that InnDB support is enabled on server or not.

You need root access to the server to modify /etc/my.cnf. If you lack root access then you will need to open a support ticket with your web host provider.

[egillette]

i am facing the same problem, how i will enable the InnDB from Phpmyadmin , i have checked the my.cnd file but it does not exist. then i checked the my.cnf file but it does not allow me to open it , it shows permission denied.

kindly show me the way how it will check that InnDB support is enabled on server or not.

** Are you accessing your my.cnf file as root on your system or are you at least using sudo??

(i.e. sudo vi /etc/my.cnf or sudo nano/pico /etc/my.cnf)

If not, that would explain the permission denied issue (you have to be root or su to root).

Let me know. . .

[hostmedic]

There are two ways to verify if innodb is supported - i will skip how to check via phpmyadmin...

If you are in the command line already simply execute the following

mysql -u root -p

place in your root password

Now Type in

show engines;

It should show something like this

mysql> show engines;
+------------+---------+----------------------------------------------------------------+
| Engine | Support | Comment |
+------------+---------+----------------------------------------------------------------+
| MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance |
| MEMORY | YES | Hash based, stored in memory, useful for temporary tables |
| InnoDB | YES | Supports transactions, row-level locking, and foreign keys |
| BerkeleyDB | NO | Supports transactions and page-level locking |
| BLACKHOLE | YES | /dev/null storage engine (anything you write to it disappears) |
| EXAMPLE | YES | Example storage engine |
| ARCHIVE | YES | Archive storage engine |
| CSV | YES | CSV storage engine |
| ndbcluster | NO | Clustered, fault-tolerant, memory-based tables |
| FEDERATED | YES | Federated MySQL storage engine |
| MRG_MYISAM | YES | Collection of identical MyISAM tables |
| ISAM | NO | Obsolete storage engine |
+------------+---------+----------------------------------------------------------------+

Notice under InnoDB - it shows YES in my example.

This example shows it is off

mysql> show engines;
+------------+----------+----------------------------------------------------------------+
| Engine | Support | Comment |
+------------+----------+----------------------------------------------------------------+
| MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance |
| MEMORY | YES | Hash based, stored in memory, useful for temporary tables |
| InnoDB | DISABLED | Supports transactions, row-level locking, and foreign keys |
| BerkeleyDB | NO | Supports transactions and page-level locking |
| BLACKHOLE | YES | /dev/null storage engine (anything you write to it disappears) |
| EXAMPLE | YES | Example storage engine |
| ARCHIVE | YES | Archive storage engine |
| CSV | YES | CSV storage engine |
| ndbcluster | NO | Clustered, fault-tolerant, memory-based tables |
| FEDERATED | YES | Federated MySQL storage engine |
| MRG_MYISAM | YES | Collection of identical MyISAM tables |
| ISAM | NO | Obsolete storage engine |
+------------+----------+----------------------------------------------------------------+

I hope that helps.

[hostmedic]

If your innodb is still not working - but you have it enabled - this could also be due to a log file issue.

FIRST STOP MYSQL BEFORE DOING THESE STEPS:

service mysql stop

now go to the mysql directory

cd /var/lib/mysql

MOVE THE ibdata1, ib_logfile0 and ib_logfile1 files to a .bak like this

mv ibdata1 ibdata1.bak
mv ib_logfile0 ib_logfile0.bak 
ib_logfile1 ib_logfile1.bak

Now restart Mysql and be patient.

service mysql restart

Now check for Innodb support as shown before:

mysql -u root -p

enter password

Now at the prompt mysql> type

show engines;

Two important disk-based resources managed by the InnoDB storage engine are its tablespace data files and its log files. If you specify no InnoDB configuration options (as is the case with most MySQL installs and the default on cPanel), MySQL creates an auto-extending 10MB data file named ibdata1 and two 5MB log files named ib_logfile0 and ib_logfile1 in the MySQL data directory

Innodb can Fail hard if those files have become corrupt.

Best wishes in your trouble shooting.

[cPanelTristan]

Actually, it's a lot easier than logging into MySQL command line:

mysqladmin var | grep have_innodb

This would return:

root@host [/home/cpfoo4]# mysqladmin var | grep have_innodb
| have_innodb                             | YES        |

If it is disabled, it would return:

root@host [/home/cpfoo4]# mysqladmin var | grep have_innodb
| have_innodb                             | DISABLED |

[hostmedic]

Awesome -and yup 100000% correct.
Forgot all about that -


A

Actually, it's a lot easier than logging into MySQL command line:

mysqladmin var | grep have_innodb

This would return:

root@host [/home/cpfoo4]# mysqladmin var | grep have_innodb
| have_innodb                             | YES        |

If it is disabled, it would return:

root@host [/home/cpfoo4]# mysqladmin var | grep have_innodb
| have_innodb                             | DISABLED |