You were fundamentally missing the mysqldump command vs mysql. that single transaction is just addition good to have.
Ad Widget
Collapse
Database seems to be growing too quick
Collapse
X
-
-
Then you don't need to run it again. Single transaction should have no effect whether you are having some table in the dump or not.Comment
-
In case you recover to empty database I think you needed to create the DB schema first (as from the Zabbix installation steps but without data) and then import the backup.Comment
-
Hi Ingus,
I didn't any feedback because I've some troubles to put my database in my test environment.
Here the things I've tried:- dump my database and then recover to empty database (DB schema created): without success, because my ibd files didn't appear
- rsync my zabbix in /var/lib/mysql/ to my other server: without success , when I tried to select any table I get "Empty set"
Comment
-
-
Hi,
I found the solution for my problem, I've to enable the innodb_file_per_table.
Enable innodb_file_per_table vi /etc/my.cnf
Apparently when I imported the dump the ibd files per table aren't created.Code:[mysqld] innodb_file_per_table = 1
I started to import again my database dump and I've the idb files per table.
Thank you.Comment
-
-
-
Hi,
After 2 days partioning my history table I got the following error:I google it and it seems are related with innodb_buffer_pool_size parameter in my.cnf. But I'm not sure the value I have to put hereCode:[SOLVED] ERROR 1206 (HY000): The total number of locks exceeds the lock table size
Comment
Comment