Error 1030 Hy000 Got Error 124 From Storage Engine
Community Podcasts MySQL.com Downloads Documentation Section Menu: MySQL Forums :: Merge Storage Engine :: storage engine error New Topic Advanced Search storage engine error Posted by: Seth Rogers () Date: August 17, 2005 04:05PM I get this error often, but not always, when I issue a query to my merge table: ERROR 1030 (HY000): Got error 124 from storage engine I'm not doing anything special- the underlying tables have a few million records each, and there are only 7 of them. It seems to happen mostly on big queries that would span multiple tables. Has anyone seen this? Thanks. --Seth Navigate:Previous Message•Next Message Options:Reply•Quote Subject Views Written By Posted storage engine error 23908 Seth Rogers 08/17/2005 04:05PM Re: storage engine error 11354 Ingo Strüwing 08/18/2005 03:29AM Re: storage engine error 12183 fabio martinelli 01/19/2006 07:34AM Re: storage engine error 12037 Ingo Strüwing 01/20/2006 03:55AM Re: storage engine error 9040 Kent Davidson 04/18/2006 02:18AM Re: storage engine error 8082 Matthijs Lambooy 03/05/2007 07:26AM Re: storage engine error 7329 Alexandre BLANC 08/29/2007 10:07AM Sorry, you can't reply to this topic. It has been closed. powered by phorum Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party. Contact Sales USA: +1-866-221-0634 Canada: +1-866-221-0634 Germany: +49 89 143 01280 France: +33 1 57 60 83 57 Italy: +39 02 249 59 120 UK: +44 207 553 8447 Japan: 0120-065556 China: 10800-811-0823 India: 0008001005870 More Countries» Contact Us Online» Products MySQL Enterprise Edition MySQL Standard Edition MySQL Classic Edition MySQL Cluster CGE MySQL Embedded (OEM/ISV) Services Training Certification Consulting Support Downloads MySQL Community Server MySQL Cluster MySQL Fabric MySQL Utilities MySQL Workbench About MySQL Contact Us How to Buy Partners Job Opportunities Site Map Documentation MySQL Reference Manuals MySQL Workbench Expert Guides Topic Guides MySQL Cluster Legal Legal Policies Your Privacy Rights Terms of Use Trademark Policy Contributor Agreement © 2015, Oracle Corporation
came across an interesting error. The particulars are below. OS: Windows Server 2008 MySQL Version: 5.1.31 64bit Usage: Supports an application Vendor Support: No After migrating the application connections to the new hardware and fresh MySQL 5.1 server, the next part of the migration was to export the data from old system into a half filled table on the new system. The servers are load balanced so data can go into the least busy server, but this does not affect anything. I should mention at this point, everything was tested and signed off on the development servers and http://forums.mysql.com/read.php?93,40005,40005 we created a particular mysqldump command to do the job. As things goes there was a delay and the client continued with our original mysqldump command. When the DBA executed the command between 40 and 70 percent of the rows were rejected and mysql client stopped the import. This was acceptable to the client because the records were duplicates and not required. The application developer noticed that the application https://sqlfreebies.wordpress.com/2013/02/13/mysql-5-1-error-1030-storage-engine/ admin page was complaining about a database connection error. The application engine was however, using the database and was happily processing new records. The application developer started up a mysql client logged in and issued two commands; SELECT COUNT(*) FROM tablename' +-------------+ | count(*) | +-------------+ | 17070556 | +-------------+ SELECT MAX(datestamp) FROM tablename; ERROR 1030 (HY000): Got error 124 from storage engine That generate a mixture of panic, amusement and confusion. The part of application was working processing records but it was also moaning about database issue and not helpfully providing the same message as the database. The table was increasing in size but issuing a SELECT MAX died while SELECT COUNT worked. That was when I got the call. It turns out that, there was another part of the application that uses the SELECT MAX statement. This along with the "changes" to the migration process, that led me to the mysqldump script as the cause. So I copied the initial datafiles to development servers and moved the 701Mb mysqldump file across. A quick search in the mysql.com libraries and I found two links. One for MySQL 4.1 and the other for MySQL 5.1.12. Out of curiosity I did look at MySQL 4.1 artical and was s
person Affects Status Importance Assigned to Milestone Maria Edit Fix Released High Oleksandr "Sanja" Byelkin Edit Maria https://bugs.launchpad.net/bugs/885162 5.3 You need to log in to change this bug's status. https://qnalist.com/questions/4201445/got-error-124-from-storage-engine Affecting: Maria Filed here by: Philip Stoev When: 2011-11-02 Confirmed: 2011-11-02 Assigned: 2011-11-02 Started work: 2011-11-29 Completed: 2011-11-29 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu error 1030 RTM Package (Find…) Project (Find…) Status Importance Milestone Fix Released High Maria 5.3 Assigned to Me Oleksandr "Sanja" Byelkin (sanja-byelkin) Remote Watch None, the status of the bug is updated manually. None, the status of the bug is updated manually. URL: The information about this bug in Launchpad is automatically pulled daily from error 1030 hy000 the remote bug. Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description When executing the following query: SELECT * FROM t1 WHERE t1.f1 IN ( SELECT 'k' UNION SELECT 'e' ) ; mysqld returned: ERROR 1030 (HY000): Got error 124 from storage engine backtrace: #0 my_error (nr=1030, MyFlags=0) at my_error.c:81 #1 0x083f34ef in handler::print_error (this=0xa7550990, error=124, errflag=0) at handler.cc:2981 #2 0x0833eb0f in report_error (table=0xa754fa18, error=124) at sql_select.cc:15468 #3 0x0833f549 in join_read_key2 (thd=0xaf82a20, tab=0xa7571840, table=0xa754fa18, table_ref=0xa757199c) at sql_select.cc:15731 #4 0x0833f3da in join_read_key (tab=0xa7571840) at sql_select.cc:15692 #5 0x0833e023 in sub_select (join=0xa7576490, join_tab=0xa7571840, end_of_records=false) at sql_select.cc:15129 #6 0x0833d8d0 in do_select (join=0xa7576490, fields=0xa754c028, table=0x0, procedure=0x0) at sql_select.cc:14795 #7 0x08322156 in JOIN::exec (this=0xa7576490) at sql_select.cc:2679 #8 0x08322982 in mysql_select (thd=0xaf82a20, rref_pointer_array=0xa754c414, tables=0xa754bdcc, wild_num=0, fields=..., conds=0x0, og_num=0, order=0x0, group=0x0, having=0x0, proc_param=0x0, select_options=268435456, result=0xa754c628, unit=0xa754bd98, select_lex=0xa754c2d8) at sql_select.cc:2900 #9 0x0846fb8c in st_select_lex_unit::exec (this=0xa754bd98) at sql_union.cc:724 #10 0x0824d00d in subselect_union
myisampack, and rebuild the index by myisamchk*A2 is a noraml table, and the struct of A1 and A2 is exactlly sametalbe A is the merge table of A1 and A2while i use:*mysql> select max(id) from A;** ERROR 1030 (HY000): Got error 124 from storage engine+---------------+-----------------------+------+-----+-------------------+----------------+| Field | Type | Null | Key | Default | Extra |+---------------+-----------------------+------+-----+-------------------+----------------+| id | bigint(20) unsigned | NO | MUL | NULL | auto_increment |*but when i try another table, the situation is as before, such as tableB1,B2,B*mysql> select max(id) from loot;+---------+| max(id) |+---------+| 110415 |+---------+1 row in set (0.00 sec)*the only difference is (*table A the id Field is auto_increment andtable B the id is not*):*+-------+-----------------------+------+-----+---------+-------+| Field | Type | Null | Key | Default | Extra |+-------+-----------------------+------+-----+---------+-------+| id | bigint(20) unsigned | NO | MUL | NULL | |*and if i do not use myisampack/myisamchk, all are work fine,*our system is freebsd 7.2, the mysql version is 5.0.84Server version: 5.0.84 Source distribution*thanks for your replytiredboy** mysql asked Aug 25 2009 at 07:23 in Mysql-General by stutiredboy Facebook Google+ Twitter 2 Answers Which version of mysql are you using? In mysql 4, you could get away with some differences between the definition of the merge table and the underlying tables.As you've discovered, the structure and index definitions must now be exactly the same, otherwise you will get errors.Regards,Gavin Towey answered Aug 25 2009 at 17:53 by Gavin Towey thanks Gavinyes, of course, the structure are exactly the sameour mysql Server version: 5.0.84 Source distributionif i do not pack and re creat the index ,everything work finema