Metabase + MySQL Installation failing

Get Help
1

Using existing MySQL and Database for Installation getting below error
Trying to install using kubernetes

Note: Used existing Database not created dedicated one for metabase

2022-10-03 06:59:25,811 INFO db.setup :: Running Database Migrations...
2022-10-03 06:59:25,813 INFO db.setup :: Setting up Liquibase...
2022-10-03 06:59:26,257 ERROR metabase.core :: Metabase Initialization FAILED
java.sql.BatchUpdateException: (conn=19535661) The table does not comply with the requirements by an external plugin.
	at org.mariadb.jdbc.MariaDbStatement.executeBatchExceptionEpilogue(MariaDbStatement.java:323)
	at org.mariadb.jdbc.ClientSidePreparedStatement.executeBatch(ClientSidePreparedStatement.java:299)
	at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:2544)
2

Hi @ganeshram.s
Which version of Metabase?
What does this mean "Note: Used existing Database not created dedicated one for metabase" ?
The error is coming from MySQL https://stackoverflow.com/questions/53268697/error-3098-hy000-the-table-does-not-comply-with-the-requirements-by-an-extern
I don't know which version of MySQL you're using, but check your MySQL logs, hopefully they will have more information.

3

Hi @flamber
Version: Metabase v0.44.3 (7d50282 release-x.44.x)

"Note: Used existing Database not created dedicated one for metabase" ?
I meant didnt create new Database in the MySQL server, used an existing DB used by other applications. Requested the internal DB team to create new DB, will share the details once tried.

Thanks for the quick reply

4

@ganeshram.s You should absolutely create an empty dedicated database for Metabase. Some applications might have table names that are similar to Metabase, so that will cause a lot of problems.

5

Even after creating new DB same issue

@flamber You were right it was due to database Mater Slave configuration. But we couldn't find anything in the logs.

GROUP REPLICATION ISSUE
As a work around after creating the DB we created the
DATABASECHANGELOG and
DATABASECHANGELOGLOCK table manually post which installation was successful.

CREATE TABLE `DATABASECHANGELOG` (
  `ID` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  `AUTHOR` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  `FILENAME` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  `DATEEXECUTED` datetime NOT NULL,
  `ORDEREXECUTED` int NOT NULL,
  `EXECTYPE` varchar(10) COLLATE utf8mb4_unicode_ci NOT NULL,
  `MD5SUM` varchar(35) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `DESCRIPTION` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `COMMENTS` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `TAG` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `LIQUIBASE` varchar(20) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `CONTEXTS` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `LABELS` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `DEPLOYMENT_ID` varchar(10) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  UNIQUE KEY `idx_databasechangelog_id_author_filename_new` (`ID`,`AUTHOR`,`FILENAME`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

CREATE TABLE `DATABASECHANGELOGLOCK` (
  `ID` int NOT NULL,
  `LOCKED` bit(1) NOT NULL,
  `LOCKGRANTED` datetime DEFAULT NULL,
  `LOCKEDBY` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  PRIMARY KEY (`ID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

Thanks for the Help.

6

@ganeshram.s There's an issue open about cluster support:
https://github.com/metabase/metabase/issues/7561 - upvote by clicking :+1: on the first post