Re: Corrupted table

2010-03-20 Thread Zakai Kinan
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 wal...@openquery.com wrote:

 From: Walter Heck wal...@openquery.com
 Subject: Re: Corrupted table
 To: Zakai Kinan titanyen2...@yahoo.com
 Cc: mysql@lists.mysql.com
 Date: Wednesday, March 10, 2010, 8:29 AM
 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 titanyen2...@yahoo.com
 wrote:
  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 unsubscribe:    http://lists.mysql.com/mysql?unsub=li...@olindata.com
 
 
 
 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:    http://lists.mysql.com/mysql?unsub=titanyen2...@yahoo.com
 
 




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org



Corrupted table

2010-03-10 Thread Zakai Kinan
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 unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org



Re: Corrupted table

2010-03-10 Thread Walter Heck
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 titanyen2...@yahoo.com wrote:
 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 unsubscribe:    http://lists.mysql.com/mysql?unsub=li...@olindata.com



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org



re: Corrupted Table (?)

2002-10-02 Thread Egor Egorov

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 given (alter table table_name add glperiod varchar (3) null 
PD first;). All of these tables are O.K. (and were correctly altered) except 1.

PD What happens is that whenever I try to perform an SQL command against this 
PD table (called codeprojects), either MySQL hangs (at the command prompt) 
PD or my perl script hangs in the $sth-execute($sql) statement. Like I 
PD said, all of these methods, etc. worked on this table in the past and still 
PD work on the rest of the tables.

PD I've tried, restarting MySQL (which seemed to work at first but now does 
PD not), dropping and rebuilding the table (it hangs on the drop command), 
PD copying a working copy of the three table files from a backup database, 
PD deleting the three files and starting over again. Nothing has worked so far.

PD Any ideas??

PD OS: Redhat 7.1 Linux
PD MySQL: 3.23.41

Use CHECK table to see if the table is corrupted. If so you should repair it with
REPAIR TABLE or myisamchk:
   http://www.mysql.com/doc/en/Repair.html



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Egor Egorov
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.net
   ___/   www.mysql.com




-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Corrupted Table (?)

2002-10-01 Thread Philip Daggett

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;). All of these tables are O.K. (and were correctly altered) except 1.

What happens is that whenever I try to perform an SQL command against this 
table (called codeprojects), either MySQL hangs (at the command prompt) 
or my perl script hangs in the $sth-execute($sql) statement. Like I 
said, all of these methods, etc. worked on this table in the past and still 
work on the rest of the tables.

I've tried, restarting MySQL (which seemed to work at first but now does 
not), dropping and rebuilding the table (it hangs on the drop command), 
copying a working copy of the three table files from a backup database, 
deleting the three files and starting over again. Nothing has worked so far.

Any ideas??

OS: Redhat 7.1 Linux
MySQL: 3.23.41

Thanks,

Phil

P.S.
My team members are big fans of MySQL and are using it exclusively for our 
web systems. Keep up the GREAT work!!


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Fixing corrupted table

2002-02-27 Thread E.Boyd

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: 79764  Deleted blocks:  0
Recordlength:   376
Record format: Packed
Using only 3 keys of 0 possibly keys

table description:
Key Start Len Index   Type

***

isamchk -e guestbook
Checking ISAM file: guestbook
Data records:   79764   Deleted blocks:   0
- check file-size
- check delete-chain
- check index reference
- check records and index references
isamchk: error: Found too long record at 0
ISAM-table 'guestbook' is corrupted
Fix it using switch -r or -o

***

isamchk -o guestbook
isamchk: error: Can't lock indexfile of 'guestbook', error: 11

***

isamchk -r guestbook
- recovering ISAM-table 'guestbook.ISM'
Data records: 79764
Wrong bytesec:   1- 67-  0 at  0; Skipped
Data records: 0

***

Any suggestions on how I can fix this? I would really appreciate it!

Emily


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Corrupted table?

2002-01-25 Thread Mikusch, Rita

I'm having a weird problem with my mysql data dump and wondering if anybody
else has had a similar problem.

I run my mysql dump program, no problem there, download the file, and view
it with a text editor (an oldie: pfe - programmers file editor). Then one
dark day pfe was about half way through 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 website content database however and I'm
wondering if I just haven't run into any other problems yet.

I'm also having this same problem with another content database -- a very
small one however, and I've found no other problems with it. 

Viewing database dumps in Word is rather painful :)  I'd also like to head
off any future problems and repair them now if necessary.

Thanks, Rita.

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Re: corrUPted tabLE questions...

2001-11-23 Thread Carl Troein


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 that you don't repeat whatever you did to
get the table corrupted. killall -9 mysqld is a BAD idea, as is
messing with the table files when mysqld is running.

//C

