Still a mystery about your missing InnoDB database files
Rithish.
I seem to remember there is an option that will allow you to
store InnoDB files in their own seperate directory safely,
and not in the /var/lib/mysql default directory.
One of the many things I like about MyISAM tables is that
each database is kept in its own subdirectory, whereas the
default for InnoDB databases seems to be mixed in with the
mysql log files. This gives me a uneasy feeling, especially
as I delete the log files when backing up mysql databases.
The moral of this post must certainly be something like:
"As the data stored in a company's databases is vital to the
operation of the company, when it comes to the integrity and
safety of your company's databases, you cannot be too
paranoid. Make regular checks and backups of your databases,
implementing a staged backup policy, so that whatever
happens, you as the DBA, are fully covered for all possible
circumstances."
Which is obviously, thank God, what you have done Rithish.
Kind Regards
Keith
In theory, theory and practice are the same;
In practice they are not.
On Tue, 28 Feb 2006, Rithish Saralaya wrote:
> To: mysql@stripped
> From: Rithish Saralaya <rithish.saralaya@stripped>
> Subject: RE: error 1016 : cant open ibd file even though it exists
>
> Hello Keith.
>
> The power outage was known before-hand, and the server was
> shutdown before the outage happened. The server was
> brought up once the power returned. So no UPs intervention
> happened here.
>
> Regards,
> Rithish.
>
> -----Original Message-----
> From: mysql@stripped [mailto:mysql@stripped]
> Sent: Saturday, February 25, 2006 8:13 PM
> To: mysql@stripped
> Subject: RE: error 1016 : cant open ibd file even though it exists
>
>
>
> I do not use Innodb tables at the moment, so all this is
> pure speculation.
>
> Is/was the server connected to a UPS when the power failure
> happened?
>
> If so, did the UPS function properly and do you have any UPS
> logs to match against the mysql error log?
>
> Things to check for would be the time the UPS took over from
> the mains supply?
>
> If there was no UPS in operation, were your InnoDB tables
> corrupted when the power failure occured.
>
> Is it possible for the InnoDB tables to have become so
> corrupted that mysql had no alternative but to re-construct
> the tables?
>
> What are your config settings for mysql at boot up time?
> Do you have any directives to force checking of InnoDB
> tables at boot-time, and if so what are they please?
>
> As soon as you mentioned 'power failure' the words 'table
> corruption' sprang to my mind.
>
> Also, are there any mysql transaction logs (*.log) you can
> check, to see what was happening when the power outage
> occured?
>
> Keith
>
> In theory, theory and practice are the same;
> In practice they are not.
>
> On Sat, 25 Feb 2006, Rithish Saralaya wrote:
>
> > To: david@stripped
> > From: Rithish Saralaya <rithish.saralaya@stripped>
> > Subject: RE: error 1016 : cant open ibd file even though it exists
> >
> > Hello David.
> >
> > There was supposed to be a power outage in our office that day. So the
> > server was shut down. Finally when the power was back, the machine was
> > plugged on. That's all. No file system change. Nothing.
> >
> > Regards,
> > Rithish.
