Re: innodb log sequence problem

2015-08-06 Thread Csepregi Árpád
Thank you for answer. The problem is that I wrote in previous message that there is no sql backup just the files for binary backup. Hardware we are using is a simple laptop with Windows 7 that runs 5.1 server in case the originally installed files are in use. It runs an 5.5 server paralelly as

innodb log sequence problem

2015-08-05 Thread Csepregi Árpád
:02:30 InnoDB: Log file .\ib_logfile0 did not exist: new to be created InnoDB: Setting log file .\ib_logfile0 size to 24 MB InnoDB: Database physically writes the file full: wait... 150805 17:02:30 InnoDB: Log file .\ib_logfile1 did not exist: new to be created InnoDB: Setting log file

Re: innodb log sequence problem

2015-08-05 Thread Reindl Harald
Am 05.08.2015 um 17:06 schrieb Csepregi Árpád: 150805 17:02:31 InnoDB: Page dump in ascii and hex (16384 bytes): hex... 150805 17:02:31 InnoDB: Page checksum 1094951825, prior-to-4.0.14-form checksum 1449969277 InnoDB: stored checksum 1467223489, prior-to-4.0.14-form stored checksum 87759728

Re: InnoDB “log sequence in the future!” crashing, won't start

2011-11-07 Thread Karen Abgarian
Log sequence in the future means that, for whatever reason, the update in the data pages happened but update in the Innodb's log didn't.The InnoDB by itself, without backups, is not protected against media failures, and this happens to be just that. Innodb_force_recovery is not really a

Re: InnoDB “log sequence in the future!” crashing, won't start

2011-11-06 Thread Reindl Harald
Am 06.11.2011 06:05, schrieb Kevin Wang: I stopped mysql only to find that it wouldn't come back up, /etc/init.d/mysql start only outputs . . . . . . failed. I've narrowed it down to an issue with InnoDB. The database starts when innodb_force_recovery = 5 and nothing lower. When I check

InnoDB “log sequence in the future!” crashing, won't start

2011-11-05 Thread Kevin Wang
I stopped mysql only to find that it wouldn't come back up, /etc/init.d/mysql start only outputs . . . . . . failed. I've narrowed it down to an issue with InnoDB. The database starts when innodb_force_recovery = 5 and nothing lower. When I check table for my MyISAM tables, they check fine, but

Re: WHY do I see this error when restoring my backup db : InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files.

2009-02-14 Thread Moon's Father
or you may have copied the InnoDB tablespace but not the InnoDB log files. GOAL: Trying to restore mysql backup on different host using InnoDB backup that copes the backed up files to a files sever where I pulle them down to the new host I place all the MySQL datafiles and InnoDB log files

WHY do I see this error when restoring my backup db : InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files.

2009-02-06 Thread my sql
WHY do I see this error when restoring my backup db : InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. GOAL: Trying to restore mysql backup on different host using InnoDB backup that copes the backed up files to a files sever where

innodb log files but we only use MYISAM

2008-09-18 Thread AM Corona
I see the following log files -rw-rw 1 mysql mysql 10485760 Sep 16 17:30 ibdata1 -rw-rw 1 mysql mysql5242880 Sep 16 17:30 ib_logfile0 -rw-rw 1 mysql mysql5242880 Jan 17 2006 ib_logfile1 I checked every table on all databases. All are using MYISAM. innodb section in

Re: innodb log files but we only use MYISAM

2008-09-18 Thread Dan Nelson
In the last episode (Sep 18), AM Corona said: I see the following log files -rw-rw 1 mysql mysql 10485760 Sep 16 17:30 ibdata1 -rw-rw 1 mysql mysql5242880 Sep 16 17:30 ib_logfile0 -rw-rw 1 mysql mysql5242880 Jan 17 2006 ib_logfile1 I checked every table on all

InnoDB Log Optimisation

2008-05-09 Thread Ben Clewett
Dear MySql, I am trying to optimise InnoDB, and trying to find out how much of the innodb log file contains row data which has not been written to storage. Therefore I can optimize the size of the log, keeping it low to reduce crash recovery time yet high enough to be useful. I can see

Re: InnoDB Log Optimisation

2008-05-09 Thread Iñigo Medina García
Hi Ben, Dear MySql, I am trying to optimise InnoDB, and trying to find out how much of the innodb log file contains row data which has not been written to storage. Therefore I can optimize the size of the log, keeping it low to reduce crash recovery time yet high enough to be useful

Re: InnoDB Log Optimisation

2008-05-09 Thread Ben Clewett
much of the innodb log file contains row data which has not been written to storage. Therefore I can optimize the size of the log, keeping it low to reduce crash recovery time yet high enough to be useful. :-) I can see the varaible 'Innodb_data_pending_writes' which may be what I need

Extracting transactional data from InnoDB log files

2007-01-09 Thread Jason J. W. Williams
Hello, Is it possible to extract transactional data from InnoDB log files? InnoDB kept crashing and trying to insert the same record (replayed from the log after the crash I assume). I'd like to try and extract the record from log to reconstruct the query and try to break it again in case

Re: Innodb log sequence error - urgent

2006-12-16 Thread Heikki Tuuri
level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php . From: Ratheesh K J Date: December 11 2006 10:23am Subject: Re: Innodb log sequence error - urgent Get Plain Text Thanks, I have

