Re: Error 1114 table full with 14000 error??
Hi!
You have hit the problem of easy installation of MySQL-4.0 :)
From the manual at http://www.innodb.com/ibman.html :
.
2 InnoDB startup options
To use InnoDB tables in MySQL-Max-3.23 you MUST specify configuration
parameters in the [mysqld] section of the configuration file my.cnf, or on
Windows optionally in my.ini.
At the minimum in 3.23 you must specify innodb_data_file_path. In MySQL-4.0
you do not need to specify even innodb_data_file_path: the default for it is
to create a 64 MB file ibdata1 to the datadir of MySQL.
But to get good performance you MUST explicitly set the InnoDB parameters
listed below in the examples.
MySQL-4.0 automatically creates a 64 MB data file ibdata1 if you do not
specify any InnoDB startup options. When that file gets full, you will get
the 'table is full error'.
Please look in the manual and specify the InnoDB options in my.cnf as
recommended.
Best regards,
Heikki Tuuri
Innobase Oy
---
Order technical MySQL/InnoDB support at https://order.mysql.com/
See http://www.innodb.com for the online manual and latest news on InnoDB
[EMAIL PROTECTED] wrote in message ...
I am running Mysql 4.0 with InnoDB on a linux 2.4.0
machine
I am doing a mass import of a file with some 40
inserts
and I get a strange unknown error 1114
Interestingly enough , this is not exactly
reproducible, i.e.
the error occurs in slightly different import
positions.
I have been able thus far to successfully import at
least 10 such files
with the same size with no problems.
Any ideas of what is wrong??
Thanks, S.Alexiou
sp@qu5:~/NEW4 perror 1114
Error code 1114: Unknown error 1114
sp@qu5:~/NEW4 su
Password:
root@qu5:/home/sp/NEW4 ulimit -n 8192
root@quy5:/home/sp/NEW4 ulimit -a limit
core file size (blocks) 0
data seg size (kbytes) unlimited
file size (blocks) unlimited
max locked memory (kbytes) unlimited
max memory size (kbytes)unlimited
open files 8192
pipe size (512 bytes) 8
stack size (kbytes) unlimited
cpu time (seconds) unlimited
max user processes 32767
virtual memory (kbytes) unlimited
root@qu5:/home/sp/NEW4 cat /proc/sys/fs/file-nr
140273 8192
root@qu5:/home/sp/NEW4
root@qu5:/home/sp/NEW4 mysql -u sp -p DB1
newbackfrom20011009_ermsc1.sql
Enter password:
ERROR 1114 at line 111235: The table 'DR_OUTGOING_49_1'
is full
root@qu5:/home/sp/NEW4 vi
newbackfrom20011009_ermsc1.sql
root@qu5:/home/sp/NEW4 mysql -u sp -p DB1
newbackfrom20011009_ermsc1.sql
Enter password:
ERROR 1114 at line 119737: The table 'DR_TRANSIT_78_0'
is full
root@quality5:/home/sp/NEW4
How big is that table?
from kmysqladmin I get:
SELECT * FROM CDR_TRANSIT_78_0 ORDER BY anum LIMIT 9
46942 row(s) found
The table newbackfrom20011009_ermsc1.sql looks
like this:
--
set autocommit=0;
INSERT INTO DATES (donedate) VALUES('2001-10-09') ;
INSERT INTO DR_TR_389_0
UES(
'','389222963',4129,5857,2,'2001-10-
08','22:59:35',0,0,0,0.205625057220459,0,28,4,'AAA1',1,0
,3,'','','',10,0,'1','1',2,'','','20011009_ermsc1',1
,0,'','','','','-128-144-163-49-2-0-90-58-6-68-3-87-0-
0-',3,'','' );
commit;
---
Similarly, I get the same type of error when doing a
report vi a gui-driven
perl script on a differnt table:
Tk::Error: DBD::mysql::st execute failed: The table
'TMP2' is full at report79.pl line 404.
[\\main::__ANON__]
SELECT * FROM TMP2 ORDER BY date LIMIT 9
16019 row(s) found
---
sp@qu5:~/QUER df -h
FilesystemSize Used Avail Use% Mounted on
/dev/sda6 9.7G 4.8G 4.9G 49% /
/dev/sda7 4.6G 3.0G 1.6G 66% /var
/dev/sda1 23M 4.8M 16M 22% /boot
/dev/sda8 20G 14G 5.6G 72%
/home
/dev/fd0 1.4M 821k 603k 58% /floppy
Here i s/etc/my.cnf
# Example mysql config file for very large systems.
#
# This is for large system with memory of 1G-2G where
the system runs mainly
# MySQL.
#
# You can copy this file to
# /etc/mf.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
(in this
# installation this directory is /var/lib/mysql) or
# ~/.my.cnf to set user-specific options.
#
# One can in this file use all long options that the
program supports.
# If you want to know which options a program support,
run the program
# with --help option.
# The following options will be passed to all MySQL
clients
[client]
#password = your_password
port = 3306
socket = /var/lib/mysql/mysql.sock
# Here follows entries for some specific programs
# The MySQL server
[mysqld]
port = 3306
socket = /var/lib/mysql/mysql.sock
skip-locking
set-variable = key_buffer=384M
set-variable = max_allowed_packet=1M
set-variable = table_cache=512
set-variable = sort_buffer=2M
set-variable = record_buffer=2M
set-variable = thread_cache=8
set-variable = thread_concurrency=2 # Try number of
CPU's*2
Error 1114 table full with 14000 error??
I am running Mysql 4.0 with InnoDB on a linux 2.4.0
machine
I am doing a mass import of a file with some 40
inserts
and I get a strange unknown error 1114
Interestingly enough , this is not exactly
reproducible, i.e.
the error occurs in slightly different import
positions.
I have been able thus far to successfully import at
least 10 such files
with the same size with no problems.
Any ideas of what is wrong??
Thanks, S.Alexiou
sp@qu5:~/NEW4 perror 1114
Error code 1114: Unknown error 1114
sp@qu5:~/NEW4 su
Password:
root@qu5:/home/sp/NEW4 ulimit -n 8192
root@quy5:/home/sp/NEW4 ulimit -a limit
core file size (blocks) 0
data seg size (kbytes) unlimited
file size (blocks) unlimited
max locked memory (kbytes) unlimited
max memory size (kbytes)unlimited
open files 8192
pipe size (512 bytes) 8
stack size (kbytes) unlimited
cpu time (seconds) unlimited
max user processes 32767
virtual memory (kbytes) unlimited
root@qu5:/home/sp/NEW4 cat /proc/sys/fs/file-nr
140273 8192
root@qu5:/home/sp/NEW4
root@qu5:/home/sp/NEW4 mysql -u sp -p DB1
newbackfrom20011009_ermsc1.sql
Enter password:
ERROR 1114 at line 111235: The table 'DR_OUTGOING_49_1'
is full
root@qu5:/home/sp/NEW4 vi
newbackfrom20011009_ermsc1.sql
root@qu5:/home/sp/NEW4 mysql -u sp -p DB1
newbackfrom20011009_ermsc1.sql
Enter password:
ERROR 1114 at line 119737: The table 'DR_TRANSIT_78_0'
is full
root@quality5:/home/sp/NEW4
How big is that table?
from kmysqladmin I get:
SELECT * FROM CDR_TRANSIT_78_0 ORDER BY anum LIMIT 9
46942 row(s) found
The table newbackfrom20011009_ermsc1.sql looks
like this:
--
set autocommit=0;
INSERT INTO DATES (donedate) VALUES('2001-10-09') ;
INSERT INTO DR_TR_389_0 VALUES(
'','389222963',4129,5857,2,'2001-10-
08','22:59:35',0,0,0,0.205625057220459,0,28,4,'AAA1',1,0
,3,'','','',10,0,'1','1',2,'','','20011009_ermsc1',1
,0,'','','','','-128-144-163-49-2-0-90-58-6-68-3-87-0-
0-',3,'','' );
commit;
---
Similarly, I get the same type of error when doing a
report vi a gui-driven
perl script on a differnt table:
Tk::Error: DBD::mysql::st execute failed: The table
'TMP2' is full at report79.pl line 404.
[\\main::__ANON__]
SELECT * FROM TMP2 ORDER BY date LIMIT 9
16019 row(s) found
---
sp@qu5:~/QUER df -h
FilesystemSize Used Avail Use% Mounted on
/dev/sda6 9.7G 4.8G 4.9G 49% /
/dev/sda7 4.6G 3.0G 1.6G 66% /var
/dev/sda1 23M 4.8M 16M 22% /boot
/dev/sda8 20G 14G 5.6G 72% /home
/dev/fd0 1.4M 821k 603k 58% /floppy
Here i s/etc/my.cnf
# Example mysql config file for very large systems.
#
# This is for large system with memory of 1G-2G where
the system runs mainly
# MySQL.
#
# You can copy this file to
# /etc/mf.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
(in this
# installation this directory is /var/lib/mysql) or
# ~/.my.cnf to set user-specific options.
#
# One can in this file use all long options that the
program supports.
# If you want to know which options a program support,
run the program
# with --help option.
# The following options will be passed to all MySQL
clients
[client]
#password = your_password
port= 3306
socket = /var/lib/mysql/mysql.sock
# Here follows entries for some specific programs
# The MySQL server
[mysqld]
port= 3306
socket = /var/lib/mysql/mysql.sock
skip-locking
set-variable= key_buffer=384M
set-variable= max_allowed_packet=1M
set-variable= table_cache=512
set-variable= sort_buffer=2M
set-variable= record_buffer=2M
set-variable= thread_cache=8
set-variable= thread_concurrency=2 # Try number of
CPU's*2
set-variable= myisam_sort_buffer_size=64M
innodb_data_file_path=ibdata1:2000M;
log-bin
server-id = 1
#set-variable= open-files-limit=8192 #ulimit is
1024,hard 8192
# Uncomment the following if you are using BDB tables
#set-variable = bdb_cache_size=384M
#set-variable = bdb_max_lock=10
# Point the following paths to different dedicated disks
#tmpdir = /tmp/
#log-update = /path-to-dedicated-directory/hostname
[mysqldump]
quick
set-variable= max_allowed_packet=256M
[mysql]
no-auto-rehash
#safe-updates # Remove the comment character if you
are not familiar with SQL
[isamchk]
set-variable= key_buffer=256M
set-variable= sort_buffer=256M
set-variable= read_buffer=2M
set-variable= write_buffer=2M
[myisamchk]
set-variable= key_buffer=256M
set-variable= sort_buffer=256M
set-variable= read_buffer=2M
set-variable= write_buffer=2M
[mysqlhotcopy]
interactive-timeout
-
