Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-28529

Can't drop a corrupted partition, need some sort of "DROP PARTITION ... FORCE"

    XMLWordPrintable

    Details

      Description

      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"

      We tried:

      • 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"

        Attachments

          Activity

            People

            Assignee:
            holyfoot Alexey Botchkov
            Reporter:
            hholzgra Hartmut Holzgraefe
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:

                Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.