MySQL Bugs: #34605: ERROR 1030 (HY000): Got error 12 from storage engine

Bug #34605	ERROR 1030 (HY000): Got error 12 from storage engine
Submitted:	15 Feb 2008 17:16	Modified:	11 Sep 2012 19:30
Reporter:	saravanan krishnarajan	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Stored Routines	Severity:	S1 (Critical)
Version:	5.0.22-log	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	from storage engine, got error 12

Description:
Hi,

I have the following memory configurations.

sort_buffer_size=1024M
max_heap_table_size=1024M

my procedure creates a huge memory table and orders it. It worked with small selections. when it tries to select huge size it exited with the following error

DB ERROR: CALL update_bounces_type(24) - Got error 12 from storage engine

and exited from that position.

and when i issue show variables. it showed the following error.

ERROR 1030 (HY000): Got error 12 from storage engine

How to repeat:
following are the options in option files

sort_buffer_size=128M
max_heap_table_size=50M

increased the size using set global as following

sort_buffer_size=1024M
max_heap_table_size=1024M

when I tried to execute the procedure i got the same error.

Many thanks for writing a bug report.

We need some more information to analyze your issue:

- add my.cnf here
- add a test case that we can reproduce your szenario
- Look, if your disk run out of space during execute
- How did you install MySQL?
- Which distribution of Linux do you use? Also important: 32bit or 64bit?

here is my.cnf

[mysqld]
user=mysql
port=3306
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1
tmpdir=/tmp

#logs
log-bin
log-error=/var/log/mysqld.log
log-slow-queries

#adding slave pieces
server-id=1

max_user_connections=300
table_cache=500

#buffers

query_cache_size=128M
query_cache_limit=1M

key_buffer_size=256M
sort_buffer_size=128M
max_heap_table_size=256M
join_buffer_size=2M
read_buffer_size=2M

innodb_buffer_pool_size=2G

but max_heap_table_size shows only 16M

Testcase
--------

I update memory table with huge records, which may grow upto 350M. 

Disk size
---------
I have enough disk space 

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      432G  107G  303G  26% /
/dev/sda1              99M   22M   72M  24% /boot
tmpfs                 4.0G     0  4.0G   0% /dev/shm

RAM size
8GB

Installation
------------

Installed using binary

Distribution of linux
---------------------
Linux hostname 2.6.18-53.el5PAE #1 SMP Mon Nov 12 02:55:09 EST 2007 i686 i686 i386 GNU/Linux

server runs with dual xeon processor

Now I have changed the my.cnf as

[mysqld]
user=mysql
port=3306
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1
tmpdir=/tmp

#logs
log-bin
log-error=/var/log/mysqld.log
log-slow-queries

#adding slave pieces
server-id=1

max_user_connections=300
table_cache=500

#buffers

query_cache_size=128M
query_cache_limit=1M

key_buffer_size=256M
sort_buffer_size=512M
max_heap_table_size=512M
tmp_table_size=512M
join_buffer_size=2M
read_buffer_size=2M

innodb_buffer_pool_size=2G
innodb_additional_mem_pool_size=40M
innodb_log_file_size=256M
innodb_log_buffer_size=8M

skip-name-resolve

Still running the procedure results with the same error. I can post the procedure if you need.

I tested the following insert statement where my script got error.

mysql> insert into Bounce1 SELECT TRIM(CONCAT(recipientname,'@',recipientdomain)) Email FROM bouncelog where bouncetype=24;
ERROR 1030 (HY000): Got error 12 from storage engine

i should update nearly 2998606 records. Which works correctly with mysql 5.0.45 version.

Thank you for the feedback.

You said: "i should update nearly 2998606 records. Which works correctly with mysql 5.0.45 version.", but reported bug in version 5.0.22. Does this mean bug does not exist in newer version?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Please let us know if we can close this issue.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".