WARNING: An Error occurred, please refresh the page and try again.

[pixelpadre]

Huh...I just read dr. last post more closely. So you are saying that ceon is innodb and ZC is myisam. Thats amazing. And it appears that all files that were myisam were left untouched. I even had non-ZC databases that were mixed with the two types. In those the same thing happened. ibdata was destroyed while the other data was fine. Sound like myisam is the only way to go. So now that we know that myisam was not vulnerable, can we say what caused the crash and/or damage?

And can I convert the ibdata to myisam?

Big kudo for the big reveal.

[DrByte]

So you are saying that ceon is innodb and ZC is misaim.

I suspect Ceon used InnoDB because he wanted to use transactions, or needed InnoDB's alternate approach to record locking to support the features in his code.

InnoDB isn't "wrong". But it's rarely properly optimized in the MySQL server. InnoDB serves a purpose. And MyISAM serves a purpose. One should use the right tool for the job. But if one is going to use it, one also needs to ensure that the infrastructure is prepared to support it.

can we say what caused the crash and/or damage?

I think whoever has access to your server is in the best position to answer that.
I doubt it has anything to do with "excess Zen Cart traffic".
But if there's some OS-vulnerability or MySQL vulnerability that an attacker was trying to exploit, that might be a culprit.

And can I convert the ibdata to myisam?

Sure: Use phpMyAdmin (or equiv) to change the table type from InnoDB to MyISAM.
But remember that in doing so you will lose all the benefits that InnoDB offers.