Re: Cloned machine mysql startup problem with innodb

2004-10-26 Thread Heikki Tuuri
Paul,
- Original Message - 
From: "Paul W" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Monday, October 25, 2004 11:33 AM
Subject: Cloned machine mysql startup problem with innodb


For backup purposes I have what amounts
to a complete clone of a live server.
During the process of copying
everything, the MySQL data was copied
over in its entirety. My problem is that
the mysqld won't start now on this
second machine. I don't need the
databases to be preserved here (intend
to rebuild them later then dump data
into them). Therefore I can delete the
database files themselves and start
again if need be, but I'm not sure what
would be a correct way to do this with
the innodb error shown below. Somebody
know if it's safe to delete most things
from /var/lib/mysql? Could I just delete
libdata1?
As to the line saying I should edit
innodb_data_file_path back to what it
was - I have no idea what it was  :-(
I'm after the simplest way to get it
started, the rest is easy.
from the startup errors:
InnoDB: Error: data file
/var/lib/mysql/ibdata1 is of a different
size
InnoDB: 6656 pages (rounded down to MB)
InnoDB: than specified in the .cnf file
128000 pages!
the error means that your my.cnf does not match to the ibdata1 file size. In 
my.cnf you have specified ibdata1 to be 2000 MB, but the actual size of 
ibdata1 is only 104 MB.

Obviously, you have not 'cloned' the server properly. Besides my.cnf and the 
database directories under the datadir of MySQL, you must copy also ibdata 
files an ib_logfiles in order to copy the InnoDB tablespace as is.

InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data
files, and it failed here,
InnoDB: you should now edit
innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the
new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB
only wrote those files full of
InnoDB: zeros, but did not yet use them
in any way. But be careful: do not
InnoDB: remove old data files which
contain your precious data!
041019 13:05:25  Can't init databases
041019 13:05:25  Aborting
TIA,
Paul W
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 technical support from https://order.mysql.com/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


Cloned machine mysql startup problem with innodb

2004-10-25 Thread Paul W
For backup purposes I have what amounts 
to a complete clone of a live server. 
During the process of copying 
everything, the MySQL data was copied 
over in its entirety. My problem is that 
the mysqld won't start now on this 
second machine. I don't need the 
databases to be preserved here (intend 
to rebuild them later then dump data 
into them). Therefore I can delete the 
database files themselves and start 
again if need be, but I'm not sure what 
would be a correct way to do this with 
the innodb error shown below. Somebody 
know if it's safe to delete most things 
from /var/lib/mysql? Could I just delete 
libdata1?

As to the line saying I should edit 
innodb_data_file_path back to what it 
was - I have no idea what it was  :-(

I'm after the simplest way to get it 
started, the rest is easy.

from the startup errors:
InnoDB: Error: data file 
/var/lib/mysql/ibdata1 is of a different 
size
InnoDB: 6656 pages (rounded down to MB)
InnoDB: than specified in the .cnf file 
128000 pages!
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data 
files, and it failed here,
InnoDB: you should now edit 
innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the 
new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB 
only wrote those files full of
InnoDB: zeros, but did not yet use them 
in any way. But be careful: do not
InnoDB: remove old data files which 
contain your precious data!
041019 13:05:25  Can't init databases
041019 13:05:25  Aborting

TIA,
Paul W
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]