Hi, i have a GPS tracking application, we use MySQL to store the data sent by devices, my application receives the data from the devices via TCP sockets and then launch a thread to insert/update the data in two innodb tables for each device (one table, eventdatalast, just to store the last report for every device and the other, eventdata, to store all the historical data). Due to the number of devices allready reporting to this server im doing between 15 and 20 inserts/updates per second. For my customers i have a java web application to track the units in a map, doing selects over eventdatalast every time i select a unit from a list.

We used MyISAM in the past but we changed to Innodb because with MyISAM i get my tables corrupted very often, and the table eventdata have 15M rows. Now with Innodb everything seems ok execept i get deadlocks in eventdatalast table.

The point of my post is, if someone is so kind, verify that the configuration of MySQL is the optimum for the type of load that the server has.

Server Configuration:
Windows 2003 Server Enterprise x64
Dual Xeon E5405(Harpertown) 2.00Ghz
8GB RAM
System HD 500GB SATA 7200RPM
HD for database 150GB Velociraptor SCSCI 10K RPM
MySQL Version: 5.5.16-log

my.ini
# CLIENT SECTION
[client]
port=3306

[mysql]
default-character-set=latin1

# SERVER SECTION
[mysqld]
port=3306

basedir="E:/MySQL/MySQL Server 5.5/"
datadir="E:/MySQL/MySQL Server 5.5/Data/"
character-set-server=latin1
default-storage-engine=INNODB

max_connections=3000
query_cache_size=0M
query_cache_type=0
table_cache=2048
tmp_table_size=1M
max_heap_table_size=1M
thread_cache_size=1500

#*** MyISAM Specific options

myisam_max_sort_file_size=100G
myisam_sort_buffer_size=20M
key_buffer_size=33554432
read_buffer_size=1048576
read_rnd_buffer_size=256K
delay_key_write=OFF
sort_buffer_size=64K


#*** INNODB Specific options ***
innodb_additional_mem_pool_size=20M
innodb_flush_log_at_trx_commit=2
innodb_log_buffer_size=8M
innodb_max_dirty_pages_pct=90
innodb_lock_wait_timeout = 300
innodb_support_xa=0
innodb_buffer_pool_size=5000M
innodb_log_file_size=1900M
innodb_file_per_table
innodb_open_files=2048
innodb_thread_concurrency=16
transaction_isolation = REPEATABLE-READ

autocommit=1
wait_timeout=60
connect_timeout=120
max_prepared_stmt_count=2000
max_allowed_packet = 1M
log_warnings=2
log_bin=CL-T078-110CN-bin
flush_time=0
binlog_format=row
innodb_locks_unsafe_for_binlog=1

Thanks in advance.

Version:

Xtrabacku 1.6
mysql 5.5.13
Linux 2.6.18-238.5.1.el5 #1 SMP Mon Feb 21 05:52:39 EST 2011 x86_64

Issue:

/mysql/xtrabackup/bin/innobackupex-1.5.1 --apply-log --ibbackup=/mysql/db01/xtrabackup-1.6/bin/xtrabackup_55 --defaults-file=/usr/local/mysql/data/my.cnf /usr/local/mysql/data/

InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 40743994, file name /mysql/binlogs/s2r2-log-bin.001072
InnoDB: Page directory corruption: infimum not pointed to
110927 13:31:50 InnoDB: Page dump in ascii and hex (16384 bytes):

InnoDB: End of page dump
110927 13:31:50 InnoDB: Page checksum 2207762029 (32bit_calc: 858448952), prior-to-4.0.14-form checksum 3632172825
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 437
InnoDB: Page lsn 437 177712030, low 4 bytes of lsn at page end 177712030
InnoDB: Page number (if stored to page already) 98306,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an update undo log page
InnoDB: Page directory corruption: supremum not pointed to
110927 13:31:50 InnoDB: Page dump in ascii and hex (16384 bytes):

InnoDB: End of page dump
110927 13:31:50 InnoDB: Page checksum 2207762029 (32bit_calc: 858448952), prior-to-4.0.14-form checksum 3632172825
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 437
InnoDB: Page lsn 437 177712030, low 4 bytes of lsn at page end 177712030
InnoDB: Page number (if stored to page already) 98306,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an update undo log page
innobackupex-1.5.1: Error:
innobackupex-1.5.1: ibbackup failed at /mysql/xtrabackup/bin/innobackupex-1.5.1 line 336.

Anyone having this issue?

Is there any option which can restore to the last valid LSN or before the corrupt log position?

I was able to start the db by doing following:

/mysql/xtrabackup/bin/innobackupex-1.5.1 --apply-log --redo-only --ibbackup=/mysql/db01/xtrabackup-1.6/bin/xtrabackup_55 --defaults-file=/usr/local/mysql/data/my.cnf /usr/local/mysql/data/

followed by the following:

/mysql/xtrabackup/bin/innobackupex-1.5.1 --apply-log --ibbackup=/mysql/db01/xtrabackup-1.6/bin/xtrabackup_55 --defaults-file=/usr/local/mysql/data/my.cnf /usr/local/mysql/data/


Any issue in doing the above? It does give me the page dump but on the same hand i was able to get my all binlog files and i was able to start the db.

I will highly appreciate if anyone can assist me in this issue.

Best Regards,

Hello,

The following InnoDB crash caused the procesor to go 100%.
Can someone help me with this issue?

111004 10:26:05 [Note] /usr/local/mysql/bin/mysqld: Normal shutdown

111004 10:26:07 [Warning] /usr/local/mysql/bin/mysqld: Forcing close of thread 45944 user: 'user1'
..
111004 10:26:07 [Warning] /usr/local/mysql/bin/mysqld: Forcing close of thread 23534 user: 'user2'

