# Pt-table-checksum causing error 4164

**URL:** <https://forums.percona.com/t/pt-table-checksum-causing-error-4164/29276>\
**Category:** Percona Toolkit\
**Created:** [March 21, 2024, 2:31pm UTC](https://forums.percona.com/t/pt-table-checksum-causing-error-4164/29276 "2024-03-21T14:31:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jason\_Stratford](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jason_stratford/32/13225_2.png) [@Jason\_Stratford](https://forums.percona.com/u/Jason_Stratford)\
**Post date:** [March 21, 2024, 2:31pm UTC](https://forums.percona.com/t/pt-table-checksum-causing-error-4164/29276/1 "2024-03-21T14:31:43Z")

</div>

Hi all,

I’m running into some sort of strange issue when running **pt-table-checksum**. For all checksum queries it is spitting out an error as below…

```auto
03-21T14:08:48 Error checksumming table InstantService.High: Error executing checksum query: Checksum query for table InstantService.High caused MySQL error 4164:
    Level: Warning
     Code: 4164
  Message: Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.
    Query: REPLACE INTO `percona`.`checksums` (db, tbl, chunk, chunk_index, lower_boundary, upper_boundary, this_cnt, this_crc) SELECT /*!99997*/ ?, ?, ?, ?, ?, ?, COUNT(*) AS cnt, COALESCE(LOWER(CONV(BIT_XOR(CAST(CRC32(CONCAT_WS('#', CRC32(`engineconfig_id`), convert(`prize` using utf8mb4))) AS UNSIGNED)), 10, 16)), 0) AS crc FROM `InstantService`.`High` /*checksum table*/

```

Toolkit version is percona-toolkit-3.5.7-1.el8.x86\_64  
Server version is percona-xtradb-cluster-8.0.35-27.1.el8.x86\_64

It is saying it is a Warning level, but I am not sure if the checksum actually still being done?

Many thanks  
Jason

---

<div class="post-metadata">

**Author:** ![Denis\_Subbota](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/denis_subbota/32/23607_2.png) [@Denis\_Subbota](https://forums.percona.com/u/Denis_Subbota)\
**Post date:** [March 25, 2024, 8:34am UTC](https://forums.percona.com/t/pt-table-checksum-causing-error-4164/29276/2 "2024-03-25T08:34:21Z")

</div>

Hello [Jason\_Stratford](https://forums.percona.com/u/Jason_Stratford),  
As per MySQL documentation, this kind of change implemented after 8.0.34

[https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html](https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html)  
Error number: `4164`; Symbol: [`ER_WARN_NO_SPACE_VERSION_COMMENT`](https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html#error_er_warn_no_space_version_comment); SQLSTATE: `HY000`

Message: Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.

[`ER_WARN_NO_SPACE_VERSION_COMMENT`](https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html#error_er_warn_no_space_version_comment) was added in 8.0.34.

For example, if your SQL statement includes a version comment like this:

```auto
/*!50505 SET @@SESSION.PSEUDO_SLAVE_MODE=1*/;

```

You should modify it to include a white-space character after the version number, like this:

```auto
/*! 50505 SET @@SESSION.PSEUDO_SLAVE_MODE=1*/;

```

Warning messages should not cause issues with pt-table-checksum execution, so I expect that your pt-table-checksum is completed well.

Regards,  
Denis Subbota.  
Managed Services, Percona.