error 134 from storage engine
Tuesday, November 17th, 2009Para corrigir isto restaure seu banco de dados.
Caso seja myisam a Engine, use o comando (após parar o mysql):
myisamchk -r -o -f /var/lib/mysql/MEU_BANCO/*.MYI
Isto deverá sanar.
Abraços.
Publicidade
Arquivos
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- September 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
Categorias
- 1 (279)
- apple (1)
- bancos de dados (15)
- bds (12)
- bsd (6)
- C (4)
- CentOs (84)
- contos (12)
- crônicas de um geek (17)
- dba (4)
- debian (28)
- delphi (1)
- Deus (3)
- entretenimento (20)
- Eventos (4)
- fedora (42)
- FreeBSD || OpenBSD (16)
- Gentoo (22)
- gnu/linux (193)
- google (4)
- Hosting (198)
- How To (146)
- html (15)
- ibm (3)
- iis (2)
- javascript (8)
- Mandriva (13)
- mozilla (3)
- Nerdice! (34)
- Open Source (103)
- OpenSuse (20)
- Painéis de Controle (78)
- parallels (46)
- php (85)
- programação (36)
- python (8)
- red hat (83)
- redes (37)
- Ruby (5)
- Segurança (35)
- Sempre Lammer! (6)
- slackware (21)
- sun (7)
- ubuntu (39)
- unix (19)
- Virtualização (4)
- whmcpanel (27)
- Windows (48)
- Windows (NT~2008 server) (52)
- wordpress (4)
- xml (9)
Extras
Outros Nerds
Utilidades para Nerds