[Zope] - Corrupted data record errors?

[Jim Fulton]

Brad Cox wrote:
> 
> Could someone please advise on what to do about corrupted data, and what
> might have caused it?

Looking at your file, it looks like the problem occurred during Zope
startup.  Did you have a problem starting Zope just prior to this?

The record that contains product information for the MySQL DA
was incompletely written at the end of the file.  I wonder if
a broken MySQL binary could have caused a memory corruption 
problem that caused the record to have been partially written
or caused Zope to crash while writing the record.

I have seen memory errors (e.g. bad pointers) cause file
writes to fail without errors on Win32.  I wonder if something
similar happened here.

I'm going to look into getting Zope to try to recognize
final records that are partially written and ignoring them.
The next generation of the database will do a much better job in
cases like this.

You can always try to repair an error like this by truncating 
the file at the position reported in the error message.
(I do this in emacs, you could do this in a variety of other ways).
This makes sense especially if the problem position is near the
end of the file.

I'll send you a repaired database file (Data.bbb) in a separate
email.

Jim

--
Jim Fulton           mailto:jim@digicool.com
Technical Director   (888) 344-4332              Python Powered!
Digital Creations    http://www.digicool.com     http://www.python.org

Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email
address may not be added to any commercial mail list with out my
permission.  Violation of my privacy with advertising or SPAM will
result in a suit for a MINIMUM of $500 damages/incident, $1500 for
repeats.