Documentation Home
MySQL Utilities Release Notes
Download these Release Notes
PDF (US Ltr) - 224.3Kb
PDF (A4) - 225.9Kb

MySQL Utilities Release Notes  /  Changes in Release 1.0  /  Changes in MySQL Utilities 1.0.5 (2012-04-10)

Changes in MySQL Utilities 1.0.5 (2012-04-10)

This section documents all changes and bug fixes applied since the release of 1.0.4.

Functionality Added or Changed

  • It is now possible for the mysqlserverclone utility to clone a downed server. Before, it was only able to clone a running server. (Bug #13698224)

  • Arguments for the utilities are no longer case-sensitive. And arguments now accept prefixed values, such as g or gr representing grid when passed to --format.

    The --format and --help arguments have been standardized across all utilities. And as such, -h no longer represents --help. (Bug #13554556)

  • Added the mysqlfailover utility, which provides replication health monitoring. It relies on Global Transaction Identifiers (GTIDs) so requires MySQL Server 5.6.5 or greater.

  • Added the mysqlrpladmin utility, which allows administration and recovery of the replication topology.

  • Added replication support to the mysqldbexport, mysqldbimport, and mysqldbcopy utilities.

    This adds the following options to the mysqldbexport and mysqldbcopy utilities: --rpl, --rpl-file, --rpl-user, and --comment-rpl. And adds the --skip-rpl option to the mysqldbimport utility.

Bugs Fixed

  • The mysqlserverinfo utility failed when used with an offline version of MySQL Server 5.6. (Bug #13916903)

  • The following utilities would not always exit properly, when executed from within MySQL Workbench: mysqlindexcheck, mysqlmetagrep, mysqlprocgrep, mysqlreplicate, mysqlrplcheck, mysqlrplshow, mysqlserverclone. (Bug #13721467)

  • The MySQL Utilities Testing tool (mut) --sorted option had no function. It now accepts either asc or desc, with asc remaining the default. (Bug #13592147)

  • The --copy-dir option was removed from the mysqluserclone and mysqldbcopy utilities. (Bug #13576571)

  • When executing a diff operation with the mysqldiff utility on a single server between two databases with missing objects, an invalid warning would be issued that did not show the correct servers involved. (Bug #13554750)