111004 10:26:55 mysqld started
111004 10:27:04 [Warning] option 'thread_stack': unsigned value 126976 adjusted to 131072
111004 10:27:04 [Warning] option 'query_cache_limit': unsigned value 12623879631451193344 adjusted to 4294967295
111004 10:27:04 [Warning] /usr/local/mysql/bin/mysqld: ignoring option '--character-set-client-handshake' due to invalid value 'utf8'
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
111004 10:27:10 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: 10 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 10 row operations to undo
InnoDB: Trx id counter is 0 826564864
111004 10:36:34 InnoDB: Error: table 'tmp/#sql1d9c_13f0a_7'
InnoDB: in InnoDB data dictionary has tablespace id 586068,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sql1d9c_13f0a_8'
InnoDB: in InnoDB data dictionary has tablespace id 586069,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sql287c_64c99_16'
InnoDB: in InnoDB data dictionary has tablespace id 806682,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sql287c_64c99_17'
InnoDB: in InnoDB data dictionary has tablespace id 806683,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sql287c_64d8a_2'
InnoDB: in InnoDB data dictionary has tablespace id 806692,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sql287c_64d8a_3'
InnoDB: in InnoDB data dictionary has tablespace id 806693,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sql3752_94589_1a'
InnoDB: in InnoDB data dictionary has tablespace id 372747,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sql9f0_cd125_14'
InnoDB: in InnoDB data dictionary has tablespace id 689944,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sql9f0_cd125_15'
InnoDB: in InnoDB data dictionary has tablespace id 689945,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sql9f0_cd79a_14'
InnoDB: in InnoDB data dictionary has tablespace id 689925,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sql9f0_cd79a_15'
InnoDB: in InnoDB data dictionary has tablespace id 689926,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sqla19_29e26_c'
InnoDB: in InnoDB data dictionary has tablespace id 699129,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sqla19_29e26_d'
InnoDB: in InnoDB data dictionary has tablespace id 699130,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sqla19_29f93_6'
InnoDB: in InnoDB data dictionary has tablespace id 699114,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sqla19_29f93_7'
InnoDB: in InnoDB data dictionary has tablespace id 699115,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sqla31_afca_0'
InnoDB: in InnoDB data dictionary has tablespace id 2456776,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sqla31_b26e_0'
InnoDB: in InnoDB data dictionary has tablespace id 2456778,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sqla31_b284_0'
InnoDB: in InnoDB data dictionary has tablespace id 2456777,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sqla31_b309_0'
InnoDB: in InnoDB data dictionary has tablespace id 2456779,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sqla31_b332_0'
InnoDB: in InnoDB data dictionary has tablespace id 2456780,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sqla31_b369_0'
InnoDB: in InnoDB data dictionary has tablespace id 2456781,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:34 InnoDB: Error: table 'tmp/#sqlb13_3ffd1_41'
InnoDB: in InnoDB data dictionary has tablespace id 2138283,
InnoDB: but tablespace with that id or name does not exist. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
InnoDB: table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
InnoDB: Last MySQL binlog file position 0 30896936, file name ./mysql-bin.000576
InnoDB: Starting in background the rollback of uncommitted transactions
111004 10:36:34 InnoDB: Rolling back trx with id 0 826564370, 1 rows to undo
111004 10:36:34 InnoDB: error: space object of table tmp/#sqla31_b369_0,
InnoDB: space id 2456781 did not exist in memory. Retrying an open.
111004 10:36:34 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
111004 10:36:34 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqla31_b369_0.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:36:35 InnoDB: Started; log sequence number 68 780960535
111004 10:36:35 [Note] Recovering after a crash using mysql-bin

InnoDB: Rolling back of trx id 0 826564370 completed
111004 10:36:35 InnoDB: Rolling back trx with id 0 826564331, 1 rows to undo

InnoDB: Rolling back of trx id 0 826564331 completed
111004 10:36:36 InnoDB: Rolling back trx with id 0 826564279, 1 rows to undo

InnoDB: Rolling back of trx id 0 826564279 completed
111004 10:36:39 InnoDB: Rolling back trx with id 0 826564275, 1 rows to undo
111004 10:36:39 InnoDB: error: space object of table tmp/#sqla31_b332_0,
InnoDB: space id 2456780 did not exist in memory. Retrying an open.
111004 10:36:39 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
111004 10:36:39 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqla31_b332_0.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.

InnoDB: Rolling back of trx id 0 826564275 completed
111004 10:36:40 InnoDB: Rolling back trx with id 0 826564229, 1 rows to undo
111004 10:36:40 InnoDB: error: space object of table tmp/#sqla31_b309_0,
InnoDB: space id 2456779 did not exist in memory. Retrying an open.
111004 10:36:40 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
111004 10:36:40 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqla31_b309_0.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.

InnoDB: Rolling back of trx id 0 826564229 completed
111004 10:36:40 InnoDB: Rolling back trx with id 0 826564209, 1 rows to undo
111004 10:36:40 InnoDB: error: space object of table tmp/#sqla31_b26e_0,
InnoDB: space id 2456778 did not exist in memory. Retrying an open.
111004 10:36:40 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
111004 10:36:40 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqla31_b26e_0.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.

InnoDB: Rolling back of trx id 0 826564209 completed
111004 10:36:40 InnoDB: Rolling back trx with id 0 826563812, 1 rows to undo
111004 10:36:40 InnoDB: error: space object of table tmp/#sqla31_b284_0,
InnoDB: space id 2456777 did not exist in memory. Retrying an open.
111004 10:36:40 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
111004 10:36:40 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqla31_b284_0.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.

InnoDB: Rolling back of trx id 0 826563812 completed
111004 10:36:40 InnoDB: Rolling back trx with id 0 826563618, 1 rows to undo

InnoDB: Rolling back of trx id 0 826563618 completed
111004 10:36:42 InnoDB: Rolling back trx with id 0 826563604, 1 rows to undo

InnoDB: Rolling back of trx id 0 826563604 completed
111004 10:36:43 InnoDB: Rolling back trx with id 0 826563602, 1 rows to undo
111004 10:36:43 InnoDB: error: space object of table tmp/#sqla31_afca_0,
InnoDB: space id 2456776 did not exist in memory. Retrying an open.
111004 10:36:43 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
111004 10:36:43 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqla31_afca_0.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.

InnoDB: Rolling back of trx id 0 826563602 completed
111004 10:36:44 InnoDB: Rollback of non-prepared transactions completed
111004 10:36:44 [Note] Starting crash recovery...
111004 10:36:44 [Note] Crash recovery finished.
111004 10:36:47 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=netlogiq-mysql-relay-bin' to avoid this problem.
111004 10:36:48 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.0.77-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
111004 10:37:15 [Note] /usr/local/mysql/bin/mysqld: Normal shutdown

111004 10:37:17 InnoDB: Starting shutdown...
111004 10:37:19 InnoDB: Shutdown completed; log sequence number 68 780961826
111004 10:37:19 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete

111004 10:37:19 mysqld ended

111004 10:38:19 mysqld started
111004 10:38:23 [Warning] option 'thread_stack': unsigned value 126976 adjusted to 131072
111004 10:38:23 [Warning] option 'query_cache_limit': unsigned value 12623879631451193344 adjusted to 4294967295
111004 10:38:23 [Warning] /usr/local/mysql/bin/mysqld: ignoring option '--character-set-client-handshake' due to invalid value 'utf8'
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sql1d9c_13f0a_7.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sql1d9c_13f0a_8.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sql287c_64c99_16.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sql287c_64c99_17.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sql287c_64d8a_2.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sql287c_64d8a_3.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sql3752_94589_1a.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sql9f0_cd125_14.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sql9f0_cd125_15.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sql9f0_cd79a_14.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sql9f0_cd79a_15.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqla19_29e26_c.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqla19_29e26_d.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqla19_29f93_6.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqla19_29f93_7.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqla31_afca_0.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqla31_b26e_0.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqla31_b284_0.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqla31_b309_0.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqla31_b332_0.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqla31_b369_0.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:39:56 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
111004 10:39:56 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sqlb13_3ffd1_41.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html
InnoDB: for how to resolve the issue.
111004 10:40:00 InnoDB: Started; log sequence number 68 780961826
111004 10:40:03 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=netlogiq-mysql-relay-bin' to avoid this problem.
111004 10:40:03 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.0.77-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)

Hi!

I have following configuration set in my.cnf (MySQL version 5.5.16):

[mysqld]
# General settings
datadir=/opt/mysql
# InnoDB settings
innodb_data_home_dir=/opt/mysql/ibdata
innodb_data_file_path=ibdata01:50M:autoextend:max:5G
innodb_autoextend_increment=10M
innodb_log_group_home_dir=/opt/mysql/ibdata/log
init_connect='SET autocommit=0'

Now I tried following:

Connect to database test two times (means with to different sessions), after that:

Session A:
create table auto_test (id int(10));
select count(1) from auto_test;
+----------+
| count(1) |
+----------+
| 0 |
+----------+