Re: Innodb log sequence error - urgent

2006-12-11 Thread 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

Innodb log sequence error - urgent

2006-12-10 Thread Ratheesh K J
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

Re: Innodb log sequence error - urgent

2006-12-10 Thread Jan Kirchhoff
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

a question about innodb log file

2006-01-18 Thread wangxu
There are many information about different logs in manual but innodb log file. Please tell me where can i find it? What's innodb log file different to binlog? Where can i find data about redo and undo? thanks

Re: a question about innodb log file

2006-01-18 Thread Gleb Paharenko
different logs in manual but innodb log file. Please tell me where can i find it? What's innodb log file different to binlog? Where can i find data about redo and undo? thanks -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored

Increasing the InnoDB log file size

2004-12-10 Thread Ronan Lucio
Hi, I need to increase the innodeb_log_file_size parameter, but when I set it higher, mysql don´t starts and give the follow erro: 041210 13:27:40 mysqld started InnoDB: Error: log file ./ib_logfile0 is of different size 0 100663296 bytes InnoDB: than specified in the .cnf

RE: Increasing the InnoDB log file size

2004-12-10 Thread Anil Doppalapudi
] Subject: Increasing the InnoDB log file size Hi, I need to increase the innodeb_log_file_size parameter, but when I set it higher, mysql don´t starts and give the follow erro: 041210 13:27:40 mysqld started InnoDB: Error: log file ./ib_logfile0 is of different size 0

Re: Increasing the InnoDB log file size

2004-12-10 Thread Ronan Lucio
Anil, First shutdown the mysql cleanly. #mysqladmin shutdown then drop log files in data directory. restart mysql. it will create new log files. Do you know if is there a risk of loosing any data? Thanks, Ronan -- MySQL General Mailing List For list archives:

RE: Increasing the InnoDB log file size

2004-12-10 Thread Anil Doppalapudi
the InnoDB log file size Anil, First shutdown the mysql cleanly. #mysqladmin shutdown then drop log files in data directory. restart mysql. it will create new log files. Do you know if is there a risk of loosing any data? Thanks, Ronan -- MySQL General Mailing List For list archives: http

RE: Increasing the InnoDB log file size

2004-12-10 Thread Oropeza Querejeta, Alejandro
original- De: Ronan Lucio [mailto:[EMAIL PROTECTED] Enviado el: Viernes, 10 de Diciembre de 2004 11:38 a.m. Para: [EMAIL PROTECTED] Asunto: Increasing the InnoDB log file size Hi, I need to increase the innodeb_log_file_size parameter, but when I set it higher, mysql don´t starts and give

Re: Increasing the InnoDB log file size

2004-12-10 Thread Ronan Lucio
Anil and Oropeza, if mysql shutdowns cleanly. then there is no chance of loosing data. for safe side take compleate database backup. Ok, thank you very much for your help. Ronan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:

Re: InnoDB Log and binlog files and Solid State Disk?

2004-12-01 Thread Heikki Tuuri
Richard, - Original Message - From: Richard F. Rebel [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Tuesday, November 30, 2004 6:11 PM Subject: InnoDB Log and binlog files and Solid State Disk? --=-JDf9WlMx8c01FXMbzrGw Content-Type: text/plain Content-Transfer-Encoding

InnoDB Log and binlog files and Solid State Disk?

2004-11-30 Thread Richard F. Rebel
. Also the 6GB SSD. Our current InnoDB table space size is about 200GB. I planned on putting the innodb log log files on the SSD. These are not that large on the system we are gonig to replace, about 90 megs each for 3 of them. Does it make much sense to increase these significantly? Normally

RV: Innodb log file

2004-10-29 Thread Oropeza Querejeta, Alejandro
Hi, How can i increase the size of the log file and log buffer size? i tried to change it on my.cnf file but it return this error message: InnoDB: Error: log file ./ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 67108864 bytes! 041028 0:10:49

Innodb log file

2004-10-28 Thread Oropeza Querejeta, Alejandro
Hi, How can i increase the size of the log file and log buffer size? i tried to change it on my.cnf file but it return this error message: InnoDB: Error: log file ./ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 67108864 bytes! 041028 0:10:49

Re: Innodb log file

2004-10-28 Thread Eric Bergen
Check out this section in the manual on innodb log files. http://dev.mysql.com/doc/mysql/en/Adding_and_removing.html -Eric On Thu, 28 Oct 2004 15:47:27 -0500, Oropeza Querejeta, Alejandro [EMAIL PROTECTED] wrote: Hi, How can i increase the size of the log file and log buffer size? i

Re: innodb log

2004-05-13 Thread Heikki Tuuri
Hi! - Original Message - From: mayuran [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Monday, May 10, 2004 11:11 PM Subject: innodb log When I do a SHOW INNODB STATUS i see a query which is waiting for a lock to be released, but innodb status doesnt show the whole query

innodb log

2004-05-10 Thread mayuran
When I do a SHOW INNODB STATUS i see a query which is waiting for a lock to be released, but innodb status doesnt show the whole query, the end of it got truncated. it looks something like: INSERT INTO test(col1, .., col10) VALUES ('9', and just stops. is it possible to see the entire query, im