Thanks,
I have the previous ib_log* files on the app server. And every thing on the cnf
file was perfect. Only the ib_log file's size was a mismatch. Whats the best
work around?
Can I copy the log files of the App server to the DB server and change the
innodb_log_file_size to 256M and then restart the MySQL server.
If I do so will I lose the updates to the database that happened today?
So my actual problem is this:
I have two sets of ib_logfile* files. To be particular there are
a.. ib_logfile0, ib_logfile1, ib_logfile2 on the App server - each
257M (when i did a du -sh). In the my.cnf file of the App server
innodb_log_file_size is set to 256M
b.. ib_logfile0, ib_logfile1, ib_logfile2 on the DB server - each
5M. These log files were created freshly by the MySQL server as the log files
from the App server was not copied to the DB server.
In the my.cnf file of the DB server innodb_log_file_size is set
to 5M by mistake. All the other settings were same as on the app server.
The ibdata1 file is that of the App server. And I get the log sequence errors
as shown in my previous post. But everything seems to be working fine. There
have been no problems accessing the data.
What I can I possibly do to get everything right. How can I correct the log
sequence error?
Should the log files of App server be in the DB server?
Thanks,
Ratheesh K J
----- Original Message -----
From: "Jan Kirchhoff" <[EMAIL PROTECTED]>
To: "Ratheesh K J" <[EMAIL PROTECTED]>
Cc: <mysql@lists.mysql.com>
Sent: Monday, December 11, 2006 1:25 PM
Subject: Re: Innodb log sequence error - urgent
> Ratheesh K J schrieb:
>> Hello all,
>>
>> yesterday we seperated our app server and db server. We moved our 70GB of
>> data from our app server to a new DB server. We installed MySQL 4.1.11 on
>> the DB server.
>>
>> Now the following happened. On the DB server the ibdata1 and all the
>> databases are the old ones (which were copied from the app server). But when
>> Mysql was installed the ib_logfile0 ib_logfile1 and ib_logfile2 were created
>> freshly on the DB serever. Each of these log files were created with 5M
>> size. on the app server these files were 256M in size (innodb_log_file_size
>> = 256M). On the DB server it is (innodb_log_file_size = 5M).
>>
>> Today morning when I checked the error log, there seems to be a lot of error
>> msg flowing in.
>>
>> 061211 11:41:47 InnoDB: Error: page 203046 log sequence number 87 3002891543
>> InnoDB: is in the future! Current system log sequence number 86 4025048037.
>> InnoDB: Your database may be corrupt.
>
> You cannot just copy innodb-databases to other servers without adjusting
> your my.cnf: Once you created an innodb-database, you cannot change
> parameters like "innodb_log_file_size" any more.
> (this is explained in the manual, you should read the chapter about
> backing up and restoring innodb-databases) So when you copy the database
> to the new server, be sure to copy the settings from the my.cnf, too!
>
> Jan
