| Bug #107100 | mysqldbcompare ERROR: Comparing the same object on the same server. | ||
|---|---|---|---|
| Submitted: | 22 Apr 2022 11:42 | Modified: | 28 Apr 2022 11:57 |
| Reporter: | cheri Aeril | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Utilities | Severity: | S3 (Non-critical) |
| Version: | 1.6.5 | OS: | CentOS |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | mysqldbcompare | ||
[28 Apr 2022 11:57]
MySQL Verification Team
Hello, Thank you for the bug report. Imho this is duplicate of Bug #85347, please see Bug #85347. Regards, Ashwini Patil
Description: [root@localhost ~]# mysqldbcompare --server1=root:'Bocom_123'@10.19.76.19 --server2=root:'Bocom_123456'@10.19.76.144 --all --run-all-test --changes-for=server2 --difftype=sql --skip-data-check --skip-row-count # WARNING: Using a password on the command line interface can be insecure. # server1 on 10.19.76.19: ... connected. # server2 on 10.19.76.144: ... connected. ERROR: Specified servers are the same (server1=10.19.76.19:3306 and server2=10.19.76.144:3306). Cannot compare all databases on the same server. When the --all parameter is used to compare two MySQL databases with different IP addresses, the following error is prompted: I've tried many times and I'm not sure if there's a problem with the way I use it. How to repeat: See description. Suggested fix: List the different databases and tables in Server1 library and server2 library