Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Table dictionary contains additional id column which is not used by other engines. #6788

Closed
Nepherim opened this issue Jun 5, 2019 · 10 comments

Comments

@Nepherim
Copy link

Nepherim commented Jun 5, 2019

Upgrading from 1.2.2 to 1.3.9, using installto.sh, and I got an error along the lines "Table dictionary contains additional id column which is not used by other engines.", same as this issue.

Everything seems to work though.

@alecpl
Copy link
Member

alecpl commented Jun 5, 2019

This was supposed to be fixed in 1.3. What database are you using?

@Nepherim
Copy link
Author

Nepherim commented Jun 5, 2019

MySQL 5.6.41-84.1.

@alecpl
Copy link
Member

alecpl commented Jun 5, 2019

Then this does not make sense to me. Does not sound like the issue you refer to. What error do you get exactly? Was it vanilla 1.2.2 installation or an upgrade from some early version?

@Nepherim
Copy link
Author

Nepherim commented Jun 6, 2019

From the web installer:

DB Schema:  NOT OK(Database schema differs)
Missing columns in table 'dictionary': id

You should run the update queries to get the schema fixed.

This is an install that originated from the first releases -- back to 0.5 or whatever the initial one was. Over the releases it's hit a few road-bumps, so this error could be the result of one of those other failed and fixed upgrades at some point.

@alecpl
Copy link
Member

alecpl commented Jun 6, 2019

I still don't see the problem. There should be "Update" button below that text. Did you use it?

@Nepherim
Copy link
Author

Nepherim commented Jun 6, 2019

When using the Update button:
Database schema update failed.

@alecpl
Copy link
Member

alecpl commented Jun 6, 2019

Check the error log or run the bin/updatedb.sh --dir=SQL --package=roundcube script by hand.

@Nepherim
Copy link
Author

Nepherim commented Jun 6, 2019

Output of the updatedb.sh script:

Updating database schema (2013052500)... [FAILED]
Error 500: Error in DDL upgrade 2013052500: [1050] Table 'cache_shared' already exists

@alecpl
Copy link
Member

alecpl commented Jun 7, 2019

Something is messed up in your database. The db-version for 1.2.2 in 2015111100 and this is what you should have in system table. Here it looks like Roundcube tries to run upgrade scripts for older version. You'll have to fix it manually, by comparing the structure, going throughout the scripts in SQL/mysql and executing what's needed.

@alecpl alecpl closed this as completed Jun 7, 2019
@Nepherim
Copy link
Author

Nepherim commented Jun 7, 2019

Yeah, over time I suspect various upgrade issues compounded. Thanks for the pointer to the db version in system table. I went through and verified tables, columns, and constraints against the mysql.initial.sql script, and updated the system table, so everything should now be consistent.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants