orangutitan New member Joined May 23, 2016 Posts 3 May 23, 2016 #1 I have worked in MySQL 5.7 database of almost half a day, then minimized it, a couple of hours rest, when I came back I saw that the program does not respond, restarted it, and application refused to open the database and generates an error 1016. Give a hint who knows what can be done?
I have worked in MySQL 5.7 database of almost half a day, then minimized it, a couple of hours rest, when I came back I saw that the program does not respond, restarted it, and application refused to open the database and generates an error 1016. Give a hint who knows what can be done?
Laxer Co-FounderSenior Administrator Staff member Joined Feb 20, 2012 Posts 4,002 Location Portland, OR May 23, 2016 #2 I'm assuming you have the community server version installed? I would backup the temp files: MySQL :: MySQL 5.7 Reference Manual :: B.5.3.5 Where MySQL Stores Temporary Files Close it and see if it restores it. What are you worried about? Loss of data(in the tables), loss of the scripts you were writing?
I'm assuming you have the community server version installed? I would backup the temp files: MySQL :: MySQL 5.7 Reference Manual :: B.5.3.5 Where MySQL Stores Temporary Files Close it and see if it restores it. What are you worried about? Loss of data(in the tables), loss of the scripts you were writing?
orangutitan New member Joined May 23, 2016 Posts 3 May 24, 2016 #3 Laxer said: I'm assuming you have the community server version installed? I would backup the temp files: MySQL :: MySQL 5.7 Reference Manual :: B.5.3.5 Where MySQL Stores Temporary Files Close it and see if it restores it. What are you worried about? Loss of data(in the tables), loss of the scripts you were writing? Click to expand... That's right I closed it, but no result For me more important is data
Laxer said: I'm assuming you have the community server version installed? I would backup the temp files: MySQL :: MySQL 5.7 Reference Manual :: B.5.3.5 Where MySQL Stores Temporary Files Close it and see if it restores it. What are you worried about? Loss of data(in the tables), loss of the scripts you were writing? Click to expand... That's right I closed it, but no result For me more important is data
Laxer Co-FounderSenior Administrator Staff member Joined Feb 20, 2012 Posts 4,002 Location Portland, OR May 24, 2016 #4 Since you are worrying about data loss is it correct that you were using transactions? If not, everything is updated and saved instantly so you should have no data loss. If you were, there is a recovery log and you can decide the best course of action: MySQL :: MySQL 5.6 Reference Manual :: 14.16.1 The InnoDB Recovery Process Note: Assuming you were following ACID you shouldn't have any data loss regardless. You might have to rerun the last script you were running as the changes might have been reverted but, there shouldn't be any damage. If the scripts you were running were not atomic they may have only partially ran. If this is the case you will have to do a bit of damage control. (Either revert and rerun everything or alter your update/insert/delete statement to check to see if it has already been changed) Hope that helps.
Since you are worrying about data loss is it correct that you were using transactions? If not, everything is updated and saved instantly so you should have no data loss. If you were, there is a recovery log and you can decide the best course of action: MySQL :: MySQL 5.6 Reference Manual :: 14.16.1 The InnoDB Recovery Process Note: Assuming you were following ACID you shouldn't have any data loss regardless. You might have to rerun the last script you were running as the changes might have been reverted but, there shouldn't be any damage. If the scripts you were running were not atomic they may have only partially ran. If this is the case you will have to do a bit of damage control. (Either revert and rerun everything or alter your update/insert/delete statement to check to see if it has already been changed) Hope that helps.
orangutitan New member Joined May 23, 2016 Posts 3 May 30, 2016 #5 Laxer, thank you very much, but InnoDB recovery process could restore only the part of data, no more.
Laxer, thank you very much, but InnoDB recovery process could restore only the part of data, no more.
aftend89 Member Joined Jun 1, 2016 Posts 6 Jun 7, 2016 #6 orangutitan said: I have worked in MySQL 5.7 database of almost half a day, then minimized it, a couple of hours rest, when I came back I saw that the program does not respond, restarted it, and application refused to open the database and generates an error 1016. Give a hint who knows what can be done? Click to expand... Try to open database in another version of MySQL, in case it won't help, then you may use next command: mysqladmin --defaults-file=/usr/local/mysql/my.cnf --user=root --password shutdown mysqlbackup --defaults-file=/usr/local/mysql/my.cnf \ --backup-dir=/export/backups/full \ copy-back When nothing helps when apply to Recovery Toolbox for MySQL, this solution has demo, you may try it on hxxps://mysql.recoverytoolbox.com Last edited by a moderator: Jun 7, 2016
orangutitan said: I have worked in MySQL 5.7 database of almost half a day, then minimized it, a couple of hours rest, when I came back I saw that the program does not respond, restarted it, and application refused to open the database and generates an error 1016. Give a hint who knows what can be done? Click to expand... Try to open database in another version of MySQL, in case it won't help, then you may use next command: mysqladmin --defaults-file=/usr/local/mysql/my.cnf --user=root --password shutdown mysqlbackup --defaults-file=/usr/local/mysql/my.cnf \ --backup-dir=/export/backups/full \ copy-back When nothing helps when apply to Recovery Toolbox for MySQL, this solution has demo, you may try it on hxxps://mysql.recoverytoolbox.com