have_innodb=NO

ankur02018 · #1 (**permalink**) 02-17-09, 04:06

hi

My sysadmin have installed MySQL version: 5.1.30

when i check
show variables like '%innodb%';

i got have_innodb =NO

i check for my.cnf there no skip_innodb
when i uncheck any innodb variable
its give
Starting MySQL.Manager of pid-file quit without updating file.[FAILED]

error when i start service

how to enable innodb

healdem · #2 (**permalink**) 02-17-09, 04:40

talk to your sysadmin.
if you need INNODB they should make sure its available.

ankur02018 · #3 (**permalink**) 02-17-09, 07:49

Quote:

Originally Posted by healdem

talk to your sysadmin.
if you need INNODB they should make sure its available.

should there would be any service pack installation for MySQL 5.1.30 version

healdem · #4 (**permalink**) 02-17-09, 11:32

dunno
try searching the mysql site for service packs. I'never isntalled a service pack.. I've updated the servers several times with new versions, but never come accros a service pack.

If I remember correctly INNODB may be an option on the windows installer.... thats why I suggest you go back to your network trolls and get them to resolve the issue

r937 · #5 (**permalink**) 02-17-09, 14:00

as far as i know (and i am ~so~ not a DBA) that setting is only your default for when you don't specify an engine, and you can happily create innodb tables simply by ensuring that you name the engine...

Code:

CREATE TABLE shoutout
( w00t INTEGER 
, foobar VARCHAR(37)
) ENGINE=InnoDB;

guelphdad · #6 (**permalink**) 02-17-09, 15:52

innodb is turned off by default in new installs of mysql and many service providers do not allow them.

ankur02018 · #7 (**permalink**) 02-19-09, 03:30

Quote:

Originally Posted by guelphdad

innodb is turned off by default in new installs of mysql and many service providers do not allow them.

innodb plugin by default is not open in this edition my system admin explicitly
open the plugin innobase now its working

ankur02018 · #8 (**permalink**) 02-20-09, 08:19

After migrating application from MySQL 5.0.51b version to 5.1.30-log

When required to update or insert through application following error occur

Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode

Is there any idea where could be problem

guelphdad · #9 (**permalink**) 02-20-09, 09:29

separate question, belongs in a new thread. again the answer will be to ask your sys admin to allow binary logging.

Internet Services

Web Development

Digital Marketing

Consumer Tech