Re: Resend: enabling storage engine with RPM install
Hi Jim, all! Jim Lyons wrote: 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. You cannot add an engine later to a MySQL 5.0 binary. This will change with newer versions when plugins can be used for table handlers. On Thu, Feb 19, 2009 at 10:08 PM, Baron Schwartz ba...@xaprb.com wrote: [[...]] On Thu, Feb 19, 2009 at 6:58 PM, Jim Lyons jlyons4...@gmail.com wrote: [[...]] 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 [[...]] Let me repeat: 5.0.22 on a test machine? We built those binaries in May, 2006, so they are nearly three years old by now. Are your tests that thorough? I checked the logs, and I found that for some reason which I really don't know any more the federated engine was not configured in that version. The oldest community builds in which I find it configured are 5.0.41 and 5.0.45, which you can still get from the archive (accessible via the download page). There were some issues with federated which later caused us to disable it by default, so it is configured in recent versions but not enabled in the my.cnf coming with the packages. Some more info can be found in bug report #37069: http://bugs.mysql.com/bug.php?id=37069 Whatever you decide about federated, you definitely should upgrade from 5.0.22 to some current versions - there were several important bugfixes (including security issues) which you are lacking. And in your next posting, please specify exactly which packages you are using - platforms *do* make a difference in some cases. HTH, Jörg -- Joerg Bruehe, MySQL Build Team, joerg.bru...@sun.com Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer Vorsitzender des Aufsichtsrates: Martin Haering Muenchen: HRB161028 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Resend: enabling storage engine with RPM install
Jim, Where did you get your RPM from? Regards John 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 __ This email has been scanned by Netintelligence http://www.netintelligence.com/email -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Resend: enabling storage engine with RPM install
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
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
Re: Resend: enabling storage engine with RPM install
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: MySQLmysql@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
Re: Resend: enabling storage engine with RPM install
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: MySQLmysql@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
Re: Resend: enabling storage engine with RPM install
Can you post you my.cnf please Sent via BlackBerry from T-Mobile -Original Message- From: Jim Lyons jlyons4...@gmail.com Date: Thu, 19 Feb 2009 23:06:33 To: chaim.rie...@gmail.com Cc: MySQLmysql@lists.mysql.com Subject: Re: Resend: enabling storage engine with RPM install 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: MySQLmysql@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
Re: Resend: enabling storage engine with RPM install
What configuration parameter in the config file could have an impact on whether a particular storage engine is supported? The binaries are built before the config is even used. I don't mind posting the file, but I don't see the point. The question is pretty simple, can one add a storage engine to an RPM install? The config file follows. Thanks. [client] socket = /db/data/mysql.sock port= 3306 [mysqld] socket = /db/data/mysql.sock datadir = /db/data tmpdir = /db/tmp port= 3306 user= mysql max_allowed_packet = 1024M lower_case_table_names=0 log-bin=/db/binlog/tlsgriffin01-bin sync_binlog = 1 expire_logs_days = 14 log-error=/db/log/tlsgriffin01-err.log log-slow-queries=/db/log/tlsgriffin01-slow.log long_query_time = 1 log_warnings=2 server-id = 101 skip-slave-start sysdate-is-now log_bin_trust_function_creators=1 skip-external-locking key_buffer_size = 128M query_cache_size = 256M table_cache = 4096 thread_concurrency = 14 thread_cache_size = 0 open_files_limit = 10240 max_connections = 1000 skip-bdb read_buffer_size = 64M read_rnd_buffer_size = 64M sort_buffer_size = 64M tmp_table_size = 512M max_heap_table_size = 250M myisam_sort_buffer_size = 64M myisam_max_sort_file_size = 20G innodb_data_home_dir = /db/innodb innodb_log_group_home_dir = /db/innodb innodb_data_file_path = ibdata1:10M:autoextend:max:4G innodb_log_files_in_group = 2 innodb_log_file_size = 256M innodb_file_per_table innodb_buffer_pool_size = 400M innodb_additional_mem_pool_size = 80M transaction-isolation = READ-COMMITTED [mysqldump] quick max_allowed_packet = 16M [mysql] no-auto-rehash [myisamchk] key_buffer = 64M sort_buffer_size = 16M read_buffer = 16M write_buffer = 16M [mysqlhotcopy] interactive-timeout [manager] socket = /db/log/manager.sock pid-file=/db/log/manager.pid password-file = /db/data/.mysqlmanager.passwd monitoring-interval = 60 port = 1998 bind-address = tlsgriffin01 [mysql.server] use-manager On Thu, Feb 19, 2009 at 11:24 PM, chaim.rie...@gmail.com wrote: Can you post you my.cnf please Sent via BlackBerry from T-Mobile -- *From*: Jim Lyons *Date*: Thu, 19 Feb 2009 23:06:33 -0600 *To*: chaim.rie...@gmail.com *Subject*: Re: Resend: enabling storage engine with RPM install 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: MySQLmysql@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
Re: Resend: enabling storage engine with RPM install
The answer is no Sent via BlackBerry from T-Mobile -Original Message- From: Jim Lyons jlyons4...@gmail.com Date: Thu, 19 Feb 2009 23:50:13 To: chaim.rie...@gmail.com Cc: MySQLmysql@lists.mysql.com Subject: Re: Resend: enabling storage engine with RPM install What configuration parameter in the config file could have an impact on whether a particular storage engine is supported? The binaries are built before the config is even used. I don't mind posting the file, but I don't see the point. The question is pretty simple, can one add a storage engine to an RPM install? The config file follows. Thanks. [client] socket = /db/data/mysql.sock port= 3306 [mysqld] socket = /db/data/mysql.sock datadir = /db/data tmpdir = /db/tmp port= 3306 user= mysql max_allowed_packet = 1024M lower_case_table_names=0 log-bin=/db/binlog/tlsgriffin01-bin sync_binlog = 1 expire_logs_days = 14 log-error=/db/log/tlsgriffin01-err.log log-slow-queries=/db/log/tlsgriffin01-slow.log long_query_time = 1 log_warnings=2 server-id = 101 skip-slave-start sysdate-is-now log_bin_trust_function_creators=1 skip-external-locking key_buffer_size = 128M query_cache_size = 256M table_cache = 4096 thread_concurrency = 14 thread_cache_size = 0 open_files_limit = 10240 max_connections = 1000 skip-bdb read_buffer_size = 64M read_rnd_buffer_size = 64M sort_buffer_size = 64M tmp_table_size = 512M max_heap_table_size = 250M myisam_sort_buffer_size = 64M myisam_max_sort_file_size = 20G innodb_data_home_dir = /db/innodb innodb_log_group_home_dir = /db/innodb innodb_data_file_path = ibdata1:10M:autoextend:max:4G innodb_log_files_in_group = 2 innodb_log_file_size = 256M innodb_file_per_table innodb_buffer_pool_size = 400M innodb_additional_mem_pool_size = 80M transaction-isolation = READ-COMMITTED [mysqldump] quick max_allowed_packet = 16M [mysql] no-auto-rehash [myisamchk] key_buffer = 64M sort_buffer_size = 16M read_buffer = 16M write_buffer = 16M [mysqlhotcopy] interactive-timeout [manager] socket = /db/log/manager.sock pid-file=/db/log/manager.pid password-file = /db/data/.mysqlmanager.passwd monitoring-interval = 60 port = 1998 bind-address = tlsgriffin01 [mysql.server] use-manager On Thu, Feb 19, 2009 at 11:24 PM, chaim.rie...@gmail.com wrote: Can you post you my.cnf please Sent via BlackBerry from T-Mobile -- *From*: Jim Lyons *Date*: Thu, 19 Feb 2009 23:06:33 -0600 *To*: chaim.rie...@gmail.com *Subject*: Re: Resend: enabling storage engine with RPM install 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: MySQLmysql@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
Re: Resend: enabling storage engine with RPM install
Hi JIm, If you are installing mysql on debian operating system you will get all the storage engines which are required. 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 | NO | /dev/null storage engine (anything you write to it disappears) | | EXAMPLE| NO | Example storage engine | | ARCHIVE| YES | Archive storage engine | | CSV| YES | CSV storage engine | | ndbcluster | DISABLED | 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| ++--++ 12 rows in set (0.00 sec) Otherwise you can have source installation on any platform to get the all or requisite storage engine. You can have full control with source installation. On Fri, Feb 20, 2009 at 11:20 AM, Jim Lyons jlyons4...@gmail.com wrote: What configuration parameter in the config file could have an impact on whether a particular storage engine is supported? The binaries are built before the config is even used. I don't mind posting the file, but I don't see the point. The question is pretty simple, can one add a storage engine to an RPM install? The config file follows. Thanks. [client] socket = /db/data/mysql.sock port= 3306 [mysqld] socket = /db/data/mysql.sock datadir = /db/data tmpdir = /db/tmp port= 3306 user= mysql max_allowed_packet = 1024M lower_case_table_names=0 log-bin=/db/binlog/tlsgriffin01-bin sync_binlog = 1 expire_logs_days = 14 log-error=/db/log/tlsgriffin01-err.log log-slow-queries=/db/log/tlsgriffin01-slow.log long_query_time = 1 log_warnings=2 server-id = 101 skip-slave-start sysdate-is-now log_bin_trust_function_creators=1 skip-external-locking key_buffer_size = 128M query_cache_size = 256M table_cache = 4096 thread_concurrency = 14 thread_cache_size = 0 open_files_limit = 10240 max_connections = 1000 skip-bdb read_buffer_size = 64M read_rnd_buffer_size = 64M sort_buffer_size = 64M tmp_table_size = 512M max_heap_table_size = 250M myisam_sort_buffer_size = 64M myisam_max_sort_file_size = 20G innodb_data_home_dir = /db/innodb innodb_log_group_home_dir = /db/innodb innodb_data_file_path = ibdata1:10M:autoextend:max:4G innodb_log_files_in_group = 2 innodb_log_file_size = 256M innodb_file_per_table innodb_buffer_pool_size = 400M innodb_additional_mem_pool_size = 80M transaction-isolation = READ-COMMITTED [mysqldump] quick max_allowed_packet = 16M [mysql] no-auto-rehash [myisamchk] key_buffer = 64M sort_buffer_size = 16M read_buffer = 16M write_buffer = 16M [mysqlhotcopy] interactive-timeout [manager] socket = /db/log/manager.sock pid-file=/db/log/manager.pid password-file = /db/data/.mysqlmanager.passwd monitoring-interval = 60 port = 1998 bind-address = tlsgriffin01 [mysql.server] use-manager On Thu, Feb 19, 2009 at 11:24 PM, chaim.rie...@gmail.com wrote: Can you post you my.cnf please Sent via BlackBerry from T-Mobile -- *From*: Jim Lyons *Date*: Thu, 19 Feb 2009 23:06:33 -0600 *To*: chaim.rie...@gmail.com *Subject*: Re: Resend: enabling storage engine with RPM install 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