Session B:
select count(1) from auto_test;
+----------+
| count(1) |
+----------+
| 0 |
+----------+

Session A:
insert into auto_test values(1);
select count(1) from auto_test;
+----------+
| count(1) |
+----------+
| 1 |
+----------+


Session B:
select count(1) from auto_test;
+----------+
| count(1) |
+----------+
| 0 |
+----------+

So far so good, beacuse there was no commit in Session A until now.

Session A:
commit;

Session B:
select count(1) from auto_test;
+----------+
| count(1) |
+----------+
| 0 |
+----------+

And that is the thing I don't get, why does Session B don't see the inserted row? Now I make a new third session:

Session C:
select count(1) from auto_test;
+----------+
| count(1) |
+----------+
| 1 |
+----------+

Can somebody explain me why only new connections see the insertes row?

Hello,

We had compiled mysql 5.5.9 on our centos 5 64bit machine. Our DB size is around 56GB and is almost totally based on InnoDB. After we started up the server we automatically see the CPU raise to 100% when the DB is idle (No queries are being ran). After digging around we found what we believe is the reason for the high CPU usage and that is the following variables from the server's status:

Innodb_buffer_pool_read_requests Avg per sec 304,941.9
Innodb_data_read Avg per sec 63,451.7
Qcache_free_memory Avg per sec 29,715.8

We have no idea why the DB is so active, please advice.

Show Variables:

