# Percona Toolkit (3.6.0) compatibility with MariaDB Servier 11.4.4 (Enterprise)

**URL:** <https://forums.percona.com/t/percona-toolkit-3-6-0-compatibility-with-mariadb-servier-11-4-4-enterprise/38249>\
**Category:** MariaDB Server & Utilities\
**Created:** [June 9, 2025, 1:18pm UTC](https://forums.percona.com/t/percona-toolkit-3-6-0-compatibility-with-mariadb-servier-11-4-4-enterprise/38249 "2025-06-09T13:18:27Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![jlaur2161](https://avatars.discourse-cdn.com/v4/letter/j/7bcc69/32.png) [@jlaur2161](https://forums.percona.com/u/jlaur2161)\
**Post date:** [June 9, 2025, 1:18pm UTC](https://forums.percona.com/t/percona-toolkit-3-6-0-compatibility-with-mariadb-servier-11-4-4-enterprise/38249/1 "2025-06-09T13:18:27Z")

</div>

Just checking in if there are known issues trying to run the toolkit (specifically the archiver) with MariaDB 11.4.4? I can run it fine in 10.6 but the same scripts bomb out thinking that a variable I have in a query is a column. Thanks for any help!

---

<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:** [June 9, 2025, 6:54pm UTC](https://forums.percona.com/t/percona-toolkit-3-6-0-compatibility-with-mariadb-servier-11-4-4-enterprise/38249/2 "2025-06-09T18:54:40Z")

</div>

@jlaur2161 Please check [Jira - Percona JIRA](https://perconadev.atlassian.net/jira/software/c/projects/PT/list) for any open bug reports on this issue. Also, it would be helpful for you to paste here the command used, the example schema, and the error message from pt-archiver. I also encourage you to open a new JIRA issue above if you don’t find anything, and you have a repeatable test case.

---

<div class="post-metadata">

**Author:** ![jlaur2161](https://avatars.discourse-cdn.com/v4/letter/j/7bcc69/32.png) [@jlaur2161](https://forums.percona.com/u/jlaur2161)\
**Post date:** [June 9, 2025, 8:18pm UTC](https://forums.percona.com/t/percona-toolkit-3-6-0-compatibility-with-mariadb-servier-11-4-4-enterprise/38249/3 "2025-06-09T20:18:21Z")

</div>

Sure no problem. Here’s the important text from the script I setup:

pt-archiver --source h=$db\_host,P=$PT\_Port,D=$source\_DB,u=$db\_user,p=$db\_pass,t=report\_data --no-check-charset --no-check-columns --where “id IN (select PyleDB\_dev.report\_data.id from PyleDB\_dev.report\_data INNER JOIN PyleDB\_dev.vCompletedTasks ON PyleDB\_dev.report\_data.task\_id = PyleDB\_dev.vCompletedTasks.id where last\_update\_timestamp \< "$Start\_Date")” --limit 200 --dest h=$db\_host,D=$dest\_DB,u=$db\_user,p=$db\_pass --txn-size 200 --progress 200 --sleep-coef 1.0

Here’s the create script for the table:

CREATE TABLE `report_data` (  
`id` BIGINT(20) UNSIGNED NOT NULL AUTO\_INCREMENT,  
`task_id` BIGINT(20) NOT NULL,  
`huid` BIGINT(20) UNSIGNED NULL DEFAULT NULL,  
`pro_num` INT(9) UNSIGNED NULL DEFAULT NULL,  
`value` BIGINT(20) UNSIGNED NOT NULL,  
`trailer_id` INT(11) NULL DEFAULT NULL,  
`create_user` INT(11) NOT NULL,  
`create_ts` DATETIME NOT NULL DEFAULT current\_timestamp(),  
PRIMARY KEY (`id`) USING BTREE,  
INDEX `FK_huid_idx` (`huid`) USING BTREE,  
INDEX `FK_task_idx` (`task_id`) USING BTREE,  
INDEX `FK_create_user_idx` (`create_user`) USING BTREE,  
INDEX `FK_value_idx` (`value`) USING BTREE,  
INDEX `FK_pro_idx` (`pro_num`) USING BTREE,  
CONSTRAINT `FK_create_user` FOREIGN KEY (`create_user`) REFERENCES `employees` (`id`) ON UPDATE NO ACTION ON DELETE NO ACTION,  
CONSTRAINT `FK_huid` FOREIGN KEY (`huid`) REFERENCES `pro_handling_units` (`huid`) ON UPDATE NO ACTION ON DELETE NO ACTION,  
CONSTRAINT `FK_pro` FOREIGN KEY (`pro_num`) REFERENCES `pro_plans` (`pro_num`) ON UPDATE NO ACTION ON DELETE NO ACTION,  
CONSTRAINT `FK_task` FOREIGN KEY (`task_id`) REFERENCES `tasks` (`id`) ON UPDATE NO ACTION ON DELETE NO ACTION,  
CONSTRAINT `FK_value` FOREIGN KEY (`value`) REFERENCES `reporting_properties` (`id`) ON UPDATE NO ACTION ON DELETE NO ACTION  
)  
COLLATE=‘latin1\_swedish\_ci’  
;

And the Error:

DBD::mysql::st execute failed: Unknown column ‘2025-05-10 16:16:43’ in ‘WHERE’ [for Statement “SELECT /\*!40001 SQL\_NO\_CACHE \*/ `id`,`task_id`,`huid`,`pro_num`,`value`,`trailer_id`,`create_user`,`create_ts` FROM `PyleDB_dev`.`report_data` FORCE INDEX(`PRIMARY`) WHERE (id IN (select PyleDB\_dev.report\_data.id from PyleDB\_dev.report\_data INNER JOIN PyleDB\_dev.vCompletedTasks ON PyleDB\_dev.report\_data.task\_id = PyleDB\_dev.vCompletedTasks.id where last\_update\_timestamp \< “2025-05-10 16:16:43”)) AND (`id` \< ‘16954626’) ORDER BY `id` LIMIT 200”] at /usr/bin/pt-archiver line 6829.

---

<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:** [June 10, 2025, 2:13pm UTC](https://forums.percona.com/t/percona-toolkit-3-6-0-compatibility-with-mariadb-servier-11-4-4-enterprise/38249/4 "2025-06-10T14:13:28Z")

</div>

Check your quotes please. You may need to escape inner quotation marks, or use single quotes inside double quotes.

---

<div class="post-metadata">

**Author:** ![jlaur2161](https://avatars.discourse-cdn.com/v4/letter/j/7bcc69/32.png) [@jlaur2161](https://forums.percona.com/u/jlaur2161)\
**Post date:** [June 10, 2025, 4:16pm UTC](https://forums.percona.com/t/percona-toolkit-3-6-0-compatibility-with-mariadb-servier-11-4-4-enterprise/38249/5 "2025-06-10T16:16:12Z")

</div>

I’ll double check them thanks.

---

<div class="post-metadata">

**Author:** ![Evgeniy\_Patlan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/evgeniy_patlan/32/41_2.png) [@Evgeniy\_Patlan](https://forums.percona.com/u/Evgeniy_Patlan)\
**Post date:** [June 11, 2025, 12:35pm UTC](https://forums.percona.com/t/percona-toolkit-3-6-0-compatibility-with-mariadb-servier-11-4-4-enterprise/38249/6 "2025-06-11T12:35:37Z")

</div>

Also I would recommend using the latest version of toolkit from our repositories.

---

<div class="post-metadata">

**Author:** ![jlaur2161](https://avatars.discourse-cdn.com/v4/letter/j/7bcc69/32.png) [@jlaur2161](https://forums.percona.com/u/jlaur2161)\
**Post date:** [June 12, 2025, 8:28pm UTC](https://forums.percona.com/t/percona-toolkit-3-6-0-compatibility-with-mariadb-servier-11-4-4-enterprise/38249/7 "2025-06-12T20:28:11Z")

</div>

Right now both servers are running 3.6.0. That’s why I am wondering if the new MariaDB doesn’t work well with it?

---

<div class="post-metadata">

**Author:** ![jlaur2161](https://avatars.discourse-cdn.com/v4/letter/j/7bcc69/32.png) [@jlaur2161](https://forums.percona.com/u/jlaur2161)\
**Post date:** [June 13, 2025, 2:06pm UTC](https://forums.percona.com/t/percona-toolkit-3-6-0-compatibility-with-mariadb-servier-11-4-4-enterprise/38249/8 "2025-06-13T14:06:24Z")

</div>

I patched the server running MariaDB 11.4 to toolkit 3.7.0 and everything is working again. Just a good to know for everyone else in this situation. Thanks for the help!