Re: Alter table killed, but change was done
Thx for replying.
Yes, it is InnoDB.
After killing the ALTER-Script the tmp-table was immediatly gone and also all of the locks on the table, so I assumed that the ALTER was immediately rolled back.
I noticed later on that about 6 hours later I got for about 5 minutes an error 28 from storage engine.
I also checked the table and all records are still existing.
Hm, really strage, so now I think that the tmp table was deleted and also I saw nothing about it anymore with "SHOW PROCESSLIST" but the ALTER was then executed because the column was changed - there is no other explanation, or?
Subject
Views
Written By
Posted
1596
June 01, 2011 01:36AM
796
June 02, 2011 10:33AM
Re: Alter table killed, but change was done
843
June 02, 2011 11:10AM
808
June 02, 2011 07:53PM
595
June 03, 2011 01:58AM
771
June 03, 2011 09:38AM
780
June 04, 2011 01:33AM
1336
June 04, 2011 09:46AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.