Hi,
thanks for you replys
Unfortunatly one can not use "REPAIR TABLE" - at least that is what MySQL tells me when trying. "Note: it is not possible on this type of database" (or was it table - don't remember exactly)
It came down to finding out wht was broken. I did it like this.
1. mysqlcheck --all-databases
tells me what database is broken - in my case it is pluto_main
2. mysqldump pluto_main >/tmp/db_sql_dump.sql
Dumps the sql that is needed to recreate the database. It then stops at the ponit where the DB is broken. Above the end of the log there then is the code to drop and recreate the broken table. It is then empty and data has to be filled again.
In my case these thre tables was broken :
DesignObjVariation_DesignObjParameter
DeviceTemplate_DeviceData
psc_dce_batdet
Does anyone know what is in these three tables ? The question is if makes sence to import just these three from the last "backup" (cold copy of the mysql directory) ? Or should I rather start over with a fresh database ?Can I find an Database documentation anywhere ?
Greetings
Viking
Example how the drop/recreate part looks :
DROP TABLE IF EXISTS `DesignObjVariation_DesignObjParameter`;
CREATE TABLE `DesignObjVariation_DesignObjParameter` (
`FK_DesignObjVariation` int(11) NOT NULL default '0',
`FK_DesignObjParameter` int(11) NOT NULL default '0',
`Value` text,
`FK_Skin` int(11) default NULL,
`FK_Language` int(11) default NULL,
`Ignore` tinyint(1) NOT NULL default '0',
`psc_id` int(11) default NULL,
`psc_batch` int(11) default NULL,
`psc_user` int(11) default NULL,
`psc_frozen` tinyint(1) default '0',
`psc_mod` timestamp NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
`psc_restrict` int(11) default NULL,
PRIMARY KEY (`FK_DesignObjVariation`,`FK_DesignObjParameter`),
UNIQUE KEY `psc_id` (`psc_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
