I cannot think of any safe alternative. Trying to recover files that
are in memory strikes me as very unwise with InnoDB.
Ananda Kumar wrote:
Hi Baron,
If the database is huge, the restoring from mysqldump would take lot of
time.
Is there any other alternative.
egards
anandkl
On 9/26/07, Baron Schwartz <[EMAIL PROTECTED]> wrote:
How do I recover them, and do you think this is wise? At this point, I
still think it might be a better idea to do a complete reinstall /
restore / transaction log run.
There's no need to reinstall :-) It's not MS Windows, it's just InnoDB.
As others have said, I'd try to do a global LOCK TABLES (I wouldn't do
a FLUSH TABLES because I'm not sure how missing files might be handled
-- it could crash) and a full dump. Then just shut down MySQL and
delete *all* the InnoDB files and let it initialize with fresh files on
restart, and import. You should be fine. But I'd do it ASAP because in
the meantime you could have a crash.
Baron
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
--
Baron Schwartz
Xaprb LLC
http://www.xaprb.com/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
