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.
