Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hello,
when I re-enable 'update manager' module, it throws:
DatabaseSchemaObjectExistsException: Table cache_update already exists. in DatabaseSchema->createTable() (line 630 of /opt/pjkaixin-stage/pjkaixin/includes/database/schema.inc).
Comments
Comment #1
bfroehle CreditAttribution: bfroehle commentedMoving this over to the base system, since I assume that is who is responsible for installing and uninstalling schemas.
Comment #2
rogical CreditAttribution: rogical commentedproblem can't be reproduced.
Comment #3
rickmanelius CreditAttribution: rickmanelius commentedSame problem.
Comment #4
astrojim CreditAttribution: astrojim commentedI get the same after migrating from 7.0 to 7.2.
DatabaseSchemaObjectExistsException: Table cache_update already exists. in DatabaseSchema->createTable() (line 629 of /var/www/awacs/includes/database/schema.inc).
Comment #5
astrojim CreditAttribution: astrojim commentedAlso I get:
"One or more problems were detected with your Drupal installation. Check the status report for more information."
But the status report is green across the board. When I disable the update module the message goes away. Also note the update module report is not visible at any time (enabled or not, even if cron has been run).
Comment #6
Damien Tournoud CreditAttribution: Damien Tournoud commentedCannot reproduce on MySQL. Which database engine are you using?
Comment #7
astrojim CreditAttribution: astrojim commentedMySQL - I managed to get the issue resolved by truncating the cache_update table by hand, not a real fix but good enough for me.
Comment #8
EpF CreditAttribution: EpF commentedI just got this error updgrading from 6.22 to 7.9 when I tried to activate the update manager.
There is no data in the table for me to truncate before or after the attempt. Dropping the table before the attempt doesn't work either.
Regarding the engine: My database contains tables of both the MyISAM and InnoDB engines. The cache_update table is InnoDB.
Please let me know if there is any more information I can provide.
Comment #9
sylv3st3r CreditAttribution: sylv3st3r commentedI also got this error message, so this is what I did after reading the update.install and inspecting my database
1. Go to "system" table, search for filename "modules/update/update.module"
2. Change the 'schema_version' into 7000
3. Then run update.php
On schema update 7001, it will drop your entire cache_update table and recreate it. It solves my problem
Comment #10
HypervisedEd CreditAttribution: HypervisedEd commentedPost #9 resolved the same exact issue for me me!
Comment #11
knalstaaf CreditAttribution: knalstaaf commented#9 didn't work right away after setting it to 7000 and running update.php. But it did after changing it manually to 7001 (and then run update.php again).Edit: it did run right away, but I had to apply the changes I made in the db with Navicat ofcourse. The module should be enabled too, despite its error (depending on your update settings for enabled/disabled modules, really).
Comment #12
vegansupreme CreditAttribution: vegansupreme commented#9 works for me too. Also, even easier workaround is the following drush command:
drush sql-query "UPDATE system SET schema_version='7000' WHERE filename='modules/update/update.module'"
I'm experiencing this error because my production site has update module disabled and uninstalled. However, when I pull the database to local dev and enable the module there, I get the aforementioned error.
I don't know if the problem is on the uninstall side, or the install side.
Comment #13
RAWDESK CreditAttribution: RAWDESK for Colruyt Group Services commentedUpgrading from 7.43 to 7.50 also gave me this error when enabling update_manager.
It was not necessary to apply #9.
Simply ran update.php and enabling was successful.
Comment #14
stefan.r CreditAttribution: stefan.r commentedComment #15
Makdomen CreditAttribution: Makdomen commentedI have this problen 4 year.
Post #9 resolved the same exact issue and for me me!
In Drupal core 7.59
Tkanks sylv3st3r
Comment #16
markabur CreditAttribution: markabur commentedThanks, #12 worked for me. Drupal 7.65