I switched the tmp directory to a much bigger partition and I am still getting
the error. Any other ideas?
TIA,
Zak
--- On Wed, 3/10/10, Walter Heck wrote:
> From: Walter Heck
> Subject: Re: Corrupted table
> To: "Zakai Kinan"
> Cc: mysql@lists.mysql.com
> Date:
That message usually means you ran out of space in your temp folder location.
cheers,
Walter Heck
--
Engineer @ Open Query
http://openquery.com | http://openquery.com/blog
On Thu, Mar 11, 2010 at 02:16, Zakai Kinan wrote:
> Is there a way to know exactly which table is corrupted with such an e
Is there a way to know exactly which table is corrupted with such an error:
[ERROR] /usr/local/mysql/bin/mysqld: Incorrect key file for table
'/tmp/#sql_7885_0.MYI'; try to repair it.
TIA,
ZK
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscri
Philip,
Tuesday, October 01, 2002, 5:49:47 PM, you wrote:
PD> I have a table which was accessible for the last couple years but is now
PD> inaccessible after performing a simple alter table command.
PD> There are approx. 10 tables in this database on which the same alter table
PD> command was
All,
I have a table which was accessible for the last couple years but is now
inaccessible after performing a simple alter table command.
There are approx. 10 tables in this database on which the same alter table
command was given ("alter table table_name add glperiod varchar (3) null
first;"
Hi. I am running MySQL 3.22.30, and am having trouble repairing a corrupted
table with isamchk. Everything that I've tried either doesn't work, or wipes
out all the data. Here's what I've tried so far:
***
isamchk -d guestbook
ISAM file: guestbook
Data records:
rough reading a file and stopped dead. It
tried it again, same thing. And it always seems to stop at the same point in
the file.
I can open that file up with no problem in Word.
Could this be caused by a corrupted table? I've had no other problems with
the database. It's a rather large
Jim Ray, @WD writes:
>
> I have a tabel that seems to be corrupted. Is there a way to fix it? It is
> running on a Lynx box.
Atari Lynx? Does MySQL really run on that? Or did you mean Linux? Hmm...
Anyway, look in the manual. REPAIR TABLE is good place to start, as
is myisamchk. And make sure
I wonder if anyone can assist me with this one.
I appear to be getting sporadic corruption of a table that is then
unrecoverable.
The error I get is as follows:
Incorrect information in file: 'user_admin_table.frm'
This is a longshot but
Has anyone seen this error before?
-
active char(1) default 'N',
>size tinyint not null default 0,
>availability mediumint not null,
>
>primary key (product_id)
>) type=innodb;
>create index i_products_active on products (active);
>create index i_products_size on products (size);
>
>I
any faults.
Note that I don't use mysql in production environment;
I'm web-developer and use mysql for development.
I recovered from this by creating second table without image field and
selecting all the data from first table into it, and then dropping
corrupted table and so on.
Sorry t
11 matches
Mail list logo