problem open a innodb table

------=_NextPart_000_00BD_01CBADEB.BBC9DE80
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_00BE_01CBADEB.BBC9DE80"


------=_NextPart_001_00BE_01CBADEB.BBC9DE80
Content-Type: text/plain;
charset="gb2312"
Content-Transfer-Encoding: quoted-printable

I messed up the ibdata1,ib_logfile1,0 files and encounter the problems =
of openning innodb tables even after I copied the back-up files of few =
months ago. I don't have many innodb tables and so this not causing too =
much trouble.

I don't know what to do for restoring those tables, and not even know if =
that is possible or not. Please help.

Attached is a table of primes that contains 2+ million primes yet it is =
so small that I can attached here.

Thanks
------=_NextPart_001_00BE_01CBADEB.BBC9DE80
Content-Type: text/html;
charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312">
<META content=3D"MSHTML 6.00.2900.6049" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><SPAN class=3DApple-style-span
style=3D"WORD-SPACING: 0px; FONT: medium 'Times New Roman'; =
TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: =
normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; =
widows: 2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: =
0px"><SPAN
class=3DApple-style-span
style=3D"FONT-SIZE: 13px; FONT-FAMILY: arial, sans-serif; =
BORDER-COLLAPSE: collapse">
<DIV><FONT face=3DArial size=3D2>I messed up the ibdata1,ib_logfile1,0 =
files and
encounter the problems of openning innodb tables even after I copied the =
back-up
files of few months ago. I don't have many innodb tables and so this not =
causing
too much trouble.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I don't know what to do for restoring =
those tables,
and not even know if that is possible or not. Please help.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Attached is a table of primes that =
contains 2+
million primes yet it is so small that I can attached here.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial
size=3D2>Thanks</FONT></DIV></SPAN></SPAN></FONT></DIV></BODY></HTML>

------=_NextPart_001_00BE_01CBADEB.BBC9DE80--


------=_NextPart_000_00BD_01CBADEB.BBC9DE80
Content-Type: text/plain; charset=us-ascii


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2 [at] m.gmane.org
------=_NextPart_000_00BD_01CBADEB.BBC9DE80--
Elim Qiu [ Fr, 07 Januar 2011 05:50 ] [ ID #2052707 ]

Re: problem open a innodb table

--001517479648f41f6604993aff55
Content-Type: text/plain; charset=ISO-8859-1

Dont you have mysql dump file for those table? It is best way to restore
InnoDB tables.

2011/1/7 Elim PDT <elim [at] pdtnetworks.net>

> I messed up the ibdata1,ib_logfile1,0 files and encounter the problems of
> openning innodb tables even after I copied the back-up files of few months
> ago. I don't have many innodb tables and so this not causing too much
> trouble.
>
> I don't know what to do for restoring those tables, and not even know if
> that is possible or not. Please help.
>
> Attached is a table of primes that contains 2+ million primes yet it is so
> small that I can attached here.
>
> Thanks
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=yogeshkore [at] gmail.com
>

--001517479648f41f6604993aff55--
Yogesh Kore [ Fr, 07 Januar 2011 06:36 ] [ ID #2052708 ]
Datenbanken » gmane.comp.db.mysql.general » problem open a innodb table

Vorheriges Thema: Slow MySQL Workbench startup
Nächstes Thema: cleaning up general_log table?