How does one do that in my.cnf? It is possible to disable a supported engine by screwing up the my.cnf configuration. For example, I once pointed the InnoDB data file to a directory that still had root as its owner. The Innodb engined appeared as DISABLED in the SHOW ENGINES output, but it was supported. I chown'd the directory to the proper owner and it was fine. (This may be why I mistyped InnoDB in my first post - I had InnoDB on my mind.)
In the case of the FEDERATED engine in my database, it's not supported at all. I don't think I can turn support on or off in my.cnf. I would love it, if I could, though. On Thu, Feb 19, 2009 at 10:47 PM, <chaim.rie...@gmail.com> wrote: > Perhaps you disabled it via my.cnf > > > Sent via BlackBerry from T-Mobile > > -----Original Message----- > From: Jim Lyons <jlyons4...@gmail.com> > > Date: Thu, 19 Feb 2009 22:45:01 > To: MySQL<mysql@lists.mysql.com> > Subject: Re: Resend: enabling storage engine with RPM install > > > Yes, I had a slip of the mind. The engine that was not supported by the > install is the Federated engine. I apologize, I had a blind spot. The > "SHOW ENGINES" command lists FEDERATED but has NO in the Support column. > > The question, though, is how does one add an unsupported engine to an RPM > install? Is it possible? Otherwise I have to either compile from source > or > upgrade to a version that I hope will have it. > > On Thu, Feb 19, 2009 at 10:08 PM, Baron Schwartz <ba...@xaprb.com> wrote: > > > Where on earth did you get an RPM that doesn't have InnoDB support? I > > find this unlikely. I think it is more likely that you have some > > configuration error that's causing InnoDB to disable itself on start. > > How do you know InnoDB isn't supported? And by "isn't supported" I > > mean "isn't compiled into mysqld". > > > > Per your commend that InnoDB wasn't installed with mysqld -- it is not > > separate. It's built into the /usr/sbin/mysqld binary (or whatever > > that is on your system). For example, look at this: > > > > strings /usr/sbin/mysqld | grep -i innodb > > > > If you see a bunch of lines starting with "InnoDB: blah blah", you > > have a binary that includes InnoDB, and it's just disabled for some > > reason. > > > > Baron > > > > On Thu, Feb 19, 2009 at 6:58 PM, Jim Lyons <jlyons4...@gmail.com> wrote: > > > Sorry, but I'm resending because I made a mistake in terminology and > want > > to > > > be clear. The problem isn't that innodb is "DISABLED" on the database. > > The > > > innodb engine is not supported by the database. > > > > > > We have 5.0.22 installed on a test machine and for some reason the > innodb > > > storage engine was not installed with it. We install from RPMs so I'm > > not > > > sure how to install the storage engine. If we compiled ourselves, we'd > > > recompile but that's not an option. > > > > > > Does anyone know how to install a storage engine once mysql's been > > installed > > > by an RPM? How does one make the selections in the first place with > > RPMs? > > > We've always just taken what we got and it was sufficient. > > > > > > Thanks, > > > Jim > > > > > > -- > > > Jim Lyons > > > Web developer / Database administrator > > > http://www.weblyons.com > > > > > > > > > > > -- > > Baron Schwartz, Director of Consulting, Percona Inc. > > Our Blog: http://www.mysqlperformanceblog.com/ > > Our Services: http://www.percona.com/services.html > > > > > > -- > Jim Lyons > Web developer / Database administrator > http://www.weblyons.com > > -- Jim Lyons Web developer / Database administrator http://www.weblyons.com
