One partition of a very large partitioned table suffered corruption by a corrupted primary key index page.
Selecting data from the other partitions is still possible, but only a few rows out of the range of the affected partition can be read.
As data for that specific partition can still be re-imported the plan was to drop and re-create the partition, but any attempt to do DML on the table now end with "table does not exist in engine"
- DROP PARTITION to get rid of the partition
- ALTER TABLE REPLACE PARTITION WITH TABLE both for the bad partition and the good ones
- FLUSH TABLES ... FOR EXPORT to then be able to move "good" tablespace files over to a new partitioned table one by one
but every time it fails with "table does not exist in engine"