Bug #85347 mysqldbcompare gives ERROR: Comparing the same object on the same server

• Submitted: 7 Mar 2017 18:01
• Modified: 8 Mar 2017 6:31
• Reporter: David Wasson
• Status: Verified
• Category: MySQL Utilities
• Severity: S1 (Critical)
• Version: 1.6.5
• OS: Any
• CPU Architecture: Any

[7 Mar 2017 18:01] David Wasson

Description:
C:\Program Files (x86)\MySQL\MySQL Workbench 6.3 CE>mysqldbcompare --server1=root:XXXXX@192.168.1.174:3306 --server2=root:XXXXX@192.168.1.170:3306 -a
# WARNING: Using a password on the command line interface can be insecure.
# server1 on 192.168.1.174: ... connected.
# server2 on 192.168.1.170: ... connected.
ERROR: Comparing the same object on the same server.

Occurs if I use localhost or 127.0.0.1 or network IP for server2

Occurs with specifying the schema names and with -t

How to repeat:
Have two DBs on two different machines and run the command as shown above

[8 Mar 2017 6:31] Chiranjeevi Battula

Hello David Wasson,

Thank you for the bug report.

Thanks,
Chiranjeevi.

[8 Mar 2017 6:31] Chiranjeevi Battula

mysqluc> mysqldbcompare --server1=root:chiran@localhost:5717 --server2=root:chiran@localhost:5717 test:test
# WARNING: Using a password on the command line interface can be insecure.
# server1 on localhost: ... connected.
# server2 on localhost: ... connected.
ERROR: Comparing the same object on the same server.

[28 Apr 2022 11:57] MySQL Verification Team

Bug #107100 marked as duplicate of this one.

[29 Apr 2022 3:05] cheri Aeril

Hello,
Dear Ashwini Patil

This is a temporary solution:
Ensure that the IP of the server running mysqldiff tool is inconsistent with that of Server1.