Tag Info

New answers tagged

0

You can try this: select * from sys.master_files store the output shut down SQL Server copy ALL the database files (data and log both) from the corrupt database to a safe location ideally a read-only location like a DVD-ROM or backup tape with infinite retention. restore the most recent pre-corruption backup of data and log files. Start SQL Server Set ...


0

If innodb_file_per_table is enabled, then a temp table is being populated with the new compression. The original table is currently intact, just not writable. Running KILL QUERY 12345 on the Connection running the ALTER TABLE should do the following: release the write lock drop the temp table leave the original table as is


0

I know it's been over a year, but here is what may have happened to this particular problem. mysql> stop slave; mysql> reset slave; mysql> change master to master_host='the-master-host', master_user='replication', master_password='the-password', master_log_file='mysql-bin.000020', master_log_pos=66395191; mysql> start slave; That looks like ...



Top 50 recent answers are included