"DBVersion" setting does not exist.

[Maik Qualmann]

I don't think that will work for changing the MySQL/MariaDB directory. Create 
a MySQL dump of the digiKam database(s) and import it again once you've 
specified a new directory and the server has restarted and created its empty 
database structure.

Maik

Am Donnerstag, 30. Oktober 2025, 08:09:55 Mitteleuropäische Normalzeit schrieb 
Pete Lindgren:
> Hi,
> 
> " The database is not valid: the "DBVersion" setting does not exist. The
> current database schema version cannot be verified. Try to start with an
> empty database."
> 
> I'm encountering the error above after trying to move the MariaDB database
> on my ubuntu server. The error popup occurs when I subsequently try to open
> the digikam application on Windows.
> 
> 
> If I click OK on this pop up, it shows me the database configuration popup.
> Clicking the 'Check Connection' button confirms 'Database connection test
> successful.' Yet, if I click OK on the database configuration popup then it
> shows the DBVersion error popup again.
> 
> 
> How can I correct this? Or what is the recommended approach to move the
> database to a new location on the same server?
> 
> 
> The migration tool does not seem appropriate here because I'm moving the db
> from one directory to another on the same server, so the digikam client
> will still be connecting to the same backend with the same credentials.
> 
> 
> Brief overview of steps taken
> 
> * Closed digikam client
> 
> * stopped mariadb service on the server
> 
> * rsync -aHAX to new location
> 
> * checked mysql:mysql ownership
> 
> * updated datadir location in /etc/mysql/mariadb.conf.d/50-server.cnf *
> restart mariadb service
> 
> 
> Thanks