Mattias,
- Original Message -
From: "Mattias J" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Friday, January 14, 2005 8:50 PM
Subject: Re: Upgrade correpted InnoDB tables
At 2005-01-14 18:09, you wrote:
this is very strange. Have you used MySQL-5.0.x
"Mattias J" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, January 13, 2005 6:57 PM
Subject: Re: Upgrade correpted InnoDB tables
There are mostly just 2 or 3 corrupted tables out of about 100 in each
database/schema/namespace and if possible we would like to k
Mattias,
was it so that you RECREATED those tables with 4.0.21, and you STILL got the
error in 4.1.8?
Regards,
Heikki
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To:
Sent: Friday, January 14, 2005 7:02 PM
Subject: Re: Upgrade correpted InnoDB tables
iday, January 14, 2005 4:39 PM
Subject: Re: Upgrade correpted InnoDB tables
Ok. This is what happened:
We removed MySQL from the server and re-installed 4.0(.21) then put back
some old data.
When trying to upgrade to 4.1.9 we encountered the same problem, with the
exact same tables being corrupted
/InnoDB_Monitor.html
Regards,
Heikki
- Original Message - From: "Mattias J" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, January 13, 2005 6:57 PM
Subject: Re: Upgrade correpted InnoDB tables
There are mostly just 2 or 3 corrupted tables out of about 100
c
Sent: Thursday, January 13, 2005 6:57 PM
Subject: Re: Upgrade correpted InnoDB tables
There are mostly just 2 or 3 corrupted tables out of about 100 in each
database/schema/namespace and if possible we would like to keep the
information in the other tables.
At 2005-01-13 17:47, you wrote:
If you don&#x
InnoDB which also backs up MyISAM
tables
http://www.innodb.com/order.php
- Original Message -
From: "Mattias J" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, January 13, 2005 6:57 PM
Subject: Re: Upgrade correpted InnoDB tables
There are mo
There are mostly just 2 or 3 corrupted tables out of about 100 in each
database/schema/namespace and if possible we would like to keep the
information in the other tables.
At 2005-01-13 17:47, you wrote:
If you don't have any data in innodb, delete and recreate the
tablespace including the frm f
If you don't have any data in innodb, delete and recreate the
tablespace including the frm files. This will give you a fresh 4.1
table space to import into.
-Eric
On Thu, 13 Jan 2005 16:37:39 +0100, Mattias J <[EMAIL PROTECTED]> wrote:
> Earlier today we tried upgrading one of our MySQL servers
