Yes. Maybe a mystery that will remain unsolved for some time; however,
hopefully will get solved.
I deleted all the related files, dropped the database, and recreated it
again freshly from a backup. It was needed to try out some migration of data
across tables, and hence the data was not 'that' critical. I shudder at the
thought of this happening on the live server... I would have ended up having
a rocket lighted behind me... ;o)
On another note, what gets written into the ibdata1 file, wrt a
database/table? Can't I write/update something into it to rectify any
dangling references it has to any db/table?
From: Heikki Tuuri [mailto:heikki.tuuri@stripped]
Sent: Monday, February 27, 2006 1:54 PM
Subject: Re: error 1016 : cant open ibd file even though it exists
----- Original Message -----
From: ""Rithish Saralaya"" <rithish.saralaya@stripped>
Sent: Monday, February 27, 2006 7:06 AM
Subject: RE: error 1016 : cant open ibd file even though it exists
> I found the ibdata1 and ib_log files located in only '/var/lib/mysql'
> is defined as the mysql home folder.
> The last time my.cnf was editied was on the 9th of Dec, and the database
> created somewhere in the month of January. So the database would have been
> created with the same configurations.
> Thankfully, I have a dump of the original database. Looks like I have to
> restore all of the 35 GB of data again.
then this remains a mystery. InnoDB never deletes ibdata files or
ib_logfiles by itself.
Oracle Corp./Innobase Oy
InnoDB - transactions, row level locking, and foreign keys for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM