Last updated on MARCH 14, 2017
Applies to:MySQL Server - Version 5.5 and later
Information in this document applies to any platform.
It is possible by removing partition tablespaces or .frm or .par files to get in a situation in which a table can neither be used nor dropped because the data dictionary is out of sync with the reality of the data files.
Tables are defined in two places:
- One is the .frm file
- The other is in the internal data dictionary
When the internal data dictionary doesn't match the .frm file, MySQL has a problem figuring out whether the table actually exists or not and it's possible to create a situation in which the table can't be created because it already exists and it can't be dropped because it doesn't exist.
Creating just the .frm (and the .par for a partitioned file) will cause the server to throw an error message about missing tablespaces, but it should still start normally and allow the table to be dropped even though the tablespace(s) are not there.
The goal is to drop a partitioned table when some of the partition tablespaces, .frm, or .par are missing.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms