Tag Info

New answers tagged

0

This situation sounds a lot like a post I answered two years ago (InnoDB table SELECT returns ERROR 2006 (HY000): MySQL server has gone away (after power outage)) First, here is the InnoDB Architecture In that post, I basically point out that the metadata of the table is still present inside the system tablespace file ibdata1. When you ran SHOW TABLES;, ...


0

Yes, you can tray to repair your innoDB table First you can backup you tables. 1.- Stop you MySQL service 2.- backup all the data from "C:\xampp\mysql\data" to another folder, example: "C:\xampp\mysql\databackup" 3.- Add or change the value on you my.ini innodb_force_recovery option. [mysqld] innodb_force_recovery = 4 4.- Start your mysql service. ...


-1

You can try creating a new table according to old one's structure. Not sure if this will realy help as you say that your original table is corrupted: CREATE TABLE `new_table` LIKE `MY_TABLE`; If new table is ok, you can drop old one: DROP TABLE `MY_TABLE`; Otherwise you will have to drop the table (with the command above) and recreate it manually or ...


0

Unfortunately the only way to recover your data is to recover them from a backup, you can import just that single table and then insert the particular row. I will edit my answer to get more precise here, first of all you write that you use dynamic row length. This makes the recover operation way harder if not impossible compared to fixed row length. If you ...


0

After googling for hours, I stumbled across a thread that wasn't really related to my issue, best I could tell, but it seemed harmless enough to try, and voilĂ ! I looked at /var/lib/postgresql/9.1/main/pg_clog, and saw: drwx------ 2 postgres postgres 4096 Mar 15 15:20 . drwx------ 13 postgres postgres 4096 Mar 25 12:15 .. -rw------- 1 postgres ...



Top 50 recent answers are included