Thanks for the help everyone. I tried changing the type to timestamp¹ and
that did not fix the problem, however when I changed the type to
int¹ and it worked as it was suppose to.
Thanks,
Lael
Heikki,
Update on this. Managed to get this to happen with the file updates you
sent, on an internal box(same config as original problem rpt), log info
follows:
//Log file starts
011002 13:28:19 mysqld started
InnoDB: Database was not shut down normally.
Hi!
The log sequence number is only 300 000 bytes :).
You have data and log files which are almost completely
full of zeros, and consequently if you compress them
with gzip, you are able to send them to me as attachments.
Some notes on possible Linux bugs:
I notice that you are running the
Heikki,
Here's the details from the .err log:
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow
instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing
Chris,
what is the exact error message? How do you know that
it comes from ibuf0ibuf.c, line 2339? Have you compiled
yourself?
Regards,
Heikki
Innobase Oy
Getting an error message in the log saying...fp=(nil), etc, etc, possible bug
from ibuf0ibuf.c, line 2339
What're the possible reasons I
Tianlin,
you are right. If InnoDB did a scan from a secondary index to an
empty table, then it returned an error code MySQL did not accept
in this context. I changed now the error code and it will be right
in the next release .38, if Monty has not yet gotten it out.
Regards,
Heikki
