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 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
