Merci de ces infos
J'ai fait des essais et voici les réponses (cf. fin du post).
Ce qui m'inquiète particulièrement ce sont les deux points principaux :
- Le message "your database my be corrupt"
L'utilisation du mode de récupération (innodb_force_recovery = 1 à 6) permet de relancer MySQL.
> Mais comment retirer la corruption de la base ?
- la fin du message dans "error.log"
130725 10:55:04 InnoDB: Assertion failure in thread 4880 in file btr0cur.c line 297
InnoDB: Failing assertion: page_is_comp(get_block->frame) == page_is_comp(page)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
par expérience, les plantages de "xxx.c, ligne y" sont très mauvais signe.
***
[SLOW.LOG]
C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld, Version: 5.5.32-log (MySQL Community Server (GPL)). started with:
TCP Port: 3306, Named Pipe: (null)
Time Id Command Argument
[LOG.LOG]
C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld, Version: 5.5.32-log (MySQL Community Server (GPL)). started with:
TCP Port: 3306, Named Pipe: (null)
Time Id Command Argument
130725 10:52:55 1 Connect root@localhost on edf_scav
...
130725 10:55:05 4 Query SELECT (
(SELECT COUNT(*) FROM `ACCES`)
+ (SELECT COUNT(*) FROM `ALARMES`)
+ (SELECT COUNT(*) FROM `ALARMES_MODELE`)
+ (SELECT COUNT(*) FROM `CRB_FILE`)
+ (SELECT COUNT(*) FROM `PARAMETRES`)
+ (SELECT COUNT(*) FROM `VOIE`)
)
[ERROR.LOG]
130725 10:50:07 [Note] Plugin 'FEDERATED' is disabled.
130725 10:50:07 InnoDB: The InnoDB memory heap is disabled
130725 10:50:07 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130725 10:50:07 InnoDB: Compressed tables use zlib 1.2.3
130725 10:50:07 InnoDB: Initializing buffer pool, size = 618.0M
130725 10:50:07 InnoDB: Completed initialization of buffer pool
130725 10:50:07 InnoDB: highest supported file format is Barracuda.
130725 10:50:07 InnoDB: Error: page 7 log sequence number 50190777377
InnoDB: is in the future! Current system log sequence number 15325538316.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
... j'ai eu 3000 message dans le même style ...
130725 10:55:04 InnoDB: Error: page 1289106 log sequence number 101991204073
InnoDB: is in the future! Current system log sequence number 15325700053.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130725 10:55:04 InnoDB: Assertion failure in thread 4880 in file btr0cur.c line 297
InnoDB: Failing assertion: page_is_comp(get_block->frame) == page_is_comp(page)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.