as well without any problems.
2015.08.05. 17:17 keltezéssel, Reindl Harald írta:
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
Hello,
We are facing a strange innodb related problem. Our client ran mysql 5.1
on WinXP having file_per_table disabled. OS crashed after 5 years
continuous running and our client of course does not have any backup
(big company with own IT department so we do not have acces to their
system
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
...@wagnerbianchi.com
Skype: wbianchijr
Em 27 de maio de 2015 14:29, Wagner Bianchi wagnerbianch...@gmail.com
escreveu:
Pessoal, depois de solicitar para o time da Oracle a inclusão de
informações de monitoramento do InnoDB Change Buffer, a adição de
informação foi levada em consideração e compartilho com
Pessoal, depois de solicitar para o time da Oracle a inclusão de
informações de monitoramento do InnoDB Change Buffer, a adição de
informação foi levada em consideração e compartilho com vocês:
https://dev.mysql.com/doc/refman/5.5/en/innodb-insert-buffering.html
https://dev.mysql.com/doc/refman
Found the cause.
sync_binlog was set to 1. I suspect that the default value is 5.5 was 0 and
that is has changed to 1
sometime after that.
Setting it to 0 boosted the performance back to normal (4x speed) and the HD
LED indicated much
lower stress on the hard disk.
Found this after I found
Hi Jørn,
Found this after I found out what caused it:
https://www.percona.com/blog/2009/01/21/beware-ext3-and-sync-binlog-do-not-play-well-together/
I suspect that this also apply to ext4, or?
I would go more specific and say that sync_binlog=1 does not play well with
single-threaded
Hello
(again I must say).
Over a year ago I experienced a severe drop in the MySQL Innodb performance
after ugrading to MySQL
5.6. I did not found any solution to that so I downgraded back to 5.5.33 and
lived with in until
recently.
After a system disk crash I replaced the system disk
Can you share the SHOW ENGINE INNODB STATUS\G ?
--
*Wagner Bianchi, +55.31.8654.9510*
Oracle ACE Director
https://apex.oracle.com/pls/otn/f?p=19297:4:105567988301604::NO:4:P4_ID:4541,
MySQL Certified Professional
Percona MySQL Forum http://www.percona.com/forums/ Community V.I.P.
Email: m
On Wednesday, May 20, 2015, wagnerbianchi.com wrote:
Can you share the SHOW ENGINE INNODB STATUS\G ?
Sure, here it is.
*** 1. row ***
Type: InnoDB
Name:
Status:
=
2015-05-20 20:29:56 0x7f9a4c189700 INNODB
.
It looks from show engine innodb status that your server is just starting up,
and caches are empty, so versus a 5.5 server that has been running for a while
it will likely be slower.
What you may be able to do to track a specific set of statements that take
longer in 5.7, is convert
On Wednesday, May 20, 2015, Morgan Tocker wrote:
Hi Jørn,
Wagner’s point about SHOW ENGINE INNODB STATUS is a good one. A couple of
other questions about your workload:
- The data collector system processing jobs, is it multi threaded?
Sorry, forgot about that. No, it is not multi
I'd like to add to the Morgan's note that if you want to restrict the
number of transactions inside InnoDB kernel to 16, you need at least
configure the tickets...
= http://www.pythian.com/blog/once-again-about-innodb-concurrency-tickets/
BTW, leave it as its default, IMHO
://www.percona.com/forums/ Community V.I.P.
Email: m...@wagnerbianchi.com
Skype: wbianchijr
2015-05-20 15:15 GMT-03:00 wagnerbianchi.com m...@wagnerbianchi.com:
Can you share the SHOW ENGINE INNODB STATUS\G ?
--
*Wagner Bianchi, +55.31.8654.9510 %2B55.31.8654.9510*
Oracle ACE Director
https
Hi Jørn,
Wagner’s point about SHOW ENGINE INNODB STATUS is a good one. A couple of
other questions about your workload:
- The data collector system processing jobs, is it multi threaded?
- Do you have a sample schema + set of queries we could look at?
(We pay close attention to regressions
On Wednesday, May 20, 2015, wagnerbianchi.com wrote:
I'd like to add to the Morgan's note that if you want to restrict the
number of transactions inside InnoDB kernel to 16, you need at least
configure the tickets...
= http://www.pythian.com/blog/once-again-about-innodb-concurrency-tickets
.
An alternative if you have the disk space, and the table has no triggers,
is using a tool like pt-online-schema change to avoid locking during the
change (it creates a shadow table with the proper data and renames the
tables once it is done).
I am looking for a way to convert about 40GB of InnoDB tables
Hi there,
I am looking for a way to convert about 40GB of InnoDB tables from latin1
character set to utf8. As true conversion will take ages, I had the idea of
just changing the character sets (and preferably collation, too) of the tables
without actually converting the data. Conversion could
Are both instances running the same MySQL version and release? Are they
MASTER and SLAVE, actively replicating? Are the InnoDB configurations
currently running on both servers the same?
--
*WB*
2014-09-06 6:00 GMT-03:00 Ajay Garg ajaygargn...@gmail.com:
Sorry, forgot to specify the engine
Sorry, forgot to specify the engine.
The table runs on InnoDB backend.
Also, changed the subject to be more specific.
On Sat, Sep 6, 2014 at 2:26 PM, Ajay Garg ajaygargn...@gmail.com wrote:
Hi all.
We are facing a very strange scenario.
We have two mysql-instances running on the same
you're seeing is simply pre-allocated space.
See also the last paragraph on
http://dev.mysql.com/doc/refman/5.6/en/innodb-multiple-tablespaces.html
File-per-table tablespace files are auto-extending regardless
of the value of innodb_autoextend_increment. The initial extensions
Could you please answer these questions also. What does data_free field
from SHOW TABLE STATUS shows?
When should we run optimize table for innodb tables?
I read various blogs. They said data_free shows free space inside the
innodb tables. But after doing *optimize table*, the value inside
innodb_file_per_table=1 and you are
seeing data_free values round about 4MB what
you're seeing is simply pre-allocated space.
See also the last paragraph on
http://dev.mysql.com/doc/refman/5.6/en/innodb-multiple-tablespaces.html
File-per-table tablespace files are auto-extending regardless
Senior Oracle and MySQL DBA Corporate Trainer and Database Security
Am I the only one worried about that line, then?
--
Unhappiness is discouraged and will be corrected with kitten pictures.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
On 8/29/2014 5:51 AM, Johan De Meersman wrote:
Senior Oracle and MySQL DBA Corporate Trainer and Database Security
Am I the only one worried about that line, then?
yes.
I welcome help from anyone willing. Expertise and willingness
both are important.
--bill
--
MySQL General Mailing
Hello Geetanjali,
On 8/26/2014 1:11 AM, geetanjali mehra wrote:
Hello to all,
I want to know whether my innodb index is fragemented. Is it possible to
know?
Best Regards,
Geetanjali Mehra
Senior Oracle and MySQL DBA Corporate Trainer and Database Security
Specialist
Just like every other
Hello to all,
I want to know whether my innodb index is fragemented. Is it possible to
know?
Best Regards,
Geetanjali Mehra
Senior Oracle and MySQL DBA Corporate Trainer and Database Security
Specialist
Hi,
i've been already reading the documentation the whole day, but still confused
and unsure what to do.
We have two databases which are important for our work. So both are stored
hourly. Now I recognized that each database has a mixture of MyISAM- and
InnoDB-tables. A backup of this mix does
- and
InnoDB-tables. A backup of this mix does not seem to be easy. Until now it
was dumped using mysqldump --opt -u root --databases mausdb What I
understand until now is that --opt is not necessary because it is default. It
includes, among others, --lock-tables which is senseful
XTrabackup can handle both InnoDB and MyISAM in
a consistent way while minimizing lock time on
MyISAM tables ...
http://www.percona.com/doc/percona-xtrabackup/2.1/
--
Hartmut Holzgraefe, Principal Support Engineer (EMEA)
SkySQL - The MariaDB Company | http://www.skysql.com/
--
MySQL General
Hi,
I want to access data from an InnoDB table. I know that I can do this using
the corresponding handler and ha_rnd_next() or ha_index_next().
My problem is that the original MySQL code is outperforming my
implementation even on simple projection queries, even though I use the same
functions
Hi Johan,
Thanks for your reply. Theorically the fragmented tables not offer the best
performance to the InnoDB engine, that's correct or not?
I don't know if is a problem or not, is a doubt/question for me. I'm not
sure if is an atypical behaviour.
Thanks in advance.
Regards,
Antonio.
*please* don't use reply-all on mailing-lists
the list by definition distributes your message
Am 30.06.2014 13:14, schrieb Antonio Fernández Pérez:
Thanks for your reply. Theorically the fragmented tables not offer the best
performance to the InnoDB engine,
that's correct or not?
practically
Hi Andre,
Thanks for your reply. I have checked the link and my configuration.
Innodb_file_per_table is enabled and in data directory appears a set of
files by each table.
Any ideas?
Thanks in advance.
Regards,
Antonio.
Am 27.06.2014 09:48, schrieb Antonio Fernández Pérez:
Thanks for your reply. I have checked the link and my configuration.
Innodb_file_per_table is enabled and in data directory appears a set of
files by each table.
Any ideas?
ideas for what?
* which files don't get shrinked (ls -lha)
*
Hi Reindl,
Thanks for your attention.
Following the previous mail, I have checked my MySQL's configuration and
innodb_file_per_table is enabled so, I think that this parameter not
affects directly to fragmented tables in InnoDB (In this case).
I would like to know, if is possible, why after
in InnoDB (In this case).
I would like to know, if is possible, why after execute an analyze table
command on some fragmented table, after that, appears fragmented again.
Regards,
Antonio.
InnoDB operates by storing multiple rows on pages. Each page is 16K.
Of that 1K is reserved for metadata
- Original Message -
From: Antonio Fernández Pérez antoniofernan...@fabergames.com
Subject: Re: Optimizing InnoDB tables
I would like to know, if is possible, why after execute an analyze table
command on some fragmented table, after that, appears fragmented again.
Simple question
Hi again,
I have enabled innodb_file_per_table (Its value is on).
I don't have clear what I should to do ...
Thanks in advance.
Regards,
Antonio.
- Original Message -
From: Antonio Fernández Pérez antoniofernan...@fabergames.com
Subject: Re: Optimizing InnoDB tables
I have enabled innodb_file_per_table (Its value is on).
I don't have clear what I should to do ...
Then all new tables will be created in their own tablespace now
Have a look at this:
https://rtcamp.com/tutorials/mysql/enable-innodb-file-per-table/
--
Andre Matos
andrema...@mineirinho.org
On Jun 25, 2014, at 2:22 AM, Antonio Fernández Pérez
antoniofernan...@fabergames.com wrote:
Hi again,
I have enabled innodb_file_per_table (Its value is on).
I
Hi list,
I was trying to optimize the InnoDB tables. I have executed the next query
to detect what are the fragmented tables.
SELECT TABLE_SCHEMA,TABLE_NAME
FROM TABLES WHERE TABLE_SCHEMA NOT IN (information_schema,mysql) AND
Data_free 0
After that, I have seen that there are 49 fragmented
Hi Antonio, como esta?
What's the mysql version you're running? Have you tried to ALTER TABLE x
ENGINE=InnoDB?
-- WB, MySQL Oracle ACE
Em 24/06/2014, às 08:03, Antonio Fernández Pérez
antoniofernan...@fabergroup.es escreveu:
Hi list,
I was trying to optimize the InnoDB tables. I have
Hi Wagner,
I'm running
MySQL Percona Server 5.5.30 64Bits. No, I don't have tried to execute
ALTER TABLE (Analyze with InnoDB tables do that, or not?).
Thanks in advance.
Regards,
Antonio.
Hello Antonio,
On 6/24/2014 7:03 AM, Antonio Fernández Pérez wrote:
Hi list,
I was trying to optimize the InnoDB tables. I have executed the next query
to detect what are the fragmented tables.
SELECT TABLE_SCHEMA,TABLE_NAME
FROM TABLES WHERE TABLE_SCHEMA NOT IN (information_schema,mysql
Am 24.06.2014 21:07, schrieb shawn l.green:
It makes a huge difference if the tables you are trying to optimize have
their own tablespace files or if they live
inside the common tablespace.
http://dev.mysql.com/doc/refman/5.5/en/innodb-parameters.html#sysvar_innodb_file_per_table
which
/innodb-parameters.html#sysvar_innodb_file_per_table
which is the most stupid default in case of innodb and only survivable
without a lot of work for people who realize that *before* start
operations and enable innodb_file_per_table from the very begin
having defaults which can't be changed later
2014-05-15 14:26 GMT+02:00 Antonio Fernández Pérez
antoniofernan...@fabergroup.es:
Hi,
I have in my server database some tables that are too much big and produce
some slow query, even with correct indexes created.
For my application, it's necessary to have all the data because we
- Original Message -
From: Manuel Arostegui man...@tuenti.com
Subject: Re: Big innodb tables, how can I work with them?
noSQL/table sharding/partitioning/archiving.
I keep wondering how people believe that NoSQL solutions magically don't need
RAM to work. Nearly all of them slow
2014-05-19 11:49 GMT+02:00 Johan De Meersman vegiv...@tuxera.be:
- Original Message -
From: Manuel Arostegui man...@tuenti.com
Subject: Re: Big innodb tables, how can I work with them?
noSQL/table sharding/partitioning/archiving.
I keep wondering how people believe that NoSQL
What kind of queries is this table serving? 8GB is not a huge amount of
data at all and IMO it's not enough to warrant sharding.
On Thu, May 15, 2014 at 1:26 PM, Antonio Fernández Pérez
antoniofernan...@fabergroup.es wrote:
Hi,
I have in my server database some tables that are too
Hi,
Thanks for your replies.
In our case, we can't implement NOSQL solution. Thats requires modify/check
all our application and all services (Including FreeRADIUS that I'm not
sure if it's compatible).
Andrew, I have heard about people that has a lot of data, more than me. I
know that MySQL
Hi,
I have in my server database some tables that are too much big and produce
some slow query, even with correct indexes created.
For my application, it's necessary to have all the data because we make an
authentication process with RADIUS users (AAA protocol) to determine if one
user can
Am 15.05.2014 14:26, schrieb Antonio Fernández Pérez:
I have in my server database some tables that are too much big and produce
some slow query, even with correct indexes created.
For my application, it's necessary to have all the data because we make an
authentication process with RADIUS
Hey Brad. What version are you using? My immediate thought is to check if
innodb_stats_on_metadata is off. If it is on, switch off and check your
timings again.
Regards
On 17 Mar 2014 04:40, Brad Heller b...@cloudability.com wrote:
Hey all,
I'm trying to figure out how InnoDB executes a SHOW
Hey Andrew,
I'm on 5.5.27. Good thought. Just flipped that setting off and getting the
same results. It pretty clearly seems to be InnoDB: If I create a HEAP
table, I don't get this behavior.
FWIW, I have (and always have had) innodb_file_per_table enabled, but my
tablespace file is still
Hi Brad,
I'm trying to figure out how InnoDB executes a SHOW CREATE TABLE query so I
can figure out what could possibly have made them suddenly slow down?
mysql SHOW CREATE TABLE `my_table`;
...
1 row in set (37.48 sec)
We tend to execute many of these statements concurrently, but it's
Hey Morgan,
That sounds right. Here's the process list (scrubbed) and the show engine
innodb status. Notice that all of the SHOW CREATE TABLE aren't for hte same
table, just got cleaned up that way.
https://gist.github.com/bradhe/c9f00eaf93ac588b8339
We have the defaults
Hi Brad,
That sounds right. Here's the process list (scrubbed) and the show engine
innodb status. Notice that all of the SHOW CREATE TABLE aren't for hte same
table, just got cleaned up that way.
It shouldn't matter if they are for the same or different - in 5.5 there is one
table open cache
, so it's probably just this machine/snapshot.
2. Stand up a snapshot of my existing machine, truncate the tables,
optimize the truncated tables, and run the test. I get the bad behavior!
Correct me if I'm wrong but it'd appear that there's just something
fundamentally broken this machines' InnoDB
just something
fundamentally broken this machines' InnoDB ibdata file/data dictionary? All
the contention comes out of the dictionary, but I'd expect the optimize to
re-write the dictionary entries...
If it's localized to the one machine, have you looked to ensure that
your physical disks are all
something
fundamentally broken this machines' InnoDB ibdata file/data dictionary? All
the contention comes out of the dictionary, but I'd expect the optimize to
re-write the dictionary entries…
InnoDB data dictionary is always stored in ibdata1 + there is MySQL data
dictionary stored in .frm
Hey all,
I'm trying to figure out how InnoDB executes a SHOW CREATE TABLE query so I
can figure out what could possibly have made them suddenly slow down?
mysql SHOW CREATE TABLE `my_table`;
...
1 row in set (37.48 sec)
We tend to execute many of these statements concurrently, but it's never
Had a system crash this morning and I can't seem to get mysql back up
and running. This is the error:
InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58
2013/11/21 Reindl Harald h.rei...@thelounge.net
Am 21.11.2013 13:51, schrieb Paul Halliday:
Had a system crash this morning and I can't seem to get mysql back up
and running. This is the error:
InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
18 19 20 21 22 23 24
at 9:46 AM, Manuel Arostegui man...@tuenti.com wrote:
2013/11/21 Reindl Harald h.rei...@thelounge.net
Am 21.11.2013 13:51, schrieb Paul Halliday:
Had a system crash this morning and I can't seem to get mysql back up
and running. This is the error:
InnoDB: Progress in percent: 1 2 3 4 5
What is the best way to backup your database. Which are the files that
I need to store on a usb disk
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
or hot copies are provided by tools that coordinate with the server
to synchronize the state of the InnoDB data to the moment the non-InnoDB
data has been captured. One example of this is MySQL Enterprise Backup.
http://dev.mysql.com/doc/mysql-enterprise-backup/3.9/en/index.html
Additional details
Am 21.11.2013 13:51, schrieb Paul Halliday:
Had a system crash this morning and I can't seem to get mysql back up
and running. This is the error:
InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
41 42 43
OOoopppsss! I do mean for recovery/continual backup. I will do it
manually, but basically get all the data on a USB disk and be able to
recover/move it (the data) on another machine, the same machine etc..
I hope I did not just open up a can of worms. We just went live and
this post gave me a
Am 21.11.2013 13:51, schrieb Paul Halliday:
Had a system crash this morning and I can't seem to get mysql back up
and running. This is the error:
InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
41
What's the MySQL error log have to say?
- Original Message -
From: Luis H. Forchesatto luisforchesa...@gmail.com
To: Johan De Meersman vegiv...@tuxera.be
Sent: Tuesday, 23 July, 2013 3:39:55 PM
Subject: Re: InnoDB problem.
Yep, I do backup of /home/mysql/ib* files too :D
What
-
From: Luis H. Forchesatto luisforchesa...@gmail.com
To: Johan De Meersman vegiv...@tuxera.be
Sent: Tuesday, 23 July, 2013 6:34:47 PM
Subject: Re: InnoDB problem.
The error log:
130723 10:04:23 [ERROR] Plugin 'InnoDB' init function returned error.
130723 10:04:23 [ERROR] Plugin 'InnoDB
Did you change innodb_log_file_size?
-Original Message-
From: Johan De Meersman [mailto:vegiv...@tuxera.be]
Sent: Tuesday, July 23, 2013 9:57 AM
To: Luis H. Forchesatto; mysql list
Subject: Re: InnoDB problem.
Eek.
No immediate clue here, but maybe someone else does - so please
-Original Message-
From: Johan De Meersman [mailto:vegiv...@tuxera.be]
Sent: Tuesday, July 23, 2013 9:57 AM
To: Luis H. Forchesatto; mysql list
Subject: Re: InnoDB problem.
Eek.
No immediate clue here, but maybe someone else does - so please keep the
list in CC at all times
: Re: InnoDB problem.
2013/7/23 Rick James rja...@yahoo-inc.commailto:rja...@yahoo-inc.com
Did you change innodb_log_file_size?
innodb_log_file_size error always appears in the logs...he only posted a few
lines of his log...but I guess (or I want to believe) he's gone through the
whole log
]
Sent: Tuesday, July 23, 2013 2:30 PM
Subject: #1341 [Com]: InnoDB ibdata1 never shrinks after data is removed
View this bug at: http://bugs.mysql.com/1341
Updated by: James Day
Reported by: Scott Ellsworth
Category: Server: InnoDB
Severity: S4
Greetings.
I've restored an MySQL backup from our MySQL server into another server.
The backup includes InnoDB tables. After the import, MySQL recognized the
innodb tables fine but when I try to do a check table ir returns that the
table doesn't exists.
Permission and owner of the table files
- Original Message -
From: Luis H. Forchesatto luisforchesa...@gmail.com
Subject: InnoDB problem.
Permission and owner of the table files (.frm files) are ok, since it
recognizes MyISAM tables (they have the same permission).
Oops. You should always read the fine manual.
You took
Well, the easy way to chunk the inserts is by use of limit. Here is what I
used for one of my projects:
Insert ignore into t1 (f1, f2, f3)
Select f1, f2, f3 from t2 limit 100, 100
Inserts 1M records at a time starting from 1M th record in t2 and you can keep
incrementing this offset as
Another technique to avoid impact to the source database is to create your
target as MyISAM, pump your records into that (no ACID overhead) and at the
end :
ALTER mytable engine=InnoDb
The alter can take awhile but it will impose no strain on the source server
at all.
On Tue, Jul 2, 2013
On Thu, Dec 1, 2011 at 5:54 PM, Miguel Angel Nieto miguel.ni...@percona.com
wrote:
You should check pt-archiver.
+1. It works very well for this type of job.
- Perrin
).
-Original Message-
From: Arjun [mailto:na...@yahoo.com]
Sent: Tuesday, July 02, 2013 12:48 AM
To: mysql@lists.mysql.com
Subject: Re: best way to copy a innodb table
Well, the easy way to chunk the inserts is by use of limit. Here is what I
used for one of my projects:
Insert
SHOW GLOBAL STATUS LIKE 'Innodb%';
Then do some math -- usually dividing by Uptime.
That will give you some insight in how hard the I/O is working, and how full
the buffer_pool is.
-Original Message-
From: Rafał Radecki [mailto:radecki.ra...@gmail.com]
Sent: Friday, June 21, 2013 4:59
Yeah, why not flush them to disk on a clean shutdown, and periodically before
that?
-Original Message-
From: Dotan Cohen [mailto:dotanco...@gmail.com]
Sent: Sunday, June 23, 2013 10:39 AM
To: mysql.
Subject: UPDATE_TIME for InnoDB in MySQL 5.7
The MySQL 5.7 changelog mentions
As I can see the changes in these values are use by percona cacti
monitoring templates to graph InnoDB I/O.
Can anyone answer the question finally? ;)
2013/6/21 Hartmut Holzgraefe hart...@skysql.com
On 21.06.2013 13:59, Rafał Radecki wrote:
Hi All.
I've searched but with no luck... what
Hello Rafał,
On 6/24/2013 4:26 AM, Rafał Radecki wrote:
As I can see the changes in these values are use by percona cacti
monitoring templates to graph InnoDB I/O.
Can anyone answer the question finally? ;)
2013/6/21 Hartmut Holzgraefe hart...@skysql.com
On 21.06.2013 13:59, Rafał Radecki
The MySQL 5.7 changelog mentions:
Beginning with MySQL 5.7.2, UPDATE_TIME displays a timestamp value
for the last UPDATE, INSERT, or DELETE performed on InnoDB tables.
Previously, UPDATE_TIME displayed a NULL value for InnoDB tables. For
MVCC, the timestamp value reflects the COMMIT time, which
information that should help you find out what is causing the crash.
130620 00:47:21 mysqld_safe Number of processes running now: 0
130620 00:47:21 mysqld_safe mysqld restarted
InnoDB: Error: tablespace size stored in header is 456832 pages, but
InnoDB: the sum of data file sizes is only 262080 pages
10:04:27 AM
Subject: Re: help: innodb database cannot recover
I removed ib_logfile0 and ib_logfile1 and restarted mysql with
innodb_force_recovery=1,
mysql keeps crashing and restart:
thd: 0x0
Attempting backtrace. You can use the following information to find
out
where mysqld died
the server started (or maybe last FLUSH call?)
and not very meaningful by themselves without knowing the time span
it took to come up to those counter values.
The per second values on the following line are much more interesting.
http://www.mysqlperformanceblog.com/2006/07/17/show-innodb-status-walk
Hi All.
I've searched but with no luck... what do exactly these variables mean:
1343928 OS file reads, 1085452262 OS file writes, 19976022 OS fsyncs
?
I am wondering if my innodb_buffer_pool setting is not to low. Does 'file
reads' show number of times innodb files have been read into memory
Hello,
I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
database directory) from one crashed machine to another.
I find that I cannot start database to get the database data any more.
I tried innodb_force_recovery=1
or innodb_force_recovery=4, it doesn't help.
Here
Am 20.06.2013 10:11, schrieb Peter:
130620 00:47:08 mysqld_safe Starting mysqld daemon with databases from
/var/lib/mysql
InnoDB: Error: tablespace size stored in header is 456832 pages, but
InnoDB: the sum of data file sizes is only 262080 pages
InnoDB: Cannot start InnoDB. The tail
2013/6/20 Peter one2001...@yahoo.com
Hello,
I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
database directory) from one crashed machine to another.
I find that I cannot start database to get the database data any more.
How did you copy the database?
Manuel
Am 20.06.2013 15:18, schrieb Peter:
2013/6/20 Peter one2001...@yahoo.com
Hello,
I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
database directory) from one crashed machine to another.
I find that I cannot start database to get the database data any more
2013/6/20 Peter one2001...@yahoo.com
Hello,
I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
database directory) from one crashed machine to another.
I find that I cannot start database to get the database data any more.
How did you copy the database?
Manuel
I copy
2013/6/20 Peter one2001...@yahoo.com
2013/6/20 Peter one2001...@yahoo.com
Hello,
I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
database directory) from one crashed machine to another.
I find that I cannot start database to get the database data any more.
How
Am 20.06.2013 15:18, schrieb Peter:
I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
database directory) from one crashed machine to another.
I find that I cannot start database to get the database data any more.
How did you copy the database?
Manuel
I copy
Am 20.06.2013 15:18, schrieb Peter:
I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
database directory) from one crashed machine to another.
I find that I cannot start database to get the database data any more.
How did you copy the database?
Manuel
I copy
1 - 100 of 5209 matches
Mail list logo
