Precise Instantiation for MySQL to MySQL Replication Using the Dump Utility
For MySQL, the precise instantiation is only valid from MySQL to MySQL and not on non-MySQL database sources and targets.
The precise instantiation in MySQL can be achieved using the dump utility of MySQL shell, and not using the OGG initial load. MySQL shell provides utilities to dump an instance, schema or tables. See the following link for details about the dump utility:
https://dev.mysql.com/doc/mysql-shell/8.0/en/mysql-shell-utilities-dump-instance-schema.html
dump utility util.dumpInstance()
to dump
or export the source MySQL database.
Note:
Thedump utility
util.dumpInstance()
is different from
mysqldump
.
The dump utility creates multiple files. The position of the last committed record is
found in the @.json file
. This file contains both
lognumber
/offset
and the gtid
set for the last committed transaction.
An example position in the @.json
file looks similar to the
following:
"binlogFile": "binlog.000005",
"binlogPosition": 1289,
"gtidExecuted": "1174b383-3441-11e8-b90a-c80aa9429920:1-9,\n1174b383-3441-11e8-b90a-c80aa9429921:1-9"