-- 
 Carl Troein - Círdan / Istari-PixelMagic - UIN 16353280
 [EMAIL PROTECTED] | http://pixelmagic.dyndns.org/~cirdan/
 Amiga user since '89, and damned proud of it too.


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Re:crashes when executing query on innodb table; probably corrupted table

2001-09-25 Thread Heikki Tuuri
 in corrupted image field.
This is the table definition:

create table products (
product_id varchar(16) not null,
name varchar(64),
description text,
price float,
image mediumblob,
weight float,
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 stored images in the image field, approx. 150-160 kb each.
There were around 10-15 records in the table.

When I subsequentally tried to perform
select product_id from products;
select product_id,name from products;
... etc. up to select product_id,..,price from products
it was ok. When I tried to select image from products, mysqld was crashing
and restarting. All the times it put to log different messages. The
difference
was in the query, equation with memory sizes and sometimes it
shows line number with assertion (sometimes not - see above).

Before it was working ok around 2 or 3 weeks without 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 that this is probably little informative bug report, however
I do not have much time to recompile mysqld with --debug option and
produce a trace. Also, I had stripped mysqld with strip, so symbolic
information is absent :-(((

How-To-Repeat:
Unknown.
Fix:
Unknown.

Submitter-Id: Max Rudensky [EMAIL PROTECTED]
Originator: root
Organization:
MySQL support: none
Synopsis: crashes when executing query on innodb table; probably corrupted
table
Severity: critical
Priority: medium
Category: mysql
Class: support
Release: mysql-3.23.41 (Source distribution)

Environment:

System: Linux petrusha.localdomain 2.2.19 #1 Thu May 17 11:49:34 EEST 2001
i686 unknown
Architecture: i686

Some paths:  /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc
/usr/bin/cc
GCC: Reading specs from
/usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
Compilation info: CC='gcc'  CFLAGS='-march=pentiumpro -O3'  CXX='gcc'
CXXFLAGS=''  LDFLAGS=''
LIBC:
lrwxrwxrwx1 root root   13 íÁÊ 13  2000 /lib/libc.so.6 -
libc-2.1.3.so
-rwxr-xr-x1 root root  4101324 æÅ× 29  2000 /lib/libc-2.1.3.so
-rw-r--r--1 root root 20272704 æÅ× 29  2000 /usr/lib/libc.a
-rw-r--r--1 root root  178 æÅ× 29  2000 /usr/lib/libc.so
Configure command:
./configure  --with-innodb --with-berkeley-db --with-charset=koi8_ru --with-
mysqld-user=dba
Perl: This is perl, version 5.005_03 built for i386-linux

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail
[EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




crashes when executing query on innodb table; probably corrupted table

2001-09-24 Thread postgres
  on products (active);
create index i_products_sizeon products (size);

I stored images in the image field, approx. 150-160 kb each.
There were around 10-15 records in the table.

When I subsequentally tried to perform 
select product_id from products;
select product_id,name from products;
... etc. up to select product_id,..,price from products
it was ok. When I tried to select image from products, mysqld was crashing 
and restarting. All the times it put to log different messages. The difference 
was in the query, equation with memory sizes and sometimes it 
shows line number with assertion (sometimes not - see above).

Before it was working ok around 2 or 3 weeks without 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 that this is probably little informative bug report, however 
I do not have much time to recompile mysqld with --debug option and 
produce a trace. Also, I had stripped mysqld with strip, so symbolic 
information is absent :-(((

How-To-Repeat:
Unknown.
Fix:
Unknown.

Submitter-Id:  Max Rudensky [EMAIL PROTECTED]
Originator:root
Organization:
MySQL support: none
Synopsis:  crashes when executing query on innodb table; probably corrupted table
Severity:  critical
Priority:  medium
Category:  mysql
Class: support
Release:   mysql-3.23.41 (Source distribution)

Environment:

System: Linux petrusha.localdomain 2.2.19 #1 Thu May 17 11:49:34 EEST 2001 i686 unknown
Architecture: i686

Some paths:  /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc /usr/bin/cc
GCC: Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
Compilation info: CC='gcc'  CFLAGS='-march=pentiumpro -O3'  CXX='gcc'  CXXFLAGS=''  
LDFLAGS=''
LIBC: 
lrwxrwxrwx1 root root   13 íÁÊ 13  2000 /lib/libc.so.6 - libc-2.1.3.so
-rwxr-xr-x1 root root  4101324 æÅ× 29  2000 /lib/libc-2.1.3.so
-rw-r--r--1 root root 20272704 æÅ× 29  2000 /usr/lib/libc.a
-rw-r--r--1 root root  178 æÅ× 29  2000 /usr/lib/libc.so
Configure command: ./configure  --with-innodb --with-berkeley-db 
--with-charset=koi8_ru --with-mysqld-user=dba
Perl: This is perl, version 5.005_03 built for i386-linux

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php