# Transactional commit not supported by involved engine(s)

**URL:** <https://forums.percona.com/t/transactional-commit-not-supported-by-involved-engine-s/28615>\
**Category:** Uncategorized\
**Created:** [February 21, 2024, 1:40pm UTC](https://forums.percona.com/t/transactional-commit-not-supported-by-involved-engine-s/28615 "2024-02-21T13:40:06Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![MALIMAHESH25](https://avatars.discourse-cdn.com/v4/letter/m/c89c15/32.png) [@MALIMAHESH25](https://forums.percona.com/u/MALIMAHESH25)\
**Post date:** [February 21, 2024, 1:40pm UTC](https://forums.percona.com/t/transactional-commit-not-supported-by-involved-engine-s/28615/1 "2024-02-21T13:40:06Z")

</div>

Hi team,

I have upgraded MariaDB from version 10.6.11 to 10.11.7  
After the upgrade, I am getting “Transactional commit not supported by involved engine(s)” error while inserting record into a table.  
Any suggestions on how to fix this issue?

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [February 21, 2024, 5:05pm UTC](https://forums.percona.com/t/transactional-commit-not-supported-by-involved-engine-s/28615/2 "2024-02-21T17:05:33Z")

</div>

Looks like you are trying to use transactions on an engine that does not support them. Please use ‘SHOW CREATE TABLE’ to identify the engine of the table.

---

<div class="post-metadata">

**Author:** ![MALIMAHESH25](https://avatars.discourse-cdn.com/v4/letter/m/c89c15/32.png) [@MALIMAHESH25](https://forums.percona.com/u/MALIMAHESH25)\
**Post date:** [February 21, 2024, 5:55pm UTC](https://forums.percona.com/t/transactional-commit-not-supported-by-involved-engine-s/28615/3 "2024-02-21T17:55:58Z")

</div>

ENGINE=InnoDB AUTO\_INCREMENT=12 DEFAULT CHARSET=utf8mb3 COLLATE=utf8mb3\_general\_ci

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [February 21, 2024, 6:05pm UTC](https://forums.percona.com/t/transactional-commit-not-supported-by-involved-engine-s/28615/4 "2024-02-21T18:05:28Z")

</div>

I found this reference in the MariaDB release notes:

> **[Open Source Database (RDBMS) for the Enterprise | MariaDB](https://mariadb.com/docs/server/release-notes/mariadb-enterprise-server-10-6/10-6-14-9/)**
>
> MariaDB is the leading enterprise open source database with features previously only available in costly proprietary databases. Enterprise grade, wallet friendly.

> With Galera, when a transaction changes multiple tables that use different storage engines, some of which support the server’s internal 2-phase commit protocol and some of which don’t support it, the node crashes with an assertion failure.
> 
> - Starting with this release, when Galera is enabled, mixed transactions are rejected in with the following error message:
> 
> ERROR HY000: Transactional commit not supported by involved engine(s)

---

<div class="post-metadata">

**Author:** ![MALIMAHESH25](https://avatars.discourse-cdn.com/v4/letter/m/c89c15/32.png) [@MALIMAHESH25](https://forums.percona.com/u/MALIMAHESH25)\
**Post date:** [February 22, 2024, 4:30am UTC](https://forums.percona.com/t/transactional-commit-not-supported-by-involved-engine-s/28615/5 "2024-02-22T04:30:33Z")

</div>

I have seen that in the release notes. But all the tables in my schema use same storage engine that is InnoDB and I am getting the error while changing single table.

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [February 22, 2024, 3:55pm UTC](https://forums.percona.com/t/transactional-commit-not-supported-by-involved-engine-s/28615/6 "2024-02-22T15:55:21Z")

</div>

If a simple INSERT to this 1 table is causing this error, I suggest looking at the error logs, and possibly opening a ticket with MariaDB. You will need a repeatable test case, and provide the table schema along with the query you are running.