I work at a software company, and used as database Mysql 5.6
Problem: In recent days MYSQL has losing days of data, like a big rollback of datas in all tables, checking the MYSQL error log, only appears the follows messages: "database was not shutdown normally" and "[Note] InnoDB: The log sequence numbers 1181074230 and 1181074230 in ibdata files do not match the log sequence number 1181075227 in the ib_logfiles ".
These messages could be related to the problem of data return days ago? May be some setting in my.ini is not recording transactional data? I never had this problem in MySQL 5.1, could it be a Mysql 5.6 bug?
The my.ini:
_______________________________________________________________
[mysql]
default-character-set = latin1
[mysqld]
sql_mode="STRICT_TRANS_TABLES,STRICT_ALL_TABLES,NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER"
collation-server = latin1_swedish_ci
character-set-server = latin1
port = 3306
datadir = C:\Program Files\MySQL\MySQL Server 5.6/data/
basedir = C:\Program Files\MySQL\MySQL Server 5.6
innodb_log_group_home_dir = C:\Program Files\MySQL\MySQL Server 5.6\data/
innodb_data_home_dir = C:\Program Files\MySQL\MySQL Server 5.6/data/
lc_messages=pt_BR
lc_time_names=pt_BR
skip-name-resolve
skip-host-cache
event-scheduler=1
performance_schema
max_allowed_packet = 32M
max_connections = 150
innodb_flush_log_at_trx_commit=1
join_buffer_size = 94M
read_rnd_buffer_size = 2M
sort_buffer_size = 4M
query_prealloc_size = 16M
query_cache_type=1
query_cache_size = 80M
query_cache_limit = 48M
innodb_file_per_table = 1
innodb_open_files = 1000
open_files_limit = 4096
innodb_print_all_deadlocks
innodb_buffer_pool_size = 1024M
innodb_log_file_size = 200M
innodb_log_buffer_size = 8M
innodb_lock_wait_timeout=180
innodb_thread_concurrency=4
innodb_read_io_threads=8
innodb_write_io_threads=8
thread_cache_size=7
innodb_io_capacity=200
tmp_table_size = 128M
max_heap_table_size = 256M
[mysqldump]
quick
max_allowed_packet = 32M
_________________________________________________________________
Any help is appreciated
Problem: In recent days MYSQL has losing days of data, like a big rollback of datas in all tables, checking the MYSQL error log, only appears the follows messages: "database was not shutdown normally" and "[Note] InnoDB: The log sequence numbers 1181074230 and 1181074230 in ibdata files do not match the log sequence number 1181075227 in the ib_logfiles ".
These messages could be related to the problem of data return days ago? May be some setting in my.ini is not recording transactional data? I never had this problem in MySQL 5.1, could it be a Mysql 5.6 bug?
The my.ini:
_______________________________________________________________
[mysql]
default-character-set = latin1
[mysqld]
sql_mode="STRICT_TRANS_TABLES,STRICT_ALL_TABLES,NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER"
collation-server = latin1_swedish_ci
character-set-server = latin1
port = 3306
datadir = C:\Program Files\MySQL\MySQL Server 5.6/data/
basedir = C:\Program Files\MySQL\MySQL Server 5.6
innodb_log_group_home_dir = C:\Program Files\MySQL\MySQL Server 5.6\data/
innodb_data_home_dir = C:\Program Files\MySQL\MySQL Server 5.6/data/
lc_messages=pt_BR
lc_time_names=pt_BR
skip-name-resolve
skip-host-cache
event-scheduler=1
performance_schema
max_allowed_packet = 32M
max_connections = 150
innodb_flush_log_at_trx_commit=1
join_buffer_size = 94M
read_rnd_buffer_size = 2M
sort_buffer_size = 4M
query_prealloc_size = 16M
query_cache_type=1
query_cache_size = 80M
query_cache_limit = 48M
innodb_file_per_table = 1
innodb_open_files = 1000
open_files_limit = 4096
innodb_print_all_deadlocks
innodb_buffer_pool_size = 1024M
innodb_log_file_size = 200M
innodb_log_buffer_size = 8M
innodb_lock_wait_timeout=180
innodb_thread_concurrency=4
innodb_read_io_threads=8
innodb_write_io_threads=8
thread_cache_size=7
innodb_io_capacity=200
tmp_table_size = 128M
max_heap_table_size = 256M
[mysqldump]
quick
max_allowed_packet = 32M
_________________________________________________________________
Any help is appreciated