| Summary: | DigiKam+MySQL: Failed to create database tables. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | alexander |
| Component: | Database-Mysql | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | Appimage | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 6.4.0 | |
| Sentry Crash Report: | |||
| Attachments: | stdout-Output from digiKam AppImage | ||
|
Description
alexander
2019-10-09 17:32:15 UTC
Try again using 6.4.0 pre-release bundle : https://files.kde.org/digikam/ Gilles Caulier > Error messages: "QMYSQL: Unable to execute query" "Cannot load from mysql.proc. > The table is probably corrupted" "1728" 2
Try:
mysql> REPAIR TABLE mysql.proc;
Maik
There is also the possibility that your MariaDB version is too current and a change is not compatible with our function "CreateIndices". I am here even under openSUSE Thumbleweed only at MariaDB-10.3.18. Maik (In reply to caulier.gilles from comment #1) > Try again using 6.4.0 pre-release bundle : > > https://files.kde.org/digikam/ > > Gilles Caulier Still getting this error: igikam::CoreDbSchemaUpdater::update: Core database: running schema update Digikam::CoreDbSchemaUpdater::startUpdates: Core database: no database file available Digikam::BdEngineBackendPrivate::debugOutputFailedQuery: Failure executing query: "" Error messages: "QMYSQL: Unable to execute query" "Cannot load from mysql.proc. The table is probably corrupted" "1728" 2 Bound values: () Digikam::BdEngineBackend::execDBAction: Error while executing DBAction [ "CreateIndices" ] Statement [ "\n DROP PROCEDURE IF EXISTS create_index_if_not_exists;\n " ] Digikam::CoreDbAccess::checkReadyForUse: Core database: cannot process schema initialization Digikam::KMemoryInfo::update: KMemoryInfo: Platform identified : "LINUX" Digikam::KMemoryInfo::bytes: KMemoryInfo: TotalRam: 33650221056 Digikam::LoadingCache::setCacheSize: Allowing a cache size of 200 MB unknown: QThreadStorage: Thread 0x7f766afee840 exited after QThreadStorage 15 destroyed and after a restart with > REPAIR TABLE mysql.proc; /Apps> ./digikam-6.4.0-git-20191005T120037-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Note: to integrate this bundle to your desktop, use AppImageLauncher. libudev.so.0 -- Preloading shared libs: Digikam::DXmlGuiWindow::setupIconTheme: Breeze icons resource file found Digikam::DXmlGuiWindow::setupIconTheme: Breeze-dark icons resource file found Digikam::AlbumWatch::AlbumWatch: AlbumWatch is disabled Digikam::AlbumManager::setDatabase: Database Parameters: Type: "QMYSQL" DB Core Name: "digikam" DB Thumbs Name: "digikam" DB Face Name: "digikam" DB Similarity Name: "digikam" Connect Options: "" Host Name: "io" Host port: 3306 Internal Server: false Internal Server Path: "" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "digikam" Password: "XXXXXXXXXXXXXXXX" Digikam::DbEngineConfigSettingsLoader::readConfig: Loading SQL code from config file "/tmp/.mount_digika0blJK9/usr/share/digikam/database/dbconfig.xml" Digikam::DbEngineConfigSettingsLoader::readConfig: Checking XML version ID => expected: 3 found: 3 Digikam::CoreDbSchemaUpdater::update: Core database: running schema update Digikam::CoreDbSchemaUpdater::startUpdates: Core database: have a structure version 0 Digikam::CoreDbSchemaUpdater::startUpdates: Core database: version not available! Giving up schema upgrading. Digikam::CoreDbAccess::checkReadyForUse: Core database: cannot process schema initialization Digikam::KMemoryInfo::update: KMemoryInfo: Platform identified : "LINUX" Digikam::KMemoryInfo::bytes: KMemoryInfo: TotalRam: 33650221056 Digikam::LoadingCache::setCacheSize: Allowing a cache size of 200 MB unknown: QThreadStorage: Thread 0x7f67332b8840 exited after QThreadStorage 11 destroyed > There is also the possibility that your MariaDB version is too current and a change is not compatible with our function "CreateIndices". I am here even under openSUSE Thumbleweed only at MariaDB-10.3.18. Maybe true. digiKam is the only software running on this instance that is experiencing hickups though. Searching for "corrupted mysql.proc table" told me that I had to run mysql_upgrade on my database. That fixed everything. Now digiKam 6.0.0 initialized all tables and runs perfectly :) Thank your very much for your help and sorry for any inconvenience. |