# Pt-table-sync does not sync table when schema and table name are the same

**URL:** <https://forums.percona.com/t/pt-table-sync-does-not-sync-table-when-schema-and-table-name-are-the-same/7450>\
**Category:** Percona Toolkit\
**Created:** [March 2, 2020, 7:55am UTC](https://forums.percona.com/t/pt-table-sync-does-not-sync-table-when-schema-and-table-name-are-the-same/7450 "2020-03-02T07:55:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![makarono](https://avatars.discourse-cdn.com/v4/letter/m/6a8cbe/32.png) [@makarono](https://forums.percona.com/u/makarono)\
**Post date:** [March 2, 2020, 7:55am UTC](https://forums.percona.com/t/pt-table-sync-does-not-sync-table-when-schema-and-table-name-are-the-same/7450/1 "2020-03-02T07:55:46Z")

</div>

pt-table-sync does not sync table when schema and table name are the same

this is my command:

```auto
PTDEBUG=1 pt-table-sync --execute --lock 0 --chunk-size 1000 --verbose --nocheck-triggers --no-foreign-key-checks --no-check-child-tables --databases tokens --tables tokens h=192.168.2.2,u=xxx,p=xxx h=192.168.2.3;

```

this is debug output:

```auto
# SchemaIterator:7853 20796 Found 1 databases
# SchemaIterator:7860 20796 Next database: tokens
# SchemaIterator:7866 20796 SHOW /*!50002 FULL*/ TABLES FROM `tokens`
# SchemaIterator:7997 20796 Table summary_status_report is not in --tables list, ignoring
# SchemaIterator:8012 20796 Table tokens is only allowed in database HASH(0x55e119d76e78)

```

---

<div class="post-metadata">

**Author:** ![Michael\_Coburn](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/michael_coburn/32/18_2.png) [@Michael\_Coburn](https://forums.percona.com/u/Michael_Coburn)\
**Post date:** [February 12, 2021, 7:05pm UTC](https://forums.percona.com/t/pt-table-sync-does-not-sync-table-when-schema-and-table-name-are-the-same/7450/2 "2021-02-12T19:05:22Z")

</div>

Hi @makarono - thanks for posting, and apologies for the tardy reply. Can you provide us with the `SHOW CREATE TABLE` for the tables? If this is reproducible then we ought to file a bug in the Percona Toolkit project:  
[https://jira.percona.com/projects/PT](https://jira.percona.com/projects/PT)
