Strona Główna
|
Szukaj
|
Użytkownicy
|
Grupy
|
Galerie
|
Rejestracja
|
Profil
|
Zaloguj się, by sprawdzić wiadomości
|
Zaloguj
Forum Draco&Mates Strona Główna
->
Regulamin
Napisz odpowiedź
Użytkownik
Temat
Treść wiadomości
Emotikony
Więcej Ikon
Kolor:
Domyślny
Ciemnoczerwony
Czerwony
Pomarańćzowy
Brązowy
Żółty
Zielony
Oliwkowy
Błękitny
Niebieski
Ciemnoniebieski
Purpurowy
Fioletowy
Biały
Czarny
Rozmiar:
Minimalny
Mały
Normalny
Duży
Ogromny
Zamknij Tagi
Opcje
HTML:
NIE
BBCode
:
TAK
Uśmieszki:
TAK
Wyłącz BBCode w tym poście
Wyłącz Uśmieszki w tym poście
Kod potwierdzający: *
Wszystkie czasy w strefie CET (Europa)
Skocz do:
Wybierz forum
Forum
----------------
Regulamin
Pomoc
Pokój Wspólny
Nasza twórczość
HP
----------------
Książki HP
Ekranizacja książek J.K.Rowling
Galeria
Wszystko i nic
----------------
Zabawy
Ulubione
RPG
Humor
Zakazany Las
Krzyczące pudełko ;)
Przestarzałe
Przegląd tematu
Autor
Wiadomość
0511VENUS87
Wysłany: Pią 4:28, 27 Maj 2011
Temat postu: Jordan 13 How to recover corrupted MyISAM file in
v class="googleright">
MySQL is one of the most popular open-source database in the world. The reasons its popularity is its availability, performance,
Jordan 13
, robust transactional support, etc. It offers three types of database engines, MyISAM, InnoDB, and MySQL Archive wherein the MyISAM table is the default table type that is fast, simple to use, and allows full-text searching. Though the MyISAM table is reliable, it can become corrupt and, thus, inaccessible following a system crash. In such cases, you should use the Repair Table command to recover MySQL table. However, if the you are still not able to repair MySQL database then you should opt for a third-party MySQL database recovery software to do the needful.
Consider a scenario wherein you are have MySQL 5.0 installed on your system. You run the myisamchk command to check a table and an error message is displayed, that is:
"clients are using or haven't closed the table properly."
Cause:
The root cause for the aforementioned error message is that the MyISAM index file has not been closed properly. There could be the following reasons for this:
A table was modified by the myisamchk command while it was in use by mysqld.
MySQL crashed while an update was being written on the table.
Multiple mysqld servers are using the table simultaneously that may result in data integrity and, hence, data corruption.
A MyISAM table has been copied without using the Lock Tables and Flush Tables command.
Resolution:
To resolve this issue, you should use the following methods:
Repair the corrupted table by using the Repair Table command, if mysqld is running.
Repair the corrupted table by using the myisamchk command, if mysqld is not running.
The aforementioned methods should be able to perform MySQL recovery. However, if you still are not able to recover MySQL database then you should consider using a third-party MySQL database repair software. Such tools are read-only in nature that do not overwrite the original database using fast yet sophisticated scanning algorithms.
Stellar Phoenix Database Recovery for MySQL is a MySQL recovery software that enables you to repair MySQL database. It is able to recover MySQL database for the MyISAM and InnoDB MySQL database storage engines. This MySQL repair tool supports MySQL recovery of MyISAM (.myd, .myi, .frm) and InnoDB (.ibdata, .ibd, .frm) files. It is compatible with Windows 7,
Jordan Spizike Planning the Optimal Cafe World Men
, Vista,
Fake Jordans Psoriases Treatment and Skin Disorder Herbal Remedies
, Server 2003,
Jordan Shoes 2011
, XP, and Server 2000. It is supported by MySQL 4.x and 5.x versions.
Report this article
<scr
fora.pl
- załóż własne forum dyskusyjne za darmo
Powered by
phpBB
© 2001, 2005 phpBB Group, modified by MAR
Inheritance
free theme by
spleen
&
Programosy
Regulamin