"Variable_name" "Value"
"auto_increment_increment" "1"
"auto_increment_offset" "1"
"autocommit" "ON"
"automatic_sp_privileges" "ON"
"back_log" "50"
"basedir" "/usr/local/mysql"
"big_tables" "OFF"
"binlog_cache_size" "32768"
"binlog_direct_non_transactional_updates" "OFF"
"binlog_format" "MIXED"
"binlog_stmt_cache_size" "32768"
"bulk_insert_buffer_size" "8388608"
"character_set_client" "utf8"
"character_set_connection" "utf8"
"character_set_database" "utf8"
"character_set_filesystem" "binary"
"character_set_results" "utf8"
"character_set_server" "latin1"
"character_set_system" "utf8"
"character_sets_dir" "/usr/local/mysql/share/charsets/"
"collation_connection" "utf8_general_ci"
"collation_database" "utf8_general_ci"
"collation_server" "latin1_swedish_ci"
"completion_type" "NO_CHAIN"
"concurrent_insert" "AUTO"
"connect_timeout" "10"
"datadir" "/usr/local/mysql/data/"
"date_format" "%Y-%m-%d"
"datetime_format" "%Y-%m-%d %H:%i:%s"
"default_storage_engine" "InnoDB"
"default_week_format" "0"
"delay_key_write" "ON"
"delayed_insert_limit" "100"
"delayed_insert_timeout" "300"
"delayed_queue_size" "1000"
"div_precision_increment" "4"
"engine_condition_pushdown" "ON"
"error_count" "0"
"event_scheduler" "OFF"
"expire_logs_days" "0"
"external_user" ""
"flush" "OFF"
"flush_time" "0"
"foreign_key_checks" "ON"
"ft_boolean_syntax" "+ -><()~*:""""&|"
"ft_max_word_len" "84"
"ft_min_word_len" "4"
"ft_query_expansion_limit" "20"
"ft_stopword_file" "(built-in)"
"general_log" "OFF"
"general_log_file" "/usr/local/mysql/data/DBLinux.log"
"group_concat_max_len" "1024"
"have_compress" "YES"
"have_crypt" "YES"
"have_csv" "YES"
"have_dynamic_loading" "YES"
"have_geometry" "YES"
"have_innodb" "YES"
"have_ndbcluster" "NO"
"have_openssl" "NO"
"have_partitioning" "YES"
"have_profiling" "YES"
"have_query_cache" "YES"
"have_rtree_keys" "YES"
"have_ssl" "NO"
"have_symlink" "YES"
"hostname" "DBLinux"
"identity" "0"
"ignore_builtin_innodb" "OFF"
"init_connect" ""
"init_file" ""
"init_slave" ""
"innodb_adaptive_flushing" "ON"
"innodb_adaptive_hash_index" "ON"
"innodb_additional_mem_pool_size" "20971520"
"innodb_autoextend_increment" "8"
"innodb_autoinc_lock_mode" "1"
"innodb_buffer_pool_instances" "1"
"innodb_buffer_pool_size" "792723456"
"innodb_change_buffering" "all"
"innodb_checksums" "ON"
"innodb_commit_concurrency" "0"
"innodb_concurrency_tickets" "500"
"innodb_data_file_path" "ibdata1:10M:autoextend"
"innodb_data_home_dir" "/usr/local/mysql/data"
"innodb_doublewrite" "ON"
"innodb_fast_shutdown" "1"
"innodb_file_format" "Antelope"
"innodb_file_format_check" "ON"
"innodb_file_format_max" "Antelope"
"innodb_file_per_table" "OFF"
"innodb_flush_log_at_trx_commit" "1"
"innodb_flush_method" ""
"innodb_force_recovery" "0"
"innodb_io_capacity" "200"
"innodb_lock_wait_timeout" "50"
"innodb_locks_unsafe_for_binlog" "OFF"
"innodb_log_buffer_size" "8388608"
"innodb_log_file_size" "188743680"
"innodb_log_files_in_group" "2"
"innodb_log_group_home_dir" "/usr/local/mysql/data"
"innodb_max_dirty_pages_pct" "75"
"innodb_max_purge_lag" "0"
"innodb_mirrored_log_groups" "1"
"innodb_old_blocks_pct" "37"
"innodb_old_blocks_time" "0"
"innodb_open_files" "300"
"innodb_purge_batch_size" "20"
"innodb_purge_threads" "0"
"innodb_read_ahead_threshold" "56"
"innodb_read_io_threads" "4"
"innodb_replication_delay" "0"
"innodb_rollback_on_timeout" "OFF"
"innodb_spin_wait_delay" "6"
"innodb_stats_on_metadata" "ON"
"innodb_stats_sample_pages" "8"
"innodb_strict_mode" "OFF"
"innodb_support_xa" "ON"
"innodb_sync_spin_loops" "30"
"innodb_table_locks" "ON"
"innodb_thread_concurrency" "20"
"innodb_thread_sleep_delay" "10000"
"innodb_use_native_aio" "OFF"
"innodb_use_sys_malloc" "ON"
"innodb_version" "1.1.5"
"innodb_write_io_threads" "4"
"insert_id" "0"
"interactive_timeout" "28800"
"join_buffer_size" "131072"
"keep_files_on_create" "OFF"
"key_buffer_size" "8388608"
"key_cache_age_threshold" "300"
"key_cache_block_size" "1024"
"key_cache_division_limit" "100"
"large_files_support" "ON"
"large_page_size" "0"
"large_pages" "OFF"
"last_insert_id" "0"
"lc_messages" "en_US"
"lc_messages_dir" "/usr/local/mysql/share/"
"lc_time_names" "en_US"
"license" "GPL"
"local_infile" "ON"
"lock_wait_timeout" "31536000"
"locked_in_memory" "OFF"
"log" "OFF"
"log_bin" "ON"
"log_bin_trust_function_creators" "OFF"
"log_error" "/usr/local/mysql/data/DBLinux.err"
"log_output" "FILE"
"log_queries_not_using_indexes" "OFF"
"log_slave_updates" "OFF"
"log_slow_queries" "OFF"
"log_warnings" "1"
"long_query_time" "10.000000"
"low_priority_updates" "OFF"
"lower_case_file_system" "OFF"
"lower_case_table_names" "0"
"max_allowed_packet" "1048576"
"max_binlog_cache_size" "18446744073709547520"
"max_binlog_size" "1073741824"
"max_binlog_stmt_cache_size" "18446744073709547520"
"max_connect_errors" "10"
"max_connections" "151"
"max_delayed_threads" "20"
"max_error_count" "64"
"max_heap_table_size" "16777216"
"max_insert_delayed_threads" "20"
"max_join_size" "18446744073709551615"
"max_length_for_sort_data" "1024"
"max_prepared_stmt_count" "16382"
"max_relay_log_size" "0"
"max_seeks_for_key" "18446744073709551615"
"max_sort_length" "1024"
"max_sp_recursion_depth" "0"
"max_tmp_tables" "32"
"max_user_connections" "0"
"max_write_lock_count" "18446744073709551615"
"min_examined_row_limit" "0"
"multi_range_count" "256"
"myisam_data_pointer_size" "6"
"myisam_max_sort_file_size" "9223372036853727232"
"myisam_mmap_size" "18446744073709551615"
"myisam_recover_options" "OFF"
"myisam_repair_threads" "1"
"myisam_sort_buffer_size" "67108864"
"myisam_stats_method" "nulls_unequal"
"myisam_use_mmap" "OFF"
"net_buffer_length" "16384"
"net_read_timeout" "30"
"net_retry_count" "10"
"net_write_timeout" "60"
"new" "OFF"
"old" "OFF"
"old_alter_table" "OFF"
"old_passwords" "OFF"
"open_files_limit" "1024"
"optimizer_prune_level" "1"
"optimizer_search_depth" "62"
"optimizer_switch" "index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,engine_condition_pushdown=on"
"performance_schema" "OFF"
"performance_schema_events_waits_history_long_size" "10000"
"performance_schema_events_waits_history_size" "10"
"performance_schema_max_cond_classes" "80"
"performance_schema_max_cond_instances" "1000"
"performance_schema_max_file_classes" "50"
"performance_schema_max_file_handles" "32768"
"performance_schema_max_file_instances" "10000"
"performance_schema_max_mutex_classes" "200"
"performance_schema_max_mutex_instances" "1000000"
"performance_schema_max_rwlock_classes" "30"
"performance_schema_max_rwlock_instances" "1000000"
"performance_schema_max_table_handles" "100000"
"performance_schema_max_table_instances" "50000"
"performance_schema_max_thread_classes" "50"
"performance_schema_max_thread_instances" "1000"
"pid_file" "/usr/local/mysql/data/DBLinux.pid"
"plugin_dir" "/usr/local/mysql/lib/plugin"
"port" "3306"
"preload_buffer_size" "32768"
"profiling" "OFF"
"profiling_history_size" "15"
"protocol_version" "10"
"proxy_user" ""
"pseudo_thread_id" "1"
"query_alloc_block_size" "8192"
"query_cache_limit" "1048576"
"query_cache_min_res_unit" "4096"
"query_cache_size" "16777216"
"query_cache_type" "ON"
"query_cache_wlock_invalidate" "OFF"
"query_prealloc_size" "8192"
"rand_seed1" "0"
"rand_seed2" "0"
"range_alloc_block_size" "4096"
"read_buffer_size" "1048576"
"read_only" "OFF"
"read_rnd_buffer_size" "4194304"
"relay_log" ""
"relay_log_index" ""
"relay_log_info_file" "relay-log.info"
"relay_log_purge" "ON"
"relay_log_recovery" "OFF"
"relay_log_space_limit" "0"
"report_host" ""
"report_password" ""
"report_port" "3306"
"report_user" ""
"rpl_recovery_rank" "0"
"secure_auth" "OFF"
"secure_file_priv" ""
"server_id" "1"
"skip_external_locking" "ON"
"skip_name_resolve" "OFF"
"skip_networking" "OFF"
"skip_show_database" "OFF"
"slave_compressed_protocol" "OFF"
"slave_exec_mode" "STRICT"
"slave_load_tmpdir" "/tmp"
"slave_net_timeout" "3600"
"slave_skip_errors" "OFF"
"slave_transaction_retries" "10"
"slave_type_conversions" ""
"slow_launch_time" "2"
"slow_query_log" "OFF"
"slow_query_log_file" "/usr/local/mysql/data/DBLinux-slow.log"
"socket" "/tmp/mysql.sock"
"sort_buffer_size" "1048576"
"sql_auto_is_null" "OFF"
"sql_big_selects" "ON"
"sql_big_tables" "OFF"
"sql_buffer_result" "OFF"
"sql_log_bin" "ON"
"sql_log_off" "OFF"
"sql_low_priority_updates" "OFF"
"sql_max_join_size" "18446744073709551615"
"sql_mode" ""
"sql_notes" "ON"
"sql_quote_show_create" "ON"
"sql_safe_updates" "OFF"
"sql_select_limit" "18446744073709551615"
"sql_slave_skip_counter" "0"
"sql_warnings" "OFF"
"ssl_ca" ""
"ssl_capath" ""
"ssl_cert" ""
"ssl_cipher" ""
"ssl_key" ""
"storage_engine" "InnoDB"
"sync_binlog" "0"
"sync_frm" "ON"
"sync_master_info" "0"
"sync_relay_log" "0"
"sync_relay_log_info" "0"
"system_time_zone" "EDT"
"table_definition_cache" "400"
"table_open_cache" "256"
"thread_cache_size" "20"
"thread_concurrency" "4"
"thread_handling" "one-thread-per-connection"
"thread_stack" "262144"
"time_format" "%H:%i:%s"
"time_zone" "SYSTEM"
"timed_mutexes" "OFF"
"timestamp" "1318192143"
"tmp_table_size" "16777216"
"tmpdir" "/tmp"
"transaction_alloc_block_size" "8192"
"transaction_prealloc_size" "4096"
"tx_isolation" "REPEATABLE-READ"
"unique_checks" "ON"
"updatable_views_with_limit" "YES"
"version" "5.5.9-log"
"version_comment" "Source distribution"
"version_compile_machine" "x86_64"
"version_compile_os" "Linux"
"wait_timeout" "28800"
"warning_count" "0"

Thanks.

HI All,

I have requirement where i want to create mysql database for end user for their application. But with that i also want to restrict db size beyond which user can not store any further data. So for each end user database i would like to store say 80 MB of space. I searched for this but i only got sql query using which we can find the size of database but not how to set dbsize.

Please reply if any one knows the answer.

Regards,
Ashok Naidu

What does the fields in the SHOW TABLE STATUS refer to when the table is an InnoDB table.
Specifically the following fields
Avg_row_length: 94
Data_length: 409600
Max_data_length: 0
Index_length: 0

I've experienced deadlock after updating the code. I checked the innodb status and noticed transaction 2 is waiting for the same lock which it already had. Why is that? The update sql in txn 2 is using the primay key. The other point is why txn 1 is terminated instead? It is just waiting for S-lock and it is not holding any lock itslef. It looks to me txn 2 is deadlocked with itself and has nothing to do with txn 1.

This is innodb status:

TRANSACTION 0 273782284, ACTIVE 18 sec, process no 3333, OS thread id 1101826368 starting index read
mysql tables in use 3, locked 3
LOCK WAIT 53 lock struct(s), heap size 14320
MySQL thread id 11662, query id 137990824 localhost 127.0.0.1 hrs Sending data
create table prog_1318503580550 select r.id, r.duration, r.type, s.pay_weekend, r.website_grp_id, r.date, convert_tz(r.date, '+0:0', '+8:0') as kl_date from ratingrecord r, websitegroup w, urlsource s where r.website_grp_id = w.id and w.source_id = s.id and r.user_id=536870920 and ((r.date>= '2011-10-12 16:00:00' and r.date <'2011-10-13 16:00:00'))
*** (1) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 105 page no 79829 n bits 248 index `PRIMARY` of table `hrs/websitegroup` trx id 0 273782284 lock mode S locks rec but not gap waiting
Record lock, heap no 68 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d4597; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d322f; asc -2/;; 3: len 1; hex 00; asc ;; 4: len 17; hex 6d796d696e69737472796170702e636f6d; asc myministryapp.com;; 5: len 13; hex 6d796d696e6973747279617070; asc myministryapp;; 6: len 3; hex 636f6d; asc com;; 7: len 4; hex 4e972700; asc N ' ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 0000000a; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d1a; asc 0 = ;; 16: len 4; hex 4e70ecfa; asc Np ;; 17: len 1; hex 01; asc ;;

*** (2) TRANSACTION:
TRANSACTION 0 273780557, ACTIVE 117 sec, process no 3333, OS thread id 1102092608 starting index read, thread declared inside InnoDB 500
mysql tables in use 1, locked 1
5 lock struct(s), heap size 1216, undo log entries 26
MySQL thread id 18336, query id 138053895 localhost 127.0.0.1 hrs Updating
update websitegroup set date='2011-10-13 10:59:58', created_date='2011-09-14 11:05:44', type=0, state=4, site_key='ideayouthforum.org', dom='ideayouthforum', tld='org', qa=0, updated_master=1, cache_proc=3, source_id=6, license_type=2, lang_id=10, location_id=3, rating_rec_id=816921876 where id=17646987
*** (2) HOLDS THE LOCK(S):
RECORD LOCKS space id 105 page no 79829 n bits 248 index `PRIMARY` of table `hrs/websitegroup` trx id 0 273780557 lock_mode X locks rec but not gap
Record lock, heap no 61 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d4582; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d2ec3; asc -. ;; 3: len 1; hex 00; asc ;; 4: len 17; hex 6d6565737465726d6174686965752e6265; asc meestermathieu.be;; 5: len 14; hex 6d6565737465726d617468696575; asc meestermathieu;; 6: len 2; hex 6265; asc be;; 7: len 4; hex 4e9726d4; asc N & ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 00000009; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d41; asc 0 =A;; 16: len 4; hex 4e70ecf7; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 62 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d4585; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d30ce; asc -0 ;; 3: len 1; hex 00; asc ;; 4: len 20; hex 6c616d6172636f6d6d756e6963617469652e6e6c; asc lamarcommunicatie.nl;; 5: len 17; hex 6c616d6172636f6d6d756e696361746965; asc lamarcommunicatie;; 6: len 2; hex 6e6c; asc nl;; 7: len 4; hex 4e9726ef; asc N & ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 00000009; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d32; asc 0 =2;; 16: len 4; hex 4e70ecf7; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 63 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d4588; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d32db; asc -2 ;; 3: len 1; hex 00; asc ;; 4: len 18; hex 6b696e642d656e2d766f6564696e672e6e6c; asc kind-en-voeding.nl;; 5: len 15; hex 6b696e642d656e2d766f6564696e67; asc kind-en-voeding;; 6: len 2; hex 6e6c; asc nl;; 7: len 4; hex 4e972709; asc N ' ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 00000009; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d35; asc 0 =5;; 16: len 4; hex 4e70ecf8; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 65 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d458e; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d2bf0; asc -+ ;; 3: len 1; hex 00; asc ;; 4: len 17; hex 696e76656e742d73797374656d732e6e6c; asc invent-systems.nl;; 5: len 14; hex 696e76656e742d73797374656d73; asc invent-systems;; 6: len 2; hex 6e6c; asc nl;; 7: len 4; hex 4e9726b2; asc N & ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 00000009; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d38; asc 0 =8;; 16: len 4; hex 4e70ecf9; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 66 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d4591; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d2e15; asc -. ;; 3: len 1; hex 00; asc ;; 4: len 20; hex 6f6e6c696e65706f6b65727370656c656e2e6265; asc onlinepokerspelen.be;; 5: len 17; hex 6f6e6c696e65706f6b65727370656c656e; asc onlinepokerspelen;; 6: len 2; hex 6265; asc be;; 7: len 4; hex 4e9726cb; asc N & ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 0000000a; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d1d; asc 0 = ;; 16: len 4; hex 4e70ecf9; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 67 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d4594; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d3022; asc -0";; 3: len 1; hex 00; asc ;; 4: len 16; hex 6c69616d6b656c6c797765622e636f6d; asc liamkellyweb.com;; 5: len 12; hex 6c69616d6b656c6c79776562; asc liamkellyweb;; 6: len 3; hex 636f6d; asc com;; 7: len 4; hex 4e9726e5; asc N & ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 0000000a; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d23; asc 0 =#;; 16: len 4; hex 4e70ecfa; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 68 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d4597; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d322f; asc -2/;; 3: len 1; hex 00; asc ;; 4: len 17; hex 6d796d696e69737472796170702e636f6d; asc myministryapp.com;; 5: len 13; hex 6d796d696e6973747279617070; asc myministryapp;; 6: len 3; hex 636f6d; asc com;; 7: len 4; hex 4e972700; asc N ' ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 0000000a; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d1a; asc 0 = ;; 16: len 4; hex 4e70ecfa; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 74 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d45a9; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d3441; asc -4A;; 3: len 1; hex 00; asc ;; 4: len 19; hex 676f677265656e626f6f7463616d702e636f6d; asc gogreenbootcamp.com;; 5: len 15; hex 676f677265656e626f6f7463616d70; asc gogreenbootcamp;; 6: len 3; hex 636f6d; asc com;; 7: len 4; hex 4e97271a; asc N ' ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 0000000a; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d26; asc 0 =&;; 16: len 4; hex 4e70ecfd; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 79 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d45b8; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d2b9a; asc -+ ;; 3: len 1; hex 00; asc ;; 4: len 15; hex 696e74657270726f746563742e6e6c; asc interprotect.nl;; 5: len 12; hex 696e74657270726f74656374; asc interprotect;; 6: len 2; hex 6e6c; asc nl;; 7: len 4; hex 4e9726ad; asc N & ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 00000009; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d3b; asc 0 =;;; 16: len 4; hex 4e70ed00; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 80 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d45bb; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d2d5d; asc --];; 3: len 1; hex 00; asc ;; 4: len 21; hex 696b77696c65656e7363686f6f6e687569732e6e6c; asc ikwileenschoonhuis.nl;; 5: len 18; hex 696b77696c65656e7363686f6f6e68756973; asc ikwileenschoonhuis;; 6: len 2; hex 6e6c; asc nl;; 7: len 4; hex 4e9726c3; asc N & ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 0000000a; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d2c; asc 0 =,;; 16: len 4; hex 4e70ed00; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 81 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d45be; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d2f72; asc -/r;; 3: len 1; hex 00; asc ;; 4: len 22; hex 6b756e73747370657572656e696e64657a616b2e6e6c; asc kunstspeurenindezak.nl;; 5: len 19; hex 6b756e73747370657572656e696e64657a616b; asc kunstspeurenindezak;; 6: len 2; hex 6e6c; asc nl;; 7: len 4; hex 4e9726dd; asc N & ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 00000009; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d44; asc 0 =D;; 16: len 4; hex 4e70ed01; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 82 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d45c1; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d3180; asc -1 ;; 3: len 1; hex 00; asc ;; 4: len 21; hex 6472756b6b6572696a76616e6b65756c656e2e6e6c; asc drukkerijvankeulen.nl;; 5: len 18; hex 6472756b6b6572696a76616e6b65756c656e; asc drukkerijvankeulen;; 6: len 2; hex 6e6c; asc nl;; 7: len 4; hex 4e9726f7; asc N & ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 00000009; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d3e; asc 0 =>;; 16: len 4; hex 4e70ed01; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 83 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d45c4; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d33e2; asc -3 ;; 3: len 1; hex 00; asc ;; 4: len 24; hex 6b756e6766757363686f6f6c616d7374657264616d2e6e6c; asc kungfuschoolamsterdam.nl;; 5: len 21; hex 6b756e6766757363686f6f6c616d7374657264616d; asc kungfuschoolamsterdam;; 6: len 2; hex 6e6c; asc nl;; 7: len 4; hex 4e972716; asc N ' ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 00000009; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d89; asc 0 = ;; 16: len 4; hex 4e70ed02; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 87 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d45d0; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d2d00; asc -- ;; 3: len 1; hex 00; asc ;; 4: len 22; hex 6275696a7a657665727a656b6572696e67656e2e6e6c; asc buijzeverzekeringen.nl;; 5: len 19; hex 6275696a7a657665727a656b6572696e67656e; asc buijzeverzekeringen;; 6: len 2; hex 6e6c; asc nl;; 7: len 4; hex 4e9726bf; asc N & ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 0000000a; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d71; asc 0 =q;; 16: len 4; hex 4e70ed04; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 88 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d45d3; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d2f1b; asc -/ ;; 3: len 1; hex 00; asc ;; 4: len 16; hex 76616e626f7572676f6e6469652e6575; asc vanbourgondie.eu;; 5: len 13; hex 76616e626f7572676f6e646965; asc vanbourgondie;; 6: len 2; hex 6575; asc eu;; 7: len 4; hex 4e9726d8; asc N & ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 00000009; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d8c; asc 0 = ;; 16: len 4; hex 4e70ed05; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 89 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d45d6; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d3129; asc -1);; 3: len 1; hex 00; asc ;; 4: len 16; hex 776572656c64696e6265656c642e6265; asc wereldinbeeld.be;; 5: len 13; hex 776572656c64696e6265656c64; asc wereldinbeeld;; 6: len 2; hex 6265; asc be;; 7: len 4; hex 4e9726f3; asc N & ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 00000009; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d8f; asc 0 = ;; 16: len 4; hex 4e70ed05; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 93 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d45e2; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d3334; asc -34;; 3: len 1; hex 00; asc ;; 4: len 16; hex 737461636b696e67636173682e636f6d; asc stackingcash.com;; 5: len 12; hex 737461636b696e6763617368; asc stackingcash;; 6: len 3; hex 636f6d; asc com;; 7: len 4; hex 4e97270d; asc N ' ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 0000000a; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d77; asc 0 =w;; 16: len 4; hex 4e70ed07; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 97 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d45ee; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d2c48; asc -,H;; 3: len 1; hex 00; asc ;; 4: len 16; hex 62656e6574746f6e7a656973742e6e6c; asc benettonzeist.nl;; 5: len 13; hex 62656e6574746f6e7a65697374; asc benettonzeist;; 6: len 2; hex 6e6c; asc nl;; 7: len 4; hex 4e9726b6; asc N & ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 00000009; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d95; asc 0 = ;; 16: len 4; hex 4e70ed09; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 99 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d45f4; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d3079; asc -0y;; 3: len 1; hex 00; asc ;; 4: len 14; hex 706c6173746963736f65702e6e6c; asc plasticsoep.nl;; 5: len 11; hex 706c6173746963736f6570; asc plasticsoep;; 6: len 2; hex 6e6c; asc nl;; 7: len 4; hex 4e9726e9; asc N & ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 00000009; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d92; asc 0 = ;; 16: len 4; hex 4e70ed0a; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 178 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d45f7; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d3287; asc -2 ;; 3: len 1; hex 00; asc ;; 4: len 13; hex 6f73647369676e61616c2e6e6c; asc osdsignaal.nl;; 5: len 10; hex 6f73647369676e61616c; asc osdsignaal;; 6: len 2; hex 6e6c; asc nl;; 7: len 4; hex 4e972704; asc N ' ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 00000009; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d9e; asc 0 = ;; 16: len 4; hex 4e70ed0b; asc Np ;; 17: len 1; hex 01; asc ;;

Record lock, heap no 179 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d45f1; asc E ;; 1: len 6; hex 000010518f4d; asc Q M;; 2: len 7; hex 000000002d2e70; asc -.p;; 3: len 1; hex 00; asc ;; 4: len 12; hex 73616e746f756368612e6e6c; asc santoucha.nl;; 5: len 9; hex 73616e746f75636861; asc santoucha;; 6: len 2; hex 6e6c; asc nl;; 7: len 4; hex 4e9726d0; asc N & ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 00000009; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13da1; asc 0 = ;; 16: len 4; hex 4e70ed0a; asc Np ;; 17: len 1; hex 01; asc ;;

*** (2) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 105 page no 79829 n bits 248 index `PRIMARY` of table `hrs/websitegroup` trx id 0 273780557 lock_mode X locks rec but not gap waiting
Record lock, heap no 64 PHYSICAL RECORD: n_fields 18; compact format; info bits 0
0: len 4; hex 010d458b; asc E ;; 1: len 6; hex 000010518120; asc Q ;; 2: len 7; hex 000000002d3537; asc -57;; 3: len 1; hex 00; asc ;; 4: len 18; hex 69646561796f757468666f72756d2e6f7267; asc ideayouthforum.org;; 5: len 14; hex 69646561796f757468666f72756d; asc ideayouthforum;; 6: len 3; hex 6f7267; asc org;; 7: len 4; hex 4e9725de; asc N % ;; 8: len 1; hex 04; asc ;; 9: len 4; hex 00000006; asc ;; 10: len 4; hex 00000003; asc ;; 11: len 4; hex 0000000a; asc ;; 12: len 4; hex 00000002; asc ;; 13: len 1; hex 03; asc ;; 14: len 1; hex 00; asc ;; 15: len 4; hex 30b13d14; asc 0 = ;; 16: len 4; hex 4e70ecf8; asc Np ;; 17: len 1; hex 00; asc ;;

*** WE ROLL BACK TRANSACTION (1)

I have a fairly large database (100G+) made up of several schemas with all tables running in the InnoDB engine, primarily so that we can take advantage of LVM snapshots for backups. I was recently asked if we should optimize our tables. Knowing that this would necessarily require some down time, I started looking for answers to a key question:

How do I really know when I need to optimize a table?

The best answer I found, so far, was in this forum. The indicator, in that case, was to look for tables that have more than 10% free space. Well, it turns out that none of my tables have that much free space. But, that doesn't take into account possible index issues that might cause performance problems.

So, I'm wondering, is free space really the only indicator? If not, what else can I be looking at to try to make that determination whether to optimize a given table?

Thanks,
Dave

East Carolina Pirates vs Memphis Tigers live,watch Nebraska game live online, watch ncaa game live online, East Carolina Pirates vs Memphis Tigers live online, East Carolina Pirates vs Memphis Tigers live on internet tv, East Carolina Pirates vs Memphis Tigers live webcast, Unlimited Free Live TV, East Carolina Pirates vs Memphis Tigers live sopcast, East Carolina Pirates vs Memphis Tigers live podcast, East Carolina Pirates vs Memphis Tigers live p2p streaming, East Carolina Pirates vs Memphis Tigers live streaming free, East Carolina Pirates vs Memphis Tigers live feed, East Carolina Pirates vs Memphis Tigers live coverage, East Carolina Pirates vs Memphis Tigers live telecast, East Carolina Pirates vs Memphis Tigers live broadcast, East Carolina Pirates vs Memphis Tigers live on pc, East Carolina Pirates vs Memphis Tigers live game, East Carolina Pirates vs Memphis Tigers live now, East Carolina Pirates vs Memphis Tigers live video, watch East Carolina Pirates vs Memphis Tigers live online free,where i can watch East Carolina Pirates vs Memphis Tigers live online, East Carolina Pirates vs Memphis Tigers live streaming online, East Carolina Pirates vs Memphis Tigers live on satellite tv,watch East Carolina Pirates vs Memphis Tigers live streaming, East Carolina Pirates vs Memphis Tigers live, East Carolina Pirates vs Memphis Tigers live, East Carolina Pirates vs Memphis Tigers live, East Carolina Pirates vs Memphis Tigers live, East Carolina Pirates vs Memphis Tigers live game,ncaa live,ncaa live online,ncaa 2011 live webcast,ncaa 2011 live podcast,ncaa 2011 live sopcast,ncaa 2011 schedule,ncaa 2011 live score

Chattanooga vs Nebraska live,watch Chattanooga game live online,watch ncaa game live online,Chattanooga vs Nebraska live online,Chattanooga vs Nebraska live on internet tv,Chattanooga vs Nebraska live webcast,Chattanooga vs Nebraska live sopcast,Chattanooga vs Nebraska live podcast,Chattanooga vs Nebraska live p2p streaming,Chattanooga vs Nebraska live streaming free,Chattanooga vs Nebraska live feed,Chattanooga vs Nebraska live coverage,Chattanooga vs Nebraska live telecast,Chattanooga vs Nebraska live broadcast,Chattanooga vs Nebraska live now,Chattanooga vs Nebraska live video,watch Chattanooga vs Nebraska live online free,where i can watch Chattanooga vs Nebraska live online,Chattanooga vs Nebraska live game,Chattanooga vs Nebraska live on pc,Chattanooga vs Nebraska live streaming online,Chattanooga vs Nebraska live on satellite tv,watch Chattanooga vs Nebraska live streaming,Chattanooga vs Nebraska live, Chattanooga vs Nebraska live,Chattanooga vs Nebraska live,ncaa live,ncaa live online,ncaa live webcast,Chattanooga vs Nebraska live,ncaa live podcast,ncaa live sopcast,ncaa schedule,ncaa live score,Unlimited Free Live TV

East Carolina Pirates vs Memphis Tigers live

██████████████████████████████████████████

From Google, Ask, Bing Survey, Over 90% people in USA, Europe and Rest of World are watching all NFL 2011/12 Football Games LIVE Online on these top sites.


██ http://NFL.Com-streams.tv (Personal Experience)

██ http://ESPN.Com-streams.tv


██ http://NFLfootballive.com (HD Quality) ██

(ESPN Presents: Live Broadcasting football on 14 channels live at a time)


100% Working, Hope this helps

http://www.warkoy.com


██████████████████████████████████████████


, East Carolina Pirates vs Memphis Tigers live online, East Carolina Pirates vs Memphis Tigers live feed, East Carolina Pirates vs Memphis Tigers live telecast, East Carolina Pirates vs Memphis Tigers live video, East Carolina Pirates vs Memphis Tigers live webcast, East Carolina Pirates vs Memphis Tigers live tv links, East Carolina Pirates vs Memphis Tigers live video links, East Carolina Pirates vs Memphis Tigers live on internet, East Carolina Pirates vs Memphis Tigers live p2p links, East Carolina Pirates vs Memphis Tigers live sopacst links, East Carolina Pirates vs Memphis Tigers live streaming, East Carolina Pirates vs Memphis Tigers live video streaming, East Carolina Pirates vs Memphis Tigers live stream online, East Carolina Pirates vs Memphis Tigers live feed video, East Carolina Pirates vs Memphis Tigers live p2p streaming,ncaa Preseason,ncaa Preseason live,ncaa Preseason match live,ncaa 2011 live,ncaa 2011 live online,ncaa 2011 live sopcast,ncaa 2011 live streaming,ncaa live,ncaa 2011 live online,ncaa live p2p links,ncaa live,ncaa live tv,ncaa live sopcast,ncaa live tv cast,ncaa live tv links

East Carolina Pirates vs Memphis Tigers LIVE STREAMING WHERE?
East Carolina Pirates vs Memphis Tigers LIVE STREAM TV LINK WHERE?
East Carolina Pirates vs Memphis Tigers LIVE STREAM FREE VIDEO BROADCAST WHERE?
East Carolina Pirates vs Memphis Tigers LIVE ONLINE WHERE?
East Carolina Pirates vs Memphis Tigers LIVE ON PC WHERE?
East Carolina Pirates vs Memphis Tigers LIVE FREE VIDEO TELECAST WHERE?
WATCH East Carolina Pirates vs Memphis Tigers LIVE STREAM TV CHANNEL WHERE?
East Carolina Pirates vs Memphis Tigers LIVE STREAM SOCCER WHERE?
East Carolina Pirates vs Memphis Tigers LIVE WHERE?
East Carolina Pirates vs Memphis Tigers WHERE?
East Carolina Pirates vs Memphis Tigers LIVE STREAMING WHERE?
East Carolina Pirates vs Memphis Tigers LIVE STREAM TV LINK WHERE?
East Carolina Pirates vs Memphis Tigers LIVE STREAM FREE VIDEO BROADCAST WHERE?
East Carolina Pirates vs Memphis Tigers LIVE ONLINE WHERE?
East Carolina Pirates vs Memphis Tigers LIVE ON PC WHERE?
East Carolina Pirates vs Memphis Tigers LIVE STREAMING WHERE?
East Carolina Pirates vs Memphis Tigers LIVE STREAM TV LINK WHERE?
East Carolina Pirates vs Memphis Tigers LIVE STREAM FREE VIDEO BROADCAST WHERE?
East Carolina Pirates vs Memphis Tigers LIVE ONLINE WHERE?
East Carolina Pirates vs Memphis Tigers LIVE ON PC WHERE?
East Carolina Pirates vs Memphis Tigers LIVE FREE VIDEO TELECAST WHERE?
WATCH East Carolina Pirates vs Memphis Tigers LIVE STREAM TV CHANNEL WHERE?
East Carolina Pirates vs Memphis Tigers LIVE STREAM SOCCER WHERE?
East Carolina Pirates vs Memphis Tigers LIVE WHERE?
East Carolina Pirates vs Memphis Tigers WHERE?

Hi,


Trying to understand the MySQL Server architecture. I couldn't understand the difference between the bin logs & Innodb/storage engine logs (transaction logs). A database in production has to have the logging turned on for backup and recovery purposes. Anyhow when i see the recovery methods in the MySQL, all they would say is restore a full backup and apply the Bin logs. There are parameters related to innodb_log_group_home_dir & innodb_log_arch_dir, which need to be turned on (both, if either one of it is turned on). I understand these logs are used for transactional purposes for the InnoDB engine.

My question is,

1) MySQL server logs the transactions in the BIN logs. That means the InnoDB engine transactions will be in the BIN logs as well right? So, what is the purpose of having InnoDB logs? Does MySQL log the transactions both in BIN & InnoDB logs? does that make it redundant?

2) In recovery purposes, we are going to roll forward using the BIN logs. Where do these InnoDB logs come in handy (except for logging transactions).

3) If we are not going to use the InnoDB logs, what is the purpose of having the innodb_log_arch_dir, where it archives the innodb logs.

Any info or direction to documentation links that could explain this would be helpful (don't link me to the dev.mysql reference links please, already have that).

Thanks,
Shiva

Is there any command to initiate a full checkpoint, force all dirty blocks in buffer pool to be written to the disk.

I have an insert statement something like the following:

insert into code_value (code_set,code_value,active_ind,display,display_key,updt_dt_tm)
values (1,1,1,"test2","TEST2",CURRENT_TIMESTAMP)
on duplicate key update
active_ind = 1,
display = "test2",
display_key = "TEST2",
updt_dt_tm = if(**WHAT GOES HERE**,CURRENT_TIMESTAMP,**WHAT GOES HERE**);

The primary keys of the table are code_set and code_value. So basically, it's supposed to work as follows:

Case 1: There is no row in the table where code_set = 1 and code_value = 1.

In this case, it will just insert the row, no problems.

Case 2: There is already a row in the table where code_set = 1 and code_value = 1, and one of active_ind, display, or display_key is different than the values that are trying to be inserted.

Here, we will update the existing row in the table, setting the updt_dt_tm column to CURRENT_TIMESTAMP, to reflect the fact that the row was actually updated.

Case 2: There is already a row in the table where code_set = 1 and code_value = 1, and none of active_ind, display, or display_key are different than the values that are trying to be inserted.

Here, we want to update the existing row in the table, but leave updt_dt_tm alone, because no true update has been done. That's where the IF() function comes in; I want to update the updt_dt_tm column only if one of the other columns is different than the values we're trying to insert.

Any ideas?

I have a table using InnoDB that has just over 11M rows. Constant inserts.

insert TabB select A from TabA limit 1 offset 7000000;

gives [Err] 1206 - The total number of locks exceeds the lock table size

insert TabB select A from TabA limit 1 offset 5000000;

works

select A from TabA limit 1 offset 7000000;

works

Changing the innodb_buffer_pool_size isn't viable at this time. What can I do?

Hi

This is regarding collection of Innodb health report at regular intervals.

From the documentation regarding enabling Innodb monitors, I can see "output generation does result in some performance decrement"
http://dev.mysql.com/doc/refman/5.5/en/innodb-monitors.html

Do you think there can be the same performance decrement if we don't enable the Innodb monitors (by not creating the monitor tables), and just get the output of SHOW ENGINE INNODB STATUS into a file at regular schedules.
The purpose is to have regular snapshot information which can be used for analysis and comparison later when required. Just like we have in oracle with snapshot and AWR reports.

Thanks

Hi All,

InnoDB now has a innodb_use_native_aio system variable that can be disabled at startup if there is a problem with the asynchronous I/O subsystem in the OS. This variable applies to Linux systems only, where the MySQL server now has a dependency on the libaio library.

How to disable that variable? In which file I have to modify the contents?
Or

If I want to modify the value of ‘innodb_use_native_aio’ where or in which file I have to change?

Thanks in Advance!!

Today a colleague ran an update on a large table:

mysql> show table status from auto like 'parts'\G
*************************** 1. row ***************************
           Name: parts
         Engine: InnoDB
        Version: 10
     Row_format: Compact
           Rows: 16209517
 Avg_row_length: 1374
    Data_length: 22272802816
Max_data_length: 0
   Index_length: 16715235328
      Data_free: 754974720
 Auto_increment: NULL
    Create_time: 2008-04-27 12:57:08
    Update_time: NULL
     Check_time: NULL
      Collation: latin1_swedish_ci
       Checksum: NULL
 Create_options:
        Comment: Parts Table
1 row in set (0.76 sec)

Server> ls -lh | grep parts.ibd
-rw-rw----   1 mysql    mysql        38G Oct 26 14:07 parts.ibd

The update was a simple one:

UPDATE parts
set
column = 'Y'

He asked me to kill his thread after about ~30 minutes. So I did. The query state then changed to Freeing Items. He ran the query without a where clause accidentally.

I tried desperately to clear the state so that other transactions could process more efficiently.

However, nothing I did brought the server back any more quickly. It took ~30 minutes more to complete whatever steps it was performing and return to normal operations.

The things I tried were;

* Disable the Query Cache and set the cache size to 0
* Flush Logs
* Reset Query Cache
* Flush Tables parts

I am wondering if folks have any insight as to a> what the server does when it is 'freeing up items' and b> how to achieve that more quickly?

As an aside, the flush tables was something I found online. That actually caused all of the queries to queue up until I killed my thread. I have now noticed that a single table should be 'flush table table_name' and not 'flush table'S' table_name' I am not sure if that would still try to flush all of the tables!

Thanks for any insight!!!

Shawn

what is the best way to convert one big ibdata file innodb and make the innodb database as per table innodb datafiles? I am looking for minimum downtime and very safe procedure

Watch @ http://jaimx.co.cc/?p=909

I'm sorry, but I'm new to this. I extracted MySQL and tried to start mysqld and got the following error, any help would be much appreciated:

111030 21:25:40 [Note] Plugin 'FEDERATED' is disabled.
111030 21:25:40 InnoDB: The InnoDB memory heap is disabled
111030 21:25:40 InnoDB: Mutexes and rw_locks use Windows interlocked func
111030 21:25:40 InnoDB: Compressed tables use zlib 1.2.3
111030 21:25:40 InnoDB: Initializing buffer pool, size = 128.0M
111030 21:25:40 InnoDB: Completed initialization of buffer pool
111030 21:25:40 InnoDB: highest supported file format is Barracuda.
111030 21:25:40 InnoDB: Waiting for the background threads to start
111030 21:25:41 InnoDB: 1.1.8 started; log sequence number 1595675
111030 21:25:41 [ERROR] Can't create IP socket: No such file or directory
111030 21:25:41 [ERROR] Aborting

111030 21:25:41 InnoDB: Starting shutdown...
111030 21:25:42 InnoDB: Shutdown completed; log sequence number 1595675