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!
@jlaur2161 Please check Jira - Percona JIRA 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.
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.
Check your quotes please. You may need to escape inner quotation marks, or use single quotes inside double quotes.
I’ll double check them thanks.
Also I would recommend using the latest version of toolkit from our repositories.
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?