Troubleshooting MySQL Error 1168 (ER_WRONG_MRG_TABLE): Ensuring Identical Table Definitions in MERGE Tables

When working with MERGE storage engines in MySQL, encountering Error 1168 – SQLSTATE: HY000 (ER_WRONG_MRG_TABLE) can be a sign that not all underlying tables are defined identically. This error can halt operations involving MERGE tables, but with a proper understanding and approach, it can be resolved effectively. Here’s a guide to help you diagnose and fix this issue.

Understanding Error 1168

Error 1168 occurs when the tables you’re trying to merge have differing definitions. For MERGE tables to work correctly, all underlying MyISAM tables must have identical column definitions, indexes, and table options. Any discrepancy can trigger this error.

Diagnosing the Error

First, verify that all MERGE table members have the same structure. You can compare the table definitions using the SHOW CREATE TABLE statement:

SHOW CREATE TABLE child_table1;
SHOW CREATE TABLE child_table2;
-- Compare the output of these statements to ensure they are identical.

Fixing the Error

Here are the steps to correct the discrepancies causing Error 1168:

1. Align Column Definitions

Ensure all columns are defined in the same order and with the same data types and attributes. If you identify differences, alter the table to match the others:

ALTER TABLE child_table2
MODIFY column1 INT(11) NOT NULL,
MODIFY column2 VARCHAR(255) DEFAULT 'value';
-- Repeat for all columns that differ.

2. Synchronize Indexes

Indexes must be identical across all tables. To check indexes, use:

SHOW INDEX FROM child_table1;
SHOW INDEX FROM child_table2;

To adjust an index, you might need to drop and recreate it:

ALTER TABLE child_table2
DROP INDEX index_name,
ADD INDEX index_name (column1, column2);

3. Standardize Table Options

Table options like ENGINE, CHARSET, and COLLATE must be consistent. Verify and change them if necessary:

ALTER TABLE child_table2
COLLATE = utf8_general_ci;

4. Re-create the MERGE Table

After ensuring all underlying tables are identical, drop and re-create the MERGE table:

DROP TABLE merge_table;
CREATE TABLE merge_table (
-- column definitions must match the MyISAM tables
) ENGINE=MERGE UNION=(child_table1,child_table2,...) INSERT_METHOD=LAST;

5. Check for Data Integrity

After alignment, ensure that the data across all tables is consistent and that there are no integrity issues.

Preventive Measures

To prevent this error in the future:

  • Always create new tables intended for MERGE by cloning the structure of an existing table using CREATE TABLE ... LIKE.
  • Regularly verify table structures, especially after making changes to individual tables.


By methodically ensuring that all MERGE table components have identical definitions, you can resolve Error 1168 and restore the functionality of your MERGE tables. Always back up your data before making structural changes to avoid accidental data loss.

For further assistance, consider referring to the MySQL documentation on the MERGE storage engine, or consult community forums like Stack Overflow where similar issues have been discussed and resolved.

Leave a Comment