Tag Info

New answers tagged

0

Sounds like you have your data file corrupted. You may try to start up your server using innodb Force Recover and then dump your table data using Select Into Command. If you had your binary log file enabled before the crash, you may restore data through Point In Time Recovery


0

This seems to be known problem with to_days and between - if there were some invalid dates in the table, to_days return NULL on them and stores them in the first partition. And when evaluating BETWEEN, mysql can sometimes decide that some dates in that range are invalid and so it thinks it has to check first partition to find them. Such dates giving NULL may ...


0

I cannot fully answer this question but I can give you some tips on what to look around for. First thing I would do is check the dates inside each partition as follows SELECT date_x,COUNT(1) datecount FROM TABLE_X partition (p13q1) GROUP BY date_x; SELECT date_x,COUNT(1) datecount FROM TABLE_X partition (p13q2) GROUP BY date_x; SELECT date_x,COUNT(1) ...


0

Instead of DROP + CREATE, simply do TRUNCATE TABLE. That should avoid the error about COMMIT. Drawback: Other code would need to originally do the CREATE and DROP.


0

I did not spot an explicit commit in the code. Therefore the following link lists the MySQL 5.1 operations that can cause an implicit commit. https://dev.mysql.com/doc/refman/5.1/en/implicit-commit.html There are quite a few possibilities. Note this comment: "CREATE TABLE and DROP TABLE statements do not commit a transaction if the TEMPORARY keyword is ...


0

Replication from MySQL 5.x to 5.6 has a bear trap just waiting for you. In Michael's comment, he stated the politically accept premise : "MySQL supports replication from one major version to the next higher major version.". He also said "this setup isn't guaranteed to work in either direction." I have a very interesting caveat on going from 5.x to 5.6: ...


2

Cringe, gag, etc. 5.1 and 5.6 differ by 2 major versions. Replication is 'guaranteed' to work one direction, not the other. Don't turn on GTIDs in 5.6; 5.1 will not like it. Don't use any features new to 5.5 or 5.6. Simply, don't do it. Get the 5.1 upgraded ASAP.



Top 50 recent answers are included