We have mysql MYISAM tables that are "rolled" weekly and/or monthly (rolled as in renameing tableX ==> tableX_archive_date) and then from that point on, then are never updated again.

We have a python process that iterates through all the archive_tables periodically and analyzes the data.

It seems like once a month, the python script will hang on a specific row and the cursor will be stuck on it until we do an optimize on the table again. i.e. all of a sudden, every time we run the script, it will always hang on a the same table/row UNTIL we run an optimize on that table.

It is not the same table every time either.

Has anyone else run into this? Having static (not updated) tables suddenly become corrupt for no apparent reason?

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.