<div class="gmail_quote">On Sat, Jan 30, 2010 at 2:51 PM, Rudá Porto Filgueiras <span dir="ltr"><<a href="mailto:rudazz@gmail.com">rudazz@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div>On Sat, Jan 30, 2010 at 6:56 AM, Shane Hathaway <span dir="ltr"><<a href="mailto:shane@hathawaymix.org" target="_blank">shane@hathawaymix.org</a>></span> wrote:<br> </div><div class="im">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
- Run the MySQL database verification and repair tools. It's possible that the object you need is there, but MySQL can't find it due to corrupted indexes or similar.<br>
<br></blockquote></div><div><br>I will do that, but it must afert 02:00 am. :-)<br></div></div></blockquote></div><br>Only to update:<br><br>After check and recover all MYISAM tables: "myisamchk -c *.MYI" and "myisamchk -r *.MYI", zodbconvert.py runs fine and read all objects and trasactions from MySQL and export to FileStorage file with 22GB.<br>
<br>I think it solve these integrity problems, but I will run the migration process to see what will happen.<br>Shane, thanks again by your support.<br><br clear="all">Cheers,<br><br>-- <br>Rudá Porto Filgueiras<br><a href="http://python-blog.blogspot.com">http://python-blog.blogspot.com</a><br>
<a href="http://twitter.com/rudaporto">http://twitter.com/rudaporto</a><br>