Re: Bizarre table type switch
Hello. Usually you should follow instructions in chapters at: http://dev.mysql.com/doc/mysql/en/Debugging_server.html Stuart Felenstein [EMAIL PROTECTED] wrote: I'm not sure what happened but when I ran some test yesterday on a transaction it failed. Being puzzled I started digging around. I have come to find out that all the tables involved were now set to MyISAM. Obviously transactions wouldn't work. The odd thing that I'd like to figure out is how did they get switched. I know this is a vague and gray question , and if there is a way to trace it I'd like to know. Is there anything that would cause this type of occurance ? Anything I can do to find out why it happened? Stuart -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Bizarre table type switch
Stuart, you probably have skip-innodb in my.cnf. Best regards, Heikki Tuuri Innobase Oy Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php - Original Message - From: Stuart Felenstein [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Monday, November 29, 2004 9:58 AM Subject: Re: Bizarre table type switch --- Stuart Felenstein [EMAIL PROTECTED] wrote: I'm not sure what happened but when I ran some test yesterday on a transaction it failed. Being puzzled I started digging around. I have come to find out that all the tables involved were now set to MyISAM. Obviously transactions wouldn't work. The odd thing that I'd like to figure out is how did they get switched. I know this is a vague and gray question , and if there is a way to trace it I'd like to know. Is there anything that would cause this type of occurance ? Anything I can do to find out why it happened? I forgot to mention this is 4.0.22-standard. I have requested my ISP check my.cnf to see if Innodb has been skipped for support. I am able to switch them back though. Stuart -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Bizarre table type switch
--- Heikki Tuuri [EMAIL PROTECTED] wrote: Stuart, you probably have skip-innodb in my.cnf. Best regards, Heikki Tuuri Heikki - Nope , doesn't seem so. My.cnf is below. Also, I'm guessing that if it was set to skip-innodb, I wouldn't not have had the ability to change them back. It's very puzzling. I'm not expecting to find an answer. The logs were checked and nothing found to inidicate anything. I'm on shared host. Supposedly my ISP did this for me. They are pretty reliable. But we are talking about 20+ tables. [mysqld] safe-show-database max_connections = 750 key_buffer = 136M myisam_sort_buffer_size = 72M join_buffer_size = 1M read_buffer_size = 1M sort_buffer_size = 2M table_cache = 1024 thread_cache_size = 128 wait_timeout = 5500 connect_timeout = 10 max_allowed_packet = 32M max_connect_errors = 10 query_cache_limit = 2M query_cache_size = 72M query_cache_type = 1 tmp_table_size = 72M read_rnd_buffer_size = 524288 bulk_insert_buffer_size = 72M [mysqld_safe] open_files_limit = 8192 [mysqldump] quick max_allowed_packet = 32M [myisamchk] key_buffer = 72M sort_buffer = 72M read_buffer = 24M write_buffer = 24M Stuart -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Bizarre table type switch
Stuart, ok, then this is a complete mystery. I have not heard about this before. Regards, Heikki - Original Message - From: Stuart Felenstein [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Monday, November 29, 2004 9:33 PM Subject: Re: Bizarre table type switch --- Heikki Tuuri [EMAIL PROTECTED] wrote: Stuart, you probably have skip-innodb in my.cnf. Best regards, Heikki Tuuri Heikki - Nope , doesn't seem so. My.cnf is below. Also, I'm guessing that if it was set to skip-innodb, I wouldn't not have had the ability to change them back. It's very puzzling. I'm not expecting to find an answer. The logs were checked and nothing found to inidicate anything. I'm on shared host. Supposedly my ISP did this for me. They are pretty reliable. But we are talking about 20+ tables. [mysqld] safe-show-database max_connections = 750 key_buffer = 136M myisam_sort_buffer_size = 72M join_buffer_size = 1M read_buffer_size = 1M sort_buffer_size = 2M table_cache = 1024 thread_cache_size = 128 wait_timeout = 5500 connect_timeout = 10 max_allowed_packet = 32M max_connect_errors = 10 query_cache_limit = 2M query_cache_size = 72M query_cache_type = 1 tmp_table_size = 72M read_rnd_buffer_size = 524288 bulk_insert_buffer_size = 72M [mysqld_safe] open_files_limit = 8192 [mysqldump] quick max_allowed_packet = 32M [myisamchk] key_buffer = 72M sort_buffer = 72M read_buffer = 24M write_buffer = 24M Stuart -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Bizarre table type switch
I'm not sure what happened but when I ran some test yesterday on a transaction it failed. Being puzzled I started digging around. I have come to find out that all the tables involved were now set to MyISAM. Obviously transactions wouldn't work. The odd thing that I'd like to figure out is how did they get switched. I know this is a vague and gray question , and if there is a way to trace it I'd like to know. Is there anything that would cause this type of occurance ? Anything I can do to find out why it happened? Stuart -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Bizarre table type switch
--- Stuart Felenstein [EMAIL PROTECTED] wrote: I'm not sure what happened but when I ran some test yesterday on a transaction it failed. Being puzzled I started digging around. I have come to find out that all the tables involved were now set to MyISAM. Obviously transactions wouldn't work. The odd thing that I'd like to figure out is how did they get switched. I know this is a vague and gray question , and if there is a way to trace it I'd like to know. Is there anything that would cause this type of occurance ? Anything I can do to find out why it happened? I forgot to mention this is 4.0.22-standard. I have requested my ISP check my.cnf to see if Innodb has been skipped for support. I am able to switch them back though. Stuart -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
