[MCOL-1209] Recovering from error "Cannot create table: table already exists (your schema is probably out-of-sync)" Created: 2018-02-07 Updated: 2018-07-30 Resolved: 2018-02-08 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | MariaDB Server |
| Affects Version/s: | None |
| Fix Version/s: | 1.1.2 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Dimitris Theodorou | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
I've lost (data loss) the MariaDB data directory, but I still have the MariaDB Columnstore data directory. All the corresponding information schema and calpontsys queries show that while MariaDB Columnstore recognizes the tables correctly, MariaDB itself doesn't know anything about them. Trying to run the create query "CREATE TABLE IF NOT EXISTS tablename ..." for a table that already exists returns the error "Internal create table error for tablename: table already exists (your schema is probably out-of-sync)". Running select queries is not possible, I get a "table does not exist" error. Is there a way to recover from this? Can I recreate the tables in the MariaDB "side" so that I can resume operations normally? |
| Comments |
| Comment by David Hill (Inactive) [ 2018-02-07 ] |
|
Try creating the table again with COMMENT='SCHEMA SYNC ONLY' example: create table tmp (c1 int) engine=columnstore COMMENT='SCHEMA SYNC ONLY; |
| Comment by Dimitris Theodorou [ 2018-02-08 ] |
|
Ok that worked, thanks |
| Comment by Abhinav santi [ 2018-07-30 ] |
|
what is the significance of comment schema sync only ? Tables behave different with and without comment schema. I did an upgrade from 1.0.11 - 1.0.14 and lost data on the tables without comment schema sync |