Skip to main content
fix links to github
Source Link
akuzminsky
  • 5k
  • 14
  • 16

Wiki answer generated from question comments by akuzminsky


If you see *.ibd files then innodb_file_per_table is ON, otherwise all tables would be in ibdata1.

If it tells a table doesn't exists then the table is missing in InnoDB dictionary. Try to dump all tables into separate sql dumps (one table - one file). Those tables you can't dump you can restore with TwinDB recovery toolkitTwinDB recovery toolkit.

There are no binary packages yet. You have to get source code from launchpadGitHub and compile it. See instructions at Recover InnoDB dictionary. It's pretty straightforward:

bzrgit lpclone [email protected]:twindb/undrop-for-innodb .git

and then

make all

Wiki answer generated from question comments by akuzminsky


If you see *.ibd files then innodb_file_per_table is ON, otherwise all tables would be in ibdata1.

If it tells a table doesn't exists then the table is missing in InnoDB dictionary. Try to dump all tables into separate sql dumps (one table - one file). Those tables you can't dump you can restore with TwinDB recovery toolkit.

There are no binary packages yet. You have to get source code from launchpad and compile it. See instructions at Recover InnoDB dictionary. It's pretty straightforward:

bzr lp:undrop-for-innodb 

and then

make all

Wiki answer generated from question comments by akuzminsky


If you see *.ibd files then innodb_file_per_table is ON, otherwise all tables would be in ibdata1.

If it tells a table doesn't exists then the table is missing in InnoDB dictionary. Try to dump all tables into separate sql dumps (one table - one file). Those tables you can't dump you can restore with TwinDB recovery toolkit.

There are no binary packages yet. You have to get source code from GitHub and compile it. See instructions at Recover InnoDB dictionary. It's pretty straightforward:

git clone [email protected]:twindb/undrop-for-innodb.git

and then

make all
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
Source Link

Wiki answer generated from question comments by akuzminskyakuzminsky


If you see *.ibd files then innodb_file_per_table is ON, otherwise all tables would be in ibdata1.

If it tells a table doesn't exists then the table is missing in InnoDB dictionary. Try to dump all tables into separate sql dumps (one table - one file). Those tables you can't dump you can restore with TwinDB recovery toolkit.

There are no binary packages yet. You have to get source code from launchpad and compile it. See instructions at Recover InnoDB dictionary. It's pretty straightforward:

bzr lp:undrop-for-innodb 

and then

make all

Wiki answer generated from question comments by akuzminsky


If you see *.ibd files then innodb_file_per_table is ON, otherwise all tables would be in ibdata1.

If it tells a table doesn't exists then the table is missing in InnoDB dictionary. Try to dump all tables into separate sql dumps (one table - one file). Those tables you can't dump you can restore with TwinDB recovery toolkit.

There are no binary packages yet. You have to get source code from launchpad and compile it. See instructions at Recover InnoDB dictionary. It's pretty straightforward:

bzr lp:undrop-for-innodb 

and then

make all

Wiki answer generated from question comments by akuzminsky


If you see *.ibd files then innodb_file_per_table is ON, otherwise all tables would be in ibdata1.

If it tells a table doesn't exists then the table is missing in InnoDB dictionary. Try to dump all tables into separate sql dumps (one table - one file). Those tables you can't dump you can restore with TwinDB recovery toolkit.

There are no binary packages yet. You have to get source code from launchpad and compile it. See instructions at Recover InnoDB dictionary. It's pretty straightforward:

bzr lp:undrop-for-innodb 

and then

make all
Source Link
Paul White
  • 90.3k
  • 30
  • 424
  • 663

Wiki answer generated from question comments by akuzminsky


If you see *.ibd files then innodb_file_per_table is ON, otherwise all tables would be in ibdata1.

If it tells a table doesn't exists then the table is missing in InnoDB dictionary. Try to dump all tables into separate sql dumps (one table - one file). Those tables you can't dump you can restore with TwinDB recovery toolkit.

There are no binary packages yet. You have to get source code from launchpad and compile it. See instructions at Recover InnoDB dictionary. It's pretty straightforward:

bzr lp:undrop-for-innodb 

and then

make all
Post Made Community Wiki by Paul White