Hello *,

I'm trying to use mk-table-checksum in a situation where a slave does
not have all the databases from the master:

Master has: DB1, DB2, DB3

Slave1 has: DB1

Slave2 hasB1, DB2, DB3

So slave1 doesn't have all the databases. A regular check fails:

../mk-table-checksum --replicate=test.tjeksom h=Master -uUsername -
pPassword

give the following output:

Cannot checksum with --replicate because replication filters are set
on these hosts:
replicate_do_db = DB1
Please read the --check-replication-filters documentation to learn how
to solve this problem. at ./mk-table-checksum line 5428.

some documentation cascade:

--[no]check-replication-filters
default: yes; group: Safety

Do not "--replicate" if any replication filters are set. When --
replicate is specified, mk-table-checksum tries to detect slaves and
look for options that filter replication, such as binlog_ignore_db and
replicate_do_db. If it finds any such filters, it aborts with an
error. Replication filtering makes it impossible to be sure that the
checksum queries wonât break replication or simply fail to replicate.
If you are sure that itâs OK to run the checksum queries, you can
negate this option to disable the checks. See also "--replicate-
database".


--replicate-database
type: string

"USE" only this database with "--replicate". By default,
mk-table-checksum executes USE to set its default database to the
database that contains the table itâs currently working on. It
changes its default database as it works on different tables. This is
is a best effort to avoid problems with replication filters such as
inlog_ignore_db and replicate_ignore_db. However, replication filters
can create a situation where there simply is no one right way to do
things. Some statements might not be replicated, and others might
cause replication to fail on the slaves. In such cases, it is up to
the user to specify a safe default database. This option specifies a
default database that mk-table-checksum selects with USE, and never
changes afterwards. See also <L"--[no]check-replication-filters">.

the just-see-what-happens-try:

../mk-table-checksum --replicate=test.checksumtab --create-replicate-
table --nocheck-replication-filters --databases=DB1 h=MASTER -uUsename
-pPasword

now the command say that it waited for the slaves to catch up - i
waited for 30 minutes before i checked the slaves for activity. Slave1
got a replication table, but slave 2 didn't get that. User and
permissions are the same on the 3 hosts.( copy & pasted the create
commands)

How to synchronise the databases?
TIA,
Willem