osx - MySQL: Remove all references to database -


while importing dump newly created database, server stopped classic server has gone away message. know why happened , fact did occur isn't part of problem. i've removed database directory /usr/local/mysql/data/ , still mysqld not start successfully, because of log or init file.

the goal fixed without having reinstall mysql.

mysql err log:

innodb: page checksum 1559794421, prior-to-4.0.14-form checksum 641317514 innodb: stored checksum 3364647797, prior-to-4.0.14-form stored checksum 641317514 innodb: page lsn 16 1049927436, low 4 bytes of lsn @ page end 1049927436 innodb: page number (if stored page already) 43379, innodb: space id (if created >= mysql-4.1.1 , stored already) 0 innodb: page may index page index id 0 3302 innodb: (index "some_index" of table "some_database"."some_table") innodb: database page corruption on disk or failed innodb: file read of page 43379. innodb: may have recover backup. innodb: possible operating innodb: system has corrupted own file cache innodb: , rebooting computer removes innodb: error. innodb: if corrupt page index page innodb: can try fix corruption innodb: dumping, dropping, , reimporting innodb: corrupt table. can use check innodb: table scan table corruption. innodb: see http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html innodb: forcing recovery. innodb: ending processing because of corrupt database page. 

mysql version:

$ mysql --version /usr/local/mysql/bin/mysql  ver 14.14 distrib 5.1.55, apple-darwin10.3.0 (i386) using readline 5.1 

mysql conf file:

$ cat /etc/my.cnf  [mysqld] max_allowed_packet=128m 

you can try force recovery way : how force recovery innodb or safer way try recovering table : table recovery after database page corruption hope you.


Comments

Popular posts from this blog

delphi - How to convert bitmaps to video? -

jasper reports - Fixed header in Excel using JasperReports -

python - ('The SQL contains 0 parameter markers, but 50 parameters were supplied', 'HY000') or TypeError: 'tuple' object is not callable -