Henrik,
the most probable reason is that someone has edited my.cnf meanwhile, and you are now reading ibdata files from somewhere else.
Best regards,
Heikki Tuuri
Innobase Oy
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables
http://www.innodb.com/order.php
Order MySQL Network from http://www.mysql.com/network/
----- Original Message ----- From: ""Henrik Skotth"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, February 23, 2005 1:16 PM
Subject: Lost InnoDB Data
------=_NextPart_000_0076_01C519A0.CE3C7EA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello all.
I have a problem which is very serious for us. After shutting down our = mysql database and starting it up again, ALL our innodb-tables are just = as they were several weeks ago (january 31). All the changes, additions, = deletions that have happened since are gone. The same thing happens if = we go back to backups which are not entirerly new but later than jan 31. = I have no idea what's causing this, and I have absolutely no clue what = to do about it. Any suggestions? We're running MySQL 4.0.21 on Red Hat.
Any help with this would be greatly appreciated! Best regards, -- Henrik Skotth ------=_NextPart_000_0076_01C519A0.CE3C7EA0--
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
