# pt-table-checksum not working as supposed in mixed format replication

**URL:** <https://forums.percona.com/t/pt-table-checksum-not-working-as-supposed-in-mixed-format-replication/5939>\
**Category:** Percona Toolkit\
**Created:** [October 17, 2017, 9:41am UTC](https://forums.percona.com/t/pt-table-checksum-not-working-as-supposed-in-mixed-format-replication/5939 "2017-10-17T09:41:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![marba](https://avatars.discourse-cdn.com/v4/letter/m/8baadc/32.png) [@marba](https://forums.percona.com/u/marba)\
**Post date:** [October 17, 2017, 9:41am UTC](https://forums.percona.com/t/pt-table-checksum-not-working-as-supposed-in-mixed-format-replication/5939/1 "2017-10-17T09:41:58Z")

</div>

I had set up a master-slave with MariaDb 10.0 percona-toolkit-3.0.4 and i had config replication format = Mixed, it worked until some days ago when it stopped finding any difference, even missing rows…  
Today I discovered i have to specify --set-vars binlog\_format=STATEMENT to make it work again.  
I think this is different from what is described in the last documentation.

Hope this can help someone else.  
Ciao  
Marco

---

<div class="post-metadata">

**Author:** ![mirfan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mirfan/32/16890_2.png) [@mirfan](https://forums.percona.com/u/mirfan)\
**Post date:** [October 26, 2017, 12:22am UTC](https://forums.percona.com/t/pt-table-checksum-not-working-as-supposed-in-mixed-format-replication/5939/2 "2017-10-26T00:22:05Z")

</div>

How does your replication topology look likes ? Do you have intermediate master too e.g. M1 → S1 → S2 ?  
pt-table-checksum set STATEMENT based binlog\_format on session level and underlying slave(s) receives checksum queries in STATEMENT level too to do the checksum.

---

<div class="post-metadata">

**Author:** ![tanj13](https://avatars.discourse-cdn.com/v4/letter/t/7feea3/32.png) [@tanj13](https://forums.percona.com/u/tanj13)\
**Post date:** [December 7, 2017, 8:27pm UTC](https://forums.percona.com/t/pt-table-checksum-not-working-as-supposed-in-mixed-format-replication/5939/3 "2017-12-07T20:27:46Z")

</div>

> [@mirfan;49942](#):
>
> How does your replication topology look likes ? Do you have intermediate master too e.g. M1 → S1 → S2 ?  
> pt-table-checksum set STATEMENT based binlog\_format on session level and underlying slave(s) receives checksum queries in STATEMENT level too to do the checksum.

how to deal with AWS RDS for MySQL which doesn’t provide the SUPER privilege?

---

<div class="post-metadata">

**Author:** ![carlos.salguero](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/carlos.salguero/32/20_2.png) [@carlos.salguero](https://forums.percona.com/u/carlos.salguero)\
**Post date:** [December 7, 2017, 8:44pm UTC](https://forums.percona.com/t/pt-table-checksum-not-working-as-supposed-in-mixed-format-replication/5939/4 "2017-12-07T20:44:03Z")

</div>

The issue was fixed in Percona Toolkit 3.0.5

---

<div class="post-metadata">

**Author:** ![tanj13](https://avatars.discourse-cdn.com/v4/letter/t/7feea3/32.png) [@tanj13](https://forums.percona.com/u/tanj13)\
**Post date:** [December 8, 2017, 2:20am UTC](https://forums.percona.com/t/pt-table-checksum-not-working-as-supposed-in-mixed-format-replication/5939/5 "2017-12-08T02:20:04Z")

</div>

> [@carlos.salguero;50281](#):
>
> The issue was fixed in Percona Toolkit 3.0.5

12-08T15:49:03 Failed to /_!50108 SET @@binlog\_format := ‘STATEMENT’_/: DBD::mysql::db do failed: Access denied; you need (at least one of) the SUPER privilege(s) for this operation [for Statement “/_!50108 SET @@binlog\_format := ‘STATEMENT’_/”] at ./pt-table-checksum line 9403.

This tool requires binlog\_format=STATEMENT, but the current binlog\_format is set to MIXED and an error occurred while attempting to change it. If running MySQL 5.1.29 or newer, setting binlog\_format requires the SUPER privilege. You will need to manually set binlog\_format to ‘STATEMENT’ before running this tool.  
[root@ip-172-0-27-13 bin]# ./pt-table-checksum --version  
pt-table-checksum 3.0.5

it’s still failed againt AWS RDS per the above message
