Bug #89459
closed
Exception due to missing cache tables on Upgrade from 9.5 to TYPO3 10.1
Added by Sybille Peters over 4 years ago. Updated over 2 years ago.
0%
Description
Doctrine\DBAL\Exception\TableNotFoundException An exception occurred while executing 'SELECT `content` FROM `cache_rootline` WHERE (`identifier` = ?) AND (`expires` >= ?)' with params ["1__0_-99", 1571466118]: Table 't3intro.cache_rootline' doesn't exist
When I look in the database tables of my TYPO3 9 installations I see only
| cf_cache_hash | | cf_cache_hash_tags | | cf_cache_imagesizes | | cf_cache_imagesizes_tags | | cf_cache_pages | | cf_cache_pages_tags |
no cache_hash etc.
Updated by Georg Ringer over 4 years ago
- Status changed from New to Needs Feedback
did you do a DB compare to get those tables?
Updated by Sybille Peters over 4 years ago
- Subject changed from Exception due to missing cache tables on Upgrade to TYPO3 10.1 to Exception due to missing cache tables on Upgrade from 9.5 to TYPO3 10.1
Updated by Sybille Peters over 4 years ago
- Status changed from Needs Feedback to Closed
Sorry, my bad. Indeed, I had to do a DB compare first.
Updated by Maximilian Winck about 3 years ago
I ran into this issue.
After upgrading, I got an exception when visiting the backend due to missing cache tables. To get rid of the exception and access the backend, I disabled all caches via `AdditionalConfiguration.php`:
foreach ($GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations'] as $cacheName => $cacheConfiguration) {
$GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations'][$cacheName]['backend'] = \TYPO3\CMS\Core\Cache\Backend\NullBackend::class;
}
But this causes the Database Analyzer to not want to create the cache tables in the first place.
The only way to fix it was visiting the Database Analyzer in the install tool directly (not through backend) while the caches were not disabled.
This took me a while to figure out, because I initially assumed the direct-access install tool was gone: I couldn't access it via `/typo3/install` anymore, only via `/typo3/install.php`.
Updated by Sybille Peters about 3 years ago
- Status changed from Closed to Needs Feedback
So, this was when updating to 10? For completeness sake, can you add the text of your exception message and the steps you performed?
I think this may actually not be a bug but just a question of how the upgrade must be performed and in which order. We might want to add a warning to the docs, e.g. in https://docs.typo3.org/m/typo3/guide-installation/10.4/en-us/Upgrade/Index.html
Updated by Stephan Boiting about 3 years ago
my solution sql:
CREATE TABLE `cache_rootline` (
`id` int(10) UNSIGNED NOT NULL,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`expires` int(10) UNSIGNED NOT NULL DEFAULT 0,
`content` longblob DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `cache_hash` (
`id` int(10) UNSIGNED NOT NULL,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`expires` int(10) UNSIGNED NOT NULL DEFAULT 0,
`content` longblob DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `cache_hash_tags` (
`id` int(10) UNSIGNED NOT NULL,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`tag` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ''
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `cache_rootline_tags` (
`id` int(10) UNSIGNED NOT NULL,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`tag` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ''
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `cache_pagesection` (
`id` int(10) UNSIGNED NOT NULL,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`expires` int(10) UNSIGNED NOT NULL DEFAULT 0,
`content` longblob DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci
CREATE TABLE `cache_pagesection_tags` (
`id` int(10) UNSIGNED NOT NULL,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`tag` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ''
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `cache_pages` (
`id` int(10) UNSIGNED NOT NULL,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`expires` int(10) UNSIGNED NOT NULL DEFAULT 0,
`content` longblob DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `cache_pages_tags` (
`id` int(10) UNSIGNED NOT NULL,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`tag` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ''
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
Updated by Maximilian Winck about 3 years ago
Sybille Peters wrote in #note-5:
So, this was when updating to 10? For completeness sake, can you add the text of your exception message and the steps you performed?
I think this may actually not be a bug but just a question of how the upgrade must be performed and in which order. We might want to add a warning to the docs, e.g. in https://docs.typo3.org/m/typo3/guide-installation/10.4/en-us/Upgrade/Index.html
IIRC the only steps needed to trigger the "issue" is switching a v9.5 installation to v10.4 - I do it via changing the typo3_src symlink. Then try to visit the backend, it will trigger an exception immediately, because the database was not yet updated to v10.4.
As I said, my main mistake was not using the install tool directly (because I failed to realize that the URL is `/typo3/install.php` and not `/typo3/install`).
The Docs do say to use the install tool here, at the top: https://docs.typo3.org/m/typo3/guide-installation/10.4/en-us/Upgrade/UseTheUpgradeWizard/Index.html
Arguably, it's easy to overlook. What would definitely have helped me is if the backend just redirected to the install tool directly upon detecting that the Database had not yet been updated with the Database Analyzer, instead of throwing an exception.
Updated by Sybille Peters almost 3 years ago
- Status changed from Needs Feedback to New
@Stephan Boiting
Thanks for the script, but I think there are some problems with it:
- missing semicolon on line with cache_pagesection
- missing auto_increment and primary key, e.g. cache_hash.id
- missing cache_imagesizes and cache_imagesizes_tags
This works for me:
CREATE TABLE `cache_rootline` (
`id` int(10) UNSIGNED NOT NULL auto_increment,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`expires` int(10) UNSIGNED NOT NULL DEFAULT 0,
`content` longblob DEFAULT NULL,
PRIMARY KEY(id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `cache_hash` (
`id` int(10) UNSIGNED NOT NULL auto_increment,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`expires` int(10) UNSIGNED NOT NULL DEFAULT 0,
`content` longblob DEFAULT NULL,
PRIMARY KEY(id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `cache_hash_tags` (
`id` int(10) UNSIGNED NOT NULL auto_increment,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`tag` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
PRIMARY KEY(id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `cache_rootline_tags` (
`id` int(10) UNSIGNED NOT NULL auto_increment,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`tag` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
PRIMARY KEY(id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `cache_pagesection` (
`id` int(10) UNSIGNED NOT NULL auto_increment,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`expires` int(10) UNSIGNED NOT NULL DEFAULT 0,
`content` longblob DEFAULT NULL,
PRIMARY KEY(id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `cache_pagesection_tags` (
`id` int(10) UNSIGNED NOT NULL auto_increment,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`tag` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
PRIMARY KEY(id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `cache_pages` (
`id` int(10) UNSIGNED NOT NULL auto_increment,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`expires` int(10) UNSIGNED NOT NULL DEFAULT 0,
`content` longblob DEFAULT NULL,
PRIMARY KEY(id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `cache_pages_tags` (
`id` int(10) UNSIGNED NOT NULL auto_increment,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`tag` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
PRIMARY KEY(id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `cache_imagesizes` (
`id` int(10) UNSIGNED NOT NULL auto_increment,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`expires` int(10) unsigned NOT NULL DEFAULT '0',
`content` longblob,
PRIMARY KEY(id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `cache_imagesizes_tags` (
`id` int(10) UNSIGNED NOT NULL auto_increment,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`tag` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
PRIMARY KEY(id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
If adminpanel installed:
CREATE TABLE `cache_adminpanel_requestcache` (
`id` int(10) UNSIGNED NOT NULL auto_increment,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`expires` int(10) unsigned NOT NULL DEFAULT '0',
`content` longblob,
PRIMARY KEY(id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `cache_adminpanel_requestcache_tags` (
`id` int(10) UNSIGNED NOT NULL auto_increment,
`identifier` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`tag` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
PRIMARY KEY(id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
Updated by Jonas Eberle over 2 years ago
I am able to reproduce but it is to be expected.
Openning the InstallTool via typo3/install.php and using "Analyze Database Structure" fixes it.
So does vendor/bin/typo3cms database:updateschema if you have the TYPO3 console installed.
Updated by Jonas Eberle over 2 years ago
- Status changed from New to Closed
Closed in accordance with bug reporter.
Updated by Stephan Boiting over 2 years ago
Sybille Peters wrote in #note-8:
@Stephan Boiting
Thanks for the script, but I think there are some problems with it:
- missing semicolon on line with cache_pagesection
- missing auto_increment and primary key, e.g. cache_hash.id
- missing cache_imagesizes and cache_imagesizes_tagsThis works for me:
[...]
If adminpanel installed:
[...]
Thanks, you are right