Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-2077

InnoDB select table failed with 'table not in engine' from User Module 2

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Not a Bug
    • Affects Version/s: 1.2.2
    • Fix Version/s: 1.2.6
    • Component/s: oam
    • Labels:
    • Environment:
      Amazon AMI 2um/3pm system

      Description

      Customer reporting error from the table select on Innodb tables from UM2, when they worked from UM1.

      MariaDB [XXXXXX]> select count(1) from XXXXXXX; ERROR
      1932 (42S02): Table 'XXXXXX' doesn't exist in engine

      Problem turned out that the InnoDB table structure file 'ibdata1' wasnt replicated from UM1 to UM2 when the rsync command is run, which is part of the upgrade process and when 'enablemysqlreplication' is run from the mcsadmin console.

      Need to investigate why this table isnt replicated from um1 to other nodes via rsync.

      ---------------------------
      work around : shutdown system and scp 'ibdata1' table from um1 to um2. startsystem

        Attachments

          Activity

            People

            Assignee:
            toddstoffel Todd Stoffel
            Reporter:
            hill David Hill (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration

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