254
MySQL Utilities
MySQL Utilities
Abstract
This is the MySQL™ Utilities Reference Manual. It documents both the GPL and commercial editions of the MySQLUtilities 1.6 release series through 1.6.4.
If you have not yet installed MySQL Utilities please download your free copy from the download site. MySQL Utilitiesis available for Windows, OS X, and Linux variants.
For notes detailing the changes in each release, see the MySQL Utilities Release Notes.
For legal information, see the Legal Notices.
For help with using MySQL, please visit either the MySQL Forums or MySQL Mailing Lists, where you can discussyour issues with other MySQL users.
Licensing information. This product may include third-party software, used under license. If you are using aCommercial release of MySQL Utilities, see the MySQL Utilities Commercial License Information User Manual forlicensing information, including licensing information relating to third-party software that may be included in thisCommercial release. If you are using a Community release of MySQL Utilities, see the MySQL Utilities CommunityLicense Information User Manual for licensing information, including licensing information relating to third-partysoftware that may be included in this Community release.
Document generated on: 2018-06-22 (revision: 57811)
iii
Table of ContentsPreface .............................................................................................................................................. v1 How to Install MySQL Utilities .......................................................................................................... 1
1.1 Prerequisites ........................................................................................................................ 11.2 Source Code ........................................................................................................................ 11.3 Oracle Linux and Red Hat Linux 6 ........................................................................................ 21.4 Debian Linux ........................................................................................................................ 21.5 Microsoft Windows ............................................................................................................... 31.6 OS X ................................................................................................................................... 3
2 Introduction ..................................................................................................................................... 52.1 Introduction to MySQL Utilities .............................................................................................. 52.2 Connecting to MySQL Servers .............................................................................................. 6
2.2.1 Connection Parameters .............................................................................................. 62.2.2 Specifying Connections in Python Library .................................................................. 102.2.3 Specifying User and Password for Replication Options .............................................. 10
3 MySQL Utilities Administrative Tasks ............................................................................................. 133.1 Binary Log Operations ........................................................................................................ 14
3.1.1 How do you change the location of the binary log files? ............................................. 143.1.2 How do you purge obsolete binary log files safely? .................................................... 15
3.2 Database Operations .......................................................................................................... 173.2.1 How do you provision a slave? ................................................................................. 173.2.2 How do you make a copy of a database on the same server? .................................... 183.2.3 How can you make a copy of a database and change the storage engine? .................. 203.2.4 How do you tell if a table on server A has the same structure as the same table onserver B? ......................................................................................................................... 213.2.5 How do you synchronize a table on two servers where neither is up-to-date? ............... 22
3.3 General Operations ............................................................................................................ 233.3.1 How do you know how much space your data uses? ................................................. 243.3.2 How do you recover the CREATE statement from a damaged or offline server? ........... 253.3.3 How do you create a new user with the same privileges as another user? ................... 273.3.4 Is there an easy way to know what options are used with each utility? ........................ 283.3.5 How do you find redundant or duplicate indexes and know which ones to drop? ........... 313.3.6 How do you find all objects that start with a given name prefix? .................................. 333.3.7 How do you run a process every night to kill certain connections? .............................. 34
3.4 High Availability Operations ................................................................................................. 353.4.1 How do you setup and use replication? .................................................................... 363.4.2 How do you add new servers to an existing topology and change the master role? ....... 383.4.3 How do you setup and use automatic failover? ......................................................... 403.4.4 How do you restore the previous master to service after failover? ............................... 433.4.5 How do you find all of the slaves attached to a master server? ................................... 463.4.6 How Can you determine if data was replicated correctly? ........................................... 473.4.7 How do you fix errant transactions on the replication topology? .................................. 49
3.5 Server Operations .............................................................................................................. 513.5.1 How can you create a temporary copy (running instance) of a server for testing? ......... 513.5.2 How do you find what MySQL servers are running on a local machine? ...................... 533.5.3 How do you setup and use a secure (encrypted) connection between Utilities and aMySQL server? ................................................................................................................ 54
3.6 Specialized Operations ....................................................................................................... 583.6.1 How do you record only login events in the audit log? ............................................... 583.6.2 How do you copy or move the audit log? .................................................................. 603.6.3 How can you find the INSERT and UPDATE queries that failed in the audit log? .......... 61
MySQL Utilities
iv
3.6.4 How do you find connections by the user 'root' in the audit log and show the resultsin CSV format? ................................................................................................................ 62
4 Overview of MySQL Utilities .......................................................................................................... 654.1 Binary Log Operations ........................................................................................................ 654.2 Database Operations .......................................................................................................... 654.3 General Operations ............................................................................................................ 664.4 High Availability Operations ................................................................................................. 674.5 Server Operations .............................................................................................................. 684.6 Specialized Operations ....................................................................................................... 68
5 Manual Pages ............................................................................................................................... 695.1 mysqlauditadmin — Allows users to perform maintenance actions on the audit log ............. 695.2 mysqlauditgrep — Allows users to search the current or an archived audit log ................... 755.3 mysqlbinlogmove — Binary log relocate utility .................................................................. 825.4 mysqlbinlogpurge — Binary log purge utility ................................................................... 895.5 mysqlbinlogrotate — Binary log rotate utility ................................................................. 925.6 mysqldbcompare — Compare Two Databases and Identify Differences ............................... 945.7 mysqldbcopy — Copy Database Objects Between Servers ............................................... 1035.8 mysqldbexport — Export Object Definitions or Data from a Database .............................. 1105.9 mysqldbimport — Import Object Definitions or Data into a Database ................................ 1195.10 mysqldiff — Identify Differences Among Database Objects ........................................... 1255.11 mysqldiskusage — Show Database Disk Usage ........................................................... 1315.12 mysqlfailover — Automatic replication health monitoring and failover ........................... 1345.13 mysqlfrm — File reader for .frm files. ............................................................................. 1465.14 mysqlgrants — Display grants by object ....................................................................... 1505.15 mysqlindexcheck — Identify Potentially Redundant Table Indexes ................................ 1575.16 mysqlmetagrep — Search Database Object Definitions .................................................. 1605.17 mysqlprocgrep — Search Server Process Lists ............................................................ 1655.18 mysqlreplicate — Set Up and Start Replication Between Two Servers ......................... 1695.19 mysqlrplms — Set Up and Start Replication from a Slave to Multiple Masters .................. 1735.20 mysqlrpladmin — Administration utility for MySQL replication ........................................ 1785.21 mysqlrplcheck — Check Replication Prerequisites ....................................................... 1905.22 mysqlrplshow — Show Slaves for Master Server .......................................................... 1945.23 mysqlrplsync — Replication synchronization checker ................................................... 1995.24 mysqlserverclone — Clone Existing Server to Create New Server ............................... 2065.25 mysqlserverinfo — Display Common Diagnostic Information from a Server .................. 2095.26 mysqlslavetrx — Slave transaction skip utility ............................................................. 2135.27 mysqluc — Command line client for running MySQL Utilities ........................................... 2165.28 mysqluserclone — Clone Existing User to Create New User ......................................... 220
6 Extending MySQL Utilities ............................................................................................................ 2256.1 Introduction to extending the MySQL Utilities ..................................................................... 2256.2 MySQL Utilities copy_server.py sample ............................................................................. 2316.3 Specialized Operations ..................................................................................................... 234
6.3.1 mysql.utilities.command.grep — Search Databases for Objects .................... 2346.3.2 mysql.utilities.command.proc — Search Processes on Servers .................... 235
6.4 Parsers ............................................................................................................................ 2376.4.1 mysql.utilities.parser — Parse MySQL Log Files ...................................................... 237
7 MySQL Utilities Testing (MUT) ..................................................................................................... 2417.1 mut — MySQL Utilities Testing ......................................................................................... 241
8 Appendix ..................................................................................................................................... 2458.1 MySQL Utilities Frequently Asked Questions ...................................................................... 245
Index .............................................................................................................................................. 247
v
PrefaceThis is the User Manual for the MySQL Utilities.
MySQL Utilities is both a set of command-line utilities as well as a Python library for making commonDevOps tasks easy to accomplish. The library is written entirely in Python, meaning that it is not necessaryto have any other tools or libraries installed to make it work. It is currently designed to work with Pythonv2.6 or later and there is no support (yet) for Python v3.1.
Layout
This manual is arranged in an order designed to provide a quick reference for how to use MySQL Utilities.It begins with a brief introduction of MySQL Utilities then presents a list of common administration taskswith examples of how utilities can be used to perform the tasks. From there, the manual begins a deeperdive into the utilities starting with overviews of each utility leading to a detailed description of each via amanual page format. Thus, the manual provides a documentation solution for several needs.
How to Use This Manual
You can use this manual to get a quick solution to an administrative task complete with explanation ofhow to run the utilities involved and the options and parameters needed. See the tasks chapter for thisinformation.
You can use the manual to learn what utilities exist and how each fits into your own administrative needs.See the utility overview chapter for this information.
You can also use the manual to get more information about each utility and what each option andparameter does via the manuals section.
The manual concludes with a look at extending the MySQL Utilities library, a look at the developer testingenvironment, and a list of frequently asked questions.
Legal Notices
Copyright © 2006, 2018, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictionson use and disclosure and are protected by intellectual property laws. Except as expressly permittedin your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast,modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by anymeans. Reverse engineering, disassembly, or decompilation of this software, unless required by law forinteroperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing iton behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,any programs installed on the hardware, and/or documentation, delivered to U.S. Government end usersare "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of theprograms, including any operating system, integrated software, any programs installed on the hardware,
Documentation Accessibility
vi
and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information managementapplications. It is not developed or intended for use in any inherently dangerous applications, includingapplications that may create a risk of personal injury. If you use this software or hardware in dangerousapplications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and othermeasures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damagescaused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarksof their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarksare used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of AdvancedMicro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content,products, and services from third parties. Oracle Corporation and its affiliates are not responsible for andexpressly disclaim all warranties of any kind with respect to third-party content, products, and servicesunless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and itsaffiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use ofthird-party content, products, or services, except as set forth in an applicable agreement between you andOracle.
This documentation is NOT distributed under a GPL license. Use of this documentation is subject to thefollowing terms:
You may create a printed copy of this documentation solely for your own personal use. Conversion to otherformats is allowed as long as the actual content is not altered or edited in any way. You shall not publishor distribute this documentation in any form or on any media, except if you distribute the documentation ina manner similar to how Oracle disseminates it (that is, electronically for download on a Web site with thesoftware) or on a CD-ROM or similar medium, provided however that the documentation is disseminatedtogether with the software on the same medium. Any other use, such as any dissemination of printedcopies or use of this documentation, in whole or in part, in another publication, requires the prior writtenconsent from an authorized representative of Oracle. Oracle and/or its affiliates reserve any and all rightsto this documentation not expressly granted above.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program websiteathttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My OracleSupport. For information, visithttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
1
Chapter 1 How to Install MySQL Utilities
Table of Contents1.1 Prerequisites ................................................................................................................................ 11.2 Source Code ................................................................................................................................ 11.3 Oracle Linux and Red Hat Linux 6 ................................................................................................ 21.4 Debian Linux ................................................................................................................................ 21.5 Microsoft Windows ....................................................................................................................... 31.6 OS X ........................................................................................................................................... 3
MySQL Utilities is available in a number of repository formats. Although you may not see your specificoperating system or platform listed, we provide general repository formats for most platforms. If none of theavailable repositories are applicable to your platform, you can use the source code repository and installMySQL Utilities from the command line.
The latest MySQL Utilities downloads are available at http://dev.mysql.com/downloads/utilities/1.6.html.The following sections discuss each repository.
1.1 PrerequisitesMySQL Utilities requires Python 2.6. All of the Python code is written to conform to this version of Python.
For connecting to MySQL, MySQL Utilities requires a MySQL Connector/Python General Availability (GA)release (version 2.0.4/2.1.2 or later). If you do not have Connector/Python installed, see the downloadsection for Connector/Python to download the appropriate repository.
MySQL Utilities also requires the Visual C++ Redistributable for Visual Studio 2013 (available at theMicrosoft Download Center) to work.
1.2 Source CodeThe source code repository for MySQL Utilities includes all of the utility code as well as the MySQL Utilitieslibrary and manual pages. It is available as an architecture independent distribution, in either Zip archiveformat (.zip file) or compressed tar archive format (.tar.gz file), or as a RPM package (.rpm file).
You can use this repository to install on any platform that has Python 2.6 installed. For example, you canuse the .tar.gz version of the repository to install MySQL Utilities on OS X or Ubuntu. Choose "Linux -Generic" from the download page, and then the file name similar to mysql-utilities-1.6.4.tar.gz.
After you download and unpack the repository distribution, open a terminal window and navigate to thedirectory containing the file. Then unpack the file and install MySQL Utilities using the setup.py script asshown below.
shell> unzip mysql-utilities-1.6.4.zipshell> cd mysql-utilities-1.6.4shell> python ./setup.py buildshell> sudo python ./setup.py install
Note
Using this repository requires that you have Connector/Python installed or install itseparately. For additional information, see Section 1.1, “Prerequisites”.
Oracle Linux and Red Hat Linux 6
2
The source code is also available as a .rpm package, which can be downloaded and uncompressed asfollows. More specifically, we first unpack the .rpm package then unzip the resulting .zip file.
On Mac and some Unix systems, you can use these commands.
shell> tar -tzvf mysql-utilities-1.6.4-1.el7.src.rpmshell> tar -xzvf mysql-utilities-1.6.4-1.el7.src.rpmshell> unzip mysql-utilities-1.6.4.zip
On Linux systems without native .rpm support, you can use these commands. For example, you can installrpm2cpio then run that utility to extract the .zip file then unzip it.
shell> sudo apt-get install rpm2cpioshell> rpm2cpio mysql-utilities-1.6.4-1.el7.src.rpm | cpio -i --make-directoriesshell> unzip mysql-utilities-1.6.4.zip
If these commands do not work for your platform, check your platform documentation for ways to open andinspect .rpm files.
1.3 Oracle Linux and Red Hat Linux 6This repository is available as an architecture-independent RPM package (.rpm file).
After you download the package, install it using the following command or similar depending on yourplatform configuration:
shell> sudo rpm -i mysql-utilities-1.6.4-el6.noarch.rpm
You can also use the RPM package manager that is part of your base operating system. See youroperating system documentation for more details.
Note
MySQL Utilities requires Connector/Python to be installed. For additionalinformation, see Section 1.1, “Prerequisites”.
1.4 Debian LinuxThe .deb repository is built for Debian 6 and is architecture independent. Although built expressly forDebian 6, it can be installed on various ports such as amd64, i386, etc.
Note
The repository does not work for Debian 7 because MySQL Utilities requires Python2.6 and Debian 7 currently ships with Python 2.7. For Debian 7, use the sourcecode repository to install MySQL Utilities.
After you download the file, install it using the following command or similar depending on your specificrelease or version of Debian:
shell> sudo dpkg -i mysql-utilities-1.6.4-debian6.0_all.deb
Note
MySQL Utilities requires Connector/Python to be installed. For additionalinformation, see Section 1.1, “Prerequisites”.
Microsoft Windows
3
1.5 Microsoft Windows
Either install MySQL Utilities using the MySQL Installer for Windows (a system that manages installationsand updates for all MySQL products on Windows), or download and execute the standalone file.
Note
• MySQL Utilities requires Connector/Python and the Visual C++ Redistributablefor Visual Studio 2013 to be installed. For additional information, see Section 1.1,“Prerequisites”.
• MySQL Installer: Download and execute the MySQL Installer MSI file. Select the MySQL Utilitiesproduct and then proceed with the installation. This is the recommended approach, and automaticallyselects and installs the required prerequisites. See the MySQL Installer manual for additional details.
• Standalone: Download and execute the MySQL Utilities standalone MSI file.
1.6 OS X
The .dmg file available for OS X is built for x84-64 bit platforms, and supports OS X version 10.7 (Lion)and newer.
After you download the .dmg file, install MySQL Utilities by opening it and double clicking the .pkg file.
Note
MySQL Utilities requires Connector/Python to be installed. For additionalinformation, see Section 1.1, “Prerequisites”.
4
5
Chapter 2 Introduction
Table of Contents2.1 Introduction to MySQL Utilities ...................................................................................................... 52.2 Connecting to MySQL Servers ...................................................................................................... 6
2.2.1 Connection Parameters ...................................................................................................... 62.2.2 Specifying Connections in Python Library ......................................................................... 102.2.3 Specifying User and Password for Replication Options ...................................................... 10
This chapter introduces MySQL Utilities and presents information on how to access and download MySQLUtilities. It also includes the basics of how to use the account login option common to all utilities.
2.1 Introduction to MySQL Utilities
What are the MySQL Utilities?
It is a package of utilities that are used for maintenance and administration of MySQL servers. Theseutilities encapsulate a set of primitive commands, and bundles them so they can be used to perform macrooperations with a single command.
The utilities are written in Python, available under the GPLv2 license, and are extensible using the suppliedlibrary. They are designed to work with Python versions 2.6 or later and there is no support (yet) for Pythonv3.1.
How do we access the MySQL Utilities?
The MySQL Utilities are command line scripts, which by default are available in your system's PATH.Alternatively, if both MySQL Utilities and MySQL Workbench are installed, you can access their locationfrom MySQL Workbench by selecting Tools from the main menu, and then Start Shell for MySQLUtilities. This opens a terminal/shell window in the mysqluc utility shell. Type "help" to list the availablecommands.
Connecting to MySQL Servers
6
Figure 2.1 Starting MySQL Utilities from Workbench
You can launch any of the utilities listed by typing the name of the command. To find out what options areavailable, use the option, or read the appropriate manual page.
The utilities are designed to work on MySQL systems with grants enabled but can also operate on serversstarted with the --skip-grant-tables startup option. However, this practice is strongly discouragedand should be used only in situations where it is appropriate or deemed a last resort.
2.2 Connecting to MySQL Servers
This section describes the ways you can connect to a MySQL server via a MySQL Utility or via the MySQLUtilities library methods.
2.2.1 Connection Parameters
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server,--master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
Connection Parameters
7
2.2.1.1 Use login-paths (.mylogin.cnf)
The best way to specify server connection information is with your .mylogin.cnf file. Not only is this fileencrypted, but any logging of the utility execution does not expose the connection information. Thus, nouser names, passwords, ports, etc. are visible in the log. This is the preferred method for using MySQLUtilities to connect to servers.
Utilities support the use of login-paths in the connection string provided they use the following format login-path-name[:port][:socket] where the port and socket parameters are optional. If used,these optional parameters override the respective options from the specified login-path file.
When using login-paths, there are no default values except on Posix systems when specifying a socket.In this case, the host option defaults to localhost on port 3306. This means that combining the valuesspecified in the login-path with the two optional values port and socket, one needs to specify at least auser, a hostname and a port or socket.
Use the mysql_config_editor tool (http://dev.mysql.com/doc/en/mysql-config-editor.html) to add theconnection information as follows.
shell> mysql_config_editor set --login-path=instance_13001 --host=localhost --user=root --port=13001 --passwordEnter password: <Password is prompted to be inserted in a more secure way>
Next, use the following command to confirm that the login-path data was correctly added to.mylogin.cnf (the encrypted file):
shell> mysql_config_editor print --login-path=instance_13001[instance_13001]user = rootpassword = *****host = localhostport = 13001
Once your .mylogin.cnf file is configured, you need only specify the section of the .mylogin.cnf filefor the server connection. For example, the section created in the previous example is 'instance_13001'.Thus, we use --server=instance_13001. The following shows the execution of a utility specifying the login-path section.
shell> mysqlserverinfo --server=instance_13001 --format=vertical
# Source on localhost: ... connected.************************* 1. row *************************server: localhost:13001config_file: /etc/my.cnf, /etc/mysql/my.cnfbinary_log: clone-bin.000001binary_log_pos: 341relay_log:relay_log_pos:version: 5.6.17-logdatadir: /Volumes/Source/source/temp_13001/basedir: /Volumes/Source/source/git/mysql-5.6plugin_dir: /Volumes/Source/source/git/mysql-5.6/lib/plugin/general_log: OFFgeneral_log_file:general_log_file_size:log_error:log_error_file_size:slow_query_log: OFFslow_query_log_file:slow_query_log_file_size:
Connection Parameters
8
1 row.#...done.
See the online MySQL Reference Manual for more information about login-paths, the .mylogin.cnf file,and the mysql_config_editor client.
Note
If you have an installation where the MySQL Server version is older (before5.6.25 or 5.7.8) and my_print_defaults is newer, then the Utilities cannotaccess the passwords in the .login-path file because the newer versions ofmy_print_defaults mask the passwords, but older versions do not.
2.2.1.2 Use a Configuration File
MySQL Utilities can also accept a configuration path and section for the server connection data. Thisallows you to store one or more sections with connection information. Saving the data in configuration filesis more secure than specifying the data on the command-line but since the file is text, the data can still beread by anyone who can access the file.
To reference the configuration file, specify the path and file name followed by a section name in squarebrackets. The path is optional. If you do not specify it, the utility attempts to use your local configuration file(for example, my.cnf) if available.
For example, if you wanted to create a configuration file in /dev/env/test1/my.cnf and you created a sectionnamed server1, you would specify it as --server=/dev/env/test1/my.cnf[server1]. The corresponding sectionin the configuration file may look like the following.
[server1]port=3308user=rootpassword=other-passhost=localhost
The following shows the execution of a utility using a configuration file.
shell> mysqlserverinfo.py --server=/dev/env/test1/my.cnf[server1] --format=vertical
# Source on localhost: ... connected.************************* 1. row *************************server: localhost:13001config_file: /etc/my.cnf, /etc/mysql/my.cnfbinary_log: clone-bin.000001binary_log_pos: 341relay_log:relay_log_pos:version: 5.6.17-logdatadir: /Volumes/Source/source/temp_13001/basedir: /Volumes/Source/source/git/mysql-5.6plugin_dir: /Volumes/Source/source/git/mysql-5.6/lib/plugin/general_log: OFFgeneral_log_file:general_log_file_size:log_error:log_error_file_size:slow_query_log: OFFslow_query_log_file:slow_query_log_file_size:1 row.#...done.
Connection Parameters
9
2.2.1.3 Command-line Options
The least secure way to provide connection information for MySQL servers is to specify the data on thecommand-line. This is least secure because the data is visible on the command-line and is also visible inany log or redirection of the execution.
In this case, we specify the data in the following order: user[:passwd]@host[:port][:socket] where thepasswd, port, and socket are optional. Each item is described in more detail below.
• user
The name of the user to connect.
• passwd
The password to use when connecting. The default if no password is supplied is the empty password.
• host
The domain name of the host or the IP address. This field accepts host names, and IPv4 and IPv6addresses. It also accepts quoted values which are not validated and passed directly to the callingmethods. This enables users to specify host names and IP addresses that are outside of the supportedvalidation mechanisms.
• port
The port to use when connecting to the server. The default if no port is supplied is 3306 (which is thedefault port for the MySQL server as well).
• unix_socket
The socket to connect to (instead of using the host and port parameters).
The following demonstrates executing a utility using command-line options for connecting to a server.
shell> mysqlserverinfo.py --server=root:other-pass@localhost:3308 --format=vertical# Source on localhost: ... connected.************************* 1. row *************************server: localhost:13001config_file: /etc/my.cnf, /etc/mysql/my.cnfbinary_log: clone-bin.000001binary_log_pos: 341relay_log:relay_log_pos:version: 5.6.17-logdatadir: /Volumes/Source/source/temp_13001/basedir: /Volumes/Source/source/git/mysql-5.6plugin_dir: /Volumes/Source/source/git/mysql-5.6/lib/plugin/general_log: OFFgeneral_log_file:general_log_file_size:log_error:log_error_file_size:slow_query_log: OFFslow_query_log_file:slow_query_log_file_size:1 row.#...done.
As of MySQL Utilities 1.4.4, this deprecated connection method issues a warning if you use this connectionmethod.
Specifying Connections in Python Library
10
2.2.2 Specifying Connections in Python Library
If you build your own utilities using the MySQL Utilities library, there are various methods for connectingto MySQL servers. Methods that deal with connecting to servers can accept the following mechanisms forsupplying the data.
• As a Python dictionary containing the connection parameters.
• As a connection specification string containing the connection parameters.
• As a Server instance.
The dictionary lists the values by name as described above. For example, you would create code like thefollowing.
# Set connection valuesdest_values = { "user" : "root", "passwd" : "secret", "host" : "localhost", "port" : 3308, "unix_socket" : None,}
The connection specification is a string the form user[:passwd]@host[:port][:socket] where thepasswd, port, and socket are optional. This string is parsed using the options.parse_connection function.
You can also specify an existing instance of the Server class. In this case, the new class copies theconnection information.
2.2.3 Specifying User and Password for Replication Options
There are two commonly used replication options for those utilities that work with MySQL replication.These include the --rpl-user= and --discover-slaves-login= options.
In either case, these options permit users to specify a user account name and (optionally) a password inthe form of user[:passwd]. Notice the use of the colon (:) to separate the values. Should a user nameor password contain a colon, the utility attempts to use the first colon encountered (left-to-right) as theseparator. Thus, you should not use colons in your user names, but you may use colons in the password.
However, it should be noted that some special characters may cause some platforms to mangle thecommand. Thus, you should use single quotes when specifying passwords with special characters asshown in the example below.
shell> mysqlreplicate [...] --rpl-user=rpl:'L5!w1SJzVuj40(p?tF@' [...]
2.2.3.1 Specifying Secure Socket Layer (SSL) Options
Security is a big concern and MySQL Utilities is prepared to use a secure connection to MySQL serversecure-connections using an encrypted connection with SSL. This section shows you how to use SSLwhen connecting to MySQL servers from any utility. All of the utilities use the same mechanism forestablishing an SSL connection and include the following options.
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
Specifying User and Password for Replication Options
11
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
In order to use SSL connections, the MySQL server must be configure using the --ssl-ca --ssl-certand --ssl-key options with a specific SSL certificate. The --ssl option is used to enforce an SSLoption. That is, if an SSL connection cannot be made, do not fall back to a normal connection. This optionis not needed unless you want to enforce an SSL connection.
Note
If you are uncertain of how to create the SSL certificates, please following the stepsindicated on Creating SSL and RSA Certificates and Keys.
Each utility permits the user to specify the --ssl-ca, --ssl-cert, --ssl-key, and --ssl options tocreate a SSL connection to a MySQL server. Simply specify the same options used when the server wasstarted.
For example, if we wanted to get the information about a server that supports SSL connections, we firstidentify the SSL certificate authority (--ssl-ca), SSL certificate (--ssl-cert), and SSL key (--ssl-key). We want the connection to default to a normal connection if an SSL connection cannot be made,thus we omit the --ssl option.
Thus, we use the values from the server SSL configuration with the corresponding options for the utility.The following is an example of the running the serverinfo command with an SSL connection.
shell> mysqlserverinfo --server=root:pass@localhost:3307 \ --ssl-ca=C:/newcerts/cacert.pem \ --ssl-cert=C:/newcerts/client-cert.pem \ --ssl-key=C:/newcerts/client-key.pem \ --format=vertical# Source on localhost: ... connected.************************* 1. row ************************* server: localhost:3307 config_file: binary_log: binary_log_pos: relay_log: relay_log_pos: version: 5.6.15 datadir: C:\MySQL\instance_3307\ basedir: C:\MySQL\mysql-5.6.15-winx64 plugin_dir: C:\MySQL\mysql-5.6.15-winx64\lib\plugin\ general_log: OFF general_log_file: general_log_file_size: log_error: C:\MySQL\instance_3307\clone.err log_error_file_size: 1569 bytes slow_query_log: OFF slow_query_log_file: slow_query_log_file_size:
Specifying User and Password for Replication Options
12
1 row.#...done.
13
Chapter 3 MySQL Utilities Administrative Tasks
Table of Contents3.1 Binary Log Operations ................................................................................................................ 14
3.1.1 How do you change the location of the binary log files? ..................................................... 143.1.2 How do you purge obsolete binary log files safely? ........................................................... 15
3.2 Database Operations .................................................................................................................. 173.2.1 How do you provision a slave? ........................................................................................ 173.2.2 How do you make a copy of a database on the same server? ............................................ 183.2.3 How can you make a copy of a database and change the storage engine? ......................... 203.2.4 How do you tell if a table on server A has the same structure as the same table on serverB? ............................................................................................................................................ 213.2.5 How do you synchronize a table on two servers where neither is up-to-date? ...................... 22
3.3 General Operations .................................................................................................................... 233.3.1 How do you know how much space your data uses? ......................................................... 243.3.2 How do you recover the CREATE statement from a damaged or offline server? ................... 253.3.3 How do you create a new user with the same privileges as another user? ........................... 273.3.4 Is there an easy way to know what options are used with each utility? ................................ 283.3.5 How do you find redundant or duplicate indexes and know which ones to drop? .................. 313.3.6 How do you find all objects that start with a given name prefix? ......................................... 333.3.7 How do you run a process every night to kill certain connections? ...................................... 34
3.4 High Availability Operations ........................................................................................................ 353.4.1 How do you setup and use replication? ............................................................................ 363.4.2 How do you add new servers to an existing topology and change the master role? .............. 383.4.3 How do you setup and use automatic failover? ................................................................. 403.4.4 How do you restore the previous master to service after failover? ....................................... 433.4.5 How do you find all of the slaves attached to a master server? ........................................... 463.4.6 How Can you determine if data was replicated correctly? ................................................... 473.4.7 How do you fix errant transactions on the replication topology? .......................................... 49
3.5 Server Operations ...................................................................................................................... 513.5.1 How can you create a temporary copy (running instance) of a server for testing? ................. 513.5.2 How do you find what MySQL servers are running on a local machine? .............................. 533.5.3 How do you setup and use a secure (encrypted) connection between Utilities and aMySQL server? ........................................................................................................................ 54
3.6 Specialized Operations ............................................................................................................... 583.6.1 How do you record only login events in the audit log? ....................................................... 583.6.2 How do you copy or move the audit log? .......................................................................... 603.6.3 How can you find the INSERT and UPDATE queries that failed in the audit log? .................. 613.6.4 How do you find connections by the user 'root' in the audit log and show the results in CSVformat? .................................................................................................................................... 62
MySQL Utilities provides a command-line set of tools for working with MySQL Servers and databases.MySQL Utilities fully supports MySQL Server versions 5.1 and above. It is also compatible with MySQLServer 5.0, but not every feature of 5.0 may be supported. It does not support MySQL Server versions 4.x.
In this section, we present a number of example administrative tasks introduced by an example "Howdo I?" question. Included in each is a description of the need, objective, goals, example execution, anda discussion about the specific options and techniques illustrated. Also included is a description of thespecific permissions required to execute the utilities demonstrated and tips for using the utility.
Binary Log Operations
14
These task descriptions are not a substitute for the full manual of each utility, rather, they representexamples of how you can use the utility. For a complete description of the utility and all of its options andarguments, see the manual page for that utility elsewhere in this manual.
3.1 Binary Log Operations
The tasks described in this section relate to those that are performed on or with binary log files.
3.1.1 How do you change the location of the binary log files?
At some point a user might want to change the location where the binary log files are stored (by default inthe datadir). There are many reasons for separating the binary log files from the database data. Theseinclude fault tolerance, performance, and disk management. For example, you may want to store thebinary log files on a different device.
You can use (or change) the --log-bin startup option, but simply changing this option is not enough andit is likely result in errors when starting the MySQL server, especially for replication scenarios. In fact, theexisting binary log files also need to be moved to the new location and/or the entries in the respective indexfile updated in order to preserve any replication topologies that rely on the binary log files.
Objectives
Change the location for the binary log files on an existing MySQL server.
Executing this task manually can be tedious and error prone, since it requires existing binary log filesto be moved to the new location and the binary log index file to be correctly updated. Fortunately, themysqlbinlogmove utility can help us perform this task in an easy way, moving all files and automaticallyupdating the respective index file entries appropriately.
Let's assume that a server is currently running and that it was started with --log-bin=server-bin,which means that the binary log files are created in the datadir with the base filename 'server-bin'. Let'salso consider that the datadir is /var/lib/mysql and that the new target directory for the binary log files is /mysql/server/binlogs.
Example Execution
1. Stop the running MySQL server.
2. Start the mysqlbinlogmove utility and specify the source directory of the binary log files and thetarget directory.
shell> mysqlbinlogmove --binlog-dir=/var/lib/mysql \ /mysql/server/binlogs## Moving bin-log files...# - server-bin.000001# - server-bin.000002# - server-bin.000003# - server-bin.000004# - server-bin.000005# - server-bin.000006# - server-bin.000007# - server-bin.000008# - server-bin.000009# - server-bin.000010# - server-bin.000011
How do you purge obsolete binary log files safely?
15
##...done.#
3. Restart the MySQL server with the new value for the --log-bin option: --log-bin=/mysql/server/binlogs/server-bin.
Discussion
The above example illustrates how to change the binary log directory in an effortless way using themysqlbinlogmove utility to move existing binary log files to the desired location.
Changing the --log-bin startup option requires the restart of the MySQL server. Moreover, the serveralso needs to be stopped in order to move all binary log files correctly, otherwise an error might occurwhile moving files currently in use by the server. In this case, to relocate all available binary log files withthe mysqlbinlogmove utility, we simply need to specify their source directory using the --binlog-diroption and the target directory as an argument.
The binary log files are identified based on the default filename format, i.e. with a base filename endingwith '-bin'. If a custom basename is used, not ending with '-bin', then the --bin-log-basename optionmust be used to specify it.
In the above example, this option is not required because the binary log basename 'server-bin' matchesthe default format. Similarly, if a custom location or name is used for the binary log index file, it must bespecified using the --bin-log-index option. By default, the binary log index file is assumed to belocated in the specified source binary log directory and to use the default filename format.
As we can see in the above example, the mysqlbinlogmove utility displays the list of all files that aremoved. This helps to confirm that all files were relocated as expected.
Permissions Required
The system user used to execute the utility must have read and write access to the source and destinationdirectories in order to move the binary log files successfully.
Tips and Tricks
By default, the utility only moves binary log files. Use the --log-type option with the value 'relay' to moverelay log files, or 'all' to move both binary log and relay log files.
The mysqlbinlogmove utility can also be used to move some binary log files to a different location whilethe server is still running. For example, suppose you want to archive the binary log files or free somedisk space on the server's partition. In this case, the --server option should be used instead of the --binlog-dir option like in the above example. The utility ensures that the binary files that might be in useby the server (those with the higher sequence number) are not moved.
The utility also provides options to filter the files to relocate based on their sequence number using the --sequence option, or their last modification date using the --modified-before option.
3.1.2 How do you purge obsolete binary log files safely?
At some point MySQL servers may generate a significant number of binary log files that may consumeconsiderable hard drive space and may be a good reason a user might want to delete them. In a replicationscenario, it is necessary to know which binary log files can be deleted without breaking replication (you can
How do you purge obsolete binary log files safely?
16
safely archive or delete those that are not in use), since replication relies on the existence of the binary logfiles.
Users need to check each slave to determine the latest master binary log file and position (for anonymousreplication). This information is then used to determine which of the binary logs on the master may beremoved. That is, which files have been read by all of the slaves. If GTIDs are enabled, we would need toknow the list of GTIDs read on the slave in order to determine which binary log files are not in use.
Objectives
The goal is to purge all unnecessary binary log files on the MySQL server in a replication topology.
Another important goal is to automate the operation. Executing this task manually can be tedious and errorprone, since it requires getting data from and verifying each slave. The more slaves, the more complicatedthis becomes.
Fortunately, the mysqlbinlogpurge utility can help us to perform this task in an easy and safe mannerby determining all the unnecessary files automatically on each slave and purging them on the master.
Let's assume that a master server is currently running on port 13001 and a few slaves are connected.
Example Execution
1. Run the mysqlbinlogpurge utility specifying the master connection string using the --masteroption and either the --slaves to indicate each slave connection string, or the --discover-slaves-login to query the master for all registered slaves and use the user name and passwordspecified to connect and determine the binary log files that can be purged.
shell> mysqlbinlogpurge --master=root:root@localhost:13001 \ --discover-slaves-login=rpl:rpl# Discovering slaves for master at localhost:13001# Discovering slave at localhost:13002# Found slave: localhost:13002# Discovering slave at localhost:13003# Found slave: localhost:13003# Discovering slave at localhost:13004# Found slave: localhost:13004# Latest binlog file replicated by all slaves: mysql-bin.000005# Purging binary logs prior to 'mysql-bin.000006'
Discussion
The previous example illustrates how to purge the binary log files from a master in a replication scenario.
We used the --master option for the master server but for the slaves, we provided the option --discover-slaves-login and the utility used the specified information to determinate the available binary log files on theserver and for each slave verified the latest binary log file that has been loaded, finally purges the latestbinary log that is not required for any of the slaves. if want
In example, all binary log files that the utility determinate that were not required by any of the slaves werepurged, but the option --binlog can be used to specify the first binary log file to keep (not to purge) fromthe not required binary log files. The binary log files that remain on the master are from the indicated file tothe current active binary log file.
As we can see in the example, the mysqlbinlogmove utility displays latest binary log file replicated by allslaves, and if you want the utility to display the current binary log file being read by the I/O thread, we canuse the --verbose option.
Database Operations
17
Permissions Required
The user requires the SUPER and REPLICATION SLAVE privileges to purge the binary log files.
Tips and Tricks
The --dry-run option can be used to display only the latest binary log file matched by all the slaveswithout actually purge the binary log files. Use it along with -vv to display even more information such asthe status of the SQL and I/O threads of each slave.
3.2 Database OperationsThe tasks described in this section relate to those that are performed on or with one or more databases.
3.2.1 How do you provision a slave?
When working with replication, one of the most frequent maintenance tasks is adding a new slave for scaleout. Although adding a new slave has been simplified with utilities like mysqlreplicate, provisioning theslave (copying data and getting replication started properly) can be a challenge (or at least tedious) if donemanually.
Fortunately, we have two utilities - mysqldbexport and mysqldbimport - that have been designed towork with replication so that when the export is generated, you can include the proper replication controlstatements in the output stream.
Objectives
Perform slave provisioning using mysqldbexport and mysqldbimport.
Example Execution
shell> mysqldbexport --server=root:root@localhost:13001 --all --export=both --rpl=master --rpl-user=rpl:rpl > data.sqlshell> mysqldbimport --server=root:root@localhost:13002 data.sql
# Source on localhost: ... connected.# Importing definitions from data.sql.ERROR: The import operation contains GTID statements that require the global gtid_executedsystem variable on the target to be empty (no value). The gtid_executed value must be resetby issuing a RESET MASTER command on the target prior to attempting the import operation.Once the global gtid_executed value is cleared, you may retry the import.
shell> mysql -uroot -proot -h 127.0.0.1 --port=13002 -e "RESET MASTER"shell> mysqldbimport --server=root:root@localhost:13002 data.sql
# Source on localhost: ... connected.# Importing definitions from data.sql.CAUTION: The following 1 warning messages were included in the import file:# WARNING: A partial export from a server that has GTIDs enabled will by default includethe GTIDs of all transactions, even those that changed suppressed parts of the database.If you don't want to generate the GTID statement, use the --skip-gtid option. To export alldatabases, use the --all and --export=both options.#...done.
Discussion
There are several operations listed here. The first one we see is the execution of the mysqldbexportutility to create a file that includes an export of all databases as designated with the --all option. We addthe '--export=both' option to ensure we include the definitions as well as the data.
How do you make a copy of a database on the same server?
18
We also add the --rpl=master option which instructs mysqldbexport to generate the replicationcommands with respect to the source server being the master. Lastly, we include the replication user andpassword to be included in the CHANGE MASTER command.
Next, we see an attempt to run the import using mysqldbimport but we see there is an error. The reasonfor the error is the mysqldbimport utility detected a possible problem on the slave whereby there wereglobal transaction identifiers (GTIDs) recorded from the master. You can see this situation if you setupreplication prior to running the import. The way to resolve the problem is to run the RESET MASTERcommand on the slave as shown in the next operation.
We then see a rerun of the import and in this case it succeeds. We see a warning that is issued any timethere are replication commands detected in the input stream whenever GTIDs are enabled.
Permissions Required
The user used to read data from the master must have the SELECT privilege on all databases exported.The user on the slave must have the SUPER privilege to start replication.
Tips and Tricks
The warning issued during the import concerning GTIDs is to ensure you are aware that the process forgathering the proper GTIDs to execute on the slave include transactions from all databases. Thus, if youran a partial export that includes the replication commands and you have GTIDs enabled, you should usethe --skip-rpl option to skip the replication commands and restart replication manually.
Should your data be large enough to make the use of mysqldbexport impractical, you canuse mysqldbexport to generate the correct replication commands anyway by using the --export=definitions option. This generates the SQL statements for the objects but not the data. Youcan then use the replication commands generated with your own backup and restore tools.
You can use the option --rpl=slave to generate a output stream that considers the source server aslave and uses the source servers master settings for generating the CHANGE MASTER command.
If you need to copy users, we can use the mysqluserclone to copy user accounts.
3.2.2 How do you make a copy of a database on the same server?
If you are working with a database and want to experiment with changes to objects or data either fromdirect manipulation (SQL commands) or as a result of interaction with an application, it is prudent to alwayshave a copy to fall back to if something should go wrong.
Naturally, a full backup is key for any production server but what if you just want to do something as a testor as a prototype? Sure, you can restore from your backup when the test is complete but who has the timefor that? Why not just make a copy of the database in question and use it in the experiment/test?
Objectives
The goal is to make a copy of a database and rename it to another name. We want to do this on a singledatabase server without resorting to messy file copies and/or stopping the server.
In this case, we want to copy the world database in its entirety and rename the copy to world_clone.
The utility of choice here is named mysqldbcopy and it is capable of copying databases from server toanother or on the same server. The following is an example of using the utility.
How do you make a copy of a database on the same server?
19
Example Execution
shell> mysqldbcopy --source=root:root@localhost \ --destination=root:root@localhost world:world_clone# Source on localhost: ... connected.# Destination on localhost: ... connected.# Copying database world renamed as world_clone# Copying TABLE world.city# Copying TABLE world.country# Copying TABLE world.countrylanguage# Copying data for TABLE world.city# Copying data for TABLE world.country# Copying data for TABLE world.countrylanguage#...done.
shell> mysql -uroot -p -e "SHOW DATABASES"+--------------------+| Database |+--------------------+| information_schema || employees || mysql || world || world_clone |+--------------------+
Discussion
Notice we specified the source of the database we wanted to copy as well as the destination. In this case,they are the same server. You must specify it this way so that it is clear we are operating on the sameserver.
Notice how we specified the new name. We used the old_name:new_name syntax. You can do this foras many databases as you want to copy. That's right - you can copy multiple databases with a singlecommand renaming each along the way.
To copy a database without renaming it (if the destination is a different server), you can omitthe :new_name portion.
Permissions Required
The user must have SELECT privileges for the database(s) on the source server and have CREATE,INSERT, UPDATE on the destination server.
Tips and Tricks
You can copy all of the databases on a source server to the destination by using the --all option,although this option does not permit rename actions. To rename, you must specify the databases one at atime using the old_name:new_name syntax.
You can specify certain objects to exclude (skip) in the copy. Use the --skip option to omit the type ofobjects. For example, you may want to exclude copying of triggers, procedures, and functions. In this case,use the option '--skip=TRIGGERS,PROCEDURES,FUNCTIONS'. The values are case-insensitive andwritten in uppercase for emphasis.
The copy is replication and GTID aware and takes actions to preserve the binary log events during thecopy.
How can you make a copy of a database and change the storage engine?
20
You can set the locking type with the --locking option. Possible values include: no-locks = do notuse any table locks, lock-all = use table locks but no transaction and no consistent read, and snapshot(default): consistent read using a single transaction.
Risks
Should the copy fail in the middle, the destination databases may be incomplete or inconsistent. Shouldthis occur, drop (delete) the destination database in question, repair the cause of the failure, and restart thecopy.
3.2.3 How can you make a copy of a database and change the storage engine?
Sometimes you may have need to create a copy of a database but want to change the storage engine ofall tables to another engine.
For example, if you are migrating your database to InnoDB (a wise choice), you can copy the database to anew database on a new server and change the storage engine to InnoDB for all of the tables. For this, wecan use the mysqldbcopy utility.
Objectives
In this example, we want to make a copy of the world database but change the storage engine to InnoDBand rename the database accordingly.
You can cause all tables in the destination databases to use a different storage engine with the --new-storage-engine option.
Example Execution
shell> mysqldbcopy --source=root:root@localhost:3306 \--destination=root:root@localhost:3307 --new-storage-engine=InnoDB \world:world_innodb# Source on localhost: ... connected.# Destination on localhost: ... connected.# Copying database world renamed as world_innodb# Replacing ENGINE=MyISAM with ENGINE=InnoDB for table `world_innodb`.city.# Copying TABLE world_innodb.city# Replacing ENGINE=MyISAM with ENGINE=InnoDB for table `world_innodb`.country.# Copying TABLE world_innodb.country# Replacing ENGINE=MyISAM with ENGINE=InnoDB for table `world_innodb`.countrylanguage.# Copying TABLE world_innodb.countrylanguage# Copying data for TABLE world_innodb.city# Copying data for TABLE world_innodb.country# Copying data for TABLE world_innodb.countrylanguage#...done.
shell> mysql -uroot -p -h 127.0.0.1 --port=3307 -e "SHOW DATABASES"+--------------------+| Database |+--------------------+| information_schema || mysql || sakila || world || world_innodb |+--------------------+
shell> mysql -uroot -p -h 127.0.0.1 --port=3307 -e "SHOW CREATE TABLE world_innodb.countrylanguage\G"*************************** 1. row *************************** Table: countrylanguage
How do you tell if a table on server A has the same structure as the same table on server B?
21
Create Table: CREATE TABLE `countrylanguage` ( `CountryCode` char(3) NOT NULL DEFAULT '', `Language` char(30) NOT NULL DEFAULT '', `IsOfficial` enum('T','F') NOT NULL DEFAULT 'F', `Percentage` float(4,1) NOT NULL DEFAULT '0.0', PRIMARY KEY (`CountryCode`,`Language`), KEY `CountryCode` (`CountryCode`)) ENGINE=InnoDB DEFAULT CHARSET=latin1
Discussion
Notice here we created a copy of the database and changed all tables in the destination database to usethe InnoDB storage engine with the --new-storage-engine option.
We show proof of the change by displaying the CREATE statement for one of the tables on the destinationserver.
Notice we also renamed the database by using the old_name:new_name syntax.
Permissions Required
The user must have SELECT privileges for the database(s) on the source server and have CREATE,INSERT, UPDATE on the destination server.
Tips and Tricks
You can exclude specific options by using the --exclude option specifying an SQL pattern expression.For example, to exclude objects that start with xy, use '--exclude=xy%'.
You can use REGEXP patterns in the --exclude option by specifying --regexp in addition to the --exclude option.
Risks
Should the copy fail in the middle, the destination databases may be incomplete or inconsistent. Shouldthis occur, drop the destination database in question, repair the cause of the failure, and restart the copy.
If you are changing the storage engine from InnoDB, you may encounter warnings or errors if the tablescontain foreign keys and the new storage engine does not support foreign keys.
3.2.4 How do you tell if a table on server A has the same structure as the sametable on server B?
Multiple database servers that are kept synchronized manually or are compartmentalized for securitypurposes but are by practice kept up-to-date manually are prone to unintentional (and sometimesintentional) divergence.
For example, you may maintain a production server and a development server. The development servermay have the same databases with the same structures as the production server (but maybe not the samedata). However, the natural course of development, administrative tasks, and maintenance can sometimesleave the development server behind.
When this happens, you need to have a way to quickly check the schema for a table on the productionserver to see if the development server has the same structure. The utility of choice for this operation ismysqldiff.
How do you synchronize a table on two servers where neither is up-to-date?
22
Objectives
The goal is to compare a table schema on one server to another and show they differ.
Example Execution
shell> mysqldiff --server1=root:root@localhost \--server2=root:root@localhost:3307 world.city:world.city --changes-for=server2# server1 on localhost: ... connected.# server2 on localhost: ... connected.# Comparing world.city to world.city [FAIL]# Object definitions differ. (--changes-for=server2)#
--- world.city+++ world.city@@ -4,6 +4,7 @@ `CountryCode` char(3) NOT NULL DEFAULT '', `District` char(20) NOT NULL DEFAULT '', `Population` int(11) NOT NULL DEFAULT '0',+ `Climate` enum('tropical','dry','mild','continental','polar') DEFAULT NULL, PRIMARY KEY (`ID`), KEY `CountryCode` (`CountryCode`), CONSTRAINT `city_ibfk_1` FOREIGN KEY (`CountryCode`) REFERENCES `Country` (`Code`)Compare failed. One or more differences found.
Discussion
Notice to accomplish this task, we simply specified each server with --server1 and --server2 thenspecified the database objects to compare with the db.object:db.object syntax.
Permissions Required
The user must have SELECT privileges for both objects on both servers as well as SELECT on the mysqldatabase.
Tips and Tricks
You can set the direction of the compare by using the --changes-for option. For example, to see thechanges for server1 as the target, use '--changes-for=server1'.
3.2.5 How do you synchronize a table on two servers where neither is up-to-date?
When working with servers that are used in different networks or are compartmentalized, or simplyintentionally manually redundant (they do not use replication), or perhaps through some crisis, you mayencounter a situation where a table (or an entire database) diverge.
We don't simply want to know which rows differ, rather, we need to know the SQL statements needed tobring the tables into synchronization. Furthermore, we aren't sure which table is most out of date so we'dlike to see the transformation statements for both directions.
In this case, it would be very helpful to know exactly how the tables differ. For this, we use themysqldbcompare utility.
Objectives
The goal is to generate the SQL transformation statements to synchronize the tables.
General Operations
23
Example Execution
shell> mysqldbcompare --server1=root:root@localhost:13001 --server2=root:root@localhost:13002 \ menagerie -a --difftype=SQL --show-reverse --quiet# Checking databases menagerie on server1 and menagerie on server2#
## Row counts are not the same among `menagerie`.`pet` and `menagerie`.`pet`.## Transformation for --changes-for=server1:#
DELETE FROM `menagerie`.`pet` WHERE `pet_num` = '10';DELETE FROM `menagerie`.`pet` WHERE `pet_num` = '12';INSERT INTO `menagerie`.`pet` (`pet_num`, `name`, `owner`, `species`, `sex`, `birth`, `death`) VALUES('11', 'Violet', 'Annette', 'dog', 'f', '2010-10-20', NULL);
## Transformation for reverse changes (--changes-for=server2):## DELETE FROM `menagerie`.`pet` WHERE `pet_num` = '11';# INSERT INTO `menagerie`.`pet` (`pet_num`, `name`, `owner`, `species`, `sex`, `birth`, `death`)# VALUES('10', 'JonJon', 'Annette', 'dog', 'm', '2010-10-20', '2012-07-01');# INSERT INTO `menagerie`.`pet` (`pet_num`, `name`, `owner`, `species`, `sex`, `birth`, `death`)# VALUES('12', 'Charlie', 'Annette', 'dog', 'f', '2010-10-20', NULL);#
Discussion
In the example above, we connected to two servers and compare the database named menagerie. Weenabled the transformation statements using a combination of options as follows.
The --difftype=SQL option instructs the utility to generate the SQL statements.
The --show-reverse option instructs the utility to generate the differences in both direction. That is, fromthe perspective of server1 as compared to server2 and server2 as compared to server1. By convention,the second set is commented out should you wish to pipe the output to a consumer.
Lastly, the --quiet option simply turns off the verbosity of print statements that normally occur forcommunicating progress.
Permissions Required
The user must have the SELECT privilege for the databases on both servers.
Tips and Tricks
You can change the direction using the --changes-for option. For example, '--changes-for=server1' isthe default direction and '--changes-for=server2' is the reverse. In the second case, the --show-reversedisplays the perspective of server1 commented out for convenience and to make it easier to determinewhich is the alternative direction.
3.3 General Operations
The tasks described in this section include general tasks such as reporting information about a server andsearching for objects or processes on a server.
How do you know how much space your data uses?
24
3.3.1 How do you know how much space your data uses?
When preparing to create a backup or when performing maintenance on a server, it is often the case weneed to know how much space is used by our data and the logs the server maintains. Fortunately, there isa utility for that.
Objectives
Show the disk space used by the databases and all logs using the mysqldiskusage utility.
Example Execution
shell> sudo env PYTHONPATH=$PYTHONPATH mysqldiskusage \--server=root:root@localhost --all# Source on localhost: ... connected.# Database totals:+-----------------+--------------+| db_name | total |+-----------------+--------------+| oltp2 | 829,669 || bvm | 15,129 || db1 | 9,895 || db2 | 11,035 || employees | 206,117,692 || griots | 14,415 || mysql | 995,722 || oltp1 | 177,393 || room_temp | 9,847 || sakila | 791,727 || test | 647,911 || test_arduino | 9,999 || welford_kindle | 72,032 || world | 472,785 || world_innodb | 829,669 |+-----------------+--------------+
Total database disk usage = 210,175,251 bytes or 200.44 MB
# Log information.+--------------------+--------------+| log_name | size |+--------------------+--------------+| host123.log | 957,282,265 || host123-slow.log | 123,647 || host123.local.err | 321,772,803 |+--------------------+--------------+
Total size of logs = 1,279,178,715 bytes or 1.19 GB
# Binary log information:Current binary log file = my_log.000287+----------------+---------+| log_file | size |+----------------+---------+| my_log.000285 | 252208 || my_log.000286 | 256 || my_log.000287 | 3063 || my_log.index | 48 |+----------------+---------+
Total size of binary logs = 255,575 bytes or 249.58 KB
# Server is not an active slave - no relay log information.
How do you recover the CREATE statement from a damaged or offline server?
25
# InnoDB tablespace information:+--------------+--------------+| innodb_file | size |+--------------+--------------+| ib_logfile0 | 5,242,880 || ib_logfile1 | 5,242,880 || ibdata1 | 815,792,128 || ibdata2 | 52,428,800 |+--------------+--------------+
Total size of InnoDB files = 889,192,448 bytes or 848.00 MB
InnoDB freespace = 635,437,056 bytes or 606.00 MB
Discussion
To see all of the logs, we use the --all option which shows all logs and the InnoDB disk usage.
Notice we used elevated privileges to allow for reading of all of the files and databases in the datadirectory. In this case, the data directory is owned by the mysql user and a normal user account does nothave read access.
The --all option instructs the utility to list all databases even if they contain no data.
Permissions Required
The user must have permissions to read the data directory or use an administrator or super user (sudo)account as shown in the example.
Tips and Tricks
You can run mysqldiskusage without privileges to read the data directory but in this case you may seean estimate of the disk usage rather than actual bytes used. You may also not be able to see a list of thelogs if you run the utility remotely.
3.3.2 How do you recover the CREATE statement from a damaged or offlineserver?
When things go wrong badly enough that your server is down or cannot be restarted, but you can stillaccess the data on disk, you may find yourself faced with a number of complex recovery tasks.
One of those is the need to discover the structure of a particular table or set of tables. Perhaps this isneeded for an emergency recovery, a redeployment, or setup for a forensic investigation. Whateverthe case, without a running MySQL server it is not possible to know the structure of a table unless youkeep meticulous notes and/or use some form of high availability (redundancy) or source control for yourdatabase schemas.
Fortunately, there is a utility for situations like this. The mysqlfrm utility can be used to discover thestructure of a table directly from the .frm files.
Objectives
With a downed or offline server, discover the structure of a table. More specifically, generate the CREATETABLE SQL command.
Example Execution
How do you recover the CREATE statement from a damaged or offline server?
26
shell> sudo env PYTHONPATH=$PYTHONPATH mysqlfrm --basedir=/usr/local/mysql \ --port=3333 --user=user /usr/local/mysql/data/welford_kindle/books.frm
# Spawning server with --user=user.# Starting the spawned server on port 3333 ... done.# Reading .frm files## Reading the books.frm file.## CREATE statement for /usr/local/mysql/data/kindle/books.frm:#
CREATE TABLE `welford_kindle`.`books` ( `ISBN` char(32) NOT NULL PRIMARY KEY, `title` char(128) DEFAULT NULL, `purchase_date` date DEFAULT NULL, `cost` float(10,2) DEFAULT NULL) ENGINE=MyISAM DEFAULT CHARSET=latin1
#...done.
Discussion
For this example, we used three required parameters; the base directory for the offline server (basedir), anew port to use for the spawned server (port), and a user name to use to run the spawned server (port).The later is necessary since we must launch the mysqlfrm utility as root (sudo) in order to be able to read(copy) files from the protected data directory of the host server.
The --port option is always required for running the utility in default mode (it is not needed for diagnosticmode). You must supply a valid unused port. The utility checks to see if the port is in use and if soproduces an error. The port is used to spawn a temporary instance of a MySQL server in order to attemptto recover the .frm file. This instance is shutdown at the end of the process and is not used for diagnosticmode.
We use the --basedir option instead of the --server option because we were faced with a situationwhere the original server was offline (down). Note that you can use the --basedir option for a runningserver if you do not want the utility to connect to the original server in any way.
Permissions Required
The permissions for using mysqlfrm vary and depend entirely on how you use it. If you use the utility toread .frm files in a protected folder like the example above (in either mode), you must have the ability to runthe spawned server with privileges that allow you to read the protected files. For example, you could use auser account that has root-level privileges.
If you use the utility with a server connection, the user you use to connect must have the ability to readsystem variables at a minimum including read access to the mysql database.
You should never use the root user to spawn the server nor should you use the mysql user when spawningthe server or running the utility.
Tips and Tricks
The utility is designed to work on the host where the .frm files reside. It does not permit connecting to aremote host to read .frm files.
If something goes wrong during the spawning of the server, use the verbosity option three times (-vvv) toturn on maximum depth debug statements. This ensures you see all of the messages from the start of the
How do you create a new user with the same privileges as another user?
27
spawned server from bootstrap onward. Look for errors in these statements as to why the spawned serverdid not start.
If you do not want to permit the utility to launch a temporary instance of a MySQL server, you should usethe diagnostic mode instead. However, the diagnostic mode may not recover all of the options for a table.
Risks
The utility performs a best effort approximation of the CREATE statement when run in diagnostic mode.As such, if you read a .frm file that uses character sets or collations other than the default and you do notuse a --server option to connect to a server to read the character sets, this can result in miscalculatedcolumn sizes.
For example, suppose your default character set is latin1 which uses 1 byte per character. Let us alsosuppose you are attempting to read a .frm file that uses a character set that uses 3 bytes per character.Furthermore, we have no server to connect. In this case, the column sizes may be off by a factor of 3. Acase in point would be a field such as col_a char(3) would appear in the output of the mysqlfrm utility ascol_a char(9).
To mitigate risks such as this and to produce the most accurate CREATE statement in diagnostic mode,always use the --server option.
3.3.3 How do you create a new user with the same privileges as another user?
The MySQL privilege system permits you to create a set of permissions for each user. Sometimes the setof permissions are complex and may require multiple GRANT statements to effect. Other times, the usermay acquire privileges over time.
Regardless of how it came about, you may find yourself needing to create a new user that has the sameprivileges as another user.
Objectives
The goal is to create one or more users whose permissions are identical to an original user on a singleserver.
Rather than discover what those privileges are using a SHOW GRANTS FOR statement, copy them into ascript, modify it, copy and paste again for each user, etc., etc., we can use a single command to copy oneuser to a list of new users. We can even set different passwords for each user as we go.
Let's assume we have a user, joe@localhost, who has a long list of permissions. We need to create aclone of his user account for two new users, sally and john. Each of these users requires a new password.
Example Execution
shell> mysqluserclone --source=root@localhost \ --destination=root@localhost \ joe@localhost sally:secret1@localhost john:secret2@localhost# Source on localhost: ... connected.# Destination on localhost: ... connected.# Cloning 2 users...# Cloning joe@localhost to user sally:secret1@localhost# Cloning joe@localhost to user john:secret2@localhost# ...done.
Is there an easy way to know what options are used with each utility?
28
Discussion
In the above example, we see the use of the mysqluserclone utility to clone the joe user to two newuser accounts.
Notice we used the --source option to connect to the original server and --destination for the sameserver.
After that, we simply list the user we want to clone and the new users we want to create. In this case weuse the format username:password@host to specify the user account name, password (optional), andhost.
When the utility finishes, you have two new user accounts that have the same privileges as the originaluser; joe@localhost.
Permissions Required
On the source server, the user must have the SELECT privilege for the mysql database.
On the destination server, the user must have the global CREATE USER privilege or the INSERT privilegefor the mysql database as well as the GRANT OPTION privilege, and the privileges that the original userhas (you grant a privilege you do not have yourself).
Tips and Tricks
You can use --destination option to specify a different server to copy a user account to another server.
Use the --dump option with only the --source option to see all user accounts.
Use the --include-global-privileges option to include GRANT statements that the user@hostcombination matches. This is useful for copying user accounts from one server to another where there areglobal privileges in effect.
3.3.4 Is there an easy way to know what options are used with each utility?
There are many utilities and it is not always easy to remember all of the options and parameters associatedwith each. Sometimes we need to run several utilities using nearly the same options. For example,you may want to run several utilities logging into a particular server. Rather than retype the connectioninformation each time, you would like to save the option value some way and reuse it.
Fortunately, the mysqluc utility does this and more. It is named the MySQL Users' Console and providestype completion for options, utility names, and even user-defined variables for working with common optionvalues. Not only that, it also provides the ability to get help for any utility supported.
Objectives
Discover what utilities exist and find the options for certain utilities.
Run several utilities with the same server using the type completion feature to make using the suite ofutilities easier.
Example Execution
Note
In the example below, keystrokes are represented using square brackets. Forexample, [TAB] indicates the tab key was pressed. Similarly, portions in the
Is there an easy way to know what options are used with each utility?
29
commands specific with angle brackets are values you would replace with actualvalues. For example, <user> indicates you would place the user's login name here.
shell> mysqlucLaunching console ...
Welcome to the MySQL Utilities Client (mysqluc) version 1.6.4Copyright (c) 2010, 2016 Oracle and/or its affiliates. All rights reserved.This is a release of dual licensed MySQL Utilities. For the avoidance ofdoubt, this particular copy of the software is releasedunder the version 2 of the GNU General Public License.MySQL Utilities is brought to you by Oracle.
Type 'help' for a list of commands or press TAB twice for list of utilities.
mysqluc> helpCommand Description ---------------------- ---------------------------------------------------help utilities Display list of all utilities supported. help <utility> Display help for a specific utility. show errors Display errors captured during the execution of the utilities. clear errors clear captured errors. show last error Display the last error captured during the execution of the utilities help | help commands Show this list. exit | quit Exit the console. set <variable>=<value> Store a variable for recall in commands. show options Display list of options specified by the user on launch. show variables Display list of variables. <ENTER> Press ENTER to execute command. <ESCAPE> Press ESCAPE to clear the command entry. <DOWN> Press DOWN to retrieve the previous command. <UP> Press UP to retrieve the next command in history.<TAB> Press TAB for type completion of utility, option, or variable names. <TAB><TAB> Press TAB twice for list of matching type completion (context sensitive).
mysqluc> help utilitiesUtility Description ---------------- ---------------------------------------------------------mysqlauditadmin audit log maintenance utility mysqlauditgrep audit log search utility mysqlbinlogmove binary log relocate utility mysqlbinlogpurge purges unnecessary binary log files mysqlbinlogrotate rotates the active binary log file mysqldbcompare compare databases for consistency mysqldbcopy copy databases from one server to another mysqldbexport export metadata and data from databases mysqldbimport import metadata and data from files mysqldiff compare object definitions among objects where the difference is how db1.obj1 differs from db2.obj2 mysqldiskusage show disk usage for databases mysqlfailover automatic replication health monitoring and failover mysqlfrm show CREATE TABLE from .frm files mysqlgrants display grants per object mysqlindexcheck check for duplicate or redundant indexes mysqlmetagrep search metadata mysqlprocgrep search process information mysqlreplicate establish replication with a master mysqlrpladmin administration utility for MySQL replication mysqlrplcheck check replication mysqlrplms establish multi-source replication
Is there an easy way to know what options are used with each utility?
30
mysqlrplshow show slaves attached to a master mysqlrplsync replication synchronization checker utility mysqlserverclone start another instance of a running server mysqlserverinfo show server information mysqlslavetrx skip transactions on slaves mysqluserclone clone a MySQL user account to one or more new users
mysqluc> help mysqldb[TAB][TAB]Utility Description -------------- -----------------------------------------------------------mysqldbcompare compare databases for consistency mysqldbcopy copy databases from one server to another mysqldbexport export metadata and data from databases mysqldbimport import metadata and data from files
mysqluc> mysqlrplshow --m[TAB][TAB]
Option Description --------------------- ------------------------------------------------------master=MASTER connection information for master server in the form: <user>[:<password>]@<host>[:<port>][:<socket>] or <login-path>[:<port>][:<socket>]. --max-depth=MAX_DEPTH limit the traversal to this depth. Valid only with the --recurse option. Valid values are non-negative integers.
mysqluc> mysqlrplshow --mast[TAB]er=<user>:<password>@localhost:13001
The console has detected that the utility 'mysqlrplshow' ended with an error code.You can get more information about the error by running the console command 'show last error'.
mysqluc> show last errorExecution of utility: mysqlrplshow --master=<user>:<password>@localhost:13001returned errorcode: 2 with error message:Usage: mysqlrplshow.py --master=root@localhost:3306
mysqlrplshow.py: error: The --discover-slaves-login is required to test slave connectivity.
mysqluc> mysqlrplshow --master=<user>:<password>@localhost:13001 \ --discover-slaves-login=<user>:<password># master on localhost: ... connected.# Finding slaves for master: localhost:13001
# Replication Topology Graphlocalhost:13001 (MASTER) | +--- localhost:13002 - (SLAVE) | +--- localhost:13003 - (SLAVE) | +--- localhost:13004 - (SLAVE) | +--- localhost:13005 - (SLAVE)
mysqluc>
Discussion
There is a lot going on here in this example! Let's look through the command entries as they occur in thetext.
The first command, mysqluc, starts the users' console. Once the console starts, a welcome banner isdisplayed followed by a simple prompt, mysqluc>. No additional options or parameters are necessary.
How do you find redundant or duplicate indexes and know which ones to drop?
31
However, it should be noted that you can pass commands to the console to execute on start. For acomplete list of options, see MySQL Users' Console manual page.
The next command, help, shows the help for the users' console itself. As you can see, there are a numberof options available. You can set user defined variables, discover the help for other utilities, display thelatest error, and see the options used to start the console.
The help utilities command shows you a list of the available utilities and a short description of each.
Next, we decide we want to get help for one of the database utilities but we do not remember the name.We know it starts with mysqldb but we are not sure of the rest. In this case, if we type mysqldb then hitTAB twice, the users' console shows us a list of all of the utilities that begin with mysqldb.
Now let's say we want to see a graph of our replication topology but we are not sure what the option forspecifying the master. In this case, we type the command to launch the mysqlrplshow utility and typethe start of the option, '--m', then press TAB twice. What we see is there are two options that match thatprefix. Notice we also see a short description (help) for each. This is a real time saving feature for theusers' console.
Notice in the next segment we do not have to type the entire name of the option. In this case we typed '--mast[TAB]' which the users' console completed with '--master='. This is tab completion for option names.
Notice the result of the command we entered, mysqlrplshow '--master=user:password@localhost:13001'. There was an error here. We can see the error with the showerrors command. We see in the error we failed to provide any connection information for the slaves.
Once we correct that omission, the last command shows how the users' console executes a utility anddisplays the results in the same stream as the console - much like the mysql client command-line tool.
Permissions Required
There are no special permissions required to run mysqluc however, you must have the necessaryprivileges to execute the desired utilities.
3.3.5 How do you find redundant or duplicate indexes and know which ones todrop?
MySQL allows its users to create several indexes that might be the same (duplicate indexes) or partiallysimilar (redundant indexes) in its structure. Although duplicate indexes have no advantages, there aresome cases where redundant indexes might be helpful. However, both have disadvantages. Duplicate andredundant indexes slow down update and insert operations. As a result it is usually a good idea to find andremove them.
Doing this manually would be a time consuming task, especially for big databases or databases with lots oftables and that is why there is a utility to automate this type of task: mysqlindexcheck.
Objectives
Our goal is to use the mysqlindexcheck utility to help us find duplicate and redundant indexes. For thatwe are going to use the following table as an example:
CREATE TABLE `test_db`.`indexcheck_test`( `emp_id` INT(11) NOT NULL,
How do you find redundant or duplicate indexes and know which ones to drop?
32
`fiscal_number` int(11) NOT NULL, `name` VARCHAR(50) NOT NULL, `surname` VARCHAR (50) NOT NULL, `job_title` VARCHAR (20), `hire_date` DATE default NULL, `birthday` DATE default NULL, PRIMARY KEY (`emp_id`), KEY `idx_fnumber`(`fiscal_number`), UNIQUE KEY `idx_unifnumber` (`fiscal_number`), UNIQUE KEY `idx_uemp_id` (`emp_id`), KEY `idx_full_name` (`name`, `surname`), KEY `idx_full_name_dup` (`name`, `surname`), KEY `idx_name` (`name`), KEY `idx_surname` (`surname`), KEY `idx_reverse_name` (`surname`,`name`), KEY `ìdx_id_name` (`emp_id`, `name`), KEY `idx_id_hdate` (`emp_id`, `hire_date`), KEY `idx_id_bday` (`emp_id`, `birthday`)) ENGINE=InnoDB DEFAULT CHARSET=utf8
Example Execution
shell> mysqlindexcheck --server=test_user@localhost:13010 test_db.indexcheck_test# Source on localhost: ... connected.# The following indexes are duplicates or redundant for table test_db.indexcheck_test:#CREATE INDEX `idx_uemp_id` ON `test_db`.`indexcheck_test` (`emp_id`) USING BTREE# may be redundant or duplicate of:ALTER TABLE `test_db`.`indexcheck_test` ADD PRIMARY KEY (`emp_id`)#CREATE INDEX `idx_fnumber` ON `test_db`.`indexcheck_test` (`fiscal_number`) USING BTREE# may be redundant or duplicate of:CREATE INDEX `idx_unifnumber` ON `test_db`.`indexcheck_test` (`fiscal_number`) USING BTREE#CREATE INDEX `idx_full_name_dup` ON `test_db`.`indexcheck_test` (`name`, `surname`) USING BTREE# may be redundant or duplicate of:CREATE INDEX `idx_full_name` ON `test_db`.`indexcheck_test` (`name`, `surname`) USING BTREE#CREATE INDEX `idx_name` ON `test_db`.`indexcheck_test` (`name`) USING BTREE# may be redundant or duplicate of:CREATE INDEX `idx_full_name` ON `test_db`.`indexcheck_test` (`name`, `surname`) USING BTREE#CREATE INDEX `idx_surname` ON `test_db`.`indexcheck_test` (`surname`) USING BTREE# may be redundant or duplicate of:CREATE INDEX `idx_reverse_name` ON `test_db`.`indexcheck_test` (`surname`, `name`) USING BTREE#ALTER TABLE `test_db`.`indexcheck_test` ADD PRIMARY KEY (`emp_id`)# may be redundant or duplicate of:CREATE INDEX `ìdx_id_name` ON `test_db`.`indexcheck_test` (`emp_id`, `name`) USING BTREE#CREATE INDEX `idx_id_hdate` ON `test_db`.`indexcheck_test` (`emp_id`, `hire_date`) USING BTREE# may be redundant or duplicate of:CREATE INDEX `ìdx_id_name` ON `test_db`.`indexcheck_test` (`emp_id`, `name`) USING BTREE#CREATE INDEX `idx_id_bday` ON `test_db`.`indexcheck_test` (`emp_id`, `birthday`) USING BTREE# may be redundant or duplicate of:CREATE INDEX `ìdx_id_name` ON `test_db`.`indexcheck_test` (`emp_id`, `name`) USING BTREE# The following indexes for table test_db.indexcheck_test contain the clustered index and# might be redundant:#CREATE INDEX `idx_uemp_id` ON `test_db`.`indexcheck_test` (`emp_id`) USING BTREE#CREATE INDEX `ìdx_id_name` ON `test_db`.`indexcheck_test` (`emp_id`, `name`) USING BTREE#CREATE INDEX `idx_id_hdate` ON `test_db`.`indexcheck_test` (`emp_id`, `hire_date`) USING BTREE#
How do you find all objects that start with a given name prefix?
33
CREATE INDEX `idx_id_bday` ON `test_db`.`indexcheck_test` (`emp_id`, `birthday`) USING BTREE
Discussion
As we can see, the utility first points out that neither the idx_uemp_id index nor the idx_fnumber arenecessary and it points out why. The first, idx_uemp_id, is redundant because the primary key alreadyensures that emp_id values have to be unique. As for idx_fnumber, it is also redundant becauseof idx_ufnumber, a UNIQUE type index which also works as a regular index. Then it points out thatidx_full_name_dup is also not necessary. In this case it is a duplicate of the idx_full_name index since itcontains the exact same columns on the same order.
Notice that it also indicates that idx_name, idx_surname and even the PRIMARY INDEX on emp_id mightbe redundant. This happens because we are dealing with BTREE type indexes and for this type of indexesan index X is redundant to an index Y if and only if the first n columns in X also appear in Y.
Given that we are using InnoDB engine, it also warns us that `idx_uemp_id`, `ìdx_id_name`, `idx_id_hdate`and `idx_id_bday` might not be needed. This happens because, in InnoDB, secondary indexes contain theprimary key columns for the row that are not in the secondary index.
Note
The indexes identified are just indications of redundant and duplicate indexes. Theymust not be followed blindly because redundant indexes can be useful dependingon how you use (query) your tables.
Permissions Required
Regarding the privileges needed to run this utility, the test_user needs SELECT privilege on the mysqldatabase as well as for the databases which tables are being checked.
Tips and Tricks
You can use the -d option to generate the SQL drop statements needed to remove the indexes.
The --stats option can be used alone or together with either --best or --worst to show statisticsabout the indexes.
Use the --show-indexes option to show each table together with its indexes.
3.3.6 How do you find all objects that start with a given name prefix?
One of the challenges for database administrators who manage servers with thousands of objects is thetask of finding an object by name. Sometimes all you have to go on is the name of a table or perhaps anobscure reference to a partial name. This can come about through a diagnosis of a problem connection,application, or via an incomplete description from a defect report.
It is also possible you need to simply check to see if certain things exist. For example, suppose amongyour databases are parts or inventory data and you want to check to see if there are any functions orprocedures that operate on a column named 'cost'. Moreover, you want to see anything related that has'cost' as part of its name.
Whatever the case, it would be a big time saver if you could search through all of the database objects andsee a list of the objects whose name matches a prefix (or pattern). Fortunately, the mysqlmetagrep utilitycan get this done.
How do you run a process every night to kill certain connections?
34
Objectives
Find all objects whose name begins with a known prefix. More specifically, find any mention of the word'cost'.
Example Execution
shell> mysqlmetagrep --server=root:root@localhost --body --pattern='%cost%'+------------------------+--------------+--------------+----------+-------------+------------------+| Connection | Object Type | Object Name | Database | Field Type | Matches |+------------------------+--------------+--------------+----------+-------------+------------------+| root:*@localhost:3306 | FUNCTION | adjust_cost | griots | ROUTINE | adjust_cost || root:*@localhost:3306 | TABLE | supplies | griots | COLUMN | cost || root:*@localhost:3306 | TABLE | film | sakila | COLUMN | replacement_cost |+------------------------+--------------+--------------+-----------------+-------------+-------------+
shell> mysql -uroot -proot -e "SHOW CREATE FUNCTION griots.adjust_cost \G"*************************** 1. row *************************** Function: adjust_cost sql_mode: Create Function: CREATE DEFINER=`root`@`localhost` FUNCTION `adjust_cost`(cost double) RETURNS double DETERMINISTICreturn cost * 1.10character_set_client: latin1collation_connection: latin1_swedish_ci Database Collation: latin1_swedish_ci
Discussion
In this example, we see the use of the database pattern '%cost%' to find objects that have 'cost' anywherein their name. We also see the use of the --body option to instruct the utility to look inside procedures andfunctions. This can be very handy to locate routines that manipulate data as you can see.
Notice once we found a routine that had 'cost' mentioned, we can examine its body via the SHOWCREATE FUNCTION command to see just how it is using the column 'cost'. In this case, we see someonehas written a function to adjust the cost by 10%'.
Therefore, not only can you find objects that have anything named 'cost', you can also discover any hiddenlogic that may operate on something named 'cost'.
Permissions Required
The user must have the SELECT privilege on the mysql database.
Tips and Tricks
If you are familiar with using regular expressions, you can use the --regexp option to use regularexpressions instead of database patterns. For example, the regular expression for the search above wouldbe --pattern='^.*cost.*' --basic-regex.
3.3.7 How do you run a process every night to kill certain connections?
Some database administrators use nightly routines to perform maintenance on their databases or servers.Sometimes these routines can be blocked by long running queries or applications that hang onto locks forlonger than expected.
Naturally, priority is given to the application and maintenance routines are often canceled rather thaninterfere with an application. Should it happen that you subscribe to this notion and you have a routine
High Availability Operations
35
that is still being blocked or for some reason hasn't completed by a certain time, you need a quick way togenerate an event to kill the connection involved. This is where the mysqlprocgrep utility can help.
Objectives
The objective is to generate an event that kills all connections based on a user login ('msaladin') but only ifthat connection is trying to run a custom administration script named 'my_admin_thingy'.
Example Execution
shell> mysqlprocgrep --sql-body \ --match-command='my_admin_thingy%' --match-user='msaladin%' --kill-connectionDECLARE kill_done INT;DECLARE kill_cursor CURSOR FOR SELECT Id, User, Host, Db, Command, Time, State, Info FROM INFORMATION_SCHEMA.PROCESSLIST WHERE COMMAND LIKE 'my_admin_thingy%' AND USER LIKE 'msaladin%'OPEN kill_cursor;BEGIN DECLARE id BIGINT; DECLARE EXIT HANDLER FOR NOT FOUND SET kill_done = 1; kill_loop: LOOP FETCH kill_cursor INTO id; KILL CONNECTION id; END LOOP kill_loop;END;CLOSE kill_cursor;
Discussion
Notice in the example above, we did not connect to any server to get this information. That is one of thegreat things about this utility - you can generate all manner of SQL statements for finding processes and trythem out on a test system before incorporating them into your events, triggers, and routines.
We specified the user with the --match-user option using a wildcard in case the user is logged in froma different system. We also specified the name of the maintenance routine in the same manner in case itgets renamed with a version number or some such.
The output of this utility then is the SQL statement we need to use to find and kill the connections that meetthese criteria. Armed with this, we can make a procedure we can call from an event and execute the SQLat a precise time every day.
Permissions Required
The user must have the SELECT permission on the mysql database.
Tips and Tricks
If you are familiar with using regular expressions, you can use the --regexp option to use regularexpressions instead of database patterns.
3.4 High Availability OperationsThe tasks described in this section include those for replication and general to specific high availabilitytasks such as automatic failover.
How do you setup and use replication?
36
3.4.1 How do you setup and use replication?
MySQL has built-in support for several types of replication. Replication is usually employed with thepurpose of increasing the performance and/or the fault-tolerance of the server and by extension theapplication. However, setting up replication can be a somewhat complicated and error prone process. Butfear not, MySQL Utilities has tools that can help simplify and even automate several replication relatedtasks.
Consider a scenario where replication is used to obtain scalability, i.e. to increase the performance. Let usimagine an online shopping service. The shop started out small so a single server was enough to handleall the requests, however now it has become quite popular and as a result that single server is no longerable to handle all the requests. Being an online store, most of the operations are read operations (checkingexisting products, reviews, stock availability, etc).
Objectives
Our goal is to use replication in order to improve the throughput of the service by adding more serverswhich becomes replicas of the already existing server. These replicas allows scaling out of the serviceby taking up all the read requests, leaving the old server (now called the master) in charge of the writes.Rather than doing everything "by hand" with the mysql command line, we are going to setup this replicationscenario using a single script, mysqlreplicate which does most of the hard work for us. We then checkthe result using the mysqlrpladmin utility.
Let us assume the existing server, Server1, is running on port 13001 on the local machine with IP198.51.100.1 and that we want to add 2 new servers, Server2 running on 198.51.100.2:13001 and Server3running on 198.51.100.3:3306.
Example Execution
shell> mysqlreplicate [email protected]:13001 \[email protected]:13001 --rpl-user=repl:slavepass -b# master on 198.51.100.1: ... connected.# slave on 198.51.100.2: ... connected.# Checking for binary logging on master...# Setting up replication...# ...done.
shell> mysqlreplicate [email protected]:13001 \ [email protected]:3306 --rpl-user=repl:slavepass -b# master on 198.51.100.1: ... connected.# slave on 198.51.100.3: ... connected.# Checking for binary logging on master...# Setting up replication...# ...done.
shell> mysqlrplcheck [email protected]:13001 \ [email protected]:13001
# master on 198.51.100.1: ... connected.# slave on 198.51.100.2: ... connected.Test Description Status---------------------------------------------------------------------------Checking for binary logging on master [pass]Are there binlog exceptions? [pass]Replication user exists? [pass]Checking server_id values [pass]Checking server_uuid values [pass]Is slave connected to master? [pass]Check master information file [pass]Checking InnoDB compatibility [pass]
How do you setup and use replication?
37
Checking storage engines compatibility [pass]Checking lower_case_table_names settings [pass]Checking slave delay (seconds behind master) [FAIL]
Slave is NNN seconds behind master.
# ...done.
shell> mysqlrplcheck [email protected]:13001 \ [email protected]:3306
# master on 198.51.100.1: ... connected.# slave on 198.51.100.3: ... connected.Test Description Status---------------------------------------------------------------------------Checking for binary logging on master [pass]Are there binlog exceptions? [pass]Replication user exists? [pass]Checking server_id values [pass]Checking server_uuid values [pass]Is slave connected to master? [pass]Check master information file [pass]Checking InnoDB compatibility [pass]Checking storage engines compatibility [pass]Checking lower_case_table_names settings [pass]Checking slave delay (seconds behind master) [FAIL]
Slave is N seconds behind master.
# ...done.
Discussion
In the above example we made use of the mysqlreplicate utility to setup a single tier replicationtopology, where the existing server is now the master for the two new servers which act as slaves. Noticehow we used the address of the old existing server in the --master option and in the --slave option weused the addresses of the new servers. Also notice the use of the -b flag, this makes replication start fromthe first event recorded in the master's binary log.
Also notice how we used the mysqlrplcheck utility to check the health of the replication. In this case, thefailing test "Check slave delay" is expected, since the slaves are catching up with the master. When theslaves have read and applied all the transactions from the master's binary log the "Check slave delay" testpasses. Also, in case the slave wasn't properly configured and pointing to the master specified the "Is slaveconnect to master" test would notify us of that with a FAIL or WARN status.
Permissions Required
The m_account user needs the following privileges for the mysqlreplicate: SELECT and INSERTprivileges on mysql database, REPLICATION SLAVE, REPLICATION CLIENT and GRANT OPTION.As for the slave_acc users, they need the SUPER privilege. The repl user, used as the argument for the--rpl-user option, is either created automatically or if it exists, it needs the REPLICATION SLAVEprivilege.
Also, when using GTIDs, the slave_acc users must also have SELECT privilege over the mysql databasein order to run the mysqlrplcheck utility successfully.
Tips and Tricks
In the mysqlreplicate utility we could have also used the --test-db option which creates a dummydatabase to test the replication setup. However, the mysqlrplcheck provides more detailed informationin that regard.
How do you add new servers to an existing topology and change the master role?
38
As previously stated, the -b option tells the utility to start replication from the first event recorded in themaster's binary log. Omitting this flag, in turn, makes the slaves replicate only what is stored in the master'sbinary log from the present moment onward.
Furthermore, using the --master-log-file and --master-log-pos options it is possible to specifyrespectively the master log file and the master log position from which the slave starts its replicationprocess.
The -p flag can be used to ensure that the replication setup is only executed in case the storage enginesmatch in both the master and the slave.
Regarding the mysqlrplcheck utility, we can use the -s option to check the output of the show slavestatus command. This can be useful for instance to check what might be causing the "Is slave connected"test to fail. We can also use the --master-log-file option to specify the name of the masterinformation file to read.
Lastly, we can use the --verbose option in order to get more information about what is happening "underthe hood".
3.4.2 How do you add new servers to an existing topology and change themaster role?
We examine a scenario similar to the previous one where we want to make one of the two new slavesadded the new master server (perhaps because it has better specs and is faster).
Objectives
Our goal in this example it create replication configuration with 3 servers, two new ones and an existingone, and we want to replicate all the information, but make one of the new servers the master server.
Like the previous example, lets assume that the existing server, Server1, is running on port 13001 on thelocal machine with IP 198.51.100.1 that the two new machines with mysql server instances are Server2running on 198.51.100.2:13001 and Server3 running on 198.51.100.3:3306. We want to make Server2 thenew master.
Example Execution
shell> mysqlreplicate [email protected]:13001 \ [email protected]:13001 --rpl-user=repl:slavepass -b# master on 198.51.100.1: ... connected.# slave on 198.51.100.2: ... connected.# Checking for binary logging on master...# Setting up replication...# ...done.
shell> mysqlreplicate [email protected]:13001 \ [email protected]:3306 --rpl-user=repl:slavepass -b# master on 198.51.100.1: ... connected.# slave on 198.51.100.3: ... connected.# Checking for binary logging on master...# Setting up replication...# ...done.
shell> mysqlrpladmin [email protected]:13001 \ [email protected]:13001,[email protected]:3306 health
# Checking privileges.#
How do you add new servers to an existing topology and change the master role?
39
# Replication Topology Health:+---------------+--------+---------+--------+------------+------------------------------+| host | port | role | state | gtid_mode | health |+---------------+--------+---------+--------+------------+------------------------------+| 198.51.100.1 | 13001 | MASTER | UP | ON | OK || 198.51.100.2 | 13001 | SLAVE | UP | ON | Slave delay is NNN seconds || 198.51.100.3 | 3306 | SLAVE | UP | ON | Slave delay is NNN seconds |+---------------+--------+---------+--------+------------+------------------------------+# ...done.
shell> mysqlrpladmin [email protected]:13001 \ [email protected]:13001,[email protected]:3306 health
# Checking privileges.## Replication Topology Health:+---------------+--------+---------+--------+------------+---------+| host | port | role | state | gtid_mode | health |+---------------+--------+---------+--------+------------+---------+| 198.51.100.1 | 13001 | MASTER | UP | ON | OK || 198.51.100.2 | 13001 | SLAVE | UP | ON | OK || 198.51.100.3 | 3306 | SLAVE | UP | ON | OK |+---------------+--------+---------+--------+------------+---------+# ...done.
shell> mysqlrpladmin [email protected]:13001 \ [email protected]:13001,[email protected]:3306 \ --new-master=slave_acc1@localhost:13002 --demote-master switchover# Checking privileges.# Performing switchover from master at 198.51.100.1:13001 to slave at 198.51.100.2:13001.# Checking candidate slave prerequisites.# Checking slaves configuration to master.# Waiting for slaves to catch up to old master.# Stopping slaves.# Performing STOP on all slaves.# Demoting old master to be a slave to the new master.# Switching slaves to new master.# Starting all slaves.# Performing START on all slaves.# Checking slaves for errors.# Switchover complete.## Replication Topology Health:+---------------+--------+---------+--------+------------+---------+| host | port | role | state | gtid_mode | health |+---------------+--------+---------+--------+------------+---------+| 198.51.100.2 | 13001 | MASTER | UP | ON | OK || 198.51.100.1 | 13001 | SLAVE | UP | ON | OK || 198.51.100.3 | 3306 | SLAVE | UP | ON | OK |+---------------+--------+---------+--------+------------+---------+
Discussion
As with our previous scenario we used the mysqlreplicate utility to set up a replication topologybetween the existing server and the two new servers. Notice the use of the -b flag which this replicationstart from the first event recorded in the master's binary log.
After creating the replication topology, we made use of the mysqlrpladmin utility specifying both themaster and slave servers and using the health command to check the status of the replication. Since ourmaster server had lots of information, it is normal for the new slaves to take some time to catch up, thusthe slave delay message on the health column of the output.
However, if all goes well, after some time the slaves will eventually catch up, and when that happens, thehealth column shows an OK status.
How do you setup and use automatic failover?
40
Once this was established, we used the mysqlrpladmin utility yet again, this time with switchovercommand. Using the --new-master option, we specify the server that becomes the new master. We alsoused the --demote-master option, which turns the old master into a slave. If we left that option out, theold master would still behave as a master just without any slaves.
After the switchover, Server2 becomes the master server for both Server1 and Server3 which are now theslaves.
Permissions Required
The m_account user needs the following privileges for the mysqlreplicate: SELECT and INSERTprivileges on mysql database, REPLICATION SLAVE, REPLICATION CLIENT and GRANT OPTION.As for the slave_acc users, they need the SUPER privilege. The repl user, used as the argument for the--rpl-user option, is either created automatically or if it exists, it needs the REPLICATION SLAVEprivilege.
To run the mysqlrpladmin utility with the health command, the m_account used on the master needs anextra SUPER privilege.
As for the switchover command all the users need the following privileges: SUPER, GRANT OPTION,SELECT, RELOAD, DROP, CREATE and REPLICATION SLAVE
Tips and Tricks
We can use the --discover-slaves-login option for mysqlrpladmin in order to detect the slavesautomatically instead of manually specifying the slaves.
The mysqlrpladmin utility allows users to specify a script to execute before and after the failover andswitchover operations using the --exec-before and --exec-after options respectively. Note that thescript specified using the exec-after option only runs in case the switchover/failover executes successfully.
We can use the mysqlrpladmin utility to start and stop all the slaves with the start/stop commands.Using the stop command only stops servers that are actually slaves of the specified master thus preventingus from stopping unwanted servers.
3.4.3 How do you setup and use automatic failover?
Once your replication topology is setup, it is important to consider the possible occurrences of failures inorder to maintain the high availability level of your system. Several failures independently from their cause(network connection issue, hard drive crash, cosmic lightning, etc.) can stop the replication process bymaking the master no longer accessible by its slaves.
In this type of situation, it is desirable to promote one of the slaves to the master while the problem withthe old master is resolved. It is better to have an application to monitor the replicate topology and performfailover automatically, minimizing downtime and keeping replication running smoothly. This is where themysqlfailover utility shines.
Objectives
The goal is to start the mysqlfailover utility to monitor a replication topology and perform failoverautomatically when required.
When the current master fails, manually promoting a slave to the new master can be a very tedious anderror prone task, as all the remaining slave have to be redirected to the new master and the new masterneeds to catch up with all the slaves to make sure that no transactions is lost.
Fortunately, the mysqlfailover utility is capable of executing this full process automatically and in aoptimized way.
How do you setup and use automatic failover?
41
Let's assume that a replication topology with one master (server1:3311) and four slaves (server2:3312,server3:3313, server4:3314, server:3315) was previously setup.
Example Execution
Start the mysqlfailover utility (in console mode - default):
shell> mysqlfailover --master=root@server1:3311 \--slaves=root@server2:3312,root@server3:3313,root@server4:3314,root@server5:3315 \--log=log.txt --rpl-user=rpl:rplNOTE: Log file 'log.txt' does not exist. Will be created.# Checking privileges.
MySQL Replication Failover UtilityFailover Mode = auto Next Interval = Fri Jul 26 10:17:52 2013
Master Information------------------Binary Log File Position Binlog_Do_DB Binlog_Ignore_DBmaster-bin.000001 151
GTID Executed SetNone
Replication Health Status+----------+-------+---------+--------+------------+---------+| host | port | role | state | gtid_mode | health |+----------+-------+---------+--------+------------+---------+| server1 | 3311 | MASTER | UP | ON | OK || server2 | 3312 | SLAVE | UP | ON | OK || server3 | 3313 | SLAVE | UP | ON | OK || server4 | 3314 | SLAVE | UP | ON | OK || server5 | 3315 | SLAVE | UP | ON | OK |+----------+-------+---------+--------+------------+---------+
Q-quit R-refresh H-health G-GTID Lists U-UUIDs L-log entries
Now imagine that the master crashed or is no longer reachable, then after a predefined time interval (bydefault 15 seconds) we can observe that the failover process starts automatically:
Failover starting in 'auto' mode...# Candidate slave server2:3312 will become the new master.# Checking slaves status (before failover).# Preparing candidate for failover.# Creating replication user if it does not exist.# Stopping slaves.# Performing STOP on all slaves.# Switching slaves to new master.# Disconnecting new master as slave.# Starting slaves.# Performing START on all slaves.# Checking slaves for errors.# Failover complete.
Failover console will restart in 5 seconds.
[...]
MySQL Replication Failover UtilityFailover Mode = auto Next Interval = Fri Jul 26 10:25:17 2013
Master Information------------------Binary Log File Position Binlog_Do_DB Binlog_Ignore_DB
How do you setup and use automatic failover?
42
master-bin.000001 151
GTID Executed SetNone
Replication Health Status+----------+-------+---------+--------+------------+---------+| host | port | role | state | gtid_mode | health |+----------+-------+---------+--------+------------+---------+| server2 | 3312 | MASTER | UP | ON | OK || server3 | 3313 | SLAVE | UP | ON | OK || server4 | 3314 | SLAVE | UP | ON | OK || server5 | 3315 | SLAVE | UP | ON | OK |+----------+-------+---------+--------+------------+---------+
Q-quit R-refresh H-health G-GTID Lists U-UUIDs L-log entries
Discussion
The above example illustrates how to start the mysqlfailover utility to monitor the health of thereplication topology and reconfigure the topology when failover occurs.
To setup this feature, we simply need to specify the master's connection with the --master option, thelist of slaves with the --slaves option and the replication user (login and password) using the --rpl-user option. As an alternative to the --slaves options, you can use the --discover-slaves-loginspecifying a user and password (or login-path) to connect to the slaves. The utility attempts to discover allof the slaves connected with the master using the specified login and password. For the above example, '--discover-slaves-login=root' could be used.
The --discover-slaves-login can be very handy especially if there is a huge number of slaves inthe topology, but bear in mind that the explicit specification of slaves is safer and that discovery can failto find some servers. In particular, it is important to note that in order for slaves to be discovered, theymust be started with the '--report-host' and '--report-port' options with the correct values and they must beconnected to the master (I/O thread running) otherwise discovery fails.
It is also recommended to use the --log options to specify a file to register all events, warning and errors.This is useful to keep a record of what happened. For example, to determine when failover occurred and ifthe process completed without errors or warnings.
An important matter to discuss is the order in which the servers are select as candidates for failover. Nodistinction is made in terms of the number of transactions to select the most up-to-date slave to becomethe new master. The reason is very simple; this criteria is non-deterministic as many circumstances (i.e.,network load, server maintenance operations) can temporarily influence the performance of a slave andcould lead to an incorrect selection of the most appropriate candidate. For example, the slave with thebest hardware should be in the long run the most appropriate candidate to become the new master, butfor some unanticipated reason it might actually have fewer transactions than other servers when themaster crashed. Therefore, a more deterministic criteria based on the order in which the servers arespecified is used, allowing the user to control the order in which the candidates are selected. The firstserver that meets the required election criteria, consisting on simple sanity checks (server reachable andrunning with the required options: GTID ON and binary logging enabled), is chosen. More specifically, theselection of the new master follows this order: first, sequentially check the list of servers specified by the--candidates option, then the servers listed in the --slaves option, and finally check any discoveredslaves in an unordered way.
Permissions Required
The user must have permissions to configure replication.
How do you restore the previous master to service after failover?
43
Tips and Tricks
In the above example the mysqlfailover utility was started in the default console mode, but it can alsobe executed as a daemon. For that purpose, the --daemon option needs to be used, more specificallysimply add '--daemon=start' to the command line. When mysqlfailover is executed as a daemon,no output is displayed and all the information is logged to file specified for the --log option, which ismandatory in this case. To stop the execution of the mysqlfailover daemon, simply invoke the utilityusing the option '--daemon=stop'. No other options is required to stop the daemon unless a specific pidfile(which contains the process PID) was specified with the --pidfile option to start the daemon and in thiscase the same option value is also required to stop it.
Another useful feature is the possibility to run external scripts along the execution of the utility to performcustomized actions. The following options can be used to execute different scripts at distinct momentsof the mysqlfailover execution: --exec-fail-check to specify a script to run periodically at eachpredefined interval instead of the default check (i.e., master is reachable and alive) to detect the needto failover, --exec-before to specify a script to execute before starting failover, --exec-after toexecute a script at the end of failover process, --exec-post-failover to run a script after completingthe failover process (before displaying the health report).
3.4.4 How do you restore the previous master to service after failover?
After a successful failover, it is sometimes required to restore the initial topology and promote the crashedserver to become the master again (or even a new server with distinctive hardware characteristics).Sometimes failover can be triggered by a simple network issue (not affecting the health of the initial masterserver) and after being resolved, it may be desirable to put the old master back in the replication topology.We can do this with several of the high availability utilities.
Objectives
The goal of this task is simply to replace the new master of a replication topology with the previous onethat might have been demoted as result of successful automatic failover execution. It is assumed thatthe server to be restored as master is healthy and any previous issue (that triggered failover) have beenresolved.
Let's consider the previous topology after failover, now with a new master (server2:3312) and three slaves(server3:3313, server4:3314, server:3315), and that we want to promote the initial server (server1:3311) tomaster again.
Performing this task manually can be delicate as one wrong or missing step can lead to errors and errorsin the replication topology or even to the lost of some transaction. Once more MySQL Utilities can providea precious assistance to perform this task, in this case requiring the user to follow three simple steps torestore the initial topology as shown below.
Example Execution
There are several steps involved in solving this problem. We walk through each in turn.
You must first stop running the mysqlfailover utility instance and start the (old) master to be restored,i.e. server1:3311.
Next, set the old master (server1:3311) as a slave of the current new master (server2:3312):
shell> mysqlreplicate --master=root@server2:3312 --slave=root@server1:3311 -rpl-user=rpl:rpl# master on localhost: ... connected.# slave on localhost: ... connected.
How do you restore the previous master to service after failover?
44
# Checking for binary logging on master...# Setting up replication...# ...done.
Next, switchover to the previous master to restore the initial replication topology:
shell> mysqlrpladmin --master=root@server2:3312 \ --slaves=root@server2:3313,root@server4:3314,root@server5:3315 \ --rpl-user=rpl:rpl --new-master=root@server1:3311 --demote-master switchover# Checking privileges.# Performing switchover from master at server2:3312 to slave at server1:3311.# Checking candidate slave prerequisites.# Checking slaves configuration to master.# Waiting for slaves to catch up to old master.# Stopping slaves.# Performing STOP on all slaves.# Demoting old master to be a slave to the new master.# Switching slaves to new master.# Starting all slaves.# Performing START on all slaves.# Checking slaves for errors.# Switchover complete.## Replication Topology Health:+----------+-------+---------+--------+------------+---------+| host | port | role | state | gtid_mode | health |+----------+-------+---------+--------+------------+---------+| server1 | 3311 | MASTER | UP | ON | OK || server2 | 3312 | SLAVE | UP | ON | OK || server3 | 3313 | SLAVE | UP | ON | OK || server4 | 3314 | SLAVE | UP | ON | OK || server5 | 3315 | SLAVE | UP | ON | OK |+----------+-------+---------+--------+------------+---------+# ...done.
The initial replication topology is now restored and mysqlfailover can be restarted (but using --force) asinitially:
shell> mysqlfailover --master=root@server1:3311 \ --slaves=root@server2:3312,root@server3:3313,root@server4:3314,server5:3315 \ --log=log.txt --rpl-user=rpl:rpl --force# Checking privileges.
MySQL Replication Failover UtilityFailover Mode = auto Next Interval = Sat Jul 27 02:17:12 2013
Master Information------------------Binary Log File Position Binlog_Do_DB Binlog_Ignore_DBmaster-bin.000002 151
GTID Executed SetNone
Replication Health Status+----------+-------+---------+--------+------------+---------+| host | port | role | state | gtid_mode | health |+----------+-------+---------+--------+------------+---------+| server1 | 3311 | MASTER | UP | ON | OK || server2 | 3312 | SLAVE | UP | ON | OK || server3 | 3313 | SLAVE | UP | ON | OK || server4 | 3314 | SLAVE | UP | ON | OK || server5 | 3315 | SLAVE | UP | ON | OK |
How do you restore the previous master to service after failover?
45
+----------+-------+---------+--------+------------+---------+
Q-quit R-refresh H-health G-GTID Lists U-UUIDs L-log entries
Discussion
The most important step is the execution of the switchover command with the mysqlrpladmin utility.The previous steps can be seen as a preparation for switchover. The first step simply makes sure that theserver is running and that there is no mysqlfailover instance still running that could affect the correctexecution of switchover. The second step sets the old master as a slave of the new master, because theswitchover command can only be performed with slaves. This step also allows the old master to catch upwith the new master. If many transaction have been performed on the new master it is recommended towait a while to let the old master catch up before switchover, otherwise the switchover command mighttake longer.
As expected, the execution of the switchover command requires the specification of the current and newmaster with the --master and --new-master options as well as the list of slaves in the topology usingthe --slaves option (without need to list the new master). The replication user is specified with the --rpl-user option. In this specific example, the use of the option --demote-master is important, becausewithout it the current master (server2:3312) is not be demoted and set as a slave of the new master(server1:3311).
The mysqlrpladmin utility executes and displays information about all required actions to performswitchover. After completing the switchover process, a health report is displayed that you can use toconfirm the successful execution of the command and verify that the topology has changed as expected.
After completing these simple steps, the replication topology is back to its initial structure (before failover)with its old master. Therefore, mysqlfailover is ready to be executed again to monitor the topology andreestablish automatic failover.
Permissions Required
The user have permissions to configure replication.
Tips and Tricks
It is important to wait for the old master to catch up with the new master in order to ensure that notransactions are lost. Depending on the time the old master was down or not accessible it might take aconsiderable time for the old master to execute all missing transactions. MySQL Utilities provide tools thatallow the visualizations of the slaves status, namely the 'health' command of the mysqlrpladmin utility.
An alternative set of steps could have been followed to perform the desired task, using the failovercommand from mysqlrpladmin instead of switchover. In this case, the old master should be specifiedin the candidates list using the option --candidates to be chosen as the preferred slave to become thenew master (no need for the --master, --new-master and --demote-master options). However, an additionalstep are required to set the previous master (server2:3312) as a slave of the old master (server1:3311)using the mysqlreplicate utility because failover does not demote the previous master as it assumesthat it is not available. Notice that unlike switchover that fails if the server specified by the --new-masteroption does not meet the requirements to become master, failover choses another server from the slaveslist to become the new master if the one specified in by the --candidates option is not suitable. It isimportant to keep this behavior differences in mind when deciding which command to apply.
The mysqlfailover utility registers its execution on the servers in order to avoid concurrent executionsof the utility, which may lead to errors and inconsistent state during failover. If the utility detects thatanother instance might be running, it is started in "fail" mode (not taking any action when it detects thatthe master failed). The mysqlfailover instance registration is cleared when the utility exits, and it is
How do you find all of the slaves attached to a master server?
46
expected that registration process can fail on crashed or not accessible servers. The --force optionoverwrite the instance execution check allowing to surpass registration failure on (crashed) old masters,allowing the mysqlfailover utility to start in 'auto' mode.
3.4.5 How do you find all of the slaves attached to a master server?
When you have a topology that has grown over time - many slaves have been added from time-to-time - itmay not be so easy to remember which servers are connected as slaves and even which are slaves to agiven master.
Most often you want to know the state of those slaves at-a-glance. Rather than connect to each slaveindividually, it would be nice to know what the state of each slaves threads using a single command.
Objectives
Show a map of the slaves connected to a master including the state of each slaves threads (IO and SQL).We can do this with a single command using the mysqlrplshow utility.
Example Execution
shell> mysqlrplshow --master=root:root@localhost:13001 \ --disco=root:root --verbosity# master on localhost: ... connected.# Finding slaves for master: localhost:13001
# Replication Topology Graphlocalhost:13001 (MASTER) | +--- localhost:13002 [IO: Yes, SQL: Yes] - (SLAVE) | +--- localhost:13003 [IO: Yes, SQL: Yes] - (SLAVE) | +--- localhost:13004 [IO: Yes, SQL: Yes] - (SLAVE) | +--- localhost:13005 [IO: Yes, SQL: Yes] - (SLAVE)
Discussion
Notice the use of the mysqlrplshow utility. Not only did it show us the slaves attached to the master, italso displayed the state of the IO and SQL thread for each slave.
We used the master server for the --master option but for the slaves, we provided the option --discover-slaves-login which provides the user name and password for the account used to connectto each slave. Without this, we would not be able to determine if the slave is attached (currently) or thestate of its threads.
The --discover-slaves-login option applies to all slaves. If you do not have the same user definedon all of your slaves, you can use the --prompt option to prompt for the user and password for eachslave.
To get the state of the slave threads, use the --verbose option.
Permissions Required
The user connected to the master must have the REPLICATION SLAVE privilege.
The user specified with the --discover-slaves-login option that logs into each slave must have theREPLICATION CLIENT privilege.
How Can you determine if data was replicated correctly?
47
Tips and Tricks
You can also display multiple tiered topologies by providing the --recurse option.
Notice in the example we used the option --discover-slaves-login but specified only --disco=. Thisis a shortcut feature built into every utility. If you type the first N letters of a utility that uniquely identifies itamong the options for said utility, the utility accepts it as if you typed the entire string. For example, the fullname of the option we used is --discover-slaves-login.
3.4.6 How Can you determine if data was replicated correctly?
Once the replication system is setup and running, it is not uncommon that one might want to verify if thedata is being replicated correctly on the slaves. In normal circumstances, the same data is expected onthe master and its slaves (excluding the use of filtering rules). Nevertheless, faults at the data level canintroduce inconsistent changes on servers without raising any kind of error. These data inconsistencies canresult from bugs, hardware malfunction, human errors, or unauthorized access.
It is desirable to detect these issues, in order to fix them and ultimately prevent them from happeningagain. Determining the cause of such issues might not be an easy task since it might be caused bybyzantine failures at distinct levels. However, the first big step toward a solution to this kind of problemis being able to detect data inconsistency and make sure that the data among the replication servers issynchronized.
Objectives
The goal is to execute the mysqlrplsync utility to detect data consistency issues on an active replicationsystem making sure that the master and its slaves are synchronized.
Executing this task manually on an active system is difficult and sometimes tedious since changes maybe continuously happening on all servers (in an asynchronous way) and the same data needs to becompared between servers. Moreover, it can introduce an undesirable and uncontrolled impact on thesystem performance if you lock the tables or stop replication.
Fortunately, the mysqlrplsync utility allows us to perform this task in an easy and optimized way with acontrolled impact on the running system (limiting the execution time of all operations).
Let's assume that a replication topology with one master (server1:3310) and two slaves (server2:3311,server3:3312) was previously setup and it is running without errors.
Example Execution
Start the mysqlrplsync utility, specifying the servers you want to check.
shell> mysqlrplsync --master=user:pass@localhost:3310 \ --slaves=rpl:pass@localhost:3311,rpl:pass@localhost:3312## GTID differences between Master and Slaves:# - Slave 'localhost@3311' is 15 transactions behind Master.# - Slave 'localhost@3312' is 12 transactions behind Master.## Checking data consistency.## Using Master 'localhost@3310' as base server for comparison.# Checking 'test_rplsync_db' database...# - Checking 't0' table data...# [OK] `test_rplsync_db`.`t0` checksum for server 'localhost@3311'.# [OK] `test_rplsync_db`.`t0` checksum for server 'localhost@3312'.
How Can you determine if data was replicated correctly?
48
# - Checking 't1' table data...# [OK] `test_rplsync_db`.`t1` checksum for server 'localhost@3311'.# [OK] `test_rplsync_db`.`t1` checksum for server 'localhost@3312'.# Checking 'test_db' database...# - Checking 't0' table data...# [OK] `test_db`.`t0` checksum for server 'localhost@3311'.# [OK] `test_db`.`t0` checksum for server 'localhost@3312'.# - Checking 't1' table data...# [OK] `test_db`.`t1` checksum for server 'localhost@3311'.# [OK] `test_db`.`t1` checksum for server 'localhost@3312'.##...done.## SUMMARY: No data consistency issue found.#
Discussion
The above example illustrates how to start the mysqlrplsync utility to check if all data on the specifiedreplication topology is synchronized.
To do this, we simply need to specify the master's connection with the --master option, and the listof slaves with the --slaves option. As an alternative to the --slaves option, one can use the --discover-slaves-login specifying a user and password (or login-path) to connect to the slaves andthe utility attempts to discover all of the slaves connected to the master using the specified login. Forexample, '--discover-slaves-login=root:secret' is used to discover all of the slaves and login to each usingthe 'root' user id and the password 'secret'.
The --discover-slaves-login can be very handy especially if there is a huge number of slaves in thetopology, but bear in mind that the explicit specification of slaves is safer and that discovery can fail to findsome servers. In particular, it is important to note that in order for slaves to be discovered, they must bestarted with the '--report-host' and '--report-port' options with appropriate values and they must be correctlyconnected to the master (IO thread running) otherwise discovery may fail to identify the slave.
In the above example, no data consistency issues were found. In case any data difference are found,each is clearly identified by the '[DIFF]' prefix followed by concise information of where and what is thedifference. Additionally, at the end the utility displays a summary of the number of issues found.
The utility also allows users to check consistency on the slaves without specifying the master. However, beadvised that only checking the slaves does not guarantee that there is no data consistency issue betweenthe master and the slaves. Also keep in mind that the results provided by the utility are valid at the time thechecks are actually performed for each table. This is because in an active system with data continuouslychanging, inconstancy issues might be introduced in the immediate instance after the check is completed.
Permissions Required
The user for the master must have permissions to lock tables, perform the checksum, and get informationabout the master status. Specifically, the user used to connect to the master requires the followingprivileges: SUPER or REPLICATION CLIENT, LOCK TABLES and SELECT.
The user for the slaves must have permissions to start/stop the slave, perform the checksum, and getinformation about the slave status. More specifically, the login user to connect to slaves requires thefollowing privileges: SUPER and SELECT.
Tips and Tricks
In the above example, the mysqlrplsync utility was used to check all the data on the servers.However, it is possible to check only specific databases and tables. For that purpose, the user only
How do you fix errant transactions on the replication topology?
49
need specify the target database and tables as arguments when invoking the utility. It is also possibleto exclude specific database and tables from the check using the --exclude option. For example, '--exclude=test_rplsync_db,test_db.t0' excludes the database 'test_rplsync_db' and table 'test_db.t0' from thecheck performed by the utility.
The utility provides important options to control the execution time of the checksum queries performedon each table and the waiting time for slaves to reach an established synchronization point, namely: the--checksum-timeout and --rpl-timeout options. A polling process is applied on each slave toperiodically check if replication has caught up with the defined sync point (all transactions have beenprocessed).
The periodic interval to perform this check can be adjusted with the --interval option. These optionsare fundamental to control the impact of the execution of the utility on the replication system allow you tolimit the execution time of the checksum queries for large tables and the time slaves wait for replication tocatch up. When the timeouts defined by those options are reached, the check is skipped. Nevertheless, theuser can always execute the utility later only for the skipped tables using higher timeout values.
The utility provides the flexibility to be executed separately for different set of servers, only affectingdifferent parts of the replication system at each time. For example, consider a heterogeneous system(where slaves have a different performance characteristics) with one master 'M' and three slaves 'S1', 'S2'and 'S3'. To minimize the impact on the master, the user can run the utility first for the master 'M' and thefastest slave 'S1', and then run it again only for the slaves 'S1', 'S2' and 'S3'. If no consistency issues arefound in the first execution (M = S1) or in the second execution (S1 = S2 = S3), then by transitivity and dueto the inclusion of the same server 'S1' in both checks, it can be said that there is no consistency issues inthe topology (M = S1 = S2 = S3) at the time the first check was completed. This kind of execution must beperformed sequentially and not concurrently, otherwise the synchronization process of each instance mayaffect the other and it may not work properly.
3.4.7 How do you fix errant transactions on the replication topology?
At some point in time, when performing some maintenance/administration operation or other task whichverify your replication topology, you may discover the existence of errant transactions. Some utilitieslike mysqlfailover and mysqlrpladmin detects errant transactions and issues a warning or errorbefore executing. This is done because errant transactions can lead to an unstable replication topology orintroduce errors after a failover or switchover.
What are errant transactions? Errant transactions are transactions directly applied by a client on a slavethat do not exist on the other slaves connected to the master. By nature, these transactions should not bereplicated and can lead to replication errors if the slave that possesses them is promoted to the master.In practice, this can happen for example if the errant transaction corresponds to a data insert or deleteon a table that only exists on that slave. These kind of transactions usually result from a mistake or poorpractice with data being changed directly on the slave without turning off the binary log.
The best way to deal with errant transaction is to avoid them, making sure that every transaction on aslave, even if needed for example to add data for reporting or execute local administrative commands,must be applied with binary logging disabled. See SET sql_log_bin Syntax, for more information abouthow to control logging to the binary log. However, in case errant transaction are found we still need to beable to deal with them in a easy and quick way, skipping those transactions and avoiding them from beingreplicated if the slave becomes the new master.
Note
Always turn off the binary log when executing queries that change data on aslave. Use sql_log_bin = 0 before the queries to turn off the binary log andsql_log_bin = 1 after the query to turn it back on.
How do you fix errant transactions on the replication topology?
50
Objectives
The goal is to execute the mysqlslavetrx utility to skip errant transactions on slaves making sure thatthose transaction are replicated if the slave that originated them becomes the new master.
Skipping errant transactions is done by injecting an empty transaction for each corresponding GTID onevery slave. This can be a very tedious task when performed manually, especially if many transactionsneed to be skipped.
Thankfully, the mysqlslavetrx utility allows us to skip multiple transactions on multiple slaves in a singlestep.
Let's assume that we have three slaves (slave1:3311, slave2:3312, and slave3:3313) and that one of theslaves (slave1:3311) has five errant transactions that need to be skipped on the other slaves. The GTIDset of those transactions is ce969d18-7b10-11e4-aaae-606720440b68:1-5.
Example Execution
Execute the mysqlslavetrx utility, specifying the GTID set of the transaction to skip and the targetslaves.
shell> mysqlslavetrx --gtid-set=ce969d18-7b10-11e4-aaae-606720440b68:1-5 \ --slaves=dba:pass@slave2:3312,dba:pass@slave3:3313WARNING: Using a password on the command line interface can be insecure.## GTID set to be skipped for each server:# - slave2@3312: ce969d18-7b10-11e4-aaae-606720440b68:1-5# - slave3@3313: ce969d18-7b10-11e4-aaae-606720440b68:1-5## Injecting empty transactions for 'slave2:3312'...# Injecting empty transactions for 'slave3:3313'...##...done.#
Discussion
The above example illustrates how to execute the mysqlslavetrx utility to skip the transactions for thespecified GTID set on all given slaves.
To achieve this task, we only need to specify the GTID set for the transactions to be skipped with the --gtid-set option, and the list of connection parameters for the target slaves with the --slaves option.
In the above example, all of the specific GTIDs were skipped on all target slaves injecting an emptytransaction for each one of them. However, it might happen that some of the GTIDs cannot be skippedon some slaves. This can happen if a transaction with the same GTID was previously applied on thetarget slave. The reason is due to the purpose of GTIDs, which is to uniquely identify a transaction,therefore two distinct transactions cannot be applied with the same GTID, otherwise an error is issued.The mysqlslavetrx utility checks the transactions that can be effectively skipped on each slave at thebeginning, excluding already executed GTIDs.
Permissions Required
The user for the slaves must have the required permissions to inject an empty transaction for a specificGTID, i.e. to set the gtid_next variable. More specifically, the login user to connect to slaves requires theSUPER privilege.
Server Operations
51
Tips and Tricks
The mysqlslavetrx provides a dry run mode that allows users to verify the GTID that would be skippedin each slave without actually injecting empty transactions. The --dryrun option must be specified to usethis read-only mode.
3.5 Server OperationsThe tasks described in this section are those used to perform server-wide operations such as cloning aserver instance, determining what MySQL servers are running, etc.
3.5.1 How can you create a temporary copy (running instance) of a server fortesting?
When diagnosing a problem or needing to experiment with a server for developing new features or testingmodifications, you often need a duplicate of your running server so that you can ensure your solution worksfor the actual server. It would be really convenient if we had a process to make a copy of a running serverfor such processes.
Although it is possible and indeed popular to use replication to replicate all of your data to multiple slavesand use one of the slaves for these purposes, for cases where you are working with a particular serveror if replication is not in use, you need some way to duplicate not only the data but also the server and itsstartup parameters.
Objectives
Create a new instance of a running server complete with the same options and the same data.
Example Execution
To meet this objective, we need to use several utilities. But before we get started, we need to know whatspecific options the host server is using. To do this, we use the mysqlserverinfo utility to discover theconfiguration file and the my_print_defaults tool to print the defaults. We can also show the process id tosee what command-line options are being used. We get this from using the --show-servers option withmysqlserverinfo. On POSIX systems, we can use the ps command to find the command line options.
shell> mysqlserverinfo --format=vertical --show-servers## The following MySQL servers are active on this host:# Process id: 2377, Data path: /usr/local/mysql/data# Process id: 2478, Data path: /Volumes/Source/source/temp_13001# Process id: 2487, Data path: /Volumes/Source/source/temp_13002## Source on localhost: ... connected.************************* 1. row ************************* server: localhost:3306 version: 5.1.50-log datadir: /usr/local/mysql/data/ basedir: /usr/local/mysql-5.1.50-osx10.6-x86_64/ plugin_dir: /usr/local/mysql-5.1.50-osx10.6-x86_64/lib/plugin config_file: /etc/my.cnf binary_log: my_log.000287 binary_log_pos: 106 relay_log: None relay_log_pos: None1 row.#...done.
shell> my_print_defaults mysqld /etc/my.cnf
How can you create a temporary copy (running instance) of a server for testing?
52
--port=3306--basedir=/usr/local/mysql--datadir=/usr/local/mysql/data--server_id=5--log-bin=my_log--general_log--slow_query_log--innodb_data_file_path=ibdata1:778M;ibdata2:50M:autoextend
shell> ps -f 2377 UID PID PPID C STIME TTY TIME CMD 74 2377 2300 0 10:56AM ?? 0:02.04 /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql \ --datadir=/usr/local/mysql/data --user=mysql \ --log-error=/logs/me.local.err --pid-file=/logs/me.local.pid \ --port=3306
Notice we now have all of the options from the configuration file as well as the startup options. Wecan now construct the proper options for creating a clone (a running instance) of this server using themysqlserverclone utility. Specifically, we can set the following options using the --mysqld option:
• --log-bin=my_log
• --general_log
• --slow_query_log
• --user=mysql
• --log-error=path
Using these options and choosing a new data directory, we can create a new instance of the host serverusing the following command.
shell> mysqlserverclone --server=root:root@localhost \ --new-data=/source/temp_clone --new-port=3307 --root=root --delete \ --new-id=123 --mysqld="--log-bin=my_log --general-log --slow-query-log \ --user=mysql --log-error=/source/temp_clone"# Cloning the MySQL server running on localhost.# Creating new data directory...# Configuring new instance...# Locating mysql tools...# Setting up empty database and mysql tables...# Starting new instance of the server...# Testing connection to new instance...# Success!# Setting the root password...# Connection Information:# -uroot -proot --socket=/source/temp_clone/mysql.sock#...done.
Now that we have a running instance, we can export all of the data from the host to the clone.
shell> mysqldbexport --server=root:root@localhost:3306 --export=both --all > data.sqlshell> mysqldbimport --server=root:root@localhost:3307 --import=both data.sql# Source on localhost: ... connected.# Importing definitions and data from data.sql.#...done.
Discussion
As you can see, this is a multiple step process. We saw examples of using the mysqlserverinfo,mysqlserverclone, mysqldbexport, and mysqldbimport utilities.
How do you find what MySQL servers are running on a local machine?
53
Notice in the example we used port 3307 for the clone which is reflected in the mysqldbimport utility --server option.
Permissions Required
The user must have permission to read all databases. Since we are using the root account for theseexamples (and you typically would), permissions are not generally a problem.
You also need permissions to create the new data directory and write data to it.
Tips and Tricks
If you want to copy all of the users and their permissions, check out the mysqluserclone utility.
3.5.2 How do you find what MySQL servers are running on a local machine?
One of the challenges for a database administrator or database developer when working with adevelopment server that has multiple instances of MySQL running is knowing exactly how many arerunning and once you know that, which ones are no longer needed.
In some cases, this may have come about by accident but mostly having multiple instances of MySQLrunning is intentional. Whichever the case, it would be nice to be able to use a single command to find allof the MySQL processes.
Objectives
Use the mysqlserverinfo utility to locate all of the MySQL processes running on a host.
Example Execution
shell> mysqlserverinfo --show-servers --server=root:root@localhost \ --format=vertical## The following MySQL servers are active on this host:# Process id: 3007, Data path: /usr/local/mysql/data# Process id: 8191, Data path: /Volumes/Source/source/temp_13001# Process id: 8196, Data path: /Volumes/Source/source/temp_13002# Process id: 8201, Data path: /Volumes/Source/source/temp_13003# Process id: 8207, Data path: /Volumes/Source/source/temp_13004# Process id: 8212, Data path: /Volumes/Source/source/temp_13005## Source on localhost: ... connected.************************* 1. row ************************* server: localhost:3306 version: 5.1.50-log datadir: /usr/local/mysql/data/ basedir: /usr/local/mysql-5.1.50-osx10.6-x86_64/ plugin_dir: /usr/local/mysql-5.1.50-osx10.6-x86_64/lib/plugin config_file: /etc/my.cnf binary_log: my_log.000286 binary_log_pos: 237 relay_log: None relay_log_pos: None1 row.#...done.
Discussion
The mysqlserverinfo utility is normally used to find information about a particular server. We can seesuch results in the example above.
How do you setup and use a secure (encrypted) connection between Utilities and a MySQL server?
54
However, the utility also has an option, --show-servers that displays a list of all of the MySQL serverprocess ids that are executing on the host. This quick glance can help diagnose problems with multipleinstances on the same machine.
Permissions Required
The permissions required include the ability to read the mysql database and to have read access to thedata directory.
Tips and Tricks
Notice the output shows the data directory for each server. You can use this information to examine thefiles in that folder to discern more information such as what databases exist and find and examine thebinary log, etc.
On POSIX systems, you can discover the command-line arguments such as the port number the server isusing with the "ps -f PID" command. For example, to discover the complete information for PID 2487, youcan do the following.
shell> ps -f 2487 UID PID PPID C STIME TTY TIME CMD 501 2487 1 0 10:58AM ttys001 0:00.41 /source/mysql-5.6/sql/mysqld --no-defaults \ --datadir=/source/temp_13002 --tmpdir=/source/temp_13002 \ --pid-file=/source/temp_13002/clone.pid --port=13002 \ --server-id=102 --basedir=/source/mysql-5.6 \ --socket=/source/temp_13002/mysql.sock --log-slave-updates \ --gtid-mode=on --enforce-gtid-consistency --log-bin \ --master-info-repository=TABLE --report-port=13002 \ --report-host=localhost
3.5.3 How do you setup and use a secure (encrypted) connection betweenUtilities and a MySQL server?
Security is a big concern and MySQL Utilities is prepared to use a secure connection to MySQL serversecure-connections using an encrypted connection with SSL. This section shows you how to use SSLwhen connecting to MySQL servers from any utility. All of the utilities use the same mechanism forestablishing an SSL connection.
Objectives
Use the mysqlserverclone utility to create a new instance of your installed MySQL Server. This newinstance is enabled for secure connections using SSL to establish a secure connection by using the SSLoptions. You can also use an options file to specify the SSL certificates needed for the secure connection.
Example Execution
To meet this objective, you need to supply values for the following options of mysqlserverclone:
• --basedir
• --new-port
• --new-data
• --mysqld
How do you setup and use a secure (encrypted) connection between Utilities and a MySQL server?
55
• --root-password
If you are unfamiliar with the previous options, you can find more info in the Section 5.24,“mysqlserverclone — Clone Existing Server to Create New Server” section.
In the --mysqld option you need to specify the --ssl-ca --ssl-cert and --ssl-key options with his respectiveSSL certificate for the new instance of the server. By doing this, the new server instance uses the givencertificates to establish a secure connection. If you are uncertain of how to create the SSL certificates,please following the steps indicated on Creating SSL and RSA Certificates and Keys. The --ssl-ca--ssl-cert and --ssl-key options of mysqlserverclone are used to connect to an existing instanceof MySQL in case you need to use ssl to connect to it and these options are not used to indicate thecertificates to use by the new server instance. For that reason it is necessary to use the --mysqld option ofmysqlserverclone.
The following is an example of the running command.
shell> mysqlserverclone --basedir=C:\MySQL\mysql-5.6.15-winx64 \ --new-data=C:\MySQL\instance_3307 \ --new-port=3307 --root-password=pass \ --mysqld="--ssl-ca=C:/newcerts/cacert.pem \ --ssl-cert=C:/newcerts/server-cert.pem \ --ssl-key=C:/newcerts/server-key.pem" # Cloning the MySQL server located at C:\MySQL\mysql-5.6.15-winx64.# Creating new data directory...# Configuring new instance...# Locating mysql tools...# Setting up empty database and mysql tables...# Starting new instance of the server...# Testing connection to new instance...# Success!# Setting the root password...# Connection Information:# -uroot -ppass --port=3307#...done.
Now we have a new MySQL server instance, and you can confirm the use of the given SSL certificateswith the MySQL command-Line tool (also called the monitor or simply the MySQL client tool) by executingthe command: "show variables like '%ssl%';".
shell> mysql -uroot -ppass --port=3307 -e"show variables like '%ssl%';"+---------------+-----------------------------+| Variable_name | Value |+---------------+-----------------------------+| have_openssl | YES || have_ssl | YES || ssl_ca | C:/newcerts/cacert.pem || ssl_capath | || ssl_cert | C:/newcerts/server-cert.pem || ssl_cipher | || ssl_crl | || ssl_crlpath | || ssl_key | C:/newcerts/server-key.pem |+---------------+-----------------------------+
However, at this moment the root account is not using an encrypted ssl connection. You can see this usingthe MySQL command-Line tool running the "status;" command:
shell> mysql -uroot -ppass --port=3307 -e"status;"--------------
How do you setup and use a secure (encrypted) connection between Utilities and a MySQL server?
56
mysql Ver 14.14 Distrib 5.6.15, for Win64 (x86_64)
Connection id: 11Current database:Current user: root@localhostSSL: Not in use...--------------
You need to add the SSL options necessarily to establish an encrypted connection with SSL, this can bedone in the following form:
shell> mysql -uroot -ppass --port=3307 --ssl-ca=C:/newcerts/cacert.pem \ --ssl-cert=C:/newcerts/server-cert.pem \ --ssl-key=C:/newcerts/server-key.pem -e"status;"--------------mysql Ver 14.14 Distrib 5.6.15, for Win64 (x86_64)
Connection id: 13Current database:Current user: root@localhostSSL: Cipher in use is DHE-RSA-AES256-SHA...--------------
Note
To configure an account to only permit SSL-encrypted connections, the grantsfor that account must include the REQUIRE SSL clause in your GRANT Syntaxstatement.
In the same form that you use the SSL options with the MySQL Command-Line Tool, you can use the SSLoptions on each of the MySQL Utilities. The following is an example of mysqlserverinfo using SSLoptions:
shell> mysqlserverinfo --server=root:pass@localhost:3307 \ --ssl-ca=C:/newcerts/cacert.pem \ --ssl-cert=C:/newcerts/client-cert.pem \ --ssl-key=C:/newcerts/client-key.pem \ --format=vertical# Source on localhost: ... connected.************************* 1. row ************************* server: localhost:3307 config_file: binary_log: binary_log_pos: relay_log: relay_log_pos: version: 5.6.15 datadir: C:\MySQL\instance_3307\ basedir: C:\MySQL\mysql-5.6.15-winx64 plugin_dir: C:\MySQL\mysql-5.6.15-winx64\lib\plugin\ general_log: OFF general_log_file: general_log_file_size: log_error: C:\MySQL\instance_3307\clone.err log_error_file_size: 1569 bytes slow_query_log: OFF slow_query_log_file: slow_query_log_file_size:1 row.#...done.
How do you setup and use a secure (encrypted) connection between Utilities and a MySQL server?
57
Or you can indicate the SSL options by Using Option Files as is mentioned in the Section 2.2, “Connectingto MySQL Servers” documentation. This is an example of how it may look for a group with the options in anoptions file for the command used above.
[instance_3307]port=3307user=rootpassword=passhost=localhostssl-ca=C:/newcerts/cacert.pemssl-cert=C:/newcerts/client-cert.pemssl-key=C:/newcerts/client-key.pem
In this case, the file is located at C:\MySQL\instance-3307.cnf and by indicating this path and thegroup name in the --server option, the options for the mysqlserverinfo of the previous exampletakes this form:
shell> mysqlserverinfo --server=c:\MySQL\instance-3307.cnf[instance_3307] \ --format=vertical# Source on localhost: ... connected.************************* 1. row ************************* server: localhost:3307 config_file: binary_log: binary_log_pos: relay_log: relay_log_pos: version: 5.6.15 datadir: C:\MySQL\instance_3307\ basedir: C:\MySQL\mysql-5.6.15-winx64 plugin_dir: C:\MySQL\mysql-5.6.15-winx64\lib\plugin\ general_log: OFF general_log_file: general_log_file_size: log_error: C:\MySQL\instance_3307\clone.err log_error_file_size: 1569 bytes slow_query_log: OFF slow_query_log_file: slow_query_log_file_size:1 row.#...done.
Discussion
The SSL options (--ssl-ca --ssl-cert and --ssl-key) are available in the MySQL Utilities thatrequires a connection to a server or servers, as is in the case of the --master and --slave options.
Note
An options file can be used to store the connection values, and the MySQL Utilitiescan read the values stored in them as mentioned in the Section 2.2, “Connecting toMySQL Servers” documentation.
Permissions Required
Required permissions include the ability to read the SSL certificate files and the path where they arelocated regardless of the form these SSL certificate paths are given to the MySQL Utilities, in addition ofthe required permissions that each utility requires to accomplish its specific task.
Specialized Operations
58
Tips and Tricks
In the configuration file, different connection options can be stored and separated in groups. The desiredgroup used by the MySQL Utilities can be expressed by indicating the group name in the form config-path["["group-name"]"], such as C:\MySQL\instances.cnf:
[instance_3307]port=3307user=rootpassword=passhost=localhostssl-ca=C:/newcerts/cacert.pemssl-cert=C:/newcerts/client-cert.pemssl-key=C:/newcerts/client-key.pem
[instance_3308]port=3308user=rootpassword=other-passhost=localhostssl-ca=C:/newcerts/cacert_2.pemssl-cert=C:/newcerts/client-cert_2.pemssl-key=C:/newcerts/client-key_2.pem
shell> mysqlreplicate --master=c:\MySQL\instances.cnf[instance_3307] \ --slave=C:\MySQL\instances.cnf[instance_3308]
3.6 Specialized Operations
The tasks described in this section relate to specific situations or configurations and may not apply in thegeneral case. For example, some tasks require a specific commercial plugin such as those for use with theAudit Log Plugin.
3.6.1 How do you record only login events in the audit log?
The audit log plugin records MySQL servers activity. By default, it is set to write all audit events to the logfile which can represent a considerable amount of information. Fortunately, it is possible to control the typeof information that is written to the audit log file by changing the audit log plugin's policy. The policy shouldbe set to log only the events of interest, avoiding wasting resources to log unnecessary events.
In particular, if the audit log plugin is only used to monitor access to the database server (for securitypurposes) then only the login events need to be recorded. The mysqlauditadmin utility allows us toperform such a change in a simple way (as well as changes to other settings).
Objectives
The goal is to set the audit log plugin to write the login events to the log file and no other events. It isassumed that the audit log plugin is enabled and running with the default settings (logging all audit events)on the localhost and default port (3306).
Example Execution
shell> mysqlauditadmin --server=root@localhost:3306 policy --value=LOGINS \ --show-options## Showing options before command.
How do you record only login events in the audit log?
59
## Audit Log Variables and Options#+---------------------------+---------------+| Variable_name | Value |+---------------------------+---------------+| audit_log_buffer_size | 1048576 || audit_log_file | audit.log || audit_log_flush | OFF || audit_log_policy | ALL || audit_log_rotate_on_size | 0 || audit_log_strategy | ASYNCHRONOUS |+---------------------------+---------------+
## Executing POLICY command.#
## Showing options after command.## Audit Log Variables and Options#+---------------------------+---------------+| Variable_name | Value |+---------------------------+---------------+| audit_log_buffer_size | 1048576 || audit_log_file | audit.log || audit_log_flush | OFF || audit_log_policy | LOGINS || audit_log_rotate_on_size | 0 || audit_log_strategy | ASYNCHRONOUS |+---------------------------+---------------+
Discussion
In order to change the type of events recorded to the audit log file, the policy settings must be changed.This is done with the mysqlauditadmin utility using the command 'policy' and specifying the desiredpolicy value with the --value option. As expected the specification of the target server is also requiredusing the --server option.
In the above example, the policy value was set to LOGINS to write only login events to the log file.Nevertheless, other values are also permitted to control the information written to the log file: ALL (write allevents), QUERIES (write only query event), NONE (disable logging), DEFAULT (use the default policy).
Permissions Required
User must have the SELECT privilege for the mysql database. To view the log file, the user must haveread access to the audit log file on the server.
Tips and Tricks
The policy value was specified using uppercase in this example, however uppercase and lowercase can bemixed to specify the policy value (such as "LoGiNs"). The values for this command are still read correctlyindependently of the used cases (case insensitive), but if an unsupported value is specified, an error isissued.
In the above example the --show-options option was used, but it is not required. This option simplydisplays the audit log settings (variables). However, when this option is combined with a command thatchanges one of the audit log variables, it displays the audit log settings before and after the execution ofthe command which can be very handy to confirm that the desired change was performed as expected.
How do you copy or move the audit log?
60
3.6.2 How do you copy or move the audit log?
The audit log information can grow quickly and considerably depending on the type of information writtenand the activity of the MySQL server. Therefore, it might be a good idea to copy the audit log files to adifferent location and free some storage on the server.
The mysqlauditadmin utility also provides this useful functionality.
Objectives
The goal of this task is to copy an existing audit log file to a different location using the mysqlauditadminutility.
It is assumed that the utility is executed on the destination host which must be a non-Windows systemwith the scp (Secure Copy) command line program, and that must have access to the MySQL remoteserver and its data directory with the provided credentials (user and password). It is also assumed that thespecified audit log file exists and user has write privileges on the target directory.
Example Execution
shell> mysqlauditadmin --audit-log-name=/MySQL/SERVER/data/audit.log.13753706179878237 \ copy --copy-to=/ARCHIVE/Audit_Logs --remote-login=user1:server1# Copying file from server1:/MySQL/SERVER/data/audit.log.13753706179878237 to /ARCHIVE/Audit_Logs:user1@server1's password:audit.log.13753706179878237 100% 4716 4.6KB/s 00:01
Discussion
The copy operation can be performed with the mysqlauditadmin utility using the 'copy' commandrequiring the following options: the --audit-log-name option to specify the path and filename of theaudit log file to copy, the --copy-to option to indicate the destination folder, and the --remote-loginoption to specify the user and remote host where the file is located (a prompt for the user password isdisplayed).
The --remote-login option is not required if the source and destination location are on the same serverwhere the utility is executed. Moreover, this option is not supported in Windows system where UNC pathsshould be used.
Permissions Required
The user must have permissions to read the audit log on disk and write the file to the remove location.
Tips and Tricks
The name of the audit log file (audit.log, by default) is defined by the audit_log_file variabledisplayed by mysqlauditadmin when using the --show-options option. Existing audit log files havea timestamp extension except the one that is currently in use. That being said, it might be useful to knowthat it is possible to get information about the existing audit log files using mysqlrpladmin. For instance,to determine which files need to be copied. To get this information use the --file-stats option and the--audit-log-name option specifying the full path of the current audit log file (i.e., without the timestampextension). For example:
shell> mysqlauditadmin --file-stats --audit-log-name=/MySQL/SERVER/data/audit.log+------------------------------+------------+---------------------------+---------------------------+| File | Size | Created | Last Modified |
How can you find the INSERT and UPDATE queries that failed in the audit log?
61
+------------------------------+------------+---------------------------+---------------------------+| audit.log.13753706179878237 | 4716 | Thu Aug 1 16:23:37 2013 | Thu Aug 1 16:23:37 2013 || audit.log | 6062 | Thu Aug 1 16:24:26 2013 | Thu Aug 1 16:24:26 2013 || audit.log.13753705495049727 | 335142503 | Thu Aug 1 16:22:29 2013 | Thu Aug 1 16:22:29 2013 |+------------------------------+------------+---------------------------+---------------------------+
Note
If an audit log file with the timestamp extension is specified in this example for the--audit-log-name option, only the information of the specified file is displayed,as opposed to the file statistics of all existing files.
3.6.3 How can you find the INSERT and UPDATE queries that failed in theaudit log?
Over time, the audit log can contain a lot of useful information. However, how filtering this information andsearching for specific events, for instance in order to determine the possible cause of a problem, can bevery tedious if done manually.
For example, suppose that someone reported that some data changes are missing (and you suspectsome INSERT or UPDATE queries failed) and you want to determine what might be the cause of thosetransaction failures. All queries are recorded to the audit log file, so you just need to get retrieve all queriesof a given type that failed (with a MySQL error) and analyze them.
This can be achieved using common 'grep' command line tools, but likely involves the use of very complexregular expression to filter the desired data. Fortunately, the mysqlauditgrep utility allows to performthis kind of task in a much easier and simple way taking advantage of the knowledge of the structure andsemantics of the audit log files.
Objectives
The goal is display all INSERT and UPDATE queries that failed (independently of error) from the currentaudit log file.
It is assumed that the audit.log file exists and is located in the directory /MySQL/SERVER/data/. Thebelow example show how easy it is to perform the desired search with the mysqlauditgrep utility.
Example Execution
shell> mysqlauditgrep --query-type=INSERT,UPDATE --status=1-9999 /MySQL/SERVER/data/audit.log+--------+---------------------+-------+-------------------------------------------------------+---------------+| STATUS | TIMESTAMP | NAME | SQLTEXT | CONNECTION_ID |+--------+---------------------+-------+-------------------------------------------------------+---------------+| 1046 | 2013-08-01T18:20:46 | Query | INSERT INTO tbl_not_exist (a,b,c) VALUES(1,2,3) | 37 || 1146 | 2013-08-01T18:21:03 | Query | INSERT INTO mysql.tbl_not_exist (a,b,c) VALUES(1,2,3) | 37 || 1054 | 2013-08-01T18:23:10 | Query | INSERT INTO test.t1 (a,b,not_col) VALUES(1,2,3) | 37 || 1146 | 2013-08-01T18:26:14 | Query | UPDATE tbl_not_exist SET a = 1 | 37 || 1054 | 2013-08-01T18:26:53 | Query | UPDATE test.t1 SET not_col = 1 | 37 |+--------+---------------------+-------+-------------------------------------------------------+---------------+
Discussion
As expected, the use of the mysqlauditgrep utility requires the specification of the target audit log fileto search and a few options corresponding to the needed search criteria. In this case, the --query-type option was used to restrict the displayed results to specific types of queries (i.e., only INSERT andUPDATE), and the --status option was used to specify the considered MySQL error codes (i.e., allranging from 1 to 9999).
How do you find connections by the user 'root' in the audit log and show the results in CSV format?
62
The --query-type option allows the specification of a comma separated list of different SQL statements.Apart from INSERT and UPDATE the list of supported values for this option also includes: CREATE,ALTER, DROP, TRUNCATE, RENAME, GRANT, REVOKE, SELECT, DELETE, COMMIT, SHOW, SET,CALL, PREPARE, EXECUTE, DEALLOCATE
The --status option accepts a comma-separated list of non-negative integers (corresponding to MySQLerror codes) or intervals marked with a dash. For example: 1051,1100-1199,1146. In this particularcase, the range value 1-9999 was used to include all MySQL error codes and display all unsuccessfulcommands. To retrieve only successful command (no errors) simply use the value 0 for the --statusoption.
Permissions Required
The user must have permissions to read the audit log on disk.
Tips and Tricks
The value specified for the --query-type option are case insensitive, therefore you can mix lowercaseand uppercase to specify the list of query types. For example, 'insert,Update' produces the same result asusing 'INSERT,UPDATE'. Of course the use of non-supported values raises an appropriate error.
Many other options and search criteria are provided by the mysqlauditgrep utility, check them in orderto use the more appropriate one to meet your needs. Note that the utility provides the --pattern optionto search entries in the audit log file using regular expressions, like common grep tools. By default, thisoption uses standard SQL pattern matching (used by 'LIKE' comparison operator), unless the --regexpoption is used to allow more powerful standard regular expressions (POSIX extended).
3.6.4 How do you find connections by the user 'root' in the audit log and showthe results in CSV format?
The audit log plugin can be used to record information about different type of events which one might needto monitor or keep a record in a different format. For example, a security record with the list of all loginsperformed to the database serve might need to be kept to later track the responsible for some change.Moreover, the retrieved information might need to be converted to a specific format (such as CSV) to feedanother application.
Objectives
The goal of this task is to retrieve from the audit log the information of all the connections established bythe root user to the MySQL Server, and display the resulting information in the comma-separated-value(CSV) format.
Besides the search/filter functionalities using different criteria, the mysqlauditgrep utility also provides afeature to display the resulting information in different formats (including CSV). This allows this task to beperformed easily with in a single step.
It is assumed that the audit.log file exists and is located in the directory /MySQL/SERVER/data/.
Example Execution
shell> mysqlauditgrep --user=root --event-type=Connect \ --format=CSV /MySQL/SERVER/data/audit.log
STATUS,NAME,TIMESTAMP,CONNECTION_ID,HOST,USER,PRIV_USER,IP0,Connect,2013-08-01T15:24:26,33,localhost,root,root,127.0.0.1
How do you find connections by the user 'root' in the audit log and show the results in CSV format?
63
0,Connect,2013-08-01T15:24:26,34,localhost,root,root,127.0.0.10,Connect,2013-08-01T15:24:26,35,localhost,root,root,127.0.0.10,Connect,2013-08-01T15:24:26,36,localhost,root,root,127.0.0.10,Connect,2013-08-01T18:18:43,37,localhost,root,root,127.0.0.10,Connect,2013-08-01T18:49:46,38,,root,root,198.51.100.1041045,Connect,2013-08-01T19:18:08,39,localhost,root,,127.0.0.1
Discussion
To perform this operation the mysqlauditgrep utility requires the indication of the target audit log file asexpected, two criteria search options, and one formatting option to convert the output to the desired format.In this case, the --users option was applied to search the records for the specified user (i.e., "root") andthe --event-type option to retrieve only event of a specific type (i.e., "connect"). The --format optionis the one used to define the output format of the obtained search results.
In this example, only the "Connect" value was used for the --event-type option which correspond tothe logging in event (when a client connects). Nevertheless, this option accepts a comma separated listof event types with the following supported values (beside "Connect"): Audit, Binlog Dump, Change user,Close stmt, Out, Connect, Create DB, Daemon, Debug, Delayed, insert, Drop DB, Execute, Fetch, FieldList, Init DB, Kill, Long Data, NoAudit, Ping, Prepare, Processlist, Query, Quit, Refresh, Register Slave,Reset stmt, Set option, Shutdown, Sleep, Statistics, Table Dump, Time.
In terms of output formats the following are supported beside CSV: GRID (used by default), TAB,VERTICAL and RAW (corresponding to the original XML format of the audit log file).
Permissions Required
The user must have permissions to read the audit log on disk.
Tips and Tricks
The values for the --event-type and --format options are case insensitive, therefore lowercase anduppercase can be mixed to specify these values as long as a supported event type name or format is used.Unlike them, the value specified for the --users option is case-sensitive, so be careful not to mix upperand lower cases here.
It is possible to find some event type values with a space in the middle, for example like "Binlog Dump"or "Init DB". If one of such values needs to be specified for the --event-type option then it must besurrounded by double (") or single (') quotes depending on the operating system.
64
65
Chapter 4 Overview of MySQL Utilities
Table of Contents4.1 Binary Log Operations ................................................................................................................ 654.2 Database Operations .................................................................................................................. 654.3 General Operations .................................................................................................................... 664.4 High Availability Operations ........................................................................................................ 674.5 Server Operations ...................................................................................................................... 684.6 Specialized Operations ............................................................................................................... 68
This chapter presents an brief overview of each of the available utilities. The utilities are grouped intosections based on the type of administrative function that they perform.
4.1 Binary Log Operations
These utilities are designed to perform operations on binary log files.
• mysqlbinlogmove
• Relocate binary log files
• Move files based on their sequence number or modified date
• mysqlbinlogpurge
• Purge binary logs
• mysqlbinlogrotate
• Rotate binary logs
4.2 Database Operations
These utilities are those designed to work at the database-level. They include utilities that can used tomanage databases on one or more servers.
• mysqldbcompare
• Compare databases on two servers or the same server
• Compare definitions and data
• Generate a difference report
• Generate SQL transformation statements
• mysqldbcopy
• Copy databases between servers
• Clone databases on the same server
• Supports rename
General Operations
66
• mysqldbexport
• Export metadata and/or data from one or more databases
• Formats: SQL, CSV, TAB, Grid, Vertical
• mysqldbimport
• Import metadata and data from one or more files
• Reads all formats from mysqldbexport
• mysqldiff
• Compare object definitions
• Generate a difference report
4.3 General OperationsThese utilities are those designed to perform general operations such as reporting and searching.
• mysqldiskusage
• Show disk usage for databases
• Generate reports in SQL, CSV, TAB, Grid, Vertical
• mysqlfrm
• Reads .frm files, optionally in byte-by-byte diagnostic mode
• Generates CREATE statements from table definition data
• mysqlgrants
• Displays grants per object.
• Produce reports by user, user with grants, and GRANT statements.
• mysqlindexcheck
• Read indexes for one or more tables
• Check for redundant and duplicate indexes
• Generate reports in SQL, CSV, TAB, Grid, Vertical
• mysqlmetagrep
• Search metadata
• Regexp, database search
• Generate SQL statement for search query
• mysqlprocgrep
• Search process information
High Availability Operations
67
• Generate SQL statement for search
• Kill processes that match query
• mysqluserclone
• Clone a user account, to the same or different server
• Show user grants
• mysqluc
• Command line client for running MySQL Utilities
• Allows a persistent connection to a MySQL Server
• Tab completion for utility names and options
• Allows calling the commands with shorter names, such as using "serverinfo" instead ofmysqlserverinfo
4.4 High Availability Operations
These utilities are those designed to support replication and high availability operations for MySQL servers.
• mysqlfailover
• Provides automatic failover on a replication topology
• Uses Global Transaction Identifiers (GTID, MySQL Server 5.6.5+)
• mysqlreplicate
• Setup replication
• Start from beginning, current, specific binlog, pos
• mysqlrplms
• Provides round-robin multi-source replication (a slave server continually cycles through multiplemasters in order to store a consolidated data set)
• Uses Global Transaction Identifiers (GTID, MySQL Server 5.6.9+)
• mysqlrpladmin
• Administers the replication topology
• Allows recovery of the master
• Commands include elect, failover, gtid, health, start, stop, and switchover
• mysqlrplcheck
• Check replication configuration
• Tests binary logging on master
Server Operations
68
• mysqlrplshow
• Show slaves attached to master
• Can search recursively
• Show the replication topology as a graph or list
• mysqlrplsync
• Check data consistency between servers in a replicated setup
• Uses Global Transaction Identifiers (GTID)
• Requires MySQL Server 5.6.14 and higher
• mysqlslavetrx
• Skip multiple transaction on slaves
• Uses Global Transaction Identifiers (GTID)
4.5 Server Operations
These utilities are used to perform server-wide operations.
• mysqlserverclone
• Start a new instance of a running server
• mysqlserverinfo
• Show server information
• Can search for running servers on a host
• Access online or offline servers
4.6 Specialized Operations
These utilities are designed to be used with a specific commercial extension. In this case, these utilitiesrequire the Audit Log Plugin.
• mysqlauditadmin
• Monitor the audit log
• Copy, rotate, and configure the audit log
• mysqlauditgrep
• Search the audit log
• Output results to different formats
69
Chapter 5 Manual Pages
Table of Contents5.1 mysqlauditadmin — Allows users to perform maintenance actions on the audit log .................... 695.2 mysqlauditgrep — Allows users to search the current or an archived audit log .......................... 755.3 mysqlbinlogmove — Binary log relocate utility .......................................................................... 825.4 mysqlbinlogpurge — Binary log purge utility ........................................................................... 895.5 mysqlbinlogrotate — Binary log rotate utility ......................................................................... 925.6 mysqldbcompare — Compare Two Databases and Identify Differences ...................................... 945.7 mysqldbcopy — Copy Database Objects Between Servers ....................................................... 1035.8 mysqldbexport — Export Object Definitions or Data from a Database ...................................... 1105.9 mysqldbimport — Import Object Definitions or Data into a Database ....................................... 1195.10 mysqldiff — Identify Differences Among Database Objects ................................................... 1255.11 mysqldiskusage — Show Database Disk Usage ................................................................... 1315.12 mysqlfailover — Automatic replication health monitoring and failover ................................... 1345.13 mysqlfrm — File reader for .frm files. ..................................................................................... 1465.14 mysqlgrants — Display grants by object .............................................................................. 1505.15 mysqlindexcheck — Identify Potentially Redundant Table Indexes ........................................ 1575.16 mysqlmetagrep — Search Database Object Definitions ......................................................... 1605.17 mysqlprocgrep — Search Server Process Lists .................................................................... 1655.18 mysqlreplicate — Set Up and Start Replication Between Two Servers ................................. 1695.19 mysqlrplms — Set Up and Start Replication from a Slave to Multiple Masters .......................... 1735.20 mysqlrpladmin — Administration utility for MySQL replication ................................................ 1785.21 mysqlrplcheck — Check Replication Prerequisites ............................................................... 1905.22 mysqlrplshow — Show Slaves for Master Server .................................................................. 1945.23 mysqlrplsync — Replication synchronization checker ........................................................... 1995.24 mysqlserverclone — Clone Existing Server to Create New Server ....................................... 2065.25 mysqlserverinfo — Display Common Diagnostic Information from a Server .......................... 2095.26 mysqlslavetrx — Slave transaction skip utility ..................................................................... 2135.27 mysqluc — Command line client for running MySQL Utilities ................................................... 2165.28 mysqluserclone — Clone Existing User to Create New User ................................................. 220
This chapter includes the manual pages for each of the utilities. Each manual page is formatted similar to atypical Unix man page.
5.1 mysqlauditadmin — Allows users to perform maintenanceactions on the audit log
This utility allows you to maintain the audit log including the ability to view and modify a subset of auditlog control variables, display the audit log file status, perform on-demand rotation of the log file, and copyfiles to other locations. These features enable you to easily monitor the audit log file growth and control itsrotation (automatically based on the defined file size threshold, or manually by a on-demand command).
Rotation refers to the action of replacing the current audit log file by a new one for continuous use,renaming (with a timestamp extension) and copying the previously used audit log file to a defined locationfor archival purposes.
The available actions include the following:
• copy
OPTIONS
70
This command copies the audit log specified by --audit-log-name to the destination path specifiedby --copy-to. The --remote-login option can be used to copy log files from a remote location.Note: the destination path must be locally accessible by the current user.
• policy
The policy command is used to change the audit logging policy. The accepted values include thefollowing, which are set using the --value option.
Note
The --server option is also required to execute this command.
Starting from MySQL server 5.6.20 and 5.7.5, the value is read only for theaudit_log_policy variable. MySQL server 5.7.9 introduced two new variables:audit_log_connection_policy and audit_log_statement_policy whose values aredetermined based on the presence and value of the audit_log_policy startupvariable. See the MySQL reference manual for more information about how thepolicy variables are set. These changes are supported starting from MySQLUtilities 1.5.2.
• ALL: log all events
• NONE: log nothing
• LOGINS: only log login events
• QUERIES: only log query events
• DEFAULT: sets the default log policy
• rotate_on_size
This command sets the file size threshold for automatic rotation of the audit log (theaudit_log_rotate_on_size variable). The value is set using the --value option, and must be inthe range (0, 4294967295). This command also requires the --server option to be specified. Note: ifthe variable is set with a value that is not a multiple of 4096, then it is truncated to the nearest multiple.
• rotate
This command is used to perform an on-demand audit log rotation, and only requires the --serveroption to be passed. Note: this command has no effect if the audit log file size is smaller than 4096,which is the minimum value allowed that is greater than 0 for the audit_log_rotate_on_sizevariable).
OPTIONS
mysqlauditadmin accepts the following command-line options:
• --audit-log-name=AUDIT_LOG_FILE
Full path and filename for the audit log file. Used by the --file-stats option, and the copy command.
• --copy-to=COPY_DESTINATION
The location to copy the specified audit log file. The path must be locally accessible for the current user.
OPTIONS
71
• --file-stats
Display the audit log file statistics.
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --remote-login=REMOTE_LOGIN
User name and host to be used for the remote login, for copying log files. It is defined using the followingformat: user:host or IP. The utility displays a prompt for the password.
• --server=SERVER
Connection information for the server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --show-options
Display the audit log system variables.
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --value=VALUE
Value used to set variables based on the specified commands, such as policy and rotate_on_size.
NOTES
72
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
NOTES
This utility can only be applied to servers with the audit log plugin enabled. And the audit log plugin isavailable as of MySQL Server versions 5.5.28 and 5.6.10.
This utility requires Python version 2.6 or higher, but does not support Python 3.
The path to the MySQL client tools should be included in the PATH environment variable in order to use theauthentication mechanism with login-paths. This allows the utility to use the my_print_defaults tools,which is required to read the login-path values from the login configuration file (.mylogin.cnf). Thisfeature exists as of MySQL Server 5.6.6, see mysql_config_editor — MySQL Configuration Utility.
Changes to MySQL Enterprise Audit are not documented here, so your output might be different than theexamples shown. For example, a new (or removed) MySQL Enterprise Audit option might affect the output.
LIMITATIONS
The --remote-login option is not supported on Microsoft Windows platforms. For Microsoft Windows,use UNC paths and perform a local copy operation, omitting the --remote-login option.
EXAMPLES
To display the audit log system variables, run the following command:
shell> mysqlauditadmin --show-options --server=root@localhost:3310
## Showing options after command.## Audit Log Variables and Options#+------------------------------+---------------+| Variable_name | Value |+------------------------------+---------------+| audit_log_buffer_size | 1048576 || audit_log_connection_policy | NONE || audit_log_current_session | ON || audit_log_exclude_accounts | || audit_log_file | audit.log || audit_log_flush | OFF || audit_log_format | OLD || audit_log_include_accounts | || audit_log_policy | ALL || audit_log_rotate_on_size | 0 || audit_log_statement_policy | ALL || audit_log_strategy | ASYNCHRONOUS |+------------------------------+---------------+
To perform a (manual) rotation of the audit log file, use the following command:
EXAMPLES
73
shell> mysqlauditadmin --server=root@localhost:3310 rotate
## Executing ROTATE command.#
To display the audit log file statistics, run the following command:
shell> mysqlauditadmin --file-stats --audit-log-name=../SERVER/data/audit.log
+------------------------------+--------+---------------------------+---------------------------+ | File | Size | Created | Last Modified | +------------------------------+--------+---------------------------+---------------------------+ | audit.log | 3258 | Wed Sep 26 11:07:43 2012 | Wed Sep 26 11:07:43 2012 | | audit.log.13486539046497235 | 47317 | Wed Sep 26 11:05:04 2012 | Wed Sep 26 11:05:04 2012 | +------------------------------+--------+---------------------------+---------------------------+
To change the audit log policy to log only query events, and show the system variables before and after theexecution of the policy command, use the following command:
shell> mysqlauditadmin --show-options --server=root@localhost:3310 policy \ --value=QUERIES
## Showing options before command.## Audit Log Variables and Options#+------------------------------+---------------+| Variable_name | Value |+------------------------------+---------------+| audit_log_buffer_size | 1048576 || audit_log_connection_policy | ALL || audit_log_current_session | ON || audit_log_exclude_accounts | || audit_log_file | audit.log || audit_log_flush | OFF || audit_log_format | OLD || audit_log_include_accounts | || audit_log_policy | ALL || audit_log_rotate_on_size | 0 || audit_log_statement_policy | ALL || audit_log_strategy | ASYNCHRONOUS |+------------------------------+---------------+
## Executing POLICY command.#
## Showing options after command.## Audit Log Variables and Options#+------------------------------+---------------+| Variable_name | Value |+------------------------------+---------------+| audit_log_buffer_size | 1048576 || audit_log_connection_policy | NONE || audit_log_current_session | ON || audit_log_exclude_accounts | || audit_log_file | audit.log || audit_log_flush | OFF || audit_log_format | OLD || audit_log_include_accounts | |
EXAMPLES
74
| audit_log_policy | ALL || audit_log_rotate_on_size | 0 || audit_log_statement_policy | ALL || audit_log_strategy | ASYNCHRONOUS |+------------------------------+---------------+
To change the audit log automatic file rotation size (audit_log_rotate_on_size) to 32535, and show thesystem variables before and after the execution of the rotate_on_size command, use the followingcommand. (Notice that the value set is actually 28672 because the specified rotate_on_size value istruncated to a multiple of 4096):
shell> mysqlauditadmin --show-options --server=root@localhost:3310 rotate_on_size \ --value=32535
## Showing options before command.## Audit Log Variables and Options#+------------------------------+---------------+| Variable_name | Value |+------------------------------+---------------+| audit_log_buffer_size | 1048576 || audit_log_connection_policy | ALL || audit_log_current_session | ON || audit_log_exclude_accounts | || audit_log_file | audit.log || audit_log_flush | OFF || audit_log_format | OLD || audit_log_include_accounts | || audit_log_policy | ALL || audit_log_rotate_on_size | 0 || audit_log_statement_policy | ALL || audit_log_strategy | ASYNCHRONOUS |+------------------------------+---------------+
## Executing POLICY command.#
## Showing options after command.## Audit Log Variables and Options#+------------------------------+---------------+| Variable_name | Value |+------------------------------+---------------+| audit_log_buffer_size | 1048576 || audit_log_connection_policy | NONE || audit_log_current_session | ON || audit_log_exclude_accounts | || audit_log_file | audit.log || audit_log_flush | OFF || audit_log_format | OLD || audit_log_include_accounts | || audit_log_policy | ALL || audit_log_rotate_on_size | 28672 || audit_log_statement_policy | ALL || audit_log_strategy | ASYNCHRONOUS |+------------------------------+---------------+
To perform a copy of a audit log file to another location, use the following command:
PERMISSIONS REQUIRED
75
shell> mysqlauditadmin --audit-log-name=../SERVER/data/audit.log.13486539046497235 \ copy --copy-to=/BACKUP/Audit_Logs
To copy a audit log file from a remote server/location to the current location (a prompt is issued for the userpassword), use the following command:
shell> mysqlauditadmin --audit-log-name=audit.log.13486539046497235 \ copy --remote-login=user:host --copy-to=.
PERMISSIONS REQUIRED
The user must have permissions to read the audit log file(s) on disk and write the file(s) to the remotelocation.
5.2 mysqlauditgrep — Allows users to search the current or anarchived audit log
This utility allows you to search the current or archived audit logs permitting you to display data from theaudit log file according to the defined search criterion. It also allows you to output the results in differentformats, namely GRID (default), TAB, CSV, VERTICAL, and RAW (the original XML format).
This utility allows you to search and filter the returned audit log records by: users (--users), date and timeranges (--start-date and --end-date), SQL query types (--query-type), logged event and recordtypes (--event-type), status (--status), and matching patterns (--pattern). Any of these searchoptions can be combined and used together, with the retrieved records resulting from all options evaluatedas an and condition (all must be true).
The --pattern supports two types of pattern matching: standard SQL, used with the SQL LIKE operator(SQL patterns), and standard REGEXP (POSIX regular expression patterns).
This utility always requires an audit log file. The AUDIT_LOG_FILE argument should contain the a full pathand filename for the audit log file. If not specified, a notification concerning this requirement is displayed.If --format is specified without search parameters, all of the records of the audit log are displayed in thespecified format. Thus, you can use this feature to view the audit log file in the supported formats.
The --file-stats option is not considered a search criteria and is used to display the file statistics of aspecified audit log. Other search options are ignored when the --file-stats option is used, except the--format option, which formats the results accordingly.
To specify the format of the generated results, use one of the following values with the --format option:
• GRID (default)
Display output in grid or table format like that of the mysql client command-line tool.
• CSV
Display output in comma-separated values format.
• VERTICAL
Display output in single-column format like that of the \G command for the mysql client command-linetool.
• RAW
Standard SQL Pattern Matching
76
Display output results in the original raw format of the audit log records, which is written in XML.
Standard SQL Pattern Matching
The simple patterns defined by the SQL standard enables users to use two characters with specialmeanings: “%” (percent) matches zero or more characters, and “_” (underscore) matches exactly onearbitrary character. In standard SQL, these types of patterns are used with the LIKE comparison operator,and they are case-insensitive by default. This utility assumes that they are case-insensitive.
For example:
• "audit%"
Match any string that starts with "audit".
• "%log%"
Match any string containing the word "log".
• "%_"
Match any string consisting of one or more characters.
For documentation about the standard SQL pattern matching syntax, see Pattern Matching.
REGEXP Pattern Matching (POSIX)
Standard REGEXP patterns are more powerful than the simple patterns defined in the SQL standard. Aregular expression is a string of ordinary and special characters specified to match other strings. UnlikeSQL Patterns, REGEXP patterns are case-sensitive. The REGEXP syntax defines the following characterswith special meaning:
• .
Match any character.
• ^
Match the beginning of a string.
• $
Match the end of a string.
• \
Match zero or more repetitions of the preceding regular expression.
• +
Match one or more repetitions of the preceding regular expression.
• ?
Match zero or one repetition of the preceding regular expression.
• |
REGEXP Pattern Matching (POSIX)
77
Match either the regular expressions from the left or right of |.
• []
Indicates a set of characters to match.
Note
Special characters lose their special meaning inside sets. In particular, the caretsymbol (^) acquires a different meaning if it is the first character of the set,matching the complementary set (i.e., all the characters that are not in the set arematched).
• {m}
Match m repetitions of the preceding regular expression.
• {m,n}
Match from m to n repetitions of the preceding regular expression.
• ()
Define a matching group, and matches the regular expression inside the parentheses.
For example:
• "a\*"
Match a sequence of zero or more a.
• "a+"
Match a sequence of one or more a.
• "a?"
Match zero or one a.
• "ab|cd"
Match ab or cd.
• "[axy]"
Match a, x or y.
• "[a-f]"
Match any character in the range a to f (that is, a, b, c, d, e, or f).
• "[^axy]"
Match any character except a, x or y.
• "a{5}"
Match exactly five copies of a.
OPTIONS
78
• "a{2,5}"
Match from two to five copies of a.
• "(abc)+"
Match one or more repetitions of abc.
This is a brief overview of regular expressions that can be used to define this type of patterns. The fullsyntax is described in the Python "re" module docs, supporting the definition of much more complex patternmatching expression.
OPTIONS
mysqlauditgrep accepts the following command-line options:
• --end-date=END_DATE
End date/time to retrieve log entries until the specified date/time range. If not specified or the value is 0,all entries to the end of the log are displayed. Accepted formats: "yyyy-mm-ddThh:mm:ss" or "yyyy-mm-dd".
• --event-type=EVENT_TYPE
Comma-separated list of event types to search in all audit log records matching the specified types.Supported values are: Audit, Binlog Dump, Change user, Close stmt, Connect Out, Connect, Create DB,Daemon, Debug, Delayed insert, Drop DB, Execute, Fetch, Field List, Init DB, Kill, Long Data, NoAudit,Ping, Prepare, Processlist, Query, Quit, Refresh, Register Slave, Reset stmt, Set option, Shutdown,Sleep, Statistics, Table Dump, Time.
• --file-stats
Display the audit log file statistics.
• --format=FORMAT, -f FORMAT
Output format to display the resulting data. Supported format values: GRID (default), TAB, CSV,VERTICAL and RAW.
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --pattern=PATTERN, -e PATTERN
Search pattern to retrieve all entries with at least one attribute value matching the specified pattern.By default the standard SQL LIKE patterns are used for matching. If the --regexp option is set, thenREGEXP patterns must be specified for matching.
• --query-type=QUERY_TYPE
Comma-separated list of SQL statements/commands to search for and match. Supported values:CREATE, ALTER, DROP, TRUNCATE, RENAME, GRANT, REVOKE, SELECT, INSERT, UPDATE,DELETE, COMMIT, SHOW, SET, CALL, PREPARE, EXECUTE, DEALLOCATE.
NOTES
79
• --regexp, --basic-regexp, -G
Indicates that pattern matching is performed using a regular expression REGEXP (from the Python remodule). By default, the simple standard SQL LIKE patterns are used for matching. This affects how thevalue specified by the --pattern option is interpreted.
• --start-date=START_DATE
Starting date/time to retrieve log entries from the specified date/time range. If not specified or the valueis 0, all entries from the start of the log are displayed. Accepted formats: yyyy-mm-ddThh:mm:ss or yyyy-mm-dd.
• --status=STATUS
Comma-separated list of status values or intervals to search for all audit log records with a matchingstatus. Status values are non-negative integers (corresponding to MySQL error codes). Status intervalsare closed (i.e., include both endpoints) and defined simply using a dash between its endpoints. ForExample: 1051,1068-1075,1109,1146.
The --status option is available as of MySQL Utilities 1.2.4 / 1.3.3.
• --users=USERS, -u USERS
Comma-separated list of user names, to search for their associated log entries. For example:"dan,jon,john,paul,philip,stefan".
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
NOTES
This utility is available as of MySQL Utilities 1.2.0.
This utility can only be applied to servers with the audit log plugin enabled. And the audit log plugin isavailable as of MySQL Server versions 5.5.28 and 5.6.10.
This utility support both of the existing audit log file formats (old and new). The new audit log format issupported as of MySQL Utilities 1.4.3. See Audit Log File Formats, for more information about available fileformats.
This utility requires the use of Python version 2.6 or higher, but does not support Python 3.
Single or double quote characters (respectively, ' or ") can be used around option values. In fact, quotesare required to set some options values correctly, such as values with whitespace. For example, to specifythe event types Create DB and Drop DB for the --event-type option, the following syntax must beused: --event-type='Create DB,Drop DB' or --event-type="Create DB,Drop DB".
EXAMPLES
To display the audit log file statistics and output the results in CSV format, run the following command:
EXAMPLES
80
shell> mysqlauditgrep --file-stats --format=CSV /SERVER/data/audit.log
# # Audit Log File Statistics: # File,Size,Created,Last Modified audit.log,9101,Thu Sep 27 13:33:11 2012,Thu Oct 11 17:40:35 2012
# # Audit Log Startup Entries: #
SERVER_ID,STARTUP_OPTIONS,NAME,TIMESTAMP,MYSQL_VERSION,OS_VERSION,VERSION 1,/SERVER/sql/mysqld --defaults-file=/SERVER/my.cnf,Audit,2012-09-27T13:33:11,5.5.29-log,x86_64-Linux,1
To display the audit log entries of specific users, use the following command:
shell> mysqlauditgrep --users=tester1,tester2 /SERVER/data/audit.log
To display the audit log file statistics, run the following command:
shell> mysqlauditgrep --users=tester1,tester2 /SERVER/data/audit.log
+---------+------------+----------+----------------------+----------------+------------+----------+------------+------------+----------------------------------+ | STATUS | SERVER_ID | NAME | TIMESTAMP | CONNECTION_ID | HOST | USER | PRIV_USER | IP | SQLTEXT | +---------+------------+----------+----------------------+----------------+------------+----------+------------+------------+----------------------------------+ | 0 | 1 | Connect | 2012-09-28T11:26:50 | 9 | localhost | root | tester1 | 127.0.0.1 | None | | 0 | 1 | Query | 2012-09-28T11:26:50 | 9 | None | root | tester1 | None | SET @@session.autocommit = OFF | | 0 | 1 | Ping | 2012-09-28T11:26:50 | 9 | None | root | tester1 | None | None | | 0 | 1 | Query | 2012-09-28T11:26:50 | 9 | None | root | tester1 | None | SHOW VARIABLES LIKE 'READ_ONLY' | | 0 | 1 | Query | 2012-09-28T11:26:50 | 9 | None | root | tester1 | None | COMMIT | | 0 | 1 | Ping | 2012-09-28T11:26:50 | 9 | None | root | tester1 | None | None | | 0 | 1 | Query | 2012-09-28T11:26:50 | 9 | None | root | tester1 | None | COMMIT | | 0 | 1 | Quit | 2012-09-28T11:26:50 | 9 | None | root | tester1 | None | None | | 0 | 1 | Connect | 2012-10-10T15:55:55 | 11 | localhost | tester2 | root | 127.0.0.1 | None | | 0 | 1 | Query | 2012-10-10T15:55:55 | 11 | None | tester2 | root | None | select @@version_comment limit 1 | | 0 | 1 | Query | 2012-10-10T15:56:10 | 11 | None | tester2 | root | None | show databases | | 1046 | 1 | Query | 2012-10-10T15:57:26 | 11 | None | tester2 | root | None | show tables test | | 1046 | 1 | Query | 2012-10-10T15:57:36 | 11 | None | tester2 | root | None | show tables test | | 0 | 1 | Query | 2012-10-10T15:57:51 | 11 | None | tester2 | root | None | show tables in test | | 0 | 1 | Quit | 2012-10-10T15:57:59 | 11 | None | tester2 | root | None | None | | 0 | 1 | Connect | 2012-10-10T17:35:42 | 12 | localhost | tester2 | root | 127.0.0.1 | None | | 0 | 1 | Query | 2012-10-10T17:35:42 | 12 | None | tester2 | root | None | select @@version_comment limit 1 | | 0 | 1 | Quit | 2012-10-10T17:47:22 | 12 | None | tester2 | root | None | None | +---------+------------+----------+----------------------+----------------+------------+----------+------------+------------+----------------------------------+
To display the audit log entries for a specific date/time range, use the following command:
shell> mysqlauditgrep --start-date=2012-09-27T13:33:47 --end-date=2012-09-28 /SERVER/data/audit.log
+---------+----------------------+--------+----------------+---------------------------------------------------------------------------+ | STATUS | TIMESTAMP | NAME | CONNECTION_ID | SQLTEXT | +---------+----------------------+--------+----------------+---------------------------------------------------------------------------+ | 0 | 2012-09-27T13:33:47 | Ping | 7 | None | | 0 | 2012-09-27T13:33:47 | Query | 7 | SELECT * FROM INFORMATION_SCHEMA.PLUGINS WHERE PLUGIN_NAME LIKE 'audit%' | | 0 | 2012-09-27T13:33:47 | Query | 7 | COMMIT | | 0 | 2012-09-27T13:34:48 | Quit | 7 | None | | 0 | 2012-09-27T13:34:48 | Quit | 8 | None | +---------+----------------------+--------+----------------+---------------------------------------------------------------------------+
To display the audit log entries matching a specific SQL LIKE pattern, use the following command:
EXAMPLES
81
shell> mysqlauditgrep --pattern="% = ___"; /SERVER/data/audit.log
+---------+----------------------+--------+---------------------------------+----------------+ | STATUS | TIMESTAMP | NAME | SQLTEXT | CONNECTION_ID | +---------+----------------------+--------+---------------------------------+----------------+ | 0 | 2012-09-27T13:33:39 | Query | SET @@session.autocommit = OFF | 7 | | 0 | 2012-09-27T13:33:39 | Query | SET @@session.autocommit = OFF | 8 | | 0 | 2012-09-28T11:26:50 | Query | SET @@session.autocommit = OFF | 9 | | 0 | 2012-09-28T11:26:50 | Query | SET @@session.autocommit = OFF | 10 | +---------+----------------------+--------+---------------------------------+----------------+
To display the audit log entries matching a specific REGEXP pattern, use the following command:
shell> mysqlauditgrep --pattern=".* = ..." --regexp /SERVER/data/audit.log
+---------+----------------------+--------+---------------------------------+----------------+ | STATUS | TIMESTAMP | NAME | SQLTEXT | CONNECTION_ID | +---------+----------------------+--------+---------------------------------+----------------+ | 0 | 2012-09-27T13:33:39 | Query | SET @@session.autocommit = OFF | 7 | | 0 | 2012-09-27T13:33:39 | Query | SET @@session.autocommit = OFF | 8 | | 0 | 2012-09-28T11:26:50 | Query | SET @@session.autocommit = OFF | 9 | | 0 | 2012-09-28T11:26:50 | Query | SET @@session.autocommit = OFF | 10 | +---------+----------------------+--------+---------------------------------+----------------+
To display the audit log entries of specific query types, use the following command:
shell> mysqlauditgrep --query-type=show,SET /SERVER/data/audit.log
+---------+----------------------+--------+-------------------------------------------------+----------------+ | STATUS | TIMESTAMP | NAME | SQLTEXT | CONNECTION_ID | +---------+----------------------+--------+-------------------------------------------------+----------------+ | 0 | 2012-09-27T13:33:39 | Query | SET NAMES 'latin1' COLLATE 'latin1_swedish_ci' | 7 | | 0 | 2012-09-27T13:33:39 | Query | SET @@session.autocommit = OFF | 7 | | 0 | 2012-09-27T13:33:39 | Query | SHOW VARIABLES LIKE 'READ_ONLY' | 7 | | 0 | 2012-09-27T13:33:39 | Query | SHOW VARIABLES LIKE 'datadir' | 7 | | 0 | 2012-09-27T13:33:39 | Query | SHOW VARIABLES LIKE 'basedir' | 7 | | 0 | 2012-09-27T13:33:39 | Query | SET NAMES 'latin1' COLLATE 'latin1_swedish_ci' | 8 | | 0 | 2012-09-27T13:33:39 | Query | SET @@session.autocommit = OFF | 8 | | 0 | 2012-09-27T13:33:39 | Query | SHOW VARIABLES LIKE 'READ_ONLY' | 8 | | 0 | 2012-09-27T13:33:39 | Query | SHOW VARIABLES LIKE 'basedir' | 8 | | 0 | 2012-09-28T11:26:50 | Query | SET NAMES 'latin1' COLLATE 'latin1_swedish_ci' | 9 | | 0 | 2012-09-28T11:26:50 | Query | SET @@session.autocommit = OFF | 9 | | 0 | 2012-09-28T11:26:50 | Query | SHOW VARIABLES LIKE 'READ_ONLY' | 9 | | 0 | 2012-09-28T11:26:50 | Query | SET NAMES 'latin1' COLLATE 'latin1_swedish_ci' | 10 | | 0 | 2012-09-28T11:26:50 | Query | SET @@session.autocommit = OFF | 10 | | 0 | 2012-09-28T11:26:50 | Query | SHOW VARIABLES LIKE 'READ_ONLY' | 10 | | 0 | 2012-09-28T11:26:50 | Query | SET @@GLOBAL.audit_log_flush = ON | 10 | | 0 | 2012-09-28T11:26:50 | Query | SHOW VARIABLES LIKE 'audit_log_policy' | 10 | | 0 | 2012-09-28T11:26:50 | Query | SHOW VARIABLES LIKE 'audit_log_rotate_on_size' | 10 | | 0 | 2012-10-10T15:56:10 | Query | show databases | 11 | | 1046 | 2012-10-10T15:57:26 | Query | show tables test | 11 | | 1046 | 2012-10-10T15:57:36 | Query | show tables test | 11 | | 0 | 2012-10-10T15:57:51 | Query | show tables in test | 11 | +---------+----------------------+--------+-------------------------------------------------+----------------+
To display the audit log entries of specific event types, use the following command:
shell> mysqlauditgrep --event-type="Ping,Connect" /SERVER/data/audit.log
+---------+----------+----------------------+----------------+------------+---------+------------+------------+ | STATUS | NAME | TIMESTAMP | CONNECTION_ID | HOST | USER | PRIV_USER | IP | +---------+----------+----------------------+----------------+------------+---------+------------+------------+ | 0 | Connect | 2012-09-27T13:33:39 | 7 | localhost | root | root | 127.0.0.1 | | 0 | Ping | 2012-09-27T13:33:39 | 7 | None | None | None | None |
PERMISSIONS REQUIRED
82
| 0 | Ping | 2012-09-27T13:33:39 | 7 | None | None | None | None | | 0 | Ping | 2012-09-27T13:33:39 | 7 | None | None | None | None | | 0 | Ping | 2012-09-27T13:33:39 | 7 | None | None | None | None | | 0 | Connect | 2012-09-27T13:33:39 | 8 | localhost | root | root | 127.0.0.1 | | 0 | Ping | 2012-09-27T13:33:39 | 8 | None | None | None | None | | 0 | Ping | 2012-09-27T13:33:39 | 8 | None | None | None | None | | 0 | Ping | 2012-09-27T13:33:47 | 7 | None | None | None | None | | 0 | Connect | 2012-09-28T11:26:50 | 9 | localhost | root | tester | 127.0.0.1 | | 0 | Ping | 2012-09-28T11:26:50 | 9 | None | None | None | None | | 0 | Ping | 2012-09-28T11:26:50 | 9 | None | None | None | None | | 0 | Connect | 2012-09-28T11:26:50 | 10 | localhost | root | root | 127.0.0.1 | | 0 | Ping | 2012-09-28T11:26:50 | 10 | None | None | None | None | | 0 | Ping | 2012-09-28T11:26:50 | 10 | None | None | None | None | | 0 | Ping | 2012-09-28T11:26:50 | 10 | None | None | None | None | | 0 | Ping | 2012-09-28T11:26:50 | 10 | None | None | None | None | | 0 | Ping | 2012-09-28T11:26:50 | 10 | None | None | None | None | | 0 | Connect | 2012-10-10T15:55:55 | 11 | localhost | tester | root | 127.0.0.1 | | 0 | Connect | 2012-10-10T17:35:42 | 12 | localhost | tester | root | 127.0.0.1 | +---------+----------+----------------------+----------------+------------+---------+------------+------------+
To display the audit log entries with a specific status, use the following command:
shell> mysqlauditgrep --status=1100-1199,1046 /SERVER/data/audit.log
+---------+----------------------+--------+---------------------------------------------------------------------+----------------+ | STATUS | TIMESTAMP | NAME | SQLTEXT | CONNECTION_ID | +---------+----------------------+--------+---------------------------------------------------------------------+----------------+ | 1046 | 2012-10-10T15:57:26 | Query | show tables test | 11 | | 1046 | 2012-10-10T15:57:36 | Query | show tables test | 11 | | 1146 | 2012-10-10T17:44:55 | Query | select * from test.employees where salary > 500 and salary < 1000 | 12 | | 1046 | 2012-10-10T17:47:17 | Query | select * from test_encoding where value = '<>"&' | 12 | +---------+----------------------+--------+---------------------------------------------------------------------+----------------+
Note
You can view all successful commands with --status=0, and all unsuccessfulcommands with --status=1-9999.
To display the audit log entries matching several search criteria, use the following command:
shell> mysqlauditgrep --users=root --start-date=0 --end-date=2012-10-10 --event-type=Query \ --query-type=SET --status=0 --pattern="%audit_log%" /SERVER/data/audit.log
+---------+------------+--------+----------------------+----------------+-------+------------+------------------------------------+ | STATUS | SERVER_ID | NAME | TIMESTAMP | CONNECTION_ID | USER | PRIV_USER | SQLTEXT | +---------+------------+--------+----------------------+----------------+-------+------------+------------------------------------+ | 0 | 1 | Query | 2012-09-28T11:26:50 | 10 | root | root | SET @@GLOBAL.audit_log_flush = ON | +---------+------------+--------+----------------------+----------------+-------+------------+------------------------------------+
PERMISSIONS REQUIRED
The user must have permissions to read the audit log file(s) on disk.
5.3 mysqlbinlogmove — Binary log relocate utilityThis utility allows binary logs to be relocated to a different location in a simple and easy way. In particular,it moves existing binary logs to a specified location and updates the necessary server files (i.e., binary logindex files) with the new location.
From a practical point of view, the use of this utility is recommended before you change the binary log basedirectory to move all binary log files to the target location, avoiding errors on the server when started with
OPTIONS
83
the new --log-bin location. It is also useful to archive older binary log files to a different location, in order tosave disk space in the current partition.
Note
In order to relocate all binary log files, the MySQL server must be stopped. Thisrequirement is not needed if binary log files that are not in use are moved.
The user must provide the destination directory to move the binary log files as an argument and the serverconnection parameters with the --server option or the source location of the binary log files using theoption --binlog-dir. When the --server option is used, the utility determines the binary logs basefilename and index file location from the server (depending on its version) and all binary log files are movedexcept the ones currently in use (with the higher sequence number). In order to move all binary logsincluding those in use, the --binlog-dir option must be used, which requires the MySQL server to bestopped.
By default, the utility only moves binary log files. If the server is performing the role of a slave or if you wantto move both binary and relay log files, you must use the --log-type option with the desired value.
When the server --server is used, binary logs are flushed at the end of the move operation to refresh thecache. Users can skip this step using the --skip-flush-binlogs option.
The utility always attempts to determine the necessary information (base filename, binary logs andindex location) based on the available server's data or the default values. Nevertheless, custom valuesmight be used and some variables might not be available for older server versions or simply the serverconnection might not provided. If custom filenames are used, the user can specify them using the options--bin-log-index, --bin-log-basename, --relay-log-index, and --relay-log-basename,respectively for binary log and relay log files.
By default, all of the binary log files found that are not in use are moved (except when the --serveroption is used). The --sequence option can be used to restrict the files to move based on their sequencenumber. It is also possible to filter the files to move based on their modification date using the --modified-before option.
The utility displays the list of binary files that are moved. Users can also use the --verbose option to seeadditional information when the utility executes (e.g., used values for server variables).
Note
This utility was added in MySQL Utilities 1.6.0.
OPTIONS
mysqlbinlogmove accepts the following command-line options:
• --binlog-dir=binlog_dir
Source directory (full path) for the binary log files to move.
• --bin-log-basename=binlog_basename
Basename for the binary log files. If not available, it is assumed to be any name ended with '-bin'.
• --bin-log-index=binlog_index
Location (full path) of the binary log index file. If not specified, it is assumed to be located in the binarylog directory.
OPTIONS
84
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --log-type=log_type
Type of the binary log files to move, i.e. binary log or relay log files. Supported values: 'bin' for binary logfiles, 'relay' for relay log files, 'all' for both binary log and relay log files.
Default = bin.
• --modified-before=modified_before
Specify the datetime or number of days to move binary log files with a modified date prior to the specifiedvalue. Accepts a datetime in the format yyyy-mm-ddThh:mm:ss or yyyy-mm-dd, or an non-negativeinteger indicating the number of elapsed days.
• --relay-log-basename=relay_log_basename
Basename for the relay log files. If not available, it is assumed to be any name ended with '-relay-bin'.
• --relay-log-index=relay_log_index
Location (full path) of the relay log index file. If not specified, it is assumed to be located in the binary logdirectory.
• --sequence=sequence_number_list
Comma-separated list of non-negative sequence integers or intervals to move binary files with amatching sequence number. Specified sequence number intervals are closed (i.e., include bothendpoints) and defined simply using a dash between its endpoints. For Example: 3,5-12,16,21.
• --server=server_connection
Connection information for the server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --skip-flush-binlogs
Skip the binary log flush operation to refresh server's internal information after moving the binary logfiles.
NOTES
85
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
NOTES
By default, binary logs are flushed after moving the files when the --server option is used. In particular,FLUSH BINARY LOGS is executed after moving all binary log files and FLUSH RELAY LOGS after movingall relay log files. This flush operation is required to refresh the binary log data on the server, otherwiseerrors might occur or inconsistent information might be displayed regarding the moved files (withoutrestarting the server). For example, when executing the following statements: SHOW BINLOG EVENTSand SHOW BINARY LOGS. Nevertheless, the flush operation also closes and reopens the binary log files.See FLUSH Syntax, for more information about the FLUSH statement. Recall that the --skip-flush-binlogs option can be used to skip the flush operation.
The path to the MySQL client tools should be included in the PATH environment variable in order to usethe authentication mechanism with login-paths. This permits the utility to use the my_print_defaults tools,which is required to read the login-path values from the login configuration file (.mylogin.cnf).
LIMITATIONS
This utility does not support remote access to binary log files and must be executed on the local server.
EXAMPLES
Move available binary log files from a running server:
shell> mysqlbinlogmove --server=user:pass@localhost:3310 \ /archive/binlog_dir## Moving bin-log files...# - server-bin.000001# - server-bin.000002# - server-bin.000003# - server-bin.000004# - server-bin.000005
EXAMPLES
86
## Flushing binary logs...##...done.#
Move all binary log files from a stopped server specifying the source binary log directory:
shell> mysqlbinlogmove --binlog-dir=/server/data \ /new/binlog_dir## Moving bin-log files...# - server-bin.000001# - server-bin.000002# - server-bin.000003# - server-bin.000004# - server-bin.000005# - server-bin.000006##...done.#
Move available relay log files from a running slave:
shell> mysqlbinlogmove --server=user:pass@localhost:3311 \ --log-type=relay /archive/slave/binlog_dir## Moving relay-log files...# - slave-relay-bin.000001# - slave-relay-bin.000002# - slave-relay-bin.000003# - slave-relay-bin.000004# - slave-relay-bin.000005# - slave-relay-bin.000006# - slave-relay-bin.000007# - slave-relay-bin.000008# - slave-relay-bin.000009# - slave-relay-bin.000010# - slave-relay-bin.000011# - slave-relay-bin.000012# - slave-relay-bin.000013# - slave-relay-bin.000014# - slave-relay-bin.000015# - slave-relay-bin.000016## Flushing relay logs...##...done.#
Move available binary log and relay log files from a running slave skipping the flush step:
shell> mysqlbinlogmove --server=user:pass@localhost:3311 \ --log-type=all --skip-flush-binlogs \ /archive/slave/binlog_dir## Moving bin-log files...# - slave-bin.000001# - slave-bin.000002# - slave-bin.000003# - slave-bin.000004# - slave-bin.000005##
EXAMPLES
87
# Moving relay-log files...# - slave-relay-bin.000001# - slave-relay-bin.000002# - slave-relay-bin.000003# - slave-relay-bin.000004# - slave-relay-bin.000005# - slave-relay-bin.000006# - slave-relay-bin.000007# - slave-relay-bin.000008# - slave-relay-bin.000009# - slave-relay-bin.000010# - slave-relay-bin.000011# - slave-relay-bin.000012# - slave-relay-bin.000013# - slave-relay-bin.000014# - slave-relay-bin.000015# - slave-relay-bin.000016##...done.#
Move available binary log files from a running slave matching the specified sequence numbers:
shell> mysqlbinlogmove --server=user:pass@localhost:3311 \ --log-type=all --sequence=2,4-7,11,13 \ /archive/slave/binlog_dir## Applying sequence filter to bin-log files...## Moving bin-log files...# - slave-bin.000002# - slave-bin.000004# - slave-bin.000005# - slave-bin.000006## Flushing binary logs...### Applying sequence filter to relay-log files...## Moving relay-log files...# - slave-relay-bin.000002# - slave-relay-bin.000004# - slave-relay-bin.000005# - slave-relay-bin.000006# - slave-relay-bin.000007# - slave-relay-bin.000011# - slave-relay-bin.000013## Flushing relay logs...##...done.#
Move available binary log files modified two days ago from a running slave:
shell> mysqlbinlogmove --server=user:pass@localhost:3311 \ --log-type=all --modified-before=2 \ /archive/slave/binlog_dir## Applying modified date filter to bin-log files...## Moving bin-log files...# - slave-bin.000001# - slave-bin.000002
PERMISSIONS REQUIRED
88
# - slave-bin.000003## Flushing binary logs...### Applying modified date filter to relay-log files...## Moving relay-log files...# - slave-relay-bin.000001# - slave-relay-bin.000002# - slave-relay-bin.000003# - slave-relay-bin.000004# - slave-relay-bin.000005# - slave-relay-bin.000006# - slave-relay-bin.000007# - slave-relay-bin.000008# - slave-relay-bin.000009# - slave-relay-bin.000010## Flushing relay logs...##...done.
Move available binary log files modified prior to the specified date from a running slave:
shell> mysqlbinlogmove --server=user:pass@localhost:3311 \ --log-type=all --modified-before=2014-08-31 \ /archive/slave/binlog_dir## Applying modified date filter to bin-log files...## Moving bin-log files...# - slave-bin.000001# - slave-bin.000002# - slave-bin.000003## Flushing binary logs...### Applying modified date filter to relay-log files...## Moving relay-log files...# - slave-relay-bin.000001# - slave-relay-bin.000002# - slave-relay-bin.000003# - slave-relay-bin.000004# - slave-relay-bin.000005# - slave-relay-bin.000006# - slave-relay-bin.000007# - slave-relay-bin.000008# - slave-relay-bin.000009# - slave-relay-bin.000010## Flushing relay logs...##...done.
PERMISSIONS REQUIRED
By default, the user account used to connect to the server must have permissions to flush the binary logs,more precisely the RELOAD privilege is required, except if the flush step is skipped.
Additionally, the user account used to execute the utility must have read and write access to the location ofthe binary log and index files as well as the destination directory to move the files.
mysqlbinlogpurge — Binary log purge utility
89
5.4 mysqlbinlogpurge — Binary log purge utilityThis utility enables you to safely purge (delete) binary logs by ensuring that any files which are in use orrequired by any of the slaves in a replication topology are not deleted. This is achieved by checking whichbinary logs have been read on each slave. This determines the minimal set of binary log files that can bepurged.
Note
In order to determine which binary logs can be purged, mysqlbinlogpurgeconnects to the master. If the specified server is not the active master,mysqlbinlogpurge cannot determine which binary logs are still needed by theslaves.
You must provide the master's connection parameters with the --master option and each slave'sconnection parameters with the --slaves option. Alternatively, use the --discover-slaves-loginoption configured with the user name and password to connect to the slaves. In case the server is not amaster, you must provide the connection parameters with the --server option.
The discover slaves option requires all slaves use the --report-host and --report-portserver startup variables with the correct hostname and port. If these are missing or report the incorrectinformation, the slave may not be detected and thus not included in the operation of the utility. Thediscover slaves option ignores any slaves to which it cannot connect.
mysqlbinlogpurge attempts to determine the binary logs to purge by logging in to each server. If a slaveis not actively participating in a replication topology, mysqlbinlogpurge does not purge any logs.
By default, mysqlbinlogpurge purges all the binary log files that are not in use. Use the --binlogoption to override this behavior and configure the first binary log file to not purge.
mysqlbinlogpurge displays the list of binary log files that were purged. Use the --verbose option tosee a list of the remaining available binary log files on the server and to display additional information whenmysqlbinlogpurge executes, such as status of the I/O and SQL threads of each slave.
OPTIONS
mysqlbinlogpurge provides the following command-line options:
• --version
Show the program's version number.
• --help
Display the help message.
• --server=server_connection
Connection information for the server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
OPTIONS
90
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --ssl
Specifies if the server connection requires SSL. If an encrypted connection cannot be established, theconnection attempt fails. By default set to 0, indicating that SSL is not required.
• --ssl-ca
The path to a file that contains a list of trusted SSL certificate authorities.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --binlog=binlog
Binary log filename to not to purge. All the binary log files prior to the specified file are removed.
• --dry-run
Run mysqlbinlogpurge without purging any binary log files, instead displaying a list of the unusedbinary log files which would be purged.
• --discover-slaves-login=slave-login
Supply a user name and password, in the form user[:passwd] or login-path, used for discoveringslaves and relay slaves in the replication topology. For example, --discover=joe:secret uses 'joe' as theuser name and 'secret' as the password for attempting to log in to each discovered slave.
• --slaves=slave connections
Connection information for slave servers. List multiple slaves in a comma-separated list. The list isevaluated literally, where each server is considered a slave of the master listed. Thus, all serversspecified in this option must be slaves of the current master.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
NOTES
91
• --master=connection
Connection information for the master server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v is verbose, -vv is more verbose, -vvv is debug level.
NOTES
If the server specified using the --server option is a master server and there are slaves connected,mysqlbinlogpurge displays an error and does not purge the binary logs that match the criteria specified.
LIMITATIONS
mysqlbinlogpurge cannot verify slaves that are finds a slave which is not actively replicating from themaster.
EXAMPLES
Purge all binary log files not in use from a master, specifying the slaves to check:
shell> mysqlbinlogpurge --master=root:root@localhost:3310 \ --slaves=root:root@localhost:3311,root:root@localhost:3312,root:root@localhost:3313 \ -vvexec_util command=python -u ../scripts/mysqlbinlogpurge.py --master=root:root@localhost:3310 --slaves=root:root@localhost:3311,root:root@localhost:3312,root:root@localhost:3313 -vv# Checking user permission to purge binary logs...## Master active binlog file: mysql-bin.000021# Checking slave: localhost@3311# I/O thread is currently reading: mysql-bin.000021# File position of the I/O thread: 120# Master binlog file with last event executed by the SQL thread: mysql-bin.000021# I/O thread running: Yes# SQL thread running: Yes# Checking slave: localhost@3312# I/O thread is currently reading: mysql-bin.000021# File position of the I/O thread: 120# Master binlog file with last event executed by the SQL thread: mysql-bin.000021# I/O thread running: Yes# SQL thread running: Yes# Checking slave: localhost@3313# I/O thread is currently reading: mysql-bin.000021
PERMISSIONS REQUIRED
92
# File position of the I/O thread: 120# Master binlog file with last event executed by the SQL thread: mysql-bin.000021# I/O thread running: Yes# SQL thread running: Yes# Range of binlog files available: from mysql-bin.000016 to mysql-bin.000021# Latest binlog file replicated by all slaves: mysql-bin.000020# Latest not active binlog file: mysql-bin.000020# Executing query PURGE BINARY LOGS TO 'mysql-bin.000021'# Binlog file available: mysql-bin.000021# Range of binlog files purged: from mysql-bin.000016 to mysql-bin.000020
Purge all binary log files not in use prior to a specific binary log file:
shell> mysqlbinlogpurge --master=root:root@localhost:3310 \ --slaves=root:root@localhost:3311,root:root@localhost:3312,root:root@localhost:3313 \ --binlog=mysql-bin.000027 -v# Checking user permission to purge binary logs...## Master active binlog file: mysql-bin.000031# Checking slave: localhost@3311# I/O thread is currently reading: mysql-bin.000031# Checking slave: localhost@3312# I/O thread is currently reading: mysql-bin.000031# Checking slave: localhost@3313# I/O thread is currently reading: mysql-bin.000031# Range of binlog files available: from mysql-bin.000023 to mysql-bin.000031# Latest binlog file replicated by all slaves: mysql-bin.000030# Purging binary logs prior to 'mysql-bin.000027'# Range of binlog files available: from mysql-bin.000027 to mysql-bin.000031# Range of binlog files purged: from mysql-bin.000023 to mysql-bin.000026
Display a query statement you could use to manually purge all binary log files not in use from a server,without actually purging them by using the --dry-run option:
shell> mysqlbinlogpurge --server=root:root@localhost:3310 --dry-run# To manually purge purge the binary logs Execute the following query:PURGE BINARY LOGS TO 'mysql-bin.000004'
PERMISSIONS REQUIRED
By default, the user name you specified to connect to the server must have SUPER and REPLICATIONSLAVE permissions to be able to purge the binary logs.
5.5 mysqlbinlogrotate — Binary log rotate utilityThis utility rotates the binary log by closing the active binary log file and opening a new binary log file.
The user must provide the server connection parameters with the --server option.
The user can also use the --min-size option to conditionally rotate the active binary log file only if the filesize exceeds the specified value in bytes.
OPTIONS
mysqlbinlogrotate accepts the following command-line options:
• --version
Shows the program's version number.
• --help
NOTES
93
Displays the help message.
• --server=server_connection
Connection information for the server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. By default 0 (SSL not required).
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --min-size=min-size
Rotate the active binary log file only if the file size exceeds the specified value in bytes.
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
NOTES
By default, the utility rotates only the active binary log file, but for MySQL Server versions prior to 5.5.3,other log files (i.e, error log, relay log, slow log) are also rotated.
The path to the MySQL client tools should be included in the PATH environment variable in order to usethe authentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
EXAMPLES
Rotate the active binary log file and display the new filename.
PERMISSIONS REQUIRED
94
shell> mysqlbinlogrotate --server=root:root@localhost:3310 -v# Checking user permission to rotate binary logs...## Active binlog file: 'mysql-bin.000002' (size: 32054 bytes)# The binlog file has been rotated.# New active binlog file: 'mysql-bin.000003'
Rotate the active binary log file only if his size exceeds 1GB (1073741824 bytes) and display newfilename.
shell> mysqlbinlogrotate --server=root:root@localhost:3310 \ --min-size=1073741824 -v# Checking user permission to rotate binary logs...## Active binlog file: 'mysql-bin.000002' (size: 1610612736 bytes)# The binlog file has been rotated.# New active binlog file: 'mysql-bin.000003'
PERMISSIONS REQUIRED
By default, the user used to connect to the server must have permissions to rotate the binary logs, moreprecisely the SUPER and REPLICATION SLAVE privileges are required.
5.6 mysqldbcompare — Compare Two Databases and IdentifyDifferences
This utility compares the objects and data from two databases to find differences. It identifies objectshaving different definitions in the two databases and presents them in a diff-style format of choice.Differences in the data are shown using a similar diff-style format. Changed or missing rows are shown in astandard format of GRID, CSV, TAB, or VERTICAL.
Use the notation db1:db2 to name two databases to compare, or, alternatively just db1 to compare twodatabases with the same name. The latter case is a convenience notation for comparing same-nameddatabases on different servers.
The comparison may be run against two databases of different names on a single server by specifying onlythe --server1 option. The user can also connect to another server by specifying the --server2 option.In this case, db1 is taken from server1 and db2 from server2.
All databases between two servers can also be compared using the --all option. In this case, only thedatabases in common (with the same name) between the servers are successively compared. Therefore,no databases need to be specified but the --server1 and --server2 options are required. Users canskip the comparison of some of the databases using the --exclude option.
Note
The data must not be changed during the comparison. Unexpected errors mayoccur if data is changed during the comparison.
The objects considered in the database include tables, views, triggers, procedures, functions, and events.A count for each object type can be shown with the -vv option.
The check is performed using a series of steps called tests. By default, the utility stops on the first failedtest, but you can specify the --run-all-tests option to cause the utility to run all tests regardless oftheir end state.
mysqldbcompare — Compare Two Databases and Identify Differences
95
Note
Using --run-all-tests may produce expected cascade failures. For example, ifthe row counts differ among two tables being compared, the data consistency alsofails.
The tests include the following:
1. Check database definitions
A database existence precondition check ensures that both databases exist. If they do not, no furtherprocessing is possible and the --run-all-tests option is ignored.
2. Check existence of objects in both databases
The test for objects in both databases identifies those objects missing from one or another database.The remaining tests apply only to those objects that appear in both databases. To skip this test, use the--skip-object-compare option. That can be useful when there are known missing objects amongthe databases.
3. Compare object definitions
The definitions (the CREATE statements) are compared and differences are presented. To skip thistest, use the --skip-diff option. That can be useful when there are object name differences onlythat you want to ignore.
4. Check table row counts
This check ensures that both tables have the same number of rows. This does not ensure that the tabledata is consistent. It is merely a cursory check to indicate possible missing rows in one table or theother. The data consistency check identifies the missing rows. To skip this test, use the --skip-row-count option.
5. Check table data consistency
This check identifies both changed rows as well as missing rows from one or another of the tables inthe databases. Changed rows are displayed as a diff-style report with the format chosen (GRID bydefault) and missing rows are also displayed using the format chosen. This check is divided in twosteps: first the full table checksum is compared between the tables, then if this step fails (or is skipped)the algorithm to find rows differences is executed. To skip the preliminary checksum table step in thistest, use the --skip-checksum-table option. To skip this full test, use the --skip-data-checkoption.
You may want to use the --skip-xxx options to run only one of the tests. This might be helpful whenworking to bring two databases into synchronization, to avoid running all of the tests repeatedly during theprocess.
Each test completes with one of the following states:
• pass
The test succeeded.
• FAIL
The test failed. Errors are displayed following the test state line.
• SKIP
mysqldbcompare — Compare Two Databases and Identify Differences
96
The test was skipped due to a missing prerequisite or a skip option.
• WARN
The test encountered an unusual but not fatal error.
• -
The test is not applicable to this object.
To specify how to display diff-style output, use one of the following values with the --difftype option:
• unified (default)
Display unified format output.
• context
Display context format output.
• differ
Display differ-style format output.
• sql
Display SQL transformation statement output.
To specify how to display output for changed or missing rows, use one of the following values with the --format option:
• grid (default)
Display output in grid or table format like that of the mysql client command-line tool.
• csv
Display output in comma-separated values format.
• tab
Display output in tab-separated format.
• vertical
Display output in single-column format like that of the \G command for the mysql client command-linetool.
The --changes-for option controls the direction of the difference (by specifying the object to betransformed) in either the difference report (default) or the transformation report (designated with the --difftype=sql option). Consider the following command:
shell> mysqldbcompare --server1=root@host1 --server2=root@host2 --difftype=sql db1:dbx
The leftmost database (db1) exists on the server designated by the --server1 option (host1). Therightmost database (dbx) exists on the server designated by the --server2 option (host2).
• --changes-for=server1: Produce output that shows how to make the definitions of objects onserver1 like the definitions of the corresponding objects on server2.
OPTIONS
97
• --changes-for=server2: Produce output that shows how to make the definitions of objects onserver2 like the definitions of the corresponding objects on server1.
The default direction is server1.
You must provide connection parameters (user, host, password, and so forth) for an account that has theappropriate privileges to access all objects in the operation.
If the utility is to be run on a server that has binary logging enabled, and you do not want the comparisonsteps logged, use the --disable-binary-logging option.
OPTIONS
mysqldbcompare accepts the following command-line options:
• --all, -a
Compare all database in common (with the same name) between two servers.
The --all option ignores the following databases: INFORMATION_SCHEMA,PERFORMANCE_SCHEMA, mysql, and sys.
Note
The sys database is ignored as of Utilities 1.6.2.
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --changes-for=direction
Specify the server to show transformations to match the other server. For example, to see thetransformation for transforming object definitions on server1 to match the corresponding definitions onserver2, use --changes-for=server1. Permitted values are server1 and server2. The default isserver1.
• --character-set=charset
Sets the client character set. The default is retrieved from the server variablecharacter_set_client.
• --difftype=difftype, -ddifftype
Specify the difference display format. Permitted format values are unified, context, differ, and sql. Thedefault is unified.
• --disable-binary-logging
If binary logging is enabled, disable it during the operation to prevent comparison operations from beingwritten to the binary log. Note: Disabling binary logging requires the SUPER privilege.
• --exclude=exclude, -xexclude
OPTIONS
98
Exclude one or more databases from the operation using either a specific name such as db1 or a searchpattern. Use this option multiple times to specify multiple exclusions. By default, patterns use databasepatterns such as LIKE. With the --regexp option, patterns use regular expressions for matchingnames.
Note
The utility attempts to determine if the pattern supplied has any specialcharacters (such as an asterisks), which may indicate that the pattern could be aREGEXP pattern. If there are special, non-SQL LIKE pattern characters and theuser has not specified the --regexp option, a warning is presented to suggestthe user check the pattern for possible use with the --regexp option.
• --format=format, -fformat
Specify the display format for changed or missing rows. Permitted format values are grid, csv, tab, andvertical. The default is grid.
• --compact
Compacts the output by reducing the number of control lines that are displayed in the diff results. Thisoption should be used together with one of the following difference types: unified or context. It is mosteffective when used with the unified difference type and the grid format.
• --quiet, -q
Do not print anything. Return only an exit code of success or failure.
• --regexp, --basic-regexp, -G
Perform pattern matches using the REGEXP operator. The default is to use LIKE for matching.
• --run-all-tests, -t
Do not halt at the first difference found. Process all objects.
• --server1=source
Connection information for the first server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --server2=source
Connection information for the second server.
OPTIONS
99
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --show-reverse
Produce a transformation report containing the SQL statements to conform the object definitionsspecified in reverse. For example, if --changes-for is set to server1, also generate the transformation forserver2. Note: The reverse changes are annotated and marked as comments.
• --skip-checksum-table
Skip the CHECKSUM TABLE step in the data consistency check. Added in release-1.4.3.
• --skip-data-check
Skip the data consistency check.
• --skip-diff
Skip the object definition difference check.
• --skip-object-compare
Skip the object comparison check.
• --skip-row-count
Skip the row count check.
• --span-key-size=number of bytes to use for key
Change the size of the key used for compare table contents. A higher value can help to get moreaccurate results comparing large databases, but may slow the algorithm.
Default value is 8.
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
NOTES
100
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
• --use-indexes
List the index to use. Use this option to select the index to use if the table has no primary keyor it has more than one unique index without null columns. Use this option in the format: --use-indexes="table1.indexA[;table2.indexB;]"
• --width=number
Change the display width of the test report. The default is 75 characters.
NOTES
The login user must have the appropriate permissions to read all databases and tables listed.
For the --difftype option, the permitted values are not case-sensitive. In addition, values may bespecified as any unambiguous prefix of a valid value. For example, --difftype=d specifies the differtype. An error occurs if a prefix matches more than one valid value.
The path to the MySQL client tools should be included in the PATH environment variable in order to use theauthentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
If any database identifier specified as an argument contains special characters or is a reservedword, then it must be appropriately quoted with backticks (`). In turn, names quoted with backticksmust also be quoted with single or double quotes depending on the operating system, i.e. (") inWindows or (') in non-Windows systems, in order for the utilities to read backtick quoted identifiersas a single argument. For example, to compare a database with the name weird`db.name withother:weird`db.name, the database pair must be specified using the following syntax (in non-Windows):'`weird``db.name`:`other:weird``db.name`'.
When comparing two databases of different names, the utility suppresses differences in the CREATEDATABASE statements when only the names differ. If any of the decorators differ, the differences in thestatements is shown.
EXAMPLES
Use the following command to compare the emp1 and emp2 databases on the local server, and run alltests even if earlier tests fail:
shell> mysqldbcompare --server1=root@localhost emp1:emp2 --run-all-tests# server1 on localhost: ... connected.# Checking databases emp1 on server1 and emp2 on server2
EXAMPLES
101
## WARNING: Objects in server2:emp2 but not in server1:emp1:# TRIGGER: trg# PROCEDURE: p1# TABLE: t1# VIEW: v1## Defn Row Data# Type Object Name Diff Count Check# ---------------------------------------------------------------------------# FUNCTION f1 pass - -# TABLE departments pass pass -# - Compare table checksum FAIL# - Find row differences FAIL## Data differences found among rows:--- emp1.departments+++ emp2.departments@@ -1,4 +1,4 @@ ************************* 1. row ************************* dept_no: d002- dept_name: dunno+ dept_name: Finance 1 rows.
# Rows in emp1.departments not in emp2.departments************************* 1. row ************************* dept_no: d008 dept_name: Research1 rows.
# Rows in emp2.departments not in emp1.departments************************* 1. row ************************* dept_no: d100 dept_name: stupid1 rows.
# TABLE dept_manager pass pass -# - Compare table checksum pass
# Database consistency check failed.## ...done
Given: two databases with the same table layout. Data for each table contains:
mysql> select * from db1.t1;+---+---------------+| a | b |+---+---------------+| 1 | Test 789 || 2 | Test 456 || 3 | Test 123 || 4 | New row - db1 |+---+---------------+4 rows in set (0.00 sec)
mysql> select * from db2.t1;+---+---------------+| a | b |+---+---------------+| 1 | Test 123 || 2 | Test 456 || 3 | Test 789 || 5 | New row - db2 |+---+---------------+4 rows in set (0.00 sec)
EXAMPLES
102
To generate the SQL statements for data transformations to make db1.t1 the same as db2.t1, usethe --changes-for=server1 option. We must also include the -a option to ensure that the dataconsistency test is run. The following command illustrates the options used and an excerpt from the resultsgenerated:
shell> mysqldbcompare --server1=root:root@localhost \ --server2=root:root@localhost db1:db2 --changes-for=server1 -a \/ --difftype=sql
[...]
# Defn Row Data# Type Object Name Diff Count Check#-------------------------------------------------------------------------# TABLE t1 pass pass -# - Compare table checksum FAIL# - Find row differences FAIL## Transformation for --changes-for=server1:#
# Data differences found among rows:UPDATE db1.t1 SET b = 'Test 123' WHERE a = '1';UPDATE db1.t1 SET b = 'Test 789' WHERE a = '3';DELETE FROM db1.t1 WHERE a = '4';INSERT INTO db1.t1 (a, b) VALUES('5', 'New row - db2');
# Database consistency check failed.## ...done
Similarly, when the same command is run with --changes-for=server2 and --difftype=sql, thefollowing report is generated:
shell> mysqldbcompare --server1=root:root@localhost \ --server2=root:root@localhost db1:db2 --changes-for=server2 -a \ --difftype=sql
[...]
# Defn Row Data# Type Object Name Diff Count Check#-------------------------------------------------------------------------# TABLE t1 pass pass -# - Compare table checksum FAIL# - Find row differences FAIL## Transformation for --changes-for=server2:#
# Data differences found among rows:UPDATE db2.t1 SET b = 'Test 789' WHERE a = '1';UPDATE db2.t1 SET b = 'Test 123' WHERE a = '3';DELETE FROM db2.t1 WHERE a = '5';INSERT INTO db2.t1 (a, b) VALUES('4', 'New row - db1');
# Database consistency check failed.## ...done
With the --difftype=sql SQL generation option set, --show-reverse shows the objecttransformations in both directions. Here is an excerpt of the results:
LIMITATIONS
103
shell> mysqldbcompare --server1=root:root@localhost \ --server2=root:root@localhost db1:db2 --changes-for=server1 \ --show-reverse -a --difftype=sql
[...]
# Defn Row Data# Type Object Name Diff Count Check# -------------------------------------------------------------------------# TABLE t1 pass pass -# - Compare table checksum FAIL# - Find row differences FAIL## Transformation for --changes-for=server1:#
# Data differences found among rows:UPDATE db1.t1 SET b = 'Test 123' WHERE a = '1';UPDATE db1.t1 SET b = 'Test 789' WHERE a = '3';DELETE FROM db1.t1 WHERE a = '4';INSERT INTO db1.t1 (a, b) VALUES('5', 'New row - db2');
## Transformation for reverse changes (--changes-for=server2):## # Data differences found among rows:# UPDATE db2.t1 SET b = 'Test 789' WHERE a = '1';# UPDATE db2.t1 SET b = 'Test 123' WHERE a = '3';# DELETE FROM db2.t1 WHERE a = '5';# INSERT INTO db2.t1 (a, b) VALUES('4', 'New row - db1');
# Database consistency check failed.## ...done
LIMITATIONS
The utility reads the primary key of each row into a data structure, which is then used to generatechecksums for each row. The primary key and checksum are then sorted and compared to detect whichrows differ. Due to this design, the utility may exhibit slower performance for very large tables (many rows)especially for tables with wide primary keys. Use of this utility with tables that have blob fields as part of theprimary key is not recommended.
PERMISSIONS REQUIRED
The user must have the SELECT, CREATE TEMPORARY TABLES and SHOW VIEW privileges for thedatabases being compared on both connections. The user must also have SELECT privilege on the mysqldatabase. If the binary log is enabled and the --disable-binary-logging option is used, the usermust also have the SUPER privilege.
5.7 mysqldbcopy — Copy Database Objects Between ServersThis utility copies a database on a source server to a database on a destination server. If the source anddestination servers are different, the database names can be the same or different. If the source anddestination servers are the same, the database names must be different.
The utility accepts one or more database pairs on the command line. To name a database pair, usedb_name:new_db_name syntax to specify the source and destination names explicitly. If the source anddestination database names are the same, db_name can be used as shorthand for db_name:db_name.
mysqldbcopy — Copy Database Objects Between Servers
104
By default, the operation copies all objects (tables, views, triggers, events, procedures, functions, anddatabase-level grants) and data to the destination server. There are options to turn off copying any or all ofthe objects as well as not copying the data.
To exclude specific objects by name, use the --exclude option with a name in db.*obj* format, or youcan supply a search pattern. For example, --exclude=db1.trig1 excludes the single trigger and --exclude=trig_ excludes all objects from all databases having a name that begins with trig and has afollowing character.
By default, the utility creates each table on the destination server using the same storage engine asthe original table. To override this and specify the storage engine to use for all tables created on thedestination server, use the --new-storage-engine option. If the destination server supports the newengine, all tables use that engine.
To specify the storage engine to use for tables for which the destination server does not support theoriginal storage engine on the source server, use the --default-storage-engine option.
The --new-storage-engine option takes precedence over --default-storage-engine if both aregiven.
If the --new-storage-engine or --default-storage-engine option is given and the destinationserver does not support the specified storage engine, a warning is issued and the server's default storageengine setting is used instead.
By default, the operation uses a consistent snapshot to read the source databases. To change the lockingmode, use the --locking option with a locking type value. Use a value of no-locks to turn off lockingaltogether or lock-all to use only table locks. The default value is snapshot. Additionally, the utility usesWRITE locks to lock the destination tables during the copy.
You can include replication statements for copying data among a master and slave or between slaves. The--rpl option permits you to select from the following replication statements to include in the export.
• master
Create and execute a CHANGE MASTER statement to make the destination server a slave of the serverspecified in the --source option. This executes the appropriate STOP and START slave statements.The STOP SLAVE statement is executed at the start of the copy and the CHANGE MASTER followedby the START SLAVE statements are executed after the copy.
• slave
Create and execute a CHANGE MASTER statement to make the destination server a slave connectedto the same master as the server specified in the --source option. This executes the appropriate STOPand START slave statements. The STOP SLAVE statement is executed at the start of the copy and theCHANGE MASTER followed by the START SLAVE statements after the copy.
To include the replication user in the CHANGE MASTER statement, use the --rpl-user option tospecify the user and password. If this option is omitted, the utility attempts to identify the replication user. Inthe event that there are multiple candidates or the user requires a password, the utility aborts with an error.
If you attempt to copy databases on a server with GTIDs enabled (GTID_MODE = ON), a warning isgenerated if the copy does not include all databases. This is because the GTID statements generatedinclude the GTIDs for all databases and not only those databases in the export.
The utility also generates a warning if you copy databases on a GTID enabled server but use the --skip-gtid option.
To make the most use of GTIDs, you should copy all of the databases on the server with the --all option.
OPTIONS
105
OPTIONS
mysqldbcopy accepts the following command-line options:
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --character-set=charset
Sets the client character set. The default is retrieved from the server variablecharacter_set_client.
• --default-storage-engine=def_engine
The engine to use for tables if the destination server does not support the original storage engine on thesource server.
• --destination=destination
Connection information for the destination server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --exclude=exclude, -xexclude
Exclude one or more objects from the operation using either a specific name such as db1.t1 or a searchpattern. Use this option multiple times to specify multiple exclusions. By default, patterns use LIKEmatching. With the --regexp option, patterns use REGEXP matching.
This option does not apply to grants.
Note
The utility attempts to determine if the pattern supplied has any specialcharacters (such as an asterisks), which may indicate that the pattern could be aREGEXP pattern. If there are special, non-SQL LIKE pattern characters and theuser has not specified the --regexp option, a warning is presented to suggestthe user check the pattern for possible use with the --regexp option.
• --drop-first
OPTIONS
106
Drop each database to be copied if exists before copying anything into it. Without this option, an erroroccurs if you attempt to copy objects into an existing database.
Note
Before MySQL Utilities 1.4.2, this option was named --force.
• --locking=locking
Choose the lock type for the operation. Permitted lock values are no-locks (do not use any table locks),lock-all (use table locks but no transaction and no consistent read), and snapshot (consistent readusing a single transaction). The default is snapshot.
• --multiprocess
Specify the number of processes to concurrently copy the specified databases. Special values: 0(number of processes equal to the number of detected CPUs) and 1 (default - no concurrency).Multiprocessing works at the database level for Windows and at the table level for Non-Windows(POSIX) systems.
• --new-storage-engine=new_engine
The engine to use for all tables created on the destination server.
• --not-null-blobs
Allow conversion of blob fields marked as NOT NULL to NULL before copy then restore NOT NULL afterthe copy. May cause indexes to be rebuilt if the affected blob fields are used in indexes.
• --quiet, -q
Turn off all messages for quiet execution.
• --regexp, --basic-regexp, -G
Perform pattern matches using the REGEXP operator. The default is to use LIKE for matching.
• --rpl=dump_option, --replication=dump_option
Include replication information. Permitted values are master (make destination a slave of the sourceserver) and slave (make destination a slave of the same master as the source - only works if the sourceserver is a slave).
• --rpl-user=replication_user
The user and password for the replication user requirement in the form: user[:password] or login-path. E.g. rpl:passwd Default = None.
• l --skip-gtid
Skip creation and execution of GTID statements during the copy operation.
• --all
Copy all of the databases on the server.
• --skip=objects
NOTES
107
Specify objects to skip in the operation as a comma-separated list (no spaces). Permitted values areCREATE_DB, DATA, EVENTS, FUNCTIONS, GRANTS, PROCEDURES, TABLES, TRIGGERS, andVIEWS.
• --source=source
Connection information for the source server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
NOTES
You must provide connection parameters (user, host, password, and so forth) for an account that has theappropriate privileges to access all objects in the operation.
On the source to copy all objects from the database, the user must have these privileges: SELECT fortables, SHOW VIEW for views, EVENT for events and TRIGGER for triggers. Additionally, the SELECTprivilege is also required for the mysql database.
EXAMPLES
108
On the destination to copy all objects, the user must have these privileges: CREATE, ALTER, SELECT,INSERT, UPDATE, LOCK TABLES, DROP if --drop-first option is used, SUPER when binary loggingis enabled, CREATE VIEW for views, CREATE ROUTINE, EXECUTE for procedures and functions,EVENT for events, TRIGGER for triggers and GRANT OPTION to copy grants. The SUPER privilege mightalso be required for some objects (views, procedures, functions, events and triggers), depending on theirDEFINER value.
Actual privileges required may differ from installation to installation depending on the security privilegespresent and whether the database contains certain objects such as views or events and whether binarylogging is enabled.
The --new-storage-engine and --default-storage-engine options apply to all destination tablesin the operation.
Some option combinations may result in errors during the operation. For example, eliminating tables butnot views may result in an error a the view is copied.
The --rpl option is not valid for copying databases on the same server. If used in this manner, an error isgenerated.
When copying data and including the GTID commands, you may encounter an error similar to"GTID_PURGED can only be set when GTID_EXECUTED is empty". This occurs because the destinationserver is not in a clean replication state. To alleviate this problem, you can issue a "RESET MASTER"command on the destination prior to executing the copy.
Cloning databases that contain foreign key constraints does not change the constraint in the cloned table.For example, if table db1.t1 has a foreign key constraint on table db1.t2, when db1 is cloned to db2, tabledb2.t1 contains a foreign key constraint on db1.t2.
Copying tables that contain 0 in auto_increment columns is accomplished by enabling theNO_AUTO_VALUE_ON_ZERO SQL_MODE prior to the copy and disabling it after.
The path to the MySQL client tools should be included in the PATH environment variable in order to use theauthentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
If any database identifier specified as an argument contains special characters or is a reservedword, then it must be appropriately quoted with backticks (`). In turn, names quoted with backticksmust also be quoted with single or double quotes depending on the operating system, i.e. (") inWindows or (') in non-Windows systems, in order for the utilities to read backtick quoted identifiersas a single argument. For example, to copy a database with the name weird`db.name withother:weird`db.name, the database pair must be specified using the following syntax (in non-Windows):'`weird``db.name`:`other:weird``db.name`'.
Keep in mind that you can only take advantage of multiprocessing if your system has multiple CPUsavailable for concurrent execution. Also note that multiprocessing is applied at a different level accordingto the operating system where the mysqldbcopy utility is executed (due to python limitations). In particular,it is applied at the database level for Windows (i.e., different databases are concurrently copied) and atthe table level for Non-Windows (POSIX) systems (i.e., different tables within the same database areconcurrently copied).
EXAMPLES
The following example demonstrates how to use the utility to copy a database named util_test to anew database named util_test_copy on the same server:
EXAMPLES
109
shell> mysqldbcopy \ --source=root:pass@localhost:3310:/test123/mysql.sock \ --destination=root:pass@localhost:3310:/test123/mysql.sock \ util_test:util_test_copy# Source on localhost: ... connected.# Destination on localhost: ... connected.# Copying database util_test renamed as util_test_copy# Copying TABLE util_test.t1# Copying table data.# Copying TABLE util_test.t2# Copying table data.# Copying TABLE util_test.t3# Copying table data.# Copying TABLE util_test.t4# Copying table data.# Copying VIEW util_test.v1# Copying TRIGGER util_test.trg# Copying PROCEDURE util_test.p1# Copying FUNCTION util_test.f1# Copying EVENT util_test.e1# Copying GRANTS from util_test#...done.
If the database to be copied does not contain only InnoDB tables and you want to ensure data integrityof the copied data by locking the tables during the read step, add a --locking=lock-all option to thecommand:
shell> mysqldbcopy \ --source=root:pass@localhost:3310:/test123/mysql.sock \ --destination=root:pass@localhost:3310:/test123/mysql.sock \ util_test:util_test_copy --locking=lock-all# Source on localhost: ... connected.# Destination on localhost: ... connected.# Copying database util_test renamed as util_test_copy# Copying TABLE util_test.t1# Copying table data.# Copying TABLE util_test.t2# Copying table data.# Copying TABLE util_test.t3# Copying table data.# Copying TABLE util_test.t4# Copying table data.# Copying VIEW util_test.v1# Copying TRIGGER util_test.trg# Copying PROCEDURE util_test.p1# Copying FUNCTION util_test.f1# Copying EVENT util_test.e1# Copying GRANTS from util_test#...done.
To copy one or more databases from a master to a slave, you can use the following command to copy thedatabases. Use the master as the source and the slave as the destination:
shell> mysqldbcopy --source=root@localhost:3310 \ --destination=root@localhost:3311 test123 --rpl=master \ --rpl-user=rpl# Source on localhost: ... connected.# Destination on localhost: ... connected.# Source on localhost: ... connected.# Stopping slave# Copying database test123# Copying TABLE test123.t1# Copying data for TABLE test123.t1
LIMITATIONS
110
# Connecting to the current server as master# Starting slave#...done.
To copy a database from one slave to another attached to the same master, you can use the followingcommand using the slave with the database to be copied as the source and the slave where the databaseneeds to copied to as the destination:
shell> mysqldbcopy --source=root@localhost:3311 \ --destination=root@localhost:3312 test123 --rpl=slave \ --rpl-user=rpl
# Source on localhost: ... connected.# Destination on localhost: ... connected.# Source on localhost: ... connected.# Stopping slave# Copying database test123# Copying TABLE test123.t1# Copying data for TABLE test123.t1# Connecting to the current server's master# Starting slave#...done.
LIMITATIONS
When copying tables with blob fields defined as NOT NULL and the --not-null-blobs option is notspecified, the copy operation stops with an error suggesting how to manually remove the restriction.
However, you can use the --not-null-blobs option to automatically convert the fields. In this case, theutility prints a warning that the fields were temporarily altered on the destination to remove the NOT NULLoption. The NOT NULL restriction is restored after the copy.
This special processing is needed because the copy attempts to use a bulk insert technique to copy thedata in two passes; one to copy the data without blob field data, and another to update the rows with theblob data. Thus, having blob fields defined as NOT NULL fails on the first pass unless the restriction isremoved before the data is copied.
PERMISSIONS REQUIRED
The user must have SELECT, SHOW VIEW, EVENT and TRIGGER privileges for the database(s) onthe source server. On the destination server, the user must have the following privileges for the copieddatabase(s): CREATE, ALTER, SELECT, INSERT, UPDATE, LOCK TABLES, DROP if --drop-firstoption is used, and SUPER depending on the objects DEFINER value. When copying tables that includeforeign keys, the user must also have the REFERENCES privilege.
5.8 mysqldbexport — Export Object Definitions or Data from aDatabase
This utility exports metadata (object definitions) or data or both from one or more databases. By default,the export includes only definitions.
mysqldbexport differs from mysqldump in that it can produce output in a variety of formats to make yourdata extraction/transport much easier. It permits you to export your data in the format most suitable to anexternal tool, another MySQL server, or other use without the need to reformat the data.
To exclude specific objects by name, use the --exclude option with a name in db.*obj* format, or youcan supply a search pattern. For example, --exclude=db1.trig1 excludes the single trigger and --
mysqldbexport — Export Object Definitions or Data from a Database
111
exclude=trig_ excludes all objects from all databases having a name that begins with trig and has afollowing character.
To skip objects by type, use the --skip option with a list of the objects to skip. This enables you to extracta particular set of objects, say, for exporting only events (by excluding all other types). Similarly, to skipcreation of UPDATE statements for BLOB data, specify the --skip-blobs option.
To specify how to display output, use one of the following values with the --format option:
• sql (default)
Display output using SQL statements. For definitions, this consists of the appropriate CREATE andGRANT statements. For data, this is an INSERT statement (or bulk insert if the --bulk-insert optionis specified).
• grid
Display output in grid or table format like that of the mysql client command-line tool.
• csv
Display output in comma-separated values format.
• tab
Display output in tab-separated format.
• vertical
Display output in single-column format like that of the \G command for the mysql client command-linetool.
To specify how much data to display, use one of the following values with the --display option:
• brief
Display only the minimal columns for recreating the objects.
• full
Display the complete column list for recreating the objects.
• names
Display only the object names.
Note
The --display option is ignored when combined with the SQL-format output type.
To turn off the headers for csv or tab display format, specify the --no-headers option.
To turn off all feedback information, specify the --quiet option.
To write the data for individual tables to separate files, use the --file-per-table option. The nameof each file is composed of the database and table names followed by the file format. For example, thefollowing command produces files named db1.*table_name*.csv:
Exporting Data with GTIDs
112
mysqldbexport --server=root@server1:3306 --format=csv db1 --export=data
By default, the operation uses a consistent snapshot to read the source databases. To change the lockingmode, use the --locking option with a locking type value. Use a value of no-locks to turn off lockingaltogether or lock-all to use only table locks. The default value is snapshot. Additionally, the utility usesWRITE locks to lock the destination tables during the copy.
You can include replication statements for exporting data among a master and slave or between slaves.The --rpl option permits you to select from the following replication statements to include in the export.
• master
Include the CHANGE MASTER statement to make the destination server a slave of the server specifiedin the --server option. This places the appropriate STOP and START slave statements in the exportwhereby the STOP SLAVE statement is placed at the start of the export and the CHANGE MASTERfollowed by the START SLAVE statements are placed after the export stream.
• slave
Include the CHANGE MASTER statement to make the destination server a slave connected to the samemaster as the server specified in the --server option. It only works if the current server is a slave. Thisplaces the appropriate STOP and START slave statements in the export whereby the STOP SLAVEstatement is placed at the start of the export and the CHANGE MASTER followed by the START SLAVEstatements are placed after the export stream.
• both
Include both the 'master' and 'slave' information for CHANGE MASTER statements for either spawninga new slave with the current server's master or using the current server as the master. All statementsgenerated are labeled and commented to enable the user to choose which to include when imported.
To include the replication user in the CHANGE MASTER statement, use the --rpl-user option tospecify the user and password. If this option is omitted, the utility attempts to identify the replication user. Inthe event that there are multiple candidates or the user requires a password, these statements are placedinside comments for the CHANGE MASTER statement.
You can also use the --comment-rpl option to place the replication statements inside comments for laterexamination.
If you specify the --rpl-file option, the utility writes the replication statements to the file specifiedinstead of including them in the export stream.
Exporting Data with GTIDs
If you attempt to export databases on a server with GTIDs enabled (GTID_MODE = ON), a warning isgenerated if the export does not include all databases. This is because the GTID statements generatedinclude the GTIDs for all databases and not only those databases in the export.
The utility also generates a warning if you export databases on a GTID enabled server but use the --skip-gtid option.
To make the most use of GTIDs and export/import, you should export all of the databases on the serverwith the --all option. This action generates an export file with all of the databases and the GTIDsexecuted to that point.
Importing this file on another server ensures that server has all of the data as well as all of the GTIDsrecorded correctly in its logs.
OPTIONS
113
OPTIONS
mysqldbexport accepts the following command-line options:
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --bulk-insert, -b
Use bulk insert statements for data.
• --character-set=charset
Sets the client character set. The default is retrieved from the server variablecharacter_set_client.
• --comment-rpl
Place the replication statements in comment statements. Valid only with the --rpl option.
• --display=display, -ddisplay
Control the number of columns shown. Permitted display values are brief (minimal columns for objectcreation), full* (all columns), and **names (only object names; not valid for --format=sql). Thedefault is brief.
• --exclude=exclude, -xexclude
Exclude one or more objects from the operation using either a specific name such as db1.t1 or asearch pattern. Use this option multiple times to specify multiple exclusions. By default, patterns useLIKE matching. With the --regexp option, all patterns specified use REGEXP matching.
This option does not apply to grants.
Note
The utility attempts to determine if the pattern supplied has any specialcharacters (such as an asterisks), which may indicate that the pattern could be aREGEXP pattern. If there are special, non-SQL LIKE pattern characters and theuser has not specified the --regexp option, a warning is presented to suggestthe user check the pattern for possible use with the --regexp option.
• --export=export, -eexport
Specify the export format. Permitted format values include the following. The default is definitions.
Table 5.1 mysqldbexport Export Types
Export Type Definition
definitions (default) Only export the definitions (metadata) for the objects in the database list
data Only export the table data for the tables in the database list
both Export both the definitions (metadata) and data
OPTIONS
114
• --file-per-table
Write table data to separate files. This is valid only if the export output includes data (thatis, if --export=data or --export=both are given). This option produces files nameddb_name.*tbl_name*.*format*. For example, a csv export of two tables named t1 and t2 in databased1, results in files named db1.t1.csv and db1.t2.csv. If table definitions are included in the export,they are written to stdout as usual.
• --format=format, -fformat
Specify the output display format. Permitted format values are sql, grid, tab, csv, and vertical. Thedefault is sql.
• --locking=locking
Choose the lock type for the operation. Permitted lock values are no-locks (do not use any table locks),lock-all (use table locks but no transaction and no consistent read), and snapshot (consistent readusing a single transaction). The default is snapshot.
• --multiprocess
Specify the number of processes to concurrently export the specified databases. Special values:0 (number of processes equal to the number of detected CPUs) and 1 (default - no concurrency).Multiprocessing works at the database level for Windows and at the table level for Non-Windows(POSIX) systems.
• --no-headers, -h
Do not display column headers. This option applies only for csv and tab output.
• --output-file
Specify the path and filename to store the generated export output. By default the standard output isused (no file).
• --quiet, -q
Turn off all messages for quiet execution.
• --regexp, --basic-regexp, -G
Perform pattern matches using the REGEXP operator. The default is to use LIKE for matching.
• --rpl=rpl_mode, --replication=rpl_mode
Include replication information. Permitted values are master (make destination a slave of the sourceserver), slave (make destination a slave of the same master as the source - only works if the sourceserver is a slave), and both (include the master and slave options where applicable).
• --rpl-file=RPL_FILE, --replication-file=RPL_FILE
The path and filename where the generated replication information should be written. Valid only with the--rpl option.
• --rpl-user=replication_user
The user and password for the replication user requirement, in the format: user[:password] or login-path. For example, rpl:passwd. The default is None.
OPTIONS
115
• --server=server
Connection information for the server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --skip=skip-objects
Specify objects to skip in the operation as a comma-separated list (no spaces). Permitted values areCREATE_DB, DATA, EVENTS, FUNCTIONS, GRANTS, PROCEDURES, TABLES, TRIGGERS, andVIEWS.
• --skip-blobs
Do not export BLOB data.
• --skip-gtid
Skip creation of GTID_PURGED statements.
• --all
Generate an export file with all of the databases and the GTIDs executed to that point.
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
NOTES
116
Display version information and exit.
NOTES
You must provide connection parameters (user, host, password, and so forth) for an account that has theappropriate privileges to access (e.g., SELECT) all objects in the operation.
To export all objects from a source database, the user must have these privileges: SELECT and SHOWVIEW on the database as well as SELECT on the mysql database.
Actual privileges needed may differ from installation to installation depending on the security privilegespresent and whether the database contains certain objects such as views, events, and stored routines.
Some combinations of the options may result in errors when the export is imported later. For example,eliminating tables but not views may result in an error when a view is imported on another server.
For the --format, --export, and --display options, the permitted values are not case-sensitive. Inaddition, values may be specified as any unambiguous prefix of a valid value. For example, --format=gspecifies the grid format. An error occurs if a prefix matches more than one valid value.
When exporting table data that contain a 0 in the auto_increment column, the export prints a warning thatyou must enable the NO_AUTO_VALUE_ON_ZERO SQL_MODE in order to import the data. A sample SQLstatement is provided to illustrate how to set the mode.
The path to the MySQL client tools should be included in the PATH environment variable in order to use theauthentication mechanism with login-paths. This allows the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
If any database identifier specified as an argument contains special characters or is a reserved word,then it must be appropriately quoted with backticks (`). In turn, names quoted with backticks must also bequoted with single or double quotes depending on the operating system, i.e. (") in Windows or (') in non-Windows systems, in order for the utilities to read backtick quoted identifiers as a single argument. Forexample, to export a database with the name weird`db.name, it must be specified as argument using thefollowing syntax (in non-Windows): '`weird``db.name`'.
Keep in mind that you can only take advantage of multiprocessing if your system has multiple CPUsavailable for concurrent execution. Also note that multiprocessing is applied at a different level accordingto the operating system where the mysqldbexport utility is executed (due to python limitations). Inparticular, it is applied at the database level for Windows (i.e., different databases are concurrentlyexported) and at the table level for Non-Windows (POSIX) systems (i.e., different tables within the samedatabase are concurrently exported).
EXAMPLES
To export the definitions of the database dev from a MySQL server on the local host via port 3306,producing output consisting of CREATE statements, use this command:
shell> mysqldbexport --server=root:pass@localhost \ --skip=GRANTS --export=DEFINITIONS util_test# Source on localhost: ... connected.# Exporting metadata from util_testDROP DATABASE IF EXISTS `util_test`;CREATE DATABASE `util_test`;USE `util_test`;
EXAMPLES
117
# TABLE: `util_test`.`t1`CREATE TABLE `t1` ( `a` char(30) DEFAULT NULL) ENGINE=MEMORY DEFAULT CHARSET=latin1;# TABLE: util_test.t2CREATE TABLE `t2` ( `a` char(30) DEFAULT NULL) ENGINE=MyISAM DEFAULT CHARSET=latin1;# TABLE: util_test.t3CREATE TABLE `t3` ( `a` int(11) NOT NULL AUTO_INCREMENT, `b` char(30) DEFAULT NULL, PRIMARY KEY (`a`)) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=latin1;# TABLE: util_test.t4CREATE TABLE `t4` ( `c` int(11) NOT NULL, `d` int(11) NOT NULL, KEY `ref_t3` (`c`), CONSTRAINT `ref_t3` FOREIGN KEY (`c`) REFERENCES `t3` (`a`)) ENGINE=InnoDB DEFAULT CHARSET=latin1;# VIEW: `util_test`.`v1`[...]#...done.
Similarly, to export the data of the database util_test, producing bulk insert statements, use thiscommand:
shell> mysqldbexport --server=root:pass@localhost \ --export=DATA --bulk-insert util_test# Source on localhost: ... connected.USE `util_test`;# Exporting data from `util_test`# Data for table `util_test`.`t1`:INSERT INTO `util_test`.`t1` VALUES ('01 Test Basic database example'), ('02 Test Basic database example'), ('03 Test Basic database example'), ('04 Test Basic database example'), ('05 Test Basic database example'), ('06 Test Basic database example'), ('07 Test Basic database example');# Data for table `util_test`.`t2`:INSERT INTO `util_test`.`t2` VALUES ('11 Test Basic database example'), ('12 Test Basic database example'), ('13 Test Basic database example');# Data for table `util_test`.`t3`:INSERT INTO util_test.t3 VALUES (1, '14 test fkeys'), (2, '15 test fkeys'), (3, '16 test fkeys');# Data for table `util_test`.`t4`:INSERT INTO `util_test`.`t4` VALUES (3, 2);#...done.
If the database to be exported does not contain only InnoDB tables and you want to ensure data integrityof the exported data by locking the tables during the read step, add a --locking=lock-all option to thecommand:
shell> mysqldbexport --server=root:pass@localhost \ --export=DATA --bulk-insert util_test --locking=lock-all# Source on localhost: ... connected.USE `util_test`;# Exporting data from `util_test`# Data for table `util_test`.`t1`:INSERT INTO `util_test`.`t1` VALUES ('01 Test Basic database example'),
EXAMPLES
118
('02 Test Basic database example'), ('03 Test Basic database example'), ('04 Test Basic database example'), ('05 Test Basic database example'), ('06 Test Basic database example'), ('07 Test Basic database example');# Data for table `util_test`.`t2`:INSERT INTO `util_test`.`t2` VALUES ('11 Test Basic database example'), ('12 Test Basic database example'), ('13 Test Basic database example');# Data for table `util_test`.`t3`:INSERT INTO `util_test`.`t3` VALUES (1, '14 test fkeys'), (2, '15 test fkeys'), (3, '16 test fkeys');# Data for table `util_test`.`t4`:INSERT INTO `util_test`.`t4` VALUES (3, 2);#...done.
To export a database and include the replication commands to use the current server as the master (forexample, to start a new slave using the current server as the master), use the following command:
shell> mysqldbexport --server=root@localhost:3311 util_test \ --export=both --rpl-user=rpl:rpl --rpl=master -v# Source on localhost: ... connected.## Stopping slaveSTOP SLAVE;## Source on localhost: ... connected.# Exporting metadata from `util_test`DROP DATABASE IF EXISTS `util_test`;CREATE DATABASE `util_test`;USE `util_test`;# TABLE: `util_test`.`t1`CREATE TABLE `t1` ( `a` char(30) DEFAULT NULL) ENGINE=MEMORY DEFAULT CHARSET=latin1;#...done.# Source on localhost: ... connected.USE `util_test`;# Exporting data from `util_test`# Data for table `util_test`.`t1`:INSERT INTO `util_test`.`t1` VALUES ('01 Test Basic database example');INSERT INTO `util_test`.`t1` VALUES ('02 Test Basic database example');INSERT INTO `util_test`.`t1` VALUES ('03 Test Basic database example');INSERT INTO `util_test`.`t1` VALUES ('04 Test Basic database example');INSERT INTO `util_test`.`t1` VALUES ('05 Test Basic database example');INSERT INTO `util_test`.`t1` VALUES ('06 Test Basic database example');INSERT INTO `util_test`.`t1` VALUES ('07 Test Basic database example');#...done.## Connecting to the current server as masterCHANGE MASTER TO MASTER_HOST = 'localhost', MASTER_USER = 'rpl', MASTER_PASSWORD = 'rpl', MASTER_PORT = 3311, MASTER_LOG_FILE = 'clone-bin.000001' , MASTER_LOG_POS = 106;## Starting slaveSTART SLAVE;#
Similarly, to export a database and include the replication commands to use the current server's master(for example, to start a new slave using the same the master), use the following command:
PERMISSIONS REQUIRED
119
shell> mysqldbexport --server=root@localhost:3311 util_test \ --export=both --rpl-user=rpl:rpl --rpl=slave -v# Source on localhost: ... connected.## Stopping slaveSTOP SLAVE;## Source on localhost: ... connected.# Exporting metadata from util_testDROP DATABASE IF EXISTS `util_test`;CREATE DATABASE `util_test`;USE `util_test`;# TABLE: `util_test`.`t1`CREATE TABLE `t1` ( `a` char(30) DEFAULT NULL) ENGINE=MEMORY DEFAULT CHARSET=latin1;#...done.# Source on localhost: ... connected.USE `util_test`;# Exporting data from `util_test`# Data for table `util_test`.`t1`:INSERT INTO `util_test`.`t1` VALUES ('01 Test Basic database example');INSERT INTO `util_test`.`t1` VALUES ('02 Test Basic database example');INSERT INTO `util_test`.`t1` VALUES ('03 Test Basic database example');INSERT INTO `util_test`.`t1` VALUES ('04 Test Basic database example');INSERT INTO `util_test`.`t1` VALUES ('05 Test Basic database example');INSERT INTO `util_test`.`t1` VALUES ('06 Test Basic database example');INSERT INTO `util_test`.`t1` VALUES ('07 Test Basic database example');#...done.## Connecting to the current server's masterCHANGE MASTER TO MASTER_HOST = 'localhost', MASTER_USER = 'rpl', MASTER_PASSWORD = 'rpl', MASTER_PORT = 3310, MASTER_LOG_FILE = 'clone-bin.000001' , MASTER_LOG_POS = 1739;## Starting slaveSTART SLAVE;#
PERMISSIONS REQUIRED
The user account specified must have permission to read all databases listed including access to anyobjects exported. For example, if the export includes stored routines, the user specified must be able toaccess and view stored routines.
5.9 mysqldbimport — Import Object Definitions or Data into aDatabase
This utility imports metadata (object definitions), data, or both for one or more databases from one or morefiles.
If an object exists on the destination server with the same name as an imported object, it may be droppedfirst by using the --drop-first option.
To skip objects by type, use the --skip option with a list of the objects to skip. This enables you to extracta particular set of objects, say, for importing only events (by excluding all other types). Similarly, to skipcreation of UPDATE statements for BLOB data, specify the --skip-blobs option.
Changing Storage Engines
120
To specify the input format, use one of the following values with the --format option. These correspondto the output formats of the mysqldbexport utility:
• sql (default)
Input consists of SQL statements. For definitions, this consists of the appropriate CREATE and GRANTstatements. For data, this is an INSERT statement (or bulk insert if the --bulk-insert option isspecified).
• grid
Display output in grid or table format like that of the mysql client command-line tool.
• csv
Input is formatted in comma-separated values format.
• raw_csv
Input is a simple CSV file containing uniform rows with values separated with commas. The file cancontain a header (the first row) that lists the table columns. The option --table is required to use thisformat.
• tab
Input is formatted in tab-separated format.
• vertical
Display output in single-column format like that of the \G command for the mysql client command-linetool.
To indicate that input in csv or tab format does not contain column headers, specify the --no-headersoption.
To turn off all feedback information, specify the --quiet option.
You must provide connection parameters (user, host, password, and so forth) for an account that has theappropriate privileges to access all objects in the operation. For details, see NOTES.
Changing Storage Engines
By default, the utility creates each table on the destination server using the same storage engine asthe original table. To override this and specify the storage engine to use for all tables created on thedestination server, use the --new-storage-engine option. If the destination server supports the newengine, all tables use that engine.
To specify the storage engine to use for tables for which the destination server does not support theoriginal storage engine on the source server, use the --default-storage-engine option.
The --new-storage-engine option takes precedence over --default-storage-engine if both aregiven.
If the --new-storage-engine or --default-storage-engine option is given and the destinationserver does not support the specified storage engine, a warning is issued and the server's default storageengine setting is used instead.
Importing Data with GTIDs
121
Importing Data with GTIDs
If you attempt to import databases on a server with GTIDs enabled (GTID_MODE = ON), a warning isgenerated if the import file did not include the GTID statements generated by mysqldbexport.
The utility also generates a warning if you import databases on a server without GTIDs enabled and thereare GTID statements present in the file. Use the --skip-gtid option to ignore the GTID statements.
To make the most use of GTIDs and export/import, you should export all of the databases on the serverwith the --all option. This action generates an export file with all of the databases and the GTIDsexecuted to that point. Importing this file on another server ensures that server has all of the data as wellas all of the GTIDs recorded correctly in its logs.
OPTIONS
mysqldbimport accepts the following command-line options:
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --autocommit
Enable autocommit for data import. By default, autocommit is off and data changes are only committedonce at the end of each imported file.
• --bulk-insert, -b
Use bulk insert statements for data.
• --character-set=charset
Sets the client character set. The default is retrieved from the server variablecharacter_set_client.
• --default-storage-engine=def_engine
The engine to use for tables if the destination server does not support the original storage engine on thesource server.
• --drop-first, -d
Drop each database to be imported if exists before importing anything into it.
• --dryrun
Import the files and generate the statements but do not execute them. This is useful for testing input filevalidity.
• --format=format, -fformat
Specify the input format. Permitted format values are sql (default), grid, tab, csv, raw_csv, andvertical.
OPTIONS
122
• --import=import_type, -iimport_type
Specify the import format. Permitted format values are:
Table 5.2 mysqldbimport Import Types
Import Type Definition
definitions (default) Only import the definitions (metadata) for the objects in the database list
data Only import the table data for the tables in the database list
both Import both the definitions (metadata) and data
If you attempt to import objects into an existing database, the result depends on the import format. Ifthe format is definitions or both, an error occurs unless --drop-first is given. If the format is data,imported table data is added to existing table data.
• --max-bulk-insert
Specify the maximum number of INSERT statements to bulk, by default 30000. This option is only usedwith --bulk-insert.
• --multiprocess
Specify the number of processes to concurrently import the specified files. Special values: 0 (numberof processes equal to the number of detected CPUs) and 1 (default - no concurrency). Multiprocessingworks at the files level for any operating systems.
• --new-storage-engine=new_engine
The engine to use for all tables created on the destination MySQL server.
• --no-headers, -h
Input does not contain column headers. This option only applies to the csv and tab file formats.
• --quiet, -q
Turn off all messages for quiet execution.
• --server=server
Connection information for the server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --skip=skip_objects
NOTES
123
Specify objects to skip in the operation as a comma-separated list (no spaces). Permitted values forthis list are; CREATE_DB, DATA, EVENTS, FUNCTIONS, GRANTS, PROCEDURES, TABLES,TRIGGERS, and VIEWS.
• --skip-blobs
Do not import BLOB data.
• --skip-gtid
Skip execution of GTID_PURGED statements.
• --skip-rpl
Do not execute replication commands.
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --table=db,table
Specify the table for importing. This option is required while using --format=raw_csv.
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
NOTES
The login user must have the appropriate permissions to create new objects, access (read) the mysqldatabase, and grant privileges. If a database to be imported already exists, the user must have readpermission for it, which is needed to check the existence of objects in the database.
Actual privileges needed may differ from installation to installation depending on the security privilegespresent and whether the database contains certain objects such as views or events and whether binarylogging is enabled.
Some combinations of the options may result in errors during the operation. For example, excluding tablesbut not views may result in an error when a view is imported.
EXAMPLES
124
The --new-storage-engine and --default-storage-engine options apply to all destination tablesin the operation.
For the --format and --import options, the permitted values are not case-sensitive. In addition, valuesmay be specified as any unambiguous prefix of a valid value. For example, --format=g specifies the gridformat. An error occurs if a prefix matches more than one valid value.
When importing table data that contain a 0 in the auto_increment column, the import fails unless theNO_AUTO_VALUE_ON_ZERO SQL_MODE SQL_MODE is set. You can view the SQL_MODE with theshow variables like 'sql_mode' command and change the SQL_MODE with the set sql_modecommand.
When importing data and including the GTID commands, you may encounter an error similar to"GTID_PURGED can only be set when GTID_EXECUTED is empty". This occurs because the destinationserver is not in a clean replication state. To solve this problem, you can issue a "RESET MASTER"command on the destination prior to executing the import.
The path to the MySQL client tools should be included in the PATH environment variable in order to use theauthentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
Keep in mind that you can only take advantage of multiprocessing if your system has multiple CPUsavailable for concurrent execution. Also note that multiprocessing is applied at the file level for themysqldbimport utility, which means that only different files can be concurrently imported.
EXAMPLES
To import the metadata from the util_test database to the server on the local host using a file in CSVformat, use this command:
shell> mysqldbimport --server=root@localhost --import=definitions \ --format=csv data.csv# Source on localhost: ... connected.# Importing definitions from data.csv.#...done.
Similarly, to import the data from the util_test database to the server on the local host, importing thedata using bulk insert statements, use this command:
shell> mysqldbimport --server=root@localhost --import=data \ --bulk-insert --format=csv data.csv# Source on localhost: ... connected.# Importing data from data.csv.#...done.
To import both data and definitions from the util_test database, importing the data using bulk insertstatements from a file that contains SQL statements, use this command:
shell> mysqldbimport --server=root@localhost --import=both --bulk-insert --format=sql data.sql
# Source on localhost: ... connected.# Importing definitions and data from data.sql.#...done.
PERMISSIONS REQUIRED
125
PERMISSIONS REQUIRED
You also need permissions to create the new data directory and write data to it including permissions tocreate all objects in the import stream such as views, events, and stored routines. Thus, actual permissionsvary based on the contents of the import stream.
5.10 mysqldiff — Identify Differences Among Database Objects
This utility reads the definitions of objects and compares them using a diff-like method to determinewhether they are the same. The utility displays the differences for objects that are not the same.
Use the notation db1:db2 to name two databases to compare, or, alternatively just db1 to compare twodatabases with the same name. The latter case is a convenience notation for comparing same-nameddatabases on different servers.
The comparison may be executed against two databases of different names on a single server byspecifying only the --server1 option. The user can also connect to another server by specifying the --server2 option. In this case, db1 is taken from server1 and db2 from server2.
When a database pair is specified, all objects in one database are compared to the corresponding objectsin the other. Objects not appearing in either database produce an error.
To compare a specific pair of objects, add an object name to each database name using the db.objformat. For example, use the db1.obj1:db2.obj2 format to compare two named objects, or db1.obj1to compare an object with the same name in databases with the same name. It is not permitted to mixa database name with an object name. For example, db1.obj1:db2 and db1:db2.obj2 are illegalformats.
The comparison may be run against a single server for comparing two databases of different names onthe same server by specifying only the --server1 option. Alternatively, you can also connect to anotherserver by specifying the --server2 option. In this case, the first object to compare is taken from server1and the second from server2.
By default, the utility generates object differences as a difference report. However, you can generatea transformation report containing SQL statements for transforming the objects for conformity instead.Use the 'sql' value for the --difftype option to produce a listing that contains the appropriate ALTERcommands to conform the object definitions for the object pairs specified. If a transformation cannot beformed, the utility reports the diff of the object along with a warning statement. See important limitations inthe NOTES section.
To specify how to display the diff styled output, use one of the following values with the --difftypeoption:
• unified (default)
Display unified format output.
• context
Display context format output.
• differ
Display differ-style format output.
• sql
OPTIONS
126
Display SQL transformation statement output.
The --changes-for option controls the direction of the difference (by specifying the object to betransformed) in either the difference report (default) or the transformation report (designated with the --difftype=sql option). Consider the following command:
shell> mysqldiff --server1=root@host1 --server2=root@host2 --difftype=sql \ db1.table1:dbx.table3
The leftmost database (db1) exists on the server designated by the --server1 option (host1). Therightmost database (dbx) exists on the server designated by the --server2 option (host2).
• --changes-for=server1: Produces output that shows how to make the definitions of objects onserver1 like the definitions of the corresponding objects on server2.
• --changes-for=server2: Produces output that shows how to make the definitions of objects onserver2 like the definitions of the corresponding objects on server1.
The default direction is server1.
For the sql difference format, you can also see the reverse transformation by specifying the --show-reverse option.
The utility stops at the first occurrence of missing objects or when an object does not match. To overridethis behavior, specify the --force option to cause the utility to attempt to compare all objects listed asarguments.
OPTIONS
mysqldiff accepts the following command-line options:
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --changes-for=direction
Specify the server to show transformations to match the other server. For example, to see thetransformation for transforming object definitions on server1 to match the corresponding definitions onserver2, use --changes-for=server1. Permitted values are server1 and server2. The default isserver1.
• --character-set=charset
Sets the client character set. The default is retrieved from the server variablecharacter_set_client.
• --difftype=difftype, -ddifftype
Specify the difference display format. Permitted format values are unified (default), context, differ, andsql.
• --compact
OPTIONS
127
Compacts the output by reducing the control lines that are displayed in the diff results. This option shouldbe used together with one of the following difference types: unified or context.
• --force
Do not halt at the first difference found. Process all objects to find all differences.
• --quiet, -q
Do not print anything. Return only an exit code of success or failure.
• --server1=source
Connection information for the first server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --server2=source
Connection information for the second server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --show-reverse
Produce a transformation report containing the SQL statements to conform the object definitionsspecified in reverse. For example, if --changes-for is set to server1, also generate the transformationfor server2.
Note
The reverse changes are annotated and marked as comments.
SQL TRANSFORMATION LIMITATIONS
128
• --skip-table-options
Ignore the differences between all table options, such as AUTO_INCREMENT, ENGINE, CHARSET,etc.). A warning is issued if the --skip-table-options option is used and table option differencesare found.
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
• --width=number
Change the display width of the test report. The default is 75 characters.
SQL TRANSFORMATION LIMITATIONS
The SQL transformation feature has these known limitations:
• When tables with partition differences are encountered, the utility generates the ALTER TABLEstatement for all other changes but prints a warning and omits the partition differences.
• If the transformation detects table options in the source table (specified with the --changes-foroption) that are not changed or do not exist in the target table, the utility generates the ALTER TABLEstatement for all other changes but prints a warning and omits the table option differences.
• Rename for events is not supported. This is because mysqldiff compares objects by name. In thiscase, depending on the direction of the diff, the event is identified as needing to be added or a DROPEVENT statement is generated.
• Changes in the definer clause for events are not supported.
• SQL extensions specific to MySQL Cluster are not supported.
NOTES
You must provide connection parameters (user, host, password, and so forth) for an account that has theappropriate privileges to access all objects to be compared.
EXAMPLES
129
For the --difftype option, the permitted values are not case-sensitive. In addition, values may bespecified as any unambiguous prefix of a valid value. For example, --difftype=d specifies the differtype. An error occurs if a prefix matches more than one valid value.
The path to the MySQL client tools should be included in the PATH environment variable in order to use theauthentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
If any database object identifier specified as an argument contains special characters or is a reservedword, then it must be appropriately quoted with backticks (`). In turn, names quoted with backticks mustalso be quoted with single or double quotes depending on the operating system, i.e. (") in Windows or (')in non-Windows systems, in order for the utilities to read backtick quoted identifiers as a single argument.For example, to show the difference between table weird`table1 from database weird`db.name and tableweird`table2 from database other:weird`db.name, the objects pair must be specified using the followingsyntax (in non-Windows): '`weird``db.name`.`weird``table1`:`other:weird``db.name`.`weird``table2`'.
EXAMPLES
To compare the employees and emp databases on the local server, use this command:
shell> mysqldiff --server1=root@localhost employees:emp1# server1 on localhost: ... connected.WARNING: Objects in server1:employees but not in server2:emp1: EVENT: e1Compare failed. One or more differences found.
shell> mysqldiff --server1=root@localhost \ employees.t1:emp1.t1 employees.t3:emp1.t3
# server1 on localhost: ... connected.# Comparing employees.t1 to emp1.t1 [PASS]# server1 on localhost: ... connected.# Comparing employees.t3 to emp1.t3 [PASS]Success. All objects are the same.
shell> mysqldiff --server1=root@localhost \ employees.salaries:emp1.salaries --differ
# server1 on localhost: ... connected.# Comparing employees.salaries to emp1.salaries [FAIL]# Object definitions are not the same: CREATE TABLE `salaries` ( `emp_no` int(11) NOT NULL, `salary` int(11) NOT NULL, `from_date` date NOT NULL, `to_date` date NOT NULL, PRIMARY KEY (`emp_no`,`from_date`), KEY `emp_no` (`emp_no`)- ) ENGINE=InnoDB DEFAULT CHARSET=latin1? ^^^^^+ ) ENGINE=MyISAM DEFAULT CHARSET=latin1? ++ ^^^Compare failed. One or more differences found.
The following examples show how to generate a transformation report. Assume the following objectdefinitions:
Host1:
CREATE TABLE db1.table1 (num int, misc char(30));
EXAMPLES
130
Host2:
CREATE TABLE dbx.table3 (num int, notes char(30), misc char(55));
To generate a set of SQL statements that transform the definition of db1.table1 to dbx.table3, usethis command:
shell> mysqldiff --server1=root@host1 --server2=root@host2 \ --changes-for=server1 --difftype=sql \ db1.table1:dbx.table3
# server1 on host1: ... connected.# server2 on host2: ... connected.# Comparing db1.table1 to dbx.table3 [FAIL]# Transformation statements:
ALTER TABLE db1.table1 ADD COLUMN notes char(30) AFTER a, CHANGE COLUMN misc misc char(55);
Compare failed. One or more differences found.
To generate a set of SQL statements that transform the definition of dbx.table3 to db1.table1, usethis command:
shell> mysqldiff --server1=root@host1 --server2=root@host2 \ --changes-for=server2 --difftype=sql \ db1.table1:dbx.table3
# server1 on host1: ... connected.# server2 on host2: ... connected.# Comparing db1.table1 to dbx.table3 [FAIL]# Transformation statements:
ALTER TABLE dbx.table3 DROP COLUMN notes, CHANGE COLUMN misc misc char(30);
Compare failed. One or more differences found.
To generate a set of SQL statements that transform the definitions of dbx.table3 and db1.table1 inboth directions, use this command:
shell> mysqldiff --server1=root@host1 --server2=root@host2 \ --show-reverse --difftype=sql \ db1.table1:dbx.table3
# server1 on host1: ... connected.# server2 on host2: ... connected.# Comparing db1.table1 to dbx.table3 [FAIL]# Transformation statements:
# --destination=server1:ALTER TABLE db1.table1 ADD COLUMN notes char(30) AFTER a, CHANGE COLUMN misc misc char(55);
# --destination=server2:# ALTER TABLE dbx.table3# DROP COLUMN notes,# CHANGE COLUMN misc misc char(30);
PERMISSIONS REQUIRED
131
Compare failed. One or more differences found.
PERMISSIONS REQUIRED
The user must have SELECT privileges for both objects on both servers as well as SELECT on the mysqldatabase.
5.11 mysqldiskusage — Show Database Disk UsageThis utility displays disk space usage for one or more databases. The utility optionally displays disk usagefor the binary log, slow query log, error log, general query log, relay log, and InnoDB tablespaces. Thedefault is to only show database disk usage.
If the command-line lists no databases, the utility shows the disk space usage for all databases.
Sizes displayed without a unit indicator (such as MB) are in bytes.
The utility determines the location of the data directory by requesting it from the server. For a local server,the utility obtains size information directly from files in the data directory and InnoDB home directory. In thiscase, you must have file system access to read those directories. Disk space usage shown includes thesum of all storage engine- specific files such as the .MYI and .MYD files for MyISAM and the tablespacefiles for InnoDB.
If the file system read fails, or if the server is not local, the utility cannot determine exact file sizes. It islimited to information that can be obtained from the system tables, which therefore should be consideredan estimate. For information read from the server, the account used to connect to the server must have theappropriate permissions to read any objects accessed during the operation.
If information requested requires file system access but is not available that way, the utility prints amessage that the information is not accessible. This occurs, for example, if you request log usage but theserver is not local and the log files cannot be examined directly.
To specify how to display output, use one of the following values with the --format option:
• grid (default)
Display output in grid or table format like that of the mysql client command-line tool.
• csv
Display output in comma-separated values format.
• tab
Display output in tab-separated format.
• vertical
Display output in single-column format like that of the \G command for the mysql client command-linetool.
To turn off the headers for grid, csv, or tab display format, specify the --no-headers option.
OPTIONS
mysqldiskusage accepts the following command-line options:
• --help
OPTIONS
132
Display a help message and exit.
• --license
Display license information and exit.
• --all, -a
Display all disk usage. This includes usage for databases, logs, and InnoDB tablespaces.
• --binlog, -b
Display binary log usage.
• --empty, -m
Include empty databases.
• --format=format, -fformat
Specify the output display format. Permitted format values are grid, csv, tab, and vertical. The default isgrid.
• --innodb, -i
Display InnoDB tablespace usage. This includes information about the shared InnoDB tablespace aswell as .idb files for InnoDB tables with their own tablespace.
• --logs, -l
Display general query log, error log, and slow query log usage.
• --no-headers, -h
Do not display column headers. This option applies only for grid, csv, and tab output.
• --quiet, -q
Suppress informational messages.
• --relaylog, -r
Display relay log usage.
• --server=server
Connection information for the server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
NOTES
133
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
For the --format option, the permitted values are not case-sensitive. In addition, values may be specifiedas any unambiguous prefix of a valid value. For example, --format=g specifies the grid format. An erroroccurs if a prefix matches more than one valid value.
NOTES
You must provide connection parameters (user, host, password, and so forth) for an account that has theappropriate privileges for all objects accessed during the operation.
The path to the MySQL client tools should be included in the PATH environment variable in order to use theauthentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
EXAMPLES
To show only the disk space usage for the employees and test databases in grid format (the default),use this command:
shell> mysqldiskusage --server=root@localhost employees test# Source on localhost: ... connected.# Database totals:+------------+--------------+| db_name | total |+------------+--------------+| employees | 205,979,648 || test | 4,096 |+------------+--------------+
Total database disk usage = 205,983,744 bytes or 196.00 MB
PERMISSIONS REQUIRED
134
#...done.
To see all disk usage for the server in CSV format, use this command:
shell> mysqldiskusage --server=root@localhost --format=csv -a -vv# Source on localhost: ... connected.# Database totals:db_name,db_dir_size,data_size,misc_files,totaltest1,0,0,0,0db3,0,0,0,0db2,0,0,0,0db1,0,0,0,0backup_test,19410,1117,18293,19410employees,242519463,205979648,242519463,448499111mysql,867211,657669,191720,849389t1,9849,1024,8825,9849test,56162,4096,52066,56162util_test_a,19625,2048,17577,19625util_test_b,17347,0,17347,17347util_test_c,19623,2048,17575,19623
Total database disk usage = 449,490,516 bytes or 428.00 MB
# Log information.# The general_log is turned off on the server.# The slow_query_log is turned off on the server.
# binary log information:Current binary log file = ./mysql-bin.000076log_file,size/data/mysql-bin.000076,125/data/mysql-bin.000077,125/data/mysql-bin.000078,556/data/mysql-bin.000079,168398223/data/mysql-bin.index,76
Total size of binary logs = 168,399,105 bytes or 160.00 MB
# Server is not an active slave - no relay log information.# InnoDB tablespace information:InnoDB_file,size,type,specification/data/ib_logfile0,5242880,log file,/data/ib_logfile1,5242880,log file,/data/ibdata1,220200960,shared tablespace,ibdata1:210M/data/ibdata2,10485760,shared tablespace,ibdata2:10M:autoextend/data/employees/departments.ibd,114688,file tablespace,/data/employees/dept_emp.ibd,30408704,file tablespace,/data/employees/dept_manager.ibd,131072,file tablespace,/data/employees/employees.ibd,23068672,file tablespace,/data/employees/salaries.ibd,146800640,file tablespace,/data/employees/titles.ibd,41943040,file tablespace,
Total size of InnoDB files = 494,125,056 bytes or 471.00 MB
#...done.
PERMISSIONS REQUIRED
The user must have permissions to read the data directory or use an administrator, super user (sudo), oran account with elevated privileges to obtain access to the data directory.
5.12 mysqlfailover — Automatic replication health monitoring andfailover
mysqlfailover — Automatic replication health monitoring and failover
135
This utility permits users to perform replication health monitoring and automatic failover on a replicationtopology consisting of a single master and its slaves. The utility is designed to run interactively orcontinuously refreshing the health information and checking the master status at periodic intervals. Itsprimary mission is to monitor the master for failure and when a failure occurs, execute failover to one of theslaves that is in a valid state. The utility accepts an optional list of slaves to be considered for the candidateslave.
This utility is designed to work exclusively for servers that support global transaction identifiers (GTIDs)and have gtid_mode=ON. MySQL server versions 5.6.5 and higher support GTIDs. See Replicationwith Global Transaction Identifiers for more information. Thus, this utility does not work with anonymousreplication servers (binary log + position).
The user can specify the interval in seconds to use for detecting the master status and generating thehealth report using the --interval option. At each interval, the utility checks to see if the server is alivevia a ping operation followed by a check of the connector to detect if the server is still reachable. The pingoperation can be controlled with the --ping option (see below).
If the master is found to be offline or unreachable, the utility executes one of the following actions based onthe --failover-mode option value. The available values are:
• auto (default): Execute automatic failover to the list of candidates first and if no slaves are viable,continue to search the remaining slaves for a viable candidate. The command tests each candidateslave listed for the prerequisites. Once a candidate slave is elected, it is made a slave of each of theother slaves thereby collecting any transactions executed on other slaves but not the candidate. In thisway, the candidate becomes the most up-to-date slave. If no slave is found to be a viable candidate, theutility generates an error and exit.
• elect: This mode is the same as auto, except if no candidates specified in the list of candidate slaves areviable, then it does not check the remaining slaves, and instead generates an error and then exits. Usethis option to force failover to one or more specific slaves using the --candidates option.
• fail: This mode produces an error and does not failover when the master is detected as down orunreachable. This mode is used to provide periodic health monitoring without the failover action taken.
For all options that permit specifying multiple servers, the options require a comma-separated list ofconnection parameters in the following form (where the password, port, and socket are optional).:
*user*[:*passwd*]@*host*[:*port*][:*socket*] or*login-path*[:*port*][:*socket*]
The utility permits users to discover slaves connected to the master. The discover slaves featureis run automatically on each interval. Furthermore, it is required that slaves use the --master-info-repository=TABLE startup setting.
The discover slaves option requires all slaves use the --report-host and --report-portserver startup variables with the correct hostname and port. If these are missing or report the incorrectinformation, the slave may not be detected and thus not included in the operation of the utility. Thediscover slaves option ignores any slaves to which it cannot connect.
Note
If you have one or more slaves which do not report their hostname and portand should a failover event occur, those slaves are not included in the resultingtopology. That is, they are not a slave of the new master. Be sure to check that allof your slaves are accounted for in the health report before relying on the utility forcomplete automatic failover.
mysqlfailover — Automatic replication health monitoring and failover
136
The utility permits the user to specify an external script to execute before and after the switchover andfailover commands. The user can specify these with the --exec-before and --exec-after options.The return code of the script is used to determine success. Each script must report 0 (success) to beconsidered successful. If a script returns a value other than 0, the result code is presented in an errormessage.
The utility also permits the user to specify a script to be used for detecting a downed master or anapplication-level event to trigger failover. This can be specified using the --exec-fail-check option.The return code for the script is used to invoke failover. A return code of 0 indicates failover should not takeplace. A return code other than 0 indicates failover should take place. This is checked at the start of eachinterval if a script is supplied. The timeout option is not used in this case and the script is run once at thestart of each interval.
The utility permits the user to log all actions taken during the commands. The --log option requires avalid path and filename of the file to use for logging operations. The log is active only when this option isspecified. The option --log-age specifies the age in days that log entries are kept. The default is seven(7) days. Older entries are automatically deleted from the log file (but only if the --log option is specified).
The format of the log file includes the date and time of the event, the level of the event (informational -INFO, warning - WARN, error - ERROR, critical failure - CRITICAL), and the message reported by theutility.
The interface provides a number of options for displaying additional information. You can choose to viewthe replication health report (default), or choose to view the list of GTIDs in use, the UUIDs in use, or viewthe log file contents if logging is enabled. Each of these reports is described below.
• health Display the replication health of the topology. This report is the default view for the interface. Bydefault, this includes the host name, port, role (MASTER or SLAVE) of the server, state of the server(UP = is connected, WARN = not connected but can ping, DOWN = not connected and cannot ping), theGTID_MODE, and health state.
The master health state is based on the following: if GTID_MODE=ON, the server must have the binarylog enabled, and a user must exist with the REPLICATE SLAVE privilege.
The --seconds-behind option is used to detect when a slave is behind the master. It allows usersto set a threshold for reporting purposes only. It does not apply to slave candidacy or selection duringfailover.
The slave health state is based on the following: the IO_THREAD and SQL_THREADS must be running,it must be connected to the master, there are no errors, the slave delay for non-GTID enabled scenariosis not more than the threshold provided by the --max-position and the slave is reading the correctmaster log file, and slave delay is not more than the --seconds-behind threshold option.
At each interval, if the discover slaves option was specified at startup and new slaves are discovered,the health report is refreshed.
• gtid: Display the master's list of executed GTIDs, contents of the GTID variables;@@GLOBAL.GTID_EXECUTED, @@GLOBAL.GTID_PURGED, and @@GLOBAL.GTID_OWNED. Thus, youcan toggle through the four screens by pressing the 'G' key.
• UUID: Display universally unique identifiers (UUIDs) for all servers.
• Log: This option displays the contents of the log file, which only visible if the --log option is specified.This can be helpful to see when failover occurred, and which actions or messages were recorded at thetime.
MODES OF OPERATION
137
The user interface is designed to match the size of the terminal window in which it is run. A refresh optionis provided to permit users to resize their terminal windows or refresh the display at any time. However, theinterface automatically resizes to the terminal window on each interval.
The interface displays the name of the utility, the master's status including binary log file, position, andfilters as well as the date and time of the next interval event.
The interface also permits the user to scroll up or down through a list longer than what the terminal windowpermits. When a long list is presented, the scroll options become enabled. The user can scroll the list upwith the up arrow key and down with the down arrow key.
Use the --verbose option to see additional information in the health report and additional messagesduring failover.
MODES OF OPERATION
The utility supports two modes of operation. The default mode, running as a console, works as describedabove. An additional mode that permits you to run the utility as a daemon is provided for POSIX platforms.
When run as a daemon, the utility does not have interactivity. However, all events are written to the log file.You can control what is written to the log by using the --report-values option.
To run the utility as a daemon, use the --daemon option. There are four commands that can be used in --daemon option. These include:
• start
Starts the daemon. The --log option is required.
• stop
Stops the daemon. If you used the option --pidfile, the value must be the same when starting thedaemon.
• restart
Restarts the daemon. If you used the option --pidfile, the value must be the same when starting thedaemon.
• nodetach
Starts the daemon, but does not detach the process from the console. The --log option is required.
OPTIONS
mysqlfailover accepts the following command-line options:
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --candidates=candidate slave connections
Connection information for candidate slave servers. Valid only with failover command. List multipleslaves in comma-separated list.
OPTIONS
138
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --connection-timeout=seconds
Set the connection timeout for TCP and Unix socket connections for all master, slaves, and candidateslaves specified. This changes the connection timeout for the Connector/Python connection to theserver. The default is 10 seconds as defined in the Connector/Python library. This setting may be helpfulfor installations with low network and server reliability.
• --daemon=command
Run as a daemon. The command can be start (start daemon), stop (stop daemon), restart (stopthen start the daemon) or nodetach (start but do not detach the process). This option is only availablefor POSIX systems.
• --discover-slaves-login=user:password
At startup, query master for all registered slaves and use the user name and password specified toconnect. Supply the user and password in the form user[:passwd] or login-path. For example, --discover=joe:secret uses 'joe' as the user and 'secret' as the password for each discovered slave.
• --exec-after=script
Name of script to execute after failover or switchover. Script name may include the path.
• --exec-before=script
Name of script to execute before failover or switchover. Script name may include the path.
• --exec-fail-check=script
Name of script to execute on each interval to invoke failover.
• --exec-post-failover=script
Name of script to execute after failover is complete and the utility has refreshed the health report.
• --failover-mode=mode, -f mode
Action to take when the master fails. 'auto' = automatically fail to best slave, 'elect' = fail to candidate listor if no candidate meets criteria fail, 'fail' = take no action and stop when master fails. Default = 'auto'.
• --force
Override the registration check on master for multiple instances of the console monitoring the samemaster. See notes.
OPTIONS
139
• --interval=seconds, -i seconds
Interval in seconds for polling the master for failure and reporting health. Default = 15 seconds. Minimumis 5 seconds.
• --log=log_file
Specify a log file to use for logging messages
• --log-age=days
Specify maximum age of log entries in days. Entries older than this are purged on startup. Default = 7days.
• --master=connection
Connection information for the master server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --master-fail-retry=seconds
Time in seconds to wait to determine if the master is down. The failover check is run again when theretry delay expires. Can be used to introduce a longer period between when master is detected asunavailable to declaring it down. This option is not used with --exec-fail-check option.
Note
This option was added in MySQL Utilities 1.6.4.
• --max-position=position
Used to detect slave delay. The maximum difference between the master's log position and the slave'sreported read position of the master. A value greater than this means the slave is too far behind themaster. Default = 0.
• --pedantic, -p
Used to stop failover if some inconsistencies are found, such as errant transactions on slaves or SQLthread errors, during server checks. By default, the utility only generates warnings if issues are foundwhen checking a slave's status during failover, and it continues execution unless this option is specified.
• --pidfile=pidfile
Pidfile for running mysqlfailover as a daemon. This file contains the PID (process identifier), thatuniquely identifies a process. It is needed to identify and control the process forked by mysqlfailover.
OPTIONS
140
• --ping=number
The code uses three attempts to contact the server with the ping command as part of the detectionalgorithm to check to see if the master is alive. This option sets the number of seconds to wait betweeneach ping attempt. The default --ping value is 3 seconds.
Note
On some platforms, this is the same as number of seconds to wait for ping toreturn.
• --report-values=report_values
Report values used in mysqlfailover running as a daemon. It can be health, gtid or uuid. Multiple valuescan be used separated by commas.
• health
Display the replication health of the topology.
• gtid
Display the master's list of executed GTIDs, contents of the GTID variables;@@GLOBAL.GTID_EXECUTED, @@GLOBAL.GTID_PURGED and @@GLOBAL.GTID_OWNED.
• uuid
Display universally unique identifiers (UUIDs) for all servers.
Default = health.
• --rpl-user=:replication_user
The user and password for the replication user requirement, in the form: user[:password] or login-path. E.g. rpl:passwd
Default = None.
• --script-threshold=return_code
Value for external scripts to trigger aborting the operation if result is greater than or equal to thethreshold.
Default = None (no threshold checking).
• --seconds-behind=seconds
Used to detect slave delay (only for health reporting purposes). The maximum number of secondsbehind the master permitted before slave is considered behind the master in the health report state.Default = 0.
• --slaves=slave connections
Connection information for slave servers. List multiple slaves in comma-separated list. The list isevaluated literally whereby each server is considered a slave to the master listed regardless if they are aslave of the master.
NOTES
141
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --timeout=seconds
Maximum timeout in seconds to wait for each replication command to complete. For example, timeout forslave waiting to catch up to master.
Default = 3.
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
NOTES
The login user must have the appropriate permissions for the utility to check servers and monitortheir status (e.g., SHOW SLAVE STATUS, SHOW MASTER STATUS). The user must alsohave permissions to execute the failover procedure (e.g., STOP SLAVE, START SLAVE,WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS, CHANGE MASTER TO ...). Lastly, the user must have theREPLICATE SLAVE privilege for slaves to connect to their master. The same permissions are requiredby the failover utility for master and slaves in order to run successfully. In particular, users connected toslaves, candidates and master require SUPER, GRANT OPTION, REPLICATION SLAVE, RELOAD, DROP,CREATE, INSERT and SELECT privileges.
NOTES
142
The DROP, CREATE, INSERT and SELECT privileges are required to register the failover instance on theinitial master or the new master (after a successful failover). Therefore, since any slave can become thenew master, slaves and candidates also require those privileges. The utility checks permissions for themaster, slaves, and candidates at startup.
While this utility can be used to perform failover should the master fail, care should be taken whendesigning your high availability solution. You must design your topology so that it can tolerate a number offailures to match your risk assessment.
In this case, the number of candidate slaves determines the number of times the utility can safely failover.For example, having a master and four candidate slaves allows up to four failures; one for the originalmaster and up to three candidates. That is, should the first new master fail, the utility will try to failover tothe next available candidate slave (or simply those listed as slaves).
When the utility has failed over to the last slave in the topology (and there are no other slaves), the utilitywill continue to monitor that master but when that master fails, the utility will stop with an error. In this case,no user supplied scripts will run (for example, --exec-before, --exec-after, --exec-post-failover).
However, if the utility is started with the auto failover mode (--failover-mode=auto), you can add slavesat any time and those new slaves will become candidates for failover. In that case, so long as there areslaves to failover to, the utility will continue to monitor the master. Slaves can be added while the utility isrunning using the normal replication procedure for adding a slave to a master. You do not need to stop theutility to add a new slave.
If the failover mode is set to elect (--failover-mode=elect), when the last candidate slave is chosen as themaster, the utility will not failover to any other slaves even if they were added to the topology after theutility was started. This is because the elect mode limits candidate selection to the list specified with the--candidates option. In this case, when the last master (candidate slave) fails, the utility will stop with anerror.
Note
While a topology with one master and one candidate slave is a basic replicationtopology, it can tolerate at most one failure and therefore is not a recommendedsetup for critical high availability scenarios.
Mixing IP and hostnames is not recommended. The replication-specific utilities attempt to comparehostnames and IP addresses as aliases for checking slave connectivity to the master. However, if yourinstallation does not support reverse name lookup, the comparison could fail. Without the ability to do areverse name lookup, the replication utilities could report a false negative that the slave is (not) connectedto the master.
For example, if you set up replication using MASTER_HOST=ubuntu.net on the slave and later connectto the slave with mysqlrplcheck and have the master specified as --master=198.51.100.6 using thevalid IP address for ubuntu.net, you must have the ability to do a reverse name lookup to compare the IP(198.51.100.6) and the hostname (ubuntu.net) to determine if they are the same machine.
Similarly, in order to avoid issues mixing local IP '127.0.0.1' with 'localhost', all the addresses '127.0.0.1'are internally converted to 'localhost' by the utility. Nevertheless, it is best to use the actual hostname of themaster when connecting or setting up replication.
The utility checks to see if the slaves are using the option --master-info-repository=TABLE. If theyare not, the utility stops with an error.
The path to the MySQL client tools should be included in the PATH environment variable in order to usethe authentication mechanism with login-paths. This allows the utility to use the my_print_defaults toolwhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
EXAMPLES
143
At startup, the console attempts to register itself with the master. If another console is already registered,and the failover mode is auto or elect, the console is blocked from running failover. When a console quits, itunregisters itself from the master. If this process is broken, the user may override the registration check byusing the --force option.
The console creates a special table in the mysql database that is used to keep track of which instance iscommunicating with the master. If you use the --force option, the console removes the rows in this table.The table is constructed with:
CREATE TABLE IF NOT EXISTS mysql.failover_console (host char(30), port char(10))
When the console starts, a row is inserted containing the hostname and port of the master. On startup, if arow matches these values, the console does not start. If you use the --force option, the row is deleted.
When running the utility using the --daemon=nodetach option, the --pidfile option can be omitted. Itis ignored if used.
When using the external scripts, the following parameters are passed in the order shown.
Suppose you have a script run_before.sh and you specify that you want it executing before the failoveris performed (using the --exec-before option). Further, let us assume the master MySQL Server isusing port 3306 on the host 'host1' and the MySQL Server that becomes the new master is using port 3308on host 'can_host2'. The script would therefore be invoked in the following manner.
% run_before.sh host1 3306 can_host2 3308
Table 5.3 External Script Parameters
MySQL Failover Option Parameters Passed to External Script
--exec-before master host, master port, candidate host, candidate port
--exec-after new master host, new master port
--exec-fail-check master host, master port
--exec-post-failover (noerrors during failover)
old master host, old master port, new master host, new master port
--exec-post-failover(errors during failover)
old master host, old master port
EXAMPLES
To launch the utility, you must specify at a minimum the --master option and either the --discover-slaves-login option or the --slaves option. The --discover-slaves-login option can be usedin conjunction with the --slaves option to specify a list of known slaves (or slaves that do not report theirhost and IP) and to discover any other slaves connected to the master.
An example of the user interface and some of the report views are shown in the following examples.
Note
The "GTID Executed Set" displays the first GTID listed in the SHOW MASTERSTATUS view. If there are multiple GTIDs listed, the utility displays [...] toindicate there are additional GTIDs to view. You can view the complete list of GTIDson the GTID display screens.
The default interface displays the replication health report like the following. In this example the log file isenabled. A sample startup command is shown below:
EXAMPLES
144
shell> mysqlfailover --master=root@localhost:3331 --discover-slaves-login=root --log=log.txt
MySQL Replication Monitor and Failover UtilityFailover Mode = auto Next Interval = Mon Mar 19 15:56:03 2012
Master Information------------------Binary Log File Position Binlog_Do_DB Binlog_Ignore_DBmysql-bin.000001 571
GTID Executed Set2A67DE00-2DA1-11E2-A711-00764F2BE90F:1-7 [...]
Replication Health Status+------------+-------+---------+--------+------------+---------+| host | port | role | state | gtid_mode | health |+------------+-------+---------+--------+------------+---------+| localhost | 3331 | MASTER | UP | ON | OK || localhost | 3332 | SLAVE | UP | ON | OK || localhost | 3333 | SLAVE | UP | ON | OK || localhost | 3334 | SLAVE | UP | ON | OK |+------------+-------+---------+--------+------------+---------+Q-quit R-refresh H-health G-GTID Lists U-UUIDs L-log entries
Press Q to exit the utility, R to refresh the current display, and H returns to the replication health report.
Press the G key to show a GTID report similar to the following. The first page shown is the master'sexecuted GTID set:
MySQL Replication Monitor and Failover UtilityFailover Mode = auto Next Interval = Mon Mar 19 15:59:33 2012
Master Information------------------Binary Log File Position Binlog_Do_DB Binlog_Ignore_DBmysql-bin.000001 571
GTID Executed Set2A67DE00-2DA1-11E2-A711-00764F2BE90F:1-7 [...]
Master GTID Executed Set+-------------------------------------------+| gtid |+-------------------------------------------+| 2A67DE00-2DA1-11E2-A711-00764F2BE90F:1-7 || 5503D37E-2DB2-11E2-A781-8077D4C14B33:1-3 |+-------------------------------------------+
Q-quit R-refresh H-health G-GTID Lists U-UUIDs L-log entries Up|Down-scroll
Continuing to press G cycles through the three GTID lists.
If the list is longer than the screen permits as shown in the example above, the scroll up and down help isalso shown. In this case, press the down arrow key to scroll down.
Press U to view the list of UUIDs used in the topology, for example:
MySQL Replication Monitor and Failover UtilityFailover Mode = auto Next Interval = Mon Mar 19 16:02:34 2012
Master Information------------------Binary Log File Position Binlog_Do_DB Binlog_Ignore_DB
EXAMPLES
145
mysql-bin.000001 571
GTID Executed Set2A67DE00-2DA1-11E2-A711-00764F2BE90F:1-7 [...]
UUIDs+------------+-------+---------+---------------------------------------+| host | port | role | uuid |+------------+-------+---------+---------------------------------------+| localhost | 3331 | MASTER | 55c65a00-71fd-11e1-9f80-ac64ef85c961 || localhost | 3332 | SLAVE | 5dd30888-71fd-11e1-9f80-dc242138b7ec || localhost | 3333 | SLAVE | 65ccbb38-71fd-11e1-9f80-bda8146bdb0a || localhost | 3334 | SLAVE | 6dd6abf4-71fd-11e1-9f80-d406a0117519 |+------------+-------+---------+---------------------------------------+Q-quit R-refresh H-health G-GTID Lists U-UUIDs L-log entries
If, once the master is detected as down and failover mode is auto or elect and there are viable candidateslaves, the failover feature engages automatically and the user sees the failover messages appear. Whenfailover is complete, the interface returns to monitoring replication health after 5 seconds. The followingshows an example of failover occurring:
Failover starting...# Candidate slave localhost:3332 will become the new master.# Preparing candidate for failover.# Creating replication user if it does not exist.# Stopping slaves.# Performing STOP on all slaves.# Switching slaves to new master.# Starting slaves.# Performing START on all slaves.# Checking slaves for errors.# Failover complete.# Discovering slaves for master at localhost:3332
Failover console will restart in 5 seconds.
After the failover event, the new topology is shown in the replication health report:
MySQL Replication Monitor and Failover UtilityFailover Mode = auto Next Interval = Mon Mar 19 16:05:12 2012
Master Information------------------Binary Log File Position Binlog_Do_DB Binlog_Ignore_DBmysql-bin.000001 1117
GTID Executed Set2A67DE00-2DA1-11E2-A711-00764F2BE90F:1-7 [...]
UUIDs+------------+-------+---------+--------+------------+---------+| host | port | role | state | gtid_mode | health |+------------+-------+---------+--------+------------+---------+| localhost | 3332 | MASTER | UP | ON | OK || localhost | 3333 | SLAVE | UP | ON | OK || localhost | 3334 | SLAVE | UP | ON | OK |+------------+-------+---------+--------+------------+---------+
Q-quit R-refresh H-health G-GTID Lists U-UUIDs L-log entries
Pressing L with the --log option specified causes the interface to show the entries in the log file, such as:
MySQL Replication Monitor and Failover Utility
LIMITATIONS
146
Failover Mode = auto Next Interval = Mon Mar 19 16:06:13 2012
Master Information------------------Binary Log File Position Binlog_Do_DB Binlog_Ignore_DBmysql-bin.000001 1117
GTID Executed Set2A67DE00-2DA1-11E2-A711-00764F2BE90F:1-7 [...]
Log File+-------------------------+----------------------------------------- ... --+| Date | Entry ... |+-------------------------+----------------------------------------- ... --+| 2012-03-19 15:55:33 PM | INFO Failover console started. ... || 2012-03-19 15:55:33 PM | INFO Failover mode = auto. ... || 2012-03-19 15:55:33 PM | INFO Getting health for master: localhos ... || 2012-03-19 15:55:33 PM | INFO Master status: binlog: mysql-bin.00 ... |+-------------------------+----------------------------------------- ... --+Q-quit R-refresh H-health G-GTID Lists U-UUIDs L-log entries Up|Down-scroll\
LIMITATIONS
When the --master-fail-retry option is used, and the value specified exceeds the value of the--interval option, it is possible for an interval event to be delayed if the master retry check is stillprocessing. In this case, should the master not be down, the next interval occurs immediately after thecheck of the master is complete.
PERMISSIONS REQUIRED
The user must have permissions to monitor the servers on the topology and configure replication tosuccessfully perform the failover operation. Additional permissions are also required to register andunregister the running mysqlfailover instance on the master and slaves. Specifically, the login user musthave the following privileges: SUPER, GRANT OPTION, REPLICATION SLAVE, RELOAD, DROP, CREATE,INSERT, and SELECT. (See Privileges Provided by MySQL, for more information about these.)
The referred permissions are required for the login users used for all servers (master, slaves, andcandidates).
5.13 mysqlfrm — File reader for .frm files.The mysqlfrm utility is designed as a recovery tool that reads .frm files and produces equivalent CREATEstatements from the table definition data found in the file. In most cases, the generated CREATE statementis usable for recreating the table on another server, or for extended diagnostics. However, some featuresare not saved in the .frm files and therefore are omitted. The exclusions include but are not limited to:
• foreign key constraints
• auto increment number sequences
The mysqlfrm utility has two modes of operation. The default mode is designed to spawn an instanceof an installed server by referencing the base directory using the --basedir option, or by connecting tothe server with the --server option. The process does not alter the original .frm file(s). This mode alsorequires the --port option to specify a port to use for the spawned server. It must be different than theport for the installed server and no other server must be using the port. The spawned server is shutdownand all temporary files removed after the .frm files are read.
A diagnostic mode is available by using the --diagnostic option. This switches the utility to readthe .frm files byte-by-byte to recover as much information as possible. The diagnostic mode has additionallimitations in that it cannot decipher character set or collation values without using an existing server
OPTIONS
147
installation specified with either the --server or --basedir option. This can also affect the size of thecolumns if the table uses multibyte characters. Use this mode when the default mode cannot read the file,or if a MySQL server is not installed on the host.
To read .frm files, list each file as a separate argument for the utility as shown in the following examples.You must specify the path for each .frm file you want to read or supply a path to a directory and all ofthe .frm files in that directory to be read.
You can specify the database name to be used in the resulting CREATE statement by adding the name ofthe database followed by a colon to the .frm filename. For example, oltp:t1.frm uses 'oltp' for the databasename in the CREATE statement. The optional database name can also be used with paths. For example, /home/me/oltp:t1.frm uses 'oltp' as the database name. If you leave off the optional database name andinclude a path, the last folder is the database name. For example /home/me/data1/t1.frm uses 'data1' asthe database name. If you do not want to use the last folder as the database name, simply specify thecolon like this: /home/me/data1/:t1.frm. In this case, the database is omitted from the CREATE statement.
OPTIONS
• --help
show the program's help page
• --license
Display license information and exit.
• --basedir=basedir
The base directory for the server installed. Use this or --server for the default mode.
• --diagnostic
Turn on diagnostic mode to read .frm files byte-by-byte and generate best-effort CREATE statement.
• --new-storage-engine=engine
Set the ENGINE= option for all .frm files read.
• --port=port
The port to use for the spawned server in the default mode. Must be a free port. Required for defaultmode.
• --server=server
Connection information for a server. Use this option or --basedir for the default mode. If provided withthe diagnostic mode, the storage engine and character set information are validated against this server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
NOTES
148
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --show-stats, -s
Show file statistics and general table information for each .frm file read.
• --start-timeout=timeout_in_seconds
Number of seconds to wait for spawned server to start. The default is 10 seconds.
• --user
Execute the spawned server using this user account. Permits the execution of the utility as one user butthe spawned server as another. Required if running the utility as the root user (e.g. su or sudo).
• --quiet
Turn off all messages for quiet execution except CREATE statements and errors.
• --verbose, -v
Control how much information is displayed. For example, -v = verbose, -vv = more verbose, -vvv =debug
• --version
Show program's version number and exit
NOTES
Tables with certain storage engines cannot be read in the default mode. These include PARTITION,PERFORMANCE_SCHEMA. You must read these with the --diagnostic mode.
Use the --diagnostic mode for tables that fail to open correctly in the default mode or if there is noserver installed on the host.
To change the storage engine in the CREATE statement generated for all .frm files read, use the --new-storage-engine option
To turn off all messages except the CREATE statement and warnings or errors, use the --quiet option.
EXAMPLES
149
Use the --show-stats option to see file statistics for each .frm file.
If you need to run the utility with elevated privileges, use the --user option to execute the spawned serverusing a normal user account.
If you encounter connection or similar errors when running in default mode, re-run the command withthe --verbose option and view the output from the spawned server and repair any errors in launchingthe server. If mysqlfrm fails in the middle, you may need to manually shutdown the server on the portspecified with --port.
EXAMPLES
The following example reads a single .frm file in the default mode from the current working directory usingthe server installed in /usr/local/bin/mysql and port 3333 for the spawned server. Notice the useof the db:table.frm format for specifying the database name for the table. The database name appears tothe left of ':' and the .frm name to the right. In this case, we have database = test1 and table = city, so theCREATE statement reads CREATE TABLE test1.city.
shell> mysqlfrm --basedir=/usr/local/bin/mysql test1:city.frm --port=3333# Starting the spawned server on port 3333 ... done.# Reading .frm files## Reading the city.frm file.## CREATE statement for city.frm:#
CREATE TABLE `test1`.`city` ( `city_id` smallint(5) unsigned NOT NULL AUTO_INCREMENT, `city` varchar(50) NOT NULL, `country_id` smallint(5) unsigned NOT NULL, `last_update` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, PRIMARY KEY (`city_id`), KEY `idx_fk_country_id` (`country_id`)) ENGINE=InnoDB DEFAULT CHARSET=utf8
#...done.
The following demonstrates reading multiple .frm files in the default mode using a running server. The .frmfiles are located in different folders. Notice the use of the database name option for each of the files. Thet1 file was given the database name temp1 since that is the folder in which it resides, t2 was given db1since that was specified in the path, and t3 was not given a database name since we used the ':' withoutproviding a database name.
shell> mysqlfrm --server=root:pass@localhost:3306 /mysql/data/temp1/t1.frm \ /mysql/data/temp2/db1:t2.frm --port=3310# Starting the spawned server on port 3333 ... done.# Reading .frm files### Reading the t1.frm file.## CREATE statement for ./mysql-test/std_data/frm_files/t1.frm:#
CREATE TABLE `temp1`.`t1` ( `a` int(11) DEFAULT NULL) ENGINE=MyISAM DEFAULT CHARSET=latin1
# Reading the t2.frm file.#
PERMISSIONS REQUIRED
150
# CREATE statement for ./mysql-test/std_data/frm_files/t2.frm:#
CREATE TABLE `db1`.`t2` ( `a` int(11) DEFAULT NULL) ENGINE=MyISAM DEFAULT CHARSET=latin1
## Reading the t3.frm file.## CREATE statement for ./mysql-test/std_data/frm_files/t3.frm:#
CREATE TABLE `t3` ( `a` int(11) DEFAULT NULL) ENGINE=MyISAM DEFAULT CHARSET=latin1
#...done.
The following demonstrates running the utility in diagnostic mode to read all of the .frm files in a directory.
shell> mysqlfrm --diagnostic /mysql/data/sakila# WARNING: Cannot generate character set or collation names without the --server option.# CAUTION: The diagnostic mode is a best-effort parse of the .frm file. As such, it may not identify all of the components of the table correctly. This is especially true for damaged files. It will also not read the default values for the columns and the resulting statement may not be syntactically correct.# Reading .frm file for /mysql/data/sakila/city.frm:# The .frm file is a TABLE.# CREATE TABLE Statement:
CREATE TABLE `city` ( `city_id` smallint(5) unsigned NOT NULL AUTO_INCREMENT, `city` varchar(150) NOT NULL, `country_id` smallint(5) unsigned NOT NULL, `last_update` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,PRIMARY KEY `PRIMARY` (`city_id`),KEY `idx_fk_country_id` (`country_id`)) ENGINE=InnoDB;
#...done.
PERMISSIONS REQUIRED
The permissions for using mysqlfrm vary and depend entirely on how you use it. If you use the utility toread .frm files in a protected folder like the example above (in either mode), you must have the ability to runthe spawned server with privileges that allow you to read the protected files. For example, you could use auser account that has root-level privileges.
If you use the utility with a server connection, the user you use to connect must have the ability to readsystem variables at a minimum including read access to the mysql database.
Note
You should never use the root user to spawn the server nor should you use themysql user when spawning the server or running the utility.
5.14 mysqlgrants — Display grants by objectManaging privileges can be a challenge. Sometimes all a DBA needs to know is which users have accessto a given list of objects such as a list of databases, tables, etc. This utility allows DBAs to see which usershave what level of access for each object listed. Objects supported include databases, tables, functions,and procedures. The utility follows the grant hierarchy within MySQL displaying global- and object-levelaccess GRANT statements.
OPTIONS
151
Note
This utility was added in MySQL Utilities 1.6.0.
The utility allows the users to choose among three reports: users, user_grants and raw.
• users
displays a list of users who have access to the list of objects
• user_grants
displays a list of users sorted by object including their access level (privileges)
• raw
display the GRANT statements that define the user's privileges
The utility also provides an optional --privileges option that permits users to specify a list of privilegesthat form the minimal set for access. The list of privileges forms a filter such that a user must have all of theprivileges specified for a specific object.
Note
It is possible that the combination of specified privileges can form an invalid set.In such cases, the utility ignores the errant privilege. For example, specifying theSELECT privilege for a routine causes the utility to exclude it from the filter check.
OPTIONS
mysqlgrants accepts the following command-line options:
• --help
Display a help message and exit.
• --inherit-level=level
Specifies the inheritance level of the GRANT operations. This parameter has three options; global,database, and object. The default value is global.
• global: (default) indicates grants shown at the global level, such as "GRANT ... ON *.*". All grants areshown.
• database: indicates grants shown at the database level, such as "GRANT ... ON db1.*". Global levelgrants are not shown.
• object: indicates grants shown at the object level, such as "GRANT ... ON db1.tbl1". Database andglobal level grants are not shown.
This option was added in MySQL Utilities 1.6.2.
• --license
Display license information and exit.
• --privileges=list of required privileges
NOTES
152
Minimum set of privileges that a user must have for any given object.
• --server=source
Connection information for the server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --show=output_type
Type of report. Options include users, user_grants and raw.
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
NOTES
To use the users value in the --show option, you must specify at least one privilege using the --privileges option.
If you specify some privileges on the --privileges option that are not valid for all the specified objects,any that do not apply are not included in the list. For example, the SELECT privilege is ignored for storedroutines and the EXECUTE privilege is ignored for tables but both are taken into account for databases.
EXAMPLES
153
EXAMPLES
Check the grantees and respective privileges over different object types: databases, tables, proceduresand functions.
shell> mysqlgrants --server=user:pass@localhost:3310 \ --show=user_grants util_test util_test.t3 util_test.t2 \ util_test.t1 util_test.p1 util_test.f1
# DATABASE `util_test`:# - 'joe'@'user' : ALL PRIVILEGES# - 'joe_wildcard'@'%' : ALL PRIVILEGES# - 'priv_test_user'@'%' : EXECUTE, GRANT OPTION, SELECT, TRIGGER, UPDATE# - 'priv_test_user2'@'%' : EXECUTE, SELECT, UPDATE# - 'priv_test_user3'@'%' : ALTER ROUTINE, DELETE, DROP, EXECUTE, TRIGGER, UPDATE
# TABLE `util_test`.`t1`:# - 'joe'@'user' : ALL PRIVILEGES# - 'joe_wildcard'@'%' : ALL PRIVILEGES# - 'priv_test_user'@'%' : GRANT OPTION, SELECT, TRIGGER, UPDATE# - 'priv_test_user2'@'%' : ALL PRIVILEGES, GRANT OPTION# - 'priv_test_user3'@'%' : DELETE, DROP, TRIGGER, UPDATE
# TABLE `util_test`.`t2`:# - 'joe'@'user' : ALL PRIVILEGES# - 'joe_wildcard'@'%' : ALL PRIVILEGES# - 'priv_test_user'@'%' : GRANT OPTION, SELECT, TRIGGER, UPDATE# - 'priv_test_user2'@'%' : SELECT, UPDATE# - 'priv_test_user3'@'%' : DELETE, DROP, TRIGGER, UPDATE
# TABLE `util_test`.`t3`:# - 'joe'@'user' : ALL PRIVILEGES# - 'joe_wildcard'@'%' : ALL PRIVILEGES# - 'priv_test_user'@'%' : GRANT OPTION, SELECT, TRIGGER, UPDATE# - 'priv_test_user2'@'%' : SELECT, UPDATE# - 'priv_test_user3'@'%' : DELETE, DROP, SELECT, TRIGGER, UPDATE
# ROUTINE `util_test`.`f1`:# - 'joe'@'user' : ALL PRIVILEGES# - 'joe_wildcard'@'%' : ALL PRIVILEGES# - 'priv_test_user'@'%' : EXECUTE, GRANT OPTION# - 'priv_test_user2'@'%' : ALL PRIVILEGES, GRANT OPTION# - 'priv_test_user3'@'%' : ALL PRIVILEGES
# ROUTINE `util_test`.`p1`:# - 'joe'@'user' : ALL PRIVILEGES# - 'joe_wildcard'@'%' : ALL PRIVILEGES# - 'priv_test_user'@'%' : EXECUTE, GRANT OPTION# - 'priv_test_user2'@'%' : EXECUTE# - 'priv_test_user3'@'%' : ALL PRIVILEGES, GRANT OPTION#...done.
Show the grantees and respective SQL grant statements over a list of objects.
shell> mysqlgrants --server=user:pass@localhost:3310 \ --show=raw util_test util_test.t3 util_test.t2 \ util_test.t1 util_test.p1 util_test.f1
# DATABASE `util_test`:# - For 'joe'@'user'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe'@'user'# - For 'joe_wildcard'@'%'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe_wildcard'@'%'
EXAMPLES
154
# - For 'priv_test_user'@'%'GRANT EXECUTE, TRIGGER ON `util_test`.* TO 'priv_test_user'@'%' WITH GRANT OPTIONGRANT SELECT, UPDATE ON *.* TO 'priv_test_user'@'%'# - For 'priv_test_user2'@'%'GRANT SELECT, UPDATE, SHUTDOWN, EXECUTE ON *.* TO 'priv_test_user2'@'%'# - For 'priv_test_user3'@'%'GRANT DROP, EXECUTE, TRIGGER ON *.* TO 'priv_test_user3'@'%'GRANT UPDATE, DELETE, ALTER ROUTINE ON `util_test`.* TO 'priv_test_user3'@'%'
# TABLE `util_test`.`t1`:# - For 'joe'@'user'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe'@'user'# - For 'joe_wildcard'@'%'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe_wildcard'@'%'# - For 'priv_test_user'@'%'GRANT EXECUTE, TRIGGER ON `util_test`.* TO 'priv_test_user'@'%' WITH GRANT OPTIONGRANT SELECT, UPDATE ON *.* TO 'priv_test_user'@'%'# - For 'priv_test_user2'@'%'GRANT INSERT, DELETE, CREATE, DROP, REFERENCES, INDEX, ALTER, CREATE VIEW, SHOW VIEW, TRIGGER ON `util_test`.`t1` TO 'priv_test_user2'@'%' WITH GRANT OPTIONGRANT SELECT, UPDATE, SHUTDOWN, EXECUTE ON *.* TO 'priv_test_user2'@'%'# - For 'priv_test_user3'@'%'GRANT DROP, EXECUTE, TRIGGER ON *.* TO 'priv_test_user3'@'%'GRANT UPDATE, DELETE, ALTER ROUTINE ON `util_test`.* TO 'priv_test_user3'@'%'
# TABLE `util_test`.`t2`:# - For 'joe'@'user'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe'@'user'# - For 'joe_wildcard'@'%'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe_wildcard'@'%'# - For 'priv_test_user'@'%'GRANT EXECUTE, TRIGGER ON `util_test`.* TO 'priv_test_user'@'%' WITH GRANT OPTIONGRANT SELECT, UPDATE ON *.* TO 'priv_test_user'@'%'# - For 'priv_test_user2'@'%'GRANT SELECT, UPDATE, SHUTDOWN, EXECUTE ON *.* TO 'priv_test_user2'@'%'# - For 'priv_test_user3'@'%'GRANT DROP, EXECUTE, TRIGGER ON *.* TO 'priv_test_user3'@'%'GRANT UPDATE, DELETE, ALTER ROUTINE ON `util_test`.* TO 'priv_test_user3'@'%'
# TABLE `util_test`.`t3`:# - For 'joe'@'user'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe'@'user'# - For 'joe_wildcard'@'%'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe_wildcard'@'%'# - For 'priv_test_user'@'%'GRANT EXECUTE, TRIGGER ON `util_test`.* TO 'priv_test_user'@'%' WITH GRANT OPTIONGRANT SELECT, UPDATE ON *.* TO 'priv_test_user'@'%'# - For 'priv_test_user2'@'%'GRANT SELECT, UPDATE, SHUTDOWN, EXECUTE ON *.* TO 'priv_test_user2'@'%'# - For 'priv_test_user3'@'%'GRANT DROP, EXECUTE, TRIGGER ON *.* TO 'priv_test_user3'@'%'GRANT SELECT ON `util_test`.`t3` TO 'priv_test_user3'@'%'GRANT UPDATE, DELETE, ALTER ROUTINE ON `util_test`.* TO 'priv_test_user3'@'%'
# ROUTINE `util_test`.`f1`:# - For 'joe'@'user'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe'@'user'# - For 'joe_wildcard'@'%'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe_wildcard'@'%'# - For 'priv_test_user'@'%'GRANT EXECUTE, TRIGGER ON `util_test`.* TO 'priv_test_user'@'%' WITH GRANT OPTION# - For 'priv_test_user2'@'%'GRANT ALTER ROUTINE ON FUNCTION `util_test`.`f1` TO 'priv_test_user2'@'%' WITH GRANT OPTIONGRANT SELECT, UPDATE, SHUTDOWN, EXECUTE ON *.* TO 'priv_test_user2'@'%'# - For 'priv_test_user3'@'%'GRANT DROP, EXECUTE, TRIGGER ON *.* TO 'priv_test_user3'@'%'GRANT UPDATE, DELETE, ALTER ROUTINE ON `util_test`.* TO 'priv_test_user3'@'%'
EXAMPLES
155
# ROUTINE `util_test`.`p1`:# - For 'joe'@'user'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe'@'user'# - For 'joe_wildcard'@'%'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe_wildcard'@'%'# - For 'priv_test_user'@'%'GRANT EXECUTE, TRIGGER ON `util_test`.* TO 'priv_test_user'@'%' WITH GRANT OPTION# - For 'priv_test_user2'@'%'GRANT SELECT, UPDATE, SHUTDOWN, EXECUTE ON *.* TO 'priv_test_user2'@'%'# - For 'priv_test_user3'@'%'GRANT ALTER ROUTINE ON PROCEDURE `util_test`.`p1` TO 'priv_test_user3'@'%' WITH GRANT OPTIONGRANT DROP, EXECUTE, TRIGGER ON *.* TO 'priv_test_user3'@'%'GRANT UPDATE, DELETE, ALTER ROUTINE ON `util_test`.* TO 'priv_test_user3'@'%'#...done.
Show only the users that have all privileges over a set of specified objects and the respective SQL grantstatements. Notice that while some grantees do not explicitly have the ALL PRIVILEGES grant overa given object, they are still shown as a result of having the set of privileges that is equivalent to ALLPRIVILEGES for the given object type.
shell> mysqlgrants --server=user:pass@localhost:3310 \ --show=raw --privileges=ALL util_test util_test.t3 util_test.t2 \ util_test.t1 util_test.p1 util_test.f1
# DATABASE `util_test`:# - For 'joe'@'user'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe'@'user'# - For 'joe_wildcard'@'%'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe_wildcard'@'%'
# TABLE `util_test`.`t1`:# - For 'joe'@'user'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe'@'user'# - For 'joe_wildcard'@'%'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe_wildcard'@'%'# - For 'priv_test_user2'@'%'GRANT INSERT, DELETE, CREATE, DROP, REFERENCES, INDEX, ALTER, CREATE VIEW, SHOW VIEW, TRIGGER ON `util_test`.`t1` TO 'priv_test_user2'@'%' WITH GRANT OPTIONGRANT SELECT, UPDATE, SHUTDOWN, EXECUTE ON *.* TO 'priv_test_user2'@'%'
# TABLE `util_test`.`t2`:# - For 'joe'@'user'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe'@'user'# - For 'joe_wildcard'@'%'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe_wildcard'@'%'
# TABLE `util_test`.`t3`:# - For 'joe'@'user'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe'@'user'# - For 'joe_wildcard'@'%'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe_wildcard'@'%'
# ROUTINE `util_test`.`f1`:# - For 'joe'@'user'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe'@'user'# - For 'joe_wildcard'@'%'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe_wildcard'@'%'# - For 'priv_test_user2'@'%'GRANT ALTER ROUTINE ON FUNCTION `util_test`.`f1` TO 'priv_test_user2'@'%' WITH GRANT OPTIONGRANT SELECT, UPDATE, SHUTDOWN, EXECUTE ON *.* TO 'priv_test_user2'@'%'# - For 'priv_test_user3'@'%'GRANT DROP, EXECUTE, TRIGGER ON *.* TO 'priv_test_user3'@'%'GRANT UPDATE, DELETE, ALTER ROUTINE ON `util_test`.* TO 'priv_test_user3'@'%'
# ROUTINE `util_test`.`p1`:
EXAMPLES
156
# - For 'joe'@'user'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe'@'user'# - For 'joe_wildcard'@'%'GRANT ALL PRIVILEGES ON `util_test`.* TO 'joe_wildcard'@'%'# - For 'priv_test_user3'@'%'GRANT ALTER ROUTINE ON PROCEDURE `util_test`.`p1` TO 'priv_test_user3'@'%' WITH GRANT OPTIONGRANT DROP, EXECUTE, TRIGGER ON *.* TO 'priv_test_user3'@'%'GRANT UPDATE, DELETE, ALTER ROUTINE ON `util_test`.* TO 'priv_test_user3'@'%'#...done.
Show just the list of users with some specific privileges over a set of objects.
shell> mysqlgrants --server=user:pass@localhost:3310 \ --show=users --privileges=SELECT,INSERT,EXECUTE \ util_test util_test.t3 util_test.t2 util_test.t1 util_test.p1 util_test.f1
# WARNING: EXECUTE does not apply to tables and will be ignored for: `util_test`.`t2`, `util_test`.`t3` and `util_test`.`t1`.# WARNING: INSERT and SELECT do not apply to routines and will be ignored for: `util_test`.`f1` and `util_test`.`p1`.
# DATABASE `util_test`:
# TABLE `util_test`.`t1`:# - 'priv_test_user2'@'%'
# TABLE `util_test`.`t2`:
# TABLE `util_test`.`t3`:
# ROUTINE `util_test`.`f1`:# - 'priv_test_user'@'%', 'priv_test_user2'@'%'
# ROUTINE `util_test`.`p1`:# - 'priv_test_user'@'%', 'priv_test_user2'@'%', 'priv_test_user3'@'%'#...done.
The following command shows all of the grants for users that have access to any object in the db1database, by passing in the --inherit-level option:
shell> mysqlgrants --server=localhost1 db1.* --inherit-level=object --show raw# Source on localhost: ... connected.
# TABLE `db1`.`tbl1`:# - For 'joe'@'host1'GRANT INSERT ON `db1`.`tbl1` TO 'joe'@'host1'#...done.
The following command shows all of the grants for users that have access to the db1 database, by passingin the --inherit-level option:
shell> mysqlgrants --server=localhost1 db1.* --inherit-level=database --show-raw# Source on localhost: ... connected.
# TABLE `db1`.`tbl1`:# - For 'joe'@'host1'GRANT INSERT ON `db1`.`tbl1` TO 'joe'@'host1'# - For 'sally'@'host2'GRANT SELECT ON `db1`.* TO 'sally'@'host2'#...done.
PRIVILEGES REQUIRED
157
PRIVILEGES REQUIRED
This utility requires the SELECT privilege on the mysql database.
5.15 mysqlindexcheck — Identify Potentially Redundant TableIndexes
This utility reads the indexes for one or more tables and identifies duplicate and potentially redundantindexes.
To check all tables in a database, only specify the database name. To check a specific table, name thetable in db.table format. It is possible to mix database and table names.
You can scan tables in any database except the internal databases mysql, INFORMATION_SCHEMA,and performance_schema.
Depending on the index type, the utility applies the following rules to compare indexes (designated asidx_a and idx_b):
• BTREE
idx_b is redundant to idx_a if and only if all the columns from idx_b are a prefix of idx_a. Order anduniqueness count.
• HASH
idx_a and idx_b are redundant if they are duplicates, i.e. if and only if they contain the same columnsin the same order.
• SPATIAL
idx_a and idx_b are duplicates if and only if they contain the same column (only one column ispermitted).
• FULLTEXT
idx_b is redundant to idx_a if and only if all columns in idx_b are included in idx_a. Order does notcount.
To see DROP statements drop redundant indexes, specify the --show-drops option. To examine theexisting indexes, use the --verbose option, which prints the equivalent CREATE INDEX (or ALTERTABLE) for primary keys.
To display the best or worst non-primary key indexes for each table, use the --best or --worst option.This causes the output to show the best or worst indexes from tables with 10 or more rows. By default,each option shows five indexes. To override that, provide an integer value for the option.
To change the format of the index lists displayed for the --show-indexes, --best, and --worstoptions, use one of the following values with the --format option:
• grid (default)
Display output in grid or table format like that of the mysql client command-line tool.
• csv
OPTIONS
158
Display output in comma-separated values format.
• tab
Display output in tab-separated format.
• sql
Print SQL statements rather than a list.
• vertical
Display output in single-column format like that of the \G command for the mysql client command-linetool.
Note
The --best and --worst lists cannot be printed as SQL statements.
OPTIONS
mysqlindexcheck accepts the following command-line options:
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --best[=N]
If --stats is given, limit index statistics to the best N indexes. The default value of N is 5 if omitted.
• --format=index_format, -findex_format
Specify the index list display format for output produced by --stats. Permitted format values are grid,csv, tab, sql, and vertical. The default is grid.
• --report-indexes, -r
Reports if a table has neither UNIQUE indexes nor a PRIMARY key.
• --server=source
Connection information for the server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
NOTES
159
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --show-drops, -d
Display DROP statements for dropping indexes.
• --show-indexes, -i
Display indexes for each table.
• --skip, -s
Skip tables that do not exist.
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --stats
Show index performance statistics.
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
• --worst[=N]
If --stats is also passed in, limit index statistics to the worst N indexes. The default value of N is 5, ifomitted.
NOTES
You must provide connection parameters (user, host, password, and so forth) for an account that has theappropriate privileges to read all objects accessed during the operation.
For the --format option, the permitted values are not case-sensitive. In addition, values may be specifiedas any unambiguous prefix of a valid value. For example, --format=g specifies the grid format. An erroroccurs if a prefix matches more than one valid value.
EXAMPLES
160
The path to the MySQL client tools should be included in the PATH environment variable in order to use theauthentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
EXAMPLES
To check all tables in the employees database on the local server to see the possible redundant andduplicate indexes, use this command:
shell> mysqlindexcheck --server=root@localhost employees# Source on localhost: ... connected.# The following indexes are duplicates or redundant \ for table employees.dept_emp:#CREATE INDEX emp_no ON employees.dept_emp (emp_no) USING BTREE# may be redundant or duplicate of:ALTER TABLE employees.dept_emp ADD PRIMARY KEY (emp_no, dept_no)# The following indexes are duplicates or redundant \ for table employees.dept_manager:#CREATE INDEX emp_no ON employees.dept_manager (emp_no) USING BTREE# may be redundant or duplicate of:ALTER TABLE employees.dept_manager ADD PRIMARY KEY (emp_no, dept_no)# The following indexes are duplicates or redundant \ for table employees.salaries:#CREATE INDEX emp_no ON employees.salaries (emp_no) USING BTREE# may be redundant or duplicate of:ALTER TABLE employees.salaries ADD PRIMARY KEY (emp_no, from_date)# The following indexes are duplicates or redundant \ for table employees.titles:#CREATE INDEX emp_no ON employees.titles (emp_no) USING BTREE# may be redundant or duplicate of:ALTER TABLE employees.titles ADD PRIMARY KEY (emp_no, title, from_date)
PERMISSIONS REQUIRED
Regarding the privileges needed to run this utility, the user needs SELECT privilege on the mysql databaseas well as for the databases which tables are being checked.
5.16 mysqlmetagrep — Search Database Object DefinitionsThis utility searches for objects matching a given pattern on all the servers specified using instances of the--server option. It produces output that displays the matching objects. By default, the first non-optionargument is taken to be the pattern unless the --pattern option is given. If the --pattern option isgiven, then all non-option arguments are treated as connection specifications.
Internally, the utility generates an SQL statement for searching the necessary tables in theINFORMATION_SCHEMA database on the designated servers, and then executes it before collecting theresult and printing it as a table. Use the --sql option to have mysqlmetagrep display the statement,rather than execute it. This can be useful if you want to feed the output of the statement to anotherapplication, such as the mysql client command-line tool.
The MySQL server supports two forms of patterns when matching strings: SQL Simple Patterns (used withthe LIKE operator) and POSIX Regular Expressions (used with the REGEXP operator).
By default, the utility uses the LIKE operator to match the name (and optionally, the body) of objects. Touse the REGEXP operator instead, use the --regexp option.
SQL Simple Patterns
161
Note
Because the REGEXP operator does substring searching, it is necessary to anchorthe expression to the beginning of the string if you want to match the beginning ofthe string.
To specify how to display output, use one of the following values with the --format option:
• grid (default)
Display output in grid or table format like that of the mysql client command-line tool.
• csv
Display output in comma-separated values format.
• tab
Display output in tab-separated format.
• vertical
Display output in single-column format like that of the \G command for the mysql client command-linetool.
SQL Simple Patterns
The simple patterns defined by the SQL standard consist of a string of characters with two characters thathave special meaning: % (percent) matches zero or more characters, and _ (underscore) matches exactlyone character.
For example:
• 'john%'
Match any string that starts with 'john'.
• '%doe%'
Match any string containing the word 'doe'.
• '%_'
Match any string consisting of one or more characters.
POSIX Regular Expressions
POSIX regular expressions are more powerful than the simple patterns defined in the SQL standard. Aregular expression is a string of characters, optionally containing characters with special meaning.
Documenting these regular expressions goes beyond the scope of this manual, but the full syntax isdescribed in the MySQL manual and other locations, such as executing 'man regex' in your terminal.
• .
Match any character.
• ^
Match the beginning of a string.
OPTIONS
162
• $
Match the end of a string.
• [axy]
Match a, x, or y.
• [a-f]
Match any character in the range a to f (that is, a, b, c, d, e, or f).
• [^axy]
Match any character except a, x, or y.
• a*
Match a sequence of zero or more a.
• a+
Match a sequence of one or more a.
• a?
Match zero or one a.
• ab|cd
Match ab or cd.
• a{5}
Match five instances of a.
• a{2,5}
Match from two to five instances of a.
• (abc)+
Match one or more repetitions of abc.
OPTIONS
mysqlmetagrep accepts the following command-line options:
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --body, -b
Search the body of stored programs (procedures, functions, triggers, and events). The default is tomatch only the name.
OPTIONS
163
• --character-set=charset
Sets the client character set. The default is retrieved from the server variablecharacter_set_client.
• --database=pattern
Look only in databases matching this pattern.
• --format=format, -fformat
Specify the output display format. Permitted format values are grid (default), csv, tab, and vertical.
• --object-types=types, --search-objects=types
Search only the object types named in types, which is a comma-separated list of one or more of thevalues database, trigger, user, routine, column, table, partition, event and view.
The default is to search in objects of all types.
• --pattern=pattern, -e=pattern
The pattern to use when matching. This is required when the first non-option argument looks like aconnection specification rather than a pattern.
If the --pattern option is given, the first non-option argument is treated as a connection specifier, notas a pattern.
• --regexp, --basic-regexp, -G
Perform pattern matches using the REGEXP operator. The default is to use LIKE for matching. Thisaffects the --database and --pattern options.
• --server=source
Connection information for a server. Use this option multiple times to search multiple servers.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --sql, --print-sql, -p
Print rather than executing the SQL code that would be executed to find all matching objects. This canbe useful to save the statement for later execution or to use it as input for other programs.
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
NOTES
164
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --version
Display version information and exit.
NOTES
For the --format option, the permitted values are not case-sensitive. In addition, values may be specifiedas any unambiguous prefix of a valid value. For example, --format=g specifies the grid format. An erroroccurs if a prefix matches more than one valid value.
The path to the MySQL client tools should be included in the PATH environment variable in order to use theauthentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
EXAMPLES
Find all objects with a name that matches the pattern 't_' (the letter t followed by any single character):
shell> mysqlmetagrep --pattern="t_" --server=john@localhost+------------------------+--------------+--------------+-----------+| Connection | Object Type | Object Name | Database |+------------------------+--------------+--------------+-----------+| john:*@localhost:3306 | TABLE | t1 | test || john:*@localhost:3306 | TABLE | t2 | test || john:*@localhost:3306 | TABLE | tm | test |+------------------------+--------------+--------------+-----------+
To find all object that contain 't2' in the name or the body (for routines, triggers, and events):
shell> mysqlmetagrep -b --pattern="%t2%" --server=john@localhost:3306+------------------------+--------------+--------------+-----------+| Connection | Object Type | Object Name | Database |+------------------------+--------------+--------------+-----------+| john:*@localhost:3306 | TRIGGER | tr_foo | test || john:*@localhost:3306 | TABLE | t2 | test |+------------------------+--------------+--------------+-----------+
In the preceding output, the trigger name does not match the pattern, but is displayed because its bodydoes.
This is the same as the previous example, but using the REGEXP operator. Note that in the pattern it is notnecessary to add wildcards before or after t2:
shell> mysqlmetagrep -Gb --pattern="t2" --server=john@localhost
PERMISSIONS REQUIRED
165
+------------------------+--------------+--------------+-----------+| Connection | Object Type | Object Name | Database |+------------------------+--------------+--------------+-----------+| root:*@localhost:3306 | TRIGGER | tr_foo | test || root:*@localhost:3306 | TABLE | t2 | test |+------------------------+--------------+--------------+-----------+
PERMISSIONS REQUIRED
The user must have the SELECT privilege on the mysql database.
5.17 mysqlprocgrep — Search Server Process ListsThis utility scans the process lists for the servers specified using instances of the --server option andselects those that match the conditions specified using the --age and --match-xxx options. For aprocess to match, all conditions given must match. The utility then either prints the selected processes (thedefault) or executes certain actions on them.
If no --age or --match-xxx options are given, the utility selects all processes.
The --match-xxx options correspond to the columns in the INFORMATION_SCHEMA.PROCESSLISTtable. For example, --match-command specifies a matching condition for PROCESSLIST.COMMANDcolumn values. There is no --match-time option. To specify a condition based on process time, use --age.
Processes that can be seen and killed are subject to whether the account used to connect to the serverhas the PROCESS and SUPER privileges. Without PROCESS, the account cannot see processesbelonging to other accounts Without SUPER, the account cannot kill processes belonging to otheraccounts.
When the --kill-query or --kill-connection option is used, the utility displays those rows from theSHOW PROCESSLIST that match the query and are killed. This behavior exists as of MySQL Utilities 1.6.0.
To specify how to display output, use one of the following values with the --format option:
• grid (default)
Display output in grid or table format like that of the mysql client command-line tool.
• csv
Display output in comma-separated values format.
• tab
Display output in tab-separated format.
• vertical
Display output in single-column format like that of the \G command for the mysql client command-linetool.
Options
mysqlprocgrep accepts the following command-line options:
• --help
Display a help message and exit.
Options
166
• --license
Display license information and exit.
• --age=time
Select only processes that have been in the current state more than a given time. The time value canbe specified in two formats: either using the hh:mm:ss format, with hours and minutes optional, or as asequence of numbers with a suffix giving the period size.
The permitted suffixes are s (second), m (minute), h (hour), d (day), and w (week). For example, 4h15mrepresents 4 hours and 15 minutes.
For both formats, the specification can optionally be preceded by + or -, where + means older than thegiven time, and - means younger than the given time.
• --character-set=charset
Sets the client character set. The default is retrieved from the server variablecharacter_set_client.
• --format=format, -fformat
Specify the output display format. Permitted format values are grid (default), csv, tab, and vertical.
• --kill-connection
Kill the connection for all matching processes (like the KILL CONNECTION statement).
• --kill-query
Kill the query for all matching processes (like the KILL QUERY statement).
• --match-command=pattern
Match all processes where the Command field matches the pattern.
• --match-db=pattern
Match all processes where the Db field matches the pattern.
• --match-host=pattern
Match all processes where the Host field matches the pattern.
• --match-id=pattern
Match all processes where the ID field matches the pattern.
• --match-info=pattern
Match all processes where the Info field matches the pattern.
• --match-state=pattern
Match all processes where the State field matches the pattern.
• --match-user=pattern
Match all processes where the User field matches the pattern.
Options
167
Print information about the matching processes. This is the default if no --kill-connection or --kill-query option is given. If a kill option is given, --print prints information about the processesbefore killing them.
• --regexp, --basic-regexp, -G
Perform pattern matches using the REGEXP operator. The default is to use LIKE for matching. Thisaffects the --match-xxx options.
• --server=source
Connection information for a server. Use this option multiple times to search multiple servers.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --sql, --print-sql, -Q
Instead of displaying the selected processes, emit the SELECT statement that retrieves informationabout them. If the --kill-connection or --kill-query option is given, the utility generates astored procedure named kill_processes() for killing the queries rather than a SELECT statement.
• --sql-body
Like --sql, but produces the output as the body of a stored procedure without the CREATEPROCEDURE part of the definition. This could be used, for example, to generate an event for the serverEvent Manager.
When used with a kill option, code for killing the matching queries is generated. Note that it is notpossible to execute the emitted code unless it is put in a stored routine, event, or trigger. For example,the following code could be generated to kill all idle connections for user www-data:
shell> mysqlprocgrep --kill-connection --sql-body \ --match-user=www-data --match-state=sleep
DECLARE kill_done INT;DECLARE kill_cursor CURSOR FOR SELECT Id, User, Host, Db, Command, Time, State, Info FROM INFORMATION_SCHEMA.PROCESSLIST WHERE user LIKE 'www-data' AND State LIKE 'sleep'OPEN kill_cursor;
NOTES
168
BEGIN DECLARE id BIGINT; DECLARE EXIT HANDLER FOR NOT FOUND SET kill_done = 1; kill_loop: LOOP FETCH kill_cursor INTO id; KILL CONNECTION id; END LOOP kill_loop;END;CLOSE kill_cursor;
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
NOTES
For the --format option, the permitted values are not case-sensitive. In addition, values may be specifiedas any unambiguous prefix of a valid value. For example, --format=g specifies the grid format. An erroroccurs if a prefix matches more than one valid value.
The path to the MySQL client tools should be included in the PATH environment variable in order to use theauthentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
EXAMPLES
For each example, assume that the root user on localhost has sufficient privileges to kill queries andconnections.
Kill all connections created by user john:
shell> mysqlprocgrep --server=root@localhost \ --match-user=john --kill-connection --format=CSV# The following KILL commands were executed:Id,User,Host,db,Command,Time,State,Info4,john,localhost:50706,mysql,Sleep,5,,
PERMISSIONS REQUIRED
169
Kill all connections that have been idle for more than 1 hour:
shell> mysqlprocgrep --server=root@localhost \ --match-command=sleep --age=1h --kill-connection
PERMISSIONS REQUIRED
The user must have the SELECT privilege on the mysql database.
5.18 mysqlreplicate — Set Up and Start Replication Between TwoServers
This utility permits an administrator to setup and start replication from one server (the master) to another(the slave). The user provides login information for the slave and connection information for connecting tothe master. It is also possible to specify a database to be used to test replication.
The utility reports conditions where the storage engines on the master and the slave differ for olderversions of the server. It also reports a warning if the InnoDB storage engine type (plugin verus built-in)differs on the master and slave. For InnoDB to be the same, both servers must be running the same "type"of InnoDB (built-in or the InnoDB Plugin), and InnoDB on both servers must have the same major andminor version numbers and enabled state.
By default, the utility issues warnings for mismatches between the sets of storage engines, the defaultstorage engine, and the InnoDB storage engine. To produce errors instead, use the --pedantic option,which requires storage engines to be the same on the master and slave.
The -vv option displays any discrepancies between the storage engines and InnoDB values, with orwithout the --pedantic option.
Replication can be started using one of the following strategies.
• Start from the current position (default)
Start replication from the current master binary log file and position. The utility uses the SHOW MASTERSTATUS statement to retrieve this information.
• Start from the beginning
Start replication from the first event recorded in the master binary log. To do this, use the --start-from-beginning option.
• Start from a binary log file
Start replication from the first event in a specific master binary log file. To do this, use the --master-log-file option.
• Start from a specific event
Start replication from specific event coordinates (specific binary log file and position). To do this, use the--master-log-file and --master-log-pos options.
OPTIONS
mysqlreplicate accepts the following command-line options:
OPTIONS
170
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --master=master
Connection information for the master server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• login-path (.mylogin.cnf) : login-path[:port][:socket]
• Configuration file : configuration-file-path[:section]
• Command-line : user[:passwd]@host[:port][:socket]
• --master-log-file=master_log_file
Begin replication from the beginning of this master log file.
• --master-log-pos=master_log_pos
Begin replication from this position in the master log file. This option is not valid unless --master-log-file is given.
• --pedantic, -p
Fail if both servers do not have the same set of storage engines, the same default storage engine, andthe same InnoDB storage engine.
• --rpl-user=replication_user
The user and password for the replication user, in the format: user[:password] or login-path.
• --slave=slave
Connection information for the slave server. You may specify only one slave for this option.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
NOTES
171
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --start-from-beginning, -b
Start replication at the beginning of events logged in the master binary log. This option is not valid unlessboth --master-log-file and --master-log-pos are given.
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --test-db=test_database
The database name to use for testing the replication setup. If this option is not given, no testing is done,only error checking.
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
NOTES
The login user for the master server must have the appropriate permissions to grant access to alldatabases, and have the ability to create user accounts. For example, the user account used to connect tothe master must have the WITH GRANT OPTION privilege.
The server IDs on the master and slave must be nonzero and unique. The utility reports an error if theserver ID is 0 on either server or the same on the master and slave. Set these values before starting thisutility.
Mixing IP and hostnames is not recommended. The replication-specific utilities attempt to comparehostnames and IP addresses as aliases for checking slave connectivity to the master. However, if your
EXAMPLES
172
installation does not support reverse name lookup, the comparison could fail. Without the ability to do areverse name lookup, the replication utilities could report a false negative that the slave is (not) connectedto the master.
For example, if you setup replication using "MASTER_HOST=ubuntu.net" on the slave and later connectto the slave with mysqlrplcheck and have the master specified as "--master=198.51.100.6" using thevalid IP address for "ubuntu.net", you must have the ability to do a reverse name lookup to compare the IP(198.51.100.6) and the hostname (ubuntu.net) to determine if they are the same machine.
The path to the MySQL client tools should be included in the PATH environment variable in order to use theauthentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
EXAMPLES
To set up replication between two MySQL instances running on different ports of the same host using thedefault settings, use this command:
shell> mysqlreplicate --master=root@localhost:3306 \ --slave=root@localhost:3307 --rpl-user=rpl:rpl# master on localhost: ... connected.# slave on localhost: ... connected.# Checking for binary logging on master...# Setting up replication...# ...done.
The following command uses --pedantic to ensure that replication between the master and slave issuccessful if and only if both servers have the same storage engines available, the same default storageengine, and the same InnoDB storage engine:
shell> mysqlreplicate --master=root@localhost:3306 \ --slave=root@localhost:3307 --rpl-user=rpl:rpl -vv --pedantic# master on localhost: ... connected.# slave on localhost: ... connected.# master id = 2# slave id = 99# Checking InnoDB statistics for type and version conflicts.# Checking storage engines...# Checking for binary logging on master...# Setting up replication...# Flushing tables on master with read lock...# Connecting slave to master...# CHANGE MASTER TO MASTER_HOST = [...omitted...]# Starting slave...# status: Waiting for master to send event# error: 0:# Unlocking tables on master...# ...done.
The following command starts replication from the current position of the master (which is the default):
shell> mysqlreplicate --master=root@localhost:3306 \ --slave=root@localhost:3307 --rpl-user=rpl:rpl # master on localhost: ... connected. # slave on localhost: ... connected. # Checking for binary logging on master... # Setting up replication... # ...done.
RECOMMENDATIONS
173
The following command starts replication from the beginning of recorded events on the master:
shell> mysqlreplicate --master=root@localhost:3306 \ --slave=root@localhost:3307 --rpl-user=rpl:rpl \ --start-from-beginning # master on localhost: ... connected. # slave on localhost: ... connected. # Checking for binary logging on master... # Setting up replication... # ...done.
The following command starts replication from the beginning of a specific master binary log file:
shell> mysqlreplicate --master=root@localhost:3306 \ --slave=root@localhost:3307 --rpl-user=rpl:rpl \ --master-log-file=my_log.000003 # master on localhost: ... connected. # slave on localhost: ... connected. # Checking for binary logging on master... # Setting up replication... # ...done.
The following command starts replication from specific master binary log coordinates (specific log file andposition):
shell> mysqlreplicate --master=root@localhost:3306 \ --slave=root@localhost:3307 --rpl-user=rpl:rpl \ --master-log-file=my_log.000001 --master-log-pos=96 # master on localhost: ... connected. # slave on localhost: ... connected. # Checking for binary logging on master... # Setting up replication... # ...done.
RECOMMENDATIONS
You should set read_only=1 in the my.cnf file for the slave to ensure that no accidental data changes,such as INSERT, DELETE, UPDATE, and so forth, are permitted on the slave other than those producedby events read from the master.
Use the --pedantic and -vv options for setting up replication on production servers to avoid possibleproblems with differing storage engines.
PERMISSIONS REQUIRED
The users on the master need the following privileges: SELECT and INSERT privileges on mysqldatabase, REPLICATION SLAVE, REPLICATION CLIENT and GRANT OPTION. The slave users needthe SUPER privilege. The repl user, used as the argument for the --rpl-user option, is either createdautomatically or if it exists, it needs the REPLICATION SLAVE privilege.
5.19 mysqlrplms — Set Up and Start Replication from a Slave toMultiple Masters
This utility permits a user to start replication from multiple master servers (also called multi-sourcereplication) to a single slave. The user provides login information for the slave and each of the masters.
OPTIONS
174
The utility reports conditions where the storage engines on the masters and the slave differ. It also reportsa warning if the InnoDB storage engine differs on the master and slave. For InnoDB to be the same, bothservers must be running the same "type" of InnoDB (built-in or the InnoDB Plugin), and InnoDB on bothservers must have the same major and minor version numbers and enabled state. By default, the utilityissues warnings for mismatches between the sets of storage engines, the default storage engine, and theInnoDB storage engine.
The -vv option displays any discrepancies between the storage engines and InnoDB values.
A round-robin scheduling is used to setup replication among the masters and slave.
The mysqlrplms utility follows these assumptions:
• All servers must have GTIDs enabled.
• There are no conflicts between transactions from different masters. For example, there are no updates tothe same object from multiple masters.
• Replication is asynchronous.
OPTIONS
mysqlrplms accepts the following command-line options:
• --daemon=command
Run as a daemon. The command can be start (start daemon), stop (stop daemon), restart (stopthen start the daemon) or nodetach (start but do not detach the process). This option is only availablefor POSIX systems.
• --format=format, -f format
Display the replication health output in either grid (default), tab, csv, or vertical format.
• --help
Display a help message and exit.
• --interval=seconds, -i seconds
Interval in seconds for reporting health. Default = 15 seconds. Minimum is 5 seconds.
• --license
Display license information and exit.
• --log=log_file
Specify a log file to use for logging messages
• --log-age=days
Specify maximum age of log entries in days. Entries older than this are purged on startup. Default = 7days.
• --masters=master connections
Connection information for master servers. List multiple masters in comma-separated list.
OPTIONS
175
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --report-values=report_values
Report values used in mysqlrplms. It can be health, gtid or uuid. Multiple values can be used separatedby commas.
• health
Display the replication health of the topology.
• gtid
Display the master's list of executed GTIDs, contents of the GTID variables;@@GLOBAL.GTID_EXECUTED, @@GLOBAL.GTID_PURGED and @@GLOBAL.GTID_OWNED.
• uuid
Display universally unique identifiers (UUIDs) for all servers.
Default = health.
• --rpl-user=replication_user
The user and password for the replication user, in the format: user[:password] or login-path.
• --slave=slave
Connection information for the slave server. You may specify only one slave for this option.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --ssl-ca
NOTES
176
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --start-from-beginning, -b
Start replication at the beginning of events logged in the master binary log.
• --switchover-interval=seconds
Interval in seconds for switching masters. Default = 60 seconds. Minimum is 30 seconds.
• --pidfile=pidfile
Pidfile for running mysqlrplms as a daemon. This file contains the PID (process identifier), that uniquelyidentify a process. It is needed to identify and control the process forked by mysqlrplms.
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
NOTES
The login user for the master servers must have the appropriate permissions to grant access to alldatabases, and have the ability to create user accounts. For example, the user accounts used to connectto each of the masters must have the WITH GRANT OPTION privilege.
The server IDs on the masters and slave must be nonzero and unique. The utility reports an error if theserver ID is 0 on either server or the same on the masters and slave. Set these values before starting thisutility.
Mixing IP and hostnames is not recommended. The replication-specific utilities attempts to comparehostnames and IP addresses as aliases for checking slave connectivity to the master. However, if yourinstallation does not support reverse name lookup, the comparison could fail. Without the ability to do areverse name lookup, the replication utilities could report a false negative that the slave is (not) connectedto the master.
The path to the MySQL client tools should be included in the PATH environment variable in order to use theauthentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
EXAMPLES
177
Due to a known server issue, there are some limitations with the use of temporary tables with multi-sourcereplication. In order to avoid problems, we recommend the execution of all statements for a temporarytable in a single transaction. See Replication and Temporary Tables, for more information.
EXAMPLES
To set up multi-source replication among two masters and a slave, running on different ports of the samehost using the default settings, use this command:
shell> mysqlrplms --slave=root:root@localhost:3306 \ --masters=root:root@localhost:3307,root:root@localhost:3308# Starting multi-source replication...# Press CTRL+C to quit.# Switching to master 'localhost:3307'.# master on localhost: ... connected.# slave on localhost: ... connected.## Current Master Information:+-------------------+-----------+---------------+-------------------+| Binary Log File | Position | Binlog_Do_DB | Binlog_Ignore_DB |+-------------------+-----------+---------------+-------------------+| clone-bin.000001 | 594 | N/A | N/A |+-------------------+-----------+---------------+-------------------+# GTID Executed Set: 00a4e027-a83a-11e3-8bd6-28d244017f26:1-2## Health Status:+------------+-------+---------+--------+------------+---------+| host | port | role | state | gtid_mode | health |+------------+-------+---------+--------+------------+---------+| localhost | 3307 | MASTER | UP | ON | OK || localhost | 3306 | SLAVE | UP | ON | OK || localhost | 3308 | MASTER | UP | ON | OK |+------------+-------+---------+--------+------------+---------+#(...)
The following command uses --report-values to report health, GTID and UUID status:
shell> mysqlrplms --slave=root:root@localhost:3306 \ --masters=root:root@localhost:3307,root:root@localhost:3308\n --report-values=health,gtid,uuid# Starting multi-source replication...# Press CTRL+C to quit.# Switching to master 'localhost:3307'.# master on localhost: ... connected.# slave on localhost: ... connected.## Current Master Information:+-------------------+-----------+---------------+-------------------+| Binary Log File | Position | Binlog_Do_DB | Binlog_Ignore_DB |+-------------------+-----------+---------------+-------------------+| clone-bin.000001 | 594 | N/A | N/A |+-------------------+-----------+---------------+-------------------+# GTID Executed Set: 00a4e027-a83a-11e3-8bd6-28d244017f26:1-2## Health Status:+------------+-------+---------+--------+------------+---------+| host | port | role | state | gtid_mode | health |+------------+-------+---------+--------+------------+---------+| localhost | 3307 | MASTER | UP | ON | OK || localhost | 3306 | SLAVE | UP | ON | OK || localhost | 3308 | MASTER | UP | ON | OK |+------------+-------+---------+--------+------------+---------+
RECOMMENDATIONS
178
## GTID Status - Transactions executed on the servers:+------------+-------+---------+-------------------------------------------+| host | port | role | gtid |+------------+-------+---------+-------------------------------------------+| localhost | 3307 | MASTER | 00a4e027-a83a-11e3-8bd6-28d244017f26:1-2 || localhost | 3306 | SLAVE | 00a4e027-a83a-11e3-8bd6-28d244017f26:1-2 || localhost | 3306 | SLAVE | faf0874f-a839-11e3-8bd6-28d244017f26:1 |+------------+-------+---------+-------------------------------------------+## UUID Status:+------------+-------+---------+---------------------------------------+| host | port | role | uuid |+------------+-------+---------+---------------------------------------+| localhost | 3307 | MASTER | 00a4e027-a83a-11e3-8bd6-28d244017f26 || localhost | 3306 | SLAVE | faf0874f-a839-11e3-8bd6-28d244017f26 |+------------+-------+---------+---------------------------------------+#(...)
Start multi-source replication running as a daemon (POSIX only):
shell> mysqlrplms --slave=root:root@localhost:3306 \ --masters=root:root@localhost:3307,root:root@localhost:3308 \ --log=rplms_daemon.log --pidfile=rplms_daemon.pid --daemon=start
Restart multi-source replication running as a daemon:
shell> mysqlrplms --slave=root:root@localhost:3306 \ --masters=root:root@localhost:3307,root:root@localhost:3308 \ --log=rplms_daemon.log --pidfile=rplms_daemon.pid --daemon=restart
Stop multi-source replication running as a daemon:
shell> mysqlrplms --slave=root:root@localhost:3306 \ --masters=root:root@localhost:3307,root:root@localhost:3308 \ --log=rplms_daemon.log --pidfile=rplms_daemon.pid --daemon=stop
RECOMMENDATIONS
You should set read_only=1 in the my.cnf file for the slave to ensure that no accidental data changes,such as INSERT, DELETE, UPDATE, and so forth, are permitted on the slave other than those producedby events read from the master.
PERMISSIONS REQUIRED
The users on the masters need the following privileges: SELECT and INSERT privileges on mysqldatabase, REPLICATION SLAVE, REPLICATION CLIENT and GRANT OPTION. The slave users needthe SUPER privilege. The rpl user, used as the argument for the --rpl-user option, is either createdautomatically or if it exists, it needs the REPLICATION SLAVE privilege.
5.20 mysqlrpladmin — Administration utility for MySQL replicationThis utility permits users to perform administrative actions on a replication topology consisting of a singlemaster and its slaves. The utility is designed to make it easy to recover from planned maintenance of themaster, or from an event that takes the master offline unexpectedly.
The act of taking the master offline intentionally and switching control to another slave is called switchover.In this case, there is no loss of transactions as the master is locked and all slaves are allowed to catch up
mysqlrpladmin — Administration utility for MySQL replication
179
to the master. Once the slaves have read all events from the master, the master is shutdown and controlswitched to a slave (in this case called a candidate slave).
Recovering from the loss of a downed master is more traumatic and since there is no way to know whattransactions the master may have failed to send, the new master (called a candidate slave) must be theslave that is most up-to-date. How this is determined depends on the version of the server (see below).However, it can result in the loss of some transactions that were executed on the downed master but notsent to the slaves.
The utility accepts a list of slaves to be considered the candidate slave. If no slave is found to meet therequirements, the operation searches the list of known slaves.
Detection of a downed master is performed as follows. If the connection to the master is lost, wait --ping seconds and check again. If the master connection is lost and the master cannot be pinged orreconnected, the failover event occurs.
For all commands that require specifying multiple servers, the options require a comma-separated list ofconnection parameters in the following form (where the password, port, and socket are optional).:
*user*[:*passwd*]@*host*[:*port*][:*socket*] or*login-path*[:*port*][:*socket*]
The utility permits users to discover slaves connected to the master.
The discover slaves option requires all slaves use the --report-host and --report-portserver startup variables with the correct hostname and port. If these are missing or report the incorrectinformation, the slave may not be detected and thus not included in the operation of the utility. Thediscover slaves option ignores any slaves to which it cannot connect.
Note
If discovered slaves are missing or report the incorrect information, the slaveshealth may not be reported correctly or the slave may not be listed at all.
The utility permits the user to demote a master to a slave during the switchover operation. The --demote-master option tells the utility to, once the new master is established, make the old master a slave of thenew master. This permits rotation of the master role among a set of servers.
The utility permits the user to specify an external script to execute before and after the switchover andfailover commands. The user can specify these with the --exec-before and --exec-after options.The return code of the script is used to determine success thus each script must report 0 (success) tobe considered successful. If a script returns a value other than 0, the result code is presented in an errormessage.
The utility permits the user to log all actions taken during the commands. The --log option requires avalid path and filename of the file to use for logging operations. The log is active only when this option isspecified. The option --log-age specifies the age in days that log entries are kept. The default is seven(7) days. Older entries are automatically deleted from the log file (but only if the --log option is specified).
The format of the log file includes the date and time of the event, the level of the event (informational -INFO, warning - WARN, error - ERROR, critical failure - CRITICAL), and the message reported by theutility.
The utility has a number of options each explained in more detail below. Some of the options are specificto certain commands. Warning messages are issued whenever an option is used that does not apply tothe command requested. A brief overview of each command and its options is presented in the followingparagraphs.
COMMANDS
180
The start, stop, and reset commands require the --slaves option to list all of the slaves in the topology.Optionally, the --master option can be specified for the utility to check if the specified slaves areassociated to the given master before executing the command, making sure that the command is onlyapplied to slaves connected to the right replication master.
The options required for the elect, health and gtid commands include the --master option to specifythe existing master, and either the --slaves option to list all of the slaves in the topology or the --discover-slaves-login option to provide the user name and password to discover any slaves in thetopology that are registered and connected to the master.
The options required for switchover include the --master option to specify the existing master, the --new-master option to specify the candidate slave (the slave to become the new master), and either the--slaves option to list the considered slaves in the topology or the --discover-slaves-login optionto provide the user name and password to discover any slaves in the topology that are registered andconnected to the master.
The failover command requires only the --slaves option to explicitly list all of the slaves in the topologybecause it is expected that the master is down when this command is used. It does not use the --discover-slaves-login option and an error is presented if the user tries to include it.
Note
The option to pass in --slaves without also passing in --master was added inMySQL Utilities 1.6.0.
Use the --verbose option to see additional information in the health report and additional messagesduring switchover or failover.
COMMANDS
The utility also provides a number of useful commands for managing a replication topology including thefollowing.
elect This command is available to only those servers supporting global transaction identifiers (GTIDs),perform slave election and report the candidate slave to use in the event a switchover or failover isrequired. Slave election is simply the first slave to meet the prerequisites. GTIDs are supported in version5.6.5 and higher. This command requires the options --master and either --slaves or --discover-slaves-login.
failover This command is available to only those servers supporting GTIDs. Conduct failover to the bestslave. The command tests each candidate slave listed for the prerequisites. Once a candidate slaveis elected, it is made a slave of each of the other slaves thereby collecting any transactions executedon other slaves but not the candidate. In this way, the candidate becomes the most up-to-date slave.This command requires the --slaves option. The --discover-slaves-login option is not allowedbecause, for failover, the master is presumed to be offline or otherwise unreachable (so there is no way todiscover the slaves). The --master option is ignored for this command.
gtid This command is available to only those servers supporting GTIDs. It displays the contentsof the GTID variables, @@GLOBAL.GTID_EXECUTED, @@GLOBAL.GTID_PURGED, and@@GLOBAL.GTID_OWNED. The command also displays universally unique identifiers (UUIDs) for allservers. This command requires one of the following combinations: --master and --slaves, or --master and --discover-slaves-login.
health Display the replication health of the topology. By default, this includes the host name, port, role(MASTER or SLAVE) of the server, state of the server (UP = is connected, WARN = not connected but canping, DOWN = not connected and cannot ping), the GTID_MODE, and health state. This command can berun with the following combination of options:
OPTIONS
181
• --master and --slaves
• --master and --discover-slaves-login
• --slaves
Note
The health column displays "no master specified" when generating a health reportfor a collection of slaves and no --master option specified.
The master health state is based on the following; if GTID_MODE=ON, the server must have binary logenabled, and there must exist a user with the REPLICATE SLAVE privilege.
The slave health state is based on the following; the IO_THREAD and SQL_THREADS must be running, itmust be connected to the master, there are no errors, the slave delay for non-gtid enabled scenarios is notmore than the threshold provided by the --max-position and the slave is reading the correct master logfile, and slave delay is not more than the --seconds-behind threshold option.
reset Execute the STOP SLAVE and RESET SLAVE commands on all slaves. This command requires the--slaves option. The --discover-slaves-login option is not allowed because it might not providethe expected result, excluding slaves with the IO thread stopped. Optionally, the --master option canalso be used and in this case the utility performs an additional check to verify if the specified slaves areassociated (replication is configured) to the given master.
start Execute the START SLAVE command on all slaves. This command requires the --slaves option.The --discover-slaves-login option is not allowed because it might not provide the expected result,excluding slaves with the IO thread stopped. Optionally, the --master option can also be used and in thiscase the utility performs an additional check to verify if the specified slaves are associated (replication isconfigured) to the given master.
stop Execute the STOP SLAVE command on all slaves. This command requires the --slaves option.The --discover-slaves-login option is not allowed because it might not provide the expected result,excluding slaves with the IO thread stopped. Optionally, the --master option can also be used and in thiscase the utility performs an additional check to verify if the specified slaves are associated (replication isconfigured) to the given master.
switchover Perform slave promotion to a specified candidate slave as designated by the --new-masteroption. This command is available for both gtid-enabled servers and non-gtid-enabled scenarios. Thiscommand requires one of the following combinations:
• --master, --new-master and --slaves
• --master, --new-master and --discover-slaves-login
OPTIONS
mysqlrpladmin accepts the following command-line options:
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --candidates=candidate slave connections
OPTIONS
182
Connection information for candidate slave servers for failover. Valid only with failover command. Listmultiple slaves in comma-separated list.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --demote-master
Make master a slave after switchover.
• --discover-slaves-login=slave_login
At startup, query master for all registered slaves and use the user name and password specified toconnect. Supply the user and password in the form user[:passwd] or login-path. For example, --discover=joe:secret uses 'joe' as the user and 'secret' as the password for each discovered slave.
• --exec-after=script
Name of external script to execute after failover or switchover. Script name may include the full path.
The return code of the script is used to determine success, thus each script must report 0 (success)to be considered successful. If a script returns a value other than 0, the result code is presented in anerror message. The script specified using this option only runs if the switchover/failover executed withsuccess.
• --exec-before=script
Name of external script to execute before failover or switchover. Script name may include the full path.
The return code of the script is used to determine success, thus each script must report 0 (success) tobe considered successful. If a script returns a value other than 0, the result code is presented in an errormessage.
• --force
Ignore prerequisite checks or any inconsistencies found, such as errant transactions on the slaves orSQL thread errors, thus forcing the execution of the specified command. This option must be usedcarefully as it does not solve any detected issue, but only ignores them and displays a warning message.
• --format=format, -f format
Display the replication health output in either grid (default), tab, csv, or vertical format.
• --log=log_file
Specify a log file to use for logging messages
OPTIONS
183
• --log-age=days
Specify maximum age of log entries in days. Entries older than this are purged on startup. Default = 7days.
• --master=connection
Connection information for the master server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --max-position=position
Used to detect slave delay. The maximum difference between the master's log position and the slave'sreported read position of the master. A value greater than this means the slave is too far behind themaster. Default = 0.
• --new-master=connection
Connection information for the slave to be used to replace the master for switchover. Valid only withswitchover command.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --no-health
Turn off health report after switchover or failover.
• --ping=number
Number of ping attempts for detecting downed server. Note: on some platforms this is the same asnumber of seconds to wait for ping to return. This value is also used to check down status of master.Failover waits for ping seconds to check master response. If no response, failover event occurs.
OPTIONS
184
• --quiet, -q
Turn off all messages for quiet execution.
• --rpl-user=replication_user
The user and password for the replication user requirement, in the format: user[:password] or login-path. E.g. rpl:passwd Default = None.
• --script-threshold=return_code
Value for external scripts to trigger aborting the operation if result is greater than or equal to thethreshold.
Default = None (no threshold checking).
• --seconds-behind=seconds
Used to detect slave delay. The maximum number of seconds behind the master permitted before slaveis considered behind the master. Default = 0.
• --slaves=slave connections
Connection information for slave servers. List multiple slaves in comma-separated list. The list isevaluated literally whereby each server is considered a slave to the master listed regardless if they are aslave of the master.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --timeout=seconds
NOTES
185
Maximum timeout in seconds to wait for each replication command to complete. For example, timeout forslave waiting to catch up to master. Default = 300 seconds.
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
NOTES
The login user must have the appropriate permissions to execute SHOW SLAVE STATUS, SHOWMASTER STATUS, and SHOW VARIABLES on the appropriate servers as well as grant the REPLICATESLAVE privilege. The utility checks permissions for the master, slaves, and candidates at startup.
Mixing IP and hostnames is not recommended. The replication-specific utilities attempts to comparehostnames and IP addresses as aliases for checking slave connectivity to the master. However, if yourinstallation does not support reverse name lookup, the comparison could fail. Without the ability to do areverse name lookup, the replication utilities could report a false negative that the slave is (not) connectedto the master.
For example, if you setup replication using "MASTER_HOST=ubuntu.net" on the slave and later connectto the slave with mysqlrplcheck and have the master specified as "--master=198.51.100.6" using thevalid IP address for "ubuntu.net", you must have the ability to do a reverse name lookup to compare the IP(198.51.100.6) and the hostname (ubuntu.net) to determine if they are the same machine.
Similarly, if you use localhost to connect to the master, the health report may not show all of the slaves. Itis best to use the actual hostname of the master when connecting or setting up replication.
If the user does not specify the --rpl-user and the user has specified the switchover or failovercommand, the utility checks to see if the slaves are using --master-info-repository=TABLE. If theyare not, the utility stops with an error.
All the commands require either the --slaves or --discover-slaves-login option but both cannotbe used at the same time. In fact, some commands only allow the use of the --slaves option which issafer to specify the list slaves, because --discover-slaves-login might not provide an up to date listof available slaves.
The path to the MySQL client tools should be included in the PATH environment variable in order to use theauthentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
When using the external scripts for the failover command, the following parameters are passed in the ordershown to the external script.
Suppose you have a script run_before.sh and you specify that you want it executing before the failoveris performed (using the --exec-before option). Further, let us assume the master MySQL Server isusing port 3306 on the host 'host1' and the MySQL Server that becomes the new master is using port 3308on host 'can_host2'. The script would therefore be invoked in the following manner.
% run_before.sh host1 3306 can_host2 3308
EXAMPLES
186
Table 5.4 External Script Parameters
External Script Option Parameters Passed to External Script
--exec-before master host, master port, candidate host, candidate port
--exec-after new master host, new master port
--exec-fail-check master host, master port
--exec-post-failover (noerrors during failover)
old master host, old master port, new master host, new master port
--exec-post-failover(errors during failover)
old master host, old master port
EXAMPLES
To perform best slave election for a topology with GTID_MODE=ON (server version 5.6.5 or higher) whereall slaves are specified with the --slaves option, run the following command.:
shell> mysqlrpladmin --master=root@localhost:3331 \ --slaves=root@localhost:3332,root@localhost:3333,root@localhost:3334 elect# Electing candidate slave from known slaves.# Best slave found is located on localhost:3332.# ...done.
To perform best slave election supplying a candidate list, use the following command.:
shell> mysqlrpladmin --master=root@localhost:3331 \ --slaves=root@localhost:3332,root@localhost:3333,root@localhost:3334 \ --candidates=root@localhost:3333,root@localhost:3334 elect# Electing candidate slave from candidate list then slaves list.# Best slave found is located on localhost:3332.# ...done.
To perform failover after a master has failed, use the following command.:
shell> mysqlrpladmin \ --slaves=root@localhost:3332,root@localhost:3333,root@localhost:3334 \ --candidates=root@localhost:3333,root@localhost:3334 failover# Performing failover.# Candidate slave localhost:3333 will become the new master.# Preparing candidate for failover.# Creating replication user if it does not exist.# Stopping slaves.# Performing STOP on all slaves.# Switching slaves to new master.# Starting slaves.# Performing START on all slaves.# Checking slaves for errors.# Failover complete.# ...done.
To see the replication health of a topology with GTID_MODE=ON (server version 5.6.5 or higher) anddiscover all slaves attached to the master, run the following command. We use the result of the failovercommand above.:
shell> mysqlrpladmin --master=root@localhost:3333 \ --slaves=root@localhost:3332,root@localhost:3334 health# Getting health for master: localhost:3333.
EXAMPLES
187
## Replication Topology Health:+------------+-------+---------+--------+------------+---------+| host | port | role | state | gtid_mode | health |+------------+-------+---------+--------+------------+---------+| localhost | 3333 | MASTER | UP | ON | OK || localhost | 3332 | SLAVE | UP | ON | OK || localhost | 3334 | SLAVE | UP | ON | OK |+------------+-------+---------+--------+------------+---------+# ...done.
To view a detailed replication health report but with all of the replication health checks revealed, use the --verbose option as shown below. In this example, we use vertical format to make viewing easier.:
shell> mysqlrpladmin --master=root@localhost:3331 \ --slaves=root@localhost:3332,root@localhost:3333,root@localhost:3334 \ --verbose health# Getting health for master: localhost:3331.# Attempting to contact localhost ... Success# Attempting to contact localhost ... Success# Attempting to contact localhost ... Success# Attempting to contact localhost ... Success## Replication Topology Health:************************* 1. row ************************* host: localhost port: 3331 role: MASTER state: UP gtid_mode: ON health: OK version: 5.6.5-m8-debug-log master_log_file: mysql-bin.000001 master_log_pos: 571 IO_Thread: SQL_Thread: Secs_Behind: Remaining_Delay: IO_Error_Num: IO_Error:************************* 2. row ************************* host: localhost port: 3332 role: SLAVE state: UP gtid_mode: ON health: OK version: 5.6.5-m8-debug-log master_log_file: mysql-bin.000001 master_log_pos: 571 IO_Thread: Yes SQL_Thread: Yes Secs_Behind: 0 Remaining_Delay: No IO_Error_Num: 0 IO_Error:************************* 3. row ************************* host: localhost port: 3333 role: SLAVE state: UP gtid_mode: ON health: OK version: 5.6.5-m8-debug-log master_log_file: mysql-bin.000001 master_log_pos: 571
EXAMPLES
188
IO_Thread: Yes SQL_Thread: Yes Secs_Behind: 0 Remaining_Delay: No IO_Error_Num: 0 IO_Error:************************* 4. row ************************* host: localhost port: 3334 role: SLAVE state: UP gtid_mode: ON health: OK version: 5.6.5-m8-debug-log master_log_file: mysql-bin.000001 master_log_pos: 571 IO_Thread: Yes SQL_Thread: Yes Secs_Behind: 0 Remaining_Delay: No IO_Error_Num: 0 IO_Error:4 rows.# ...done.
To run the same failover command above, but specify a log file, use the following command.:
shell> mysqlrpladmin \ --slaves=root@localhost:3332,root@localhost:3333,root@localhost:3334 \ --candidates=root@localhost:3333,root@localhost:3334 \ --log=test_log.txt failover# Performing failover.# Candidate slave localhost:3333 will become the new master.# Preparing candidate for failover.# Creating replication user if it does not exist.# Stopping slaves.# Performing STOP on all slaves.# Switching slaves to new master.# Starting slaves.# Performing START on all slaves.# Checking slaves for errors.# Failover complete.# ...done.
After this command, the log file contains entries like the following:
2012-03-19 14:44:17 PM INFO Executing failover command...2012-03-19 14:44:17 PM INFO Performing failover.2012-03-19 14:44:17 PM INFO Candidate slave localhost:3333 will become the new master.2012-03-19 14:44:17 PM INFO Preparing candidate for failover.2012-03-19 14:44:19 PM INFO Creating replication user if it does not exist.2012-03-19 14:44:19 PM INFO Stopping slaves.2012-03-19 14:44:19 PM INFO Performing STOP on all slaves.2012-03-19 14:44:19 PM INFO Switching slaves to new master.2012-03-19 14:44:20 PM INFO Starting slaves.2012-03-19 14:44:20 PM INFO Performing START on all slaves.2012-03-19 14:44:20 PM INFO Checking slaves for errors.2012-03-19 14:44:21 PM INFO Failover complete.2012-03-19 14:44:21 PM INFO ...done.
To perform switchover and demote the current master to a slave, use the following command.:
shell> mysqlrpladmin --master=root@localhost:3331 \ --slaves=root@localhost:3332,root@localhost:3333,root@localhost:3334 \
PERMISSIONS REQUIRED
189
--new-master=root@localhost:3332 --demote-master switchover# Performing switchover from master at localhost:3331 to slave at localhost:3332.# Checking candidate slave prerequisites.# Waiting for slaves to catch up to old master.# Stopping slaves.# Performing STOP on all slaves.# Demoting old master to be a slave to the new master.# Switching slaves to new master.# Starting all slaves.# Performing START on all slaves.# Checking slaves for errors.# Switchover complete.# ...done.
If the replication health report is generated on the topology following the above command, it displays theold master as a slave as shown below.:
# Replication Topology Health:+------------+-------+---------+--------+------------+---------+| host | port | role | state | gtid_mode | health |+------------+-------+---------+--------+------------+---------+| localhost | 3332 | MASTER | UP | ON | OK || localhost | 3331 | SLAVE | UP | ON | OK || localhost | 3333 | SLAVE | UP | ON | OK || localhost | 3334 | SLAVE | UP | ON | OK |+------------+-------+---------+--------+------------+---------+
You can use the discover slaves feature, if and only if all slaves report their host and port to the master.A sample command to generate a replication health report with discovery is shown below. Note that theoption --discover-slaves-login cannot be used in conjunction with the --slaves option.:
shell> mysqlrpladmin --master=root@localhost:3332 --discover-slaves-login=root health
# Discovering slaves for master at localhost:3332# Discovering slave at localhost:3331# Found slave: localhost:3331# Discovering slave at localhost:3333# Found slave: localhost:3333# Discovering slave at localhost:3334# Found slave: localhost:3334# Checking privileges.## Replication Topology Health:+------------+-------+---------+--------+------------+---------+| host | port | role | state | gtid_mode | health |+------------+-------+---------+--------+------------+---------+| localhost | 3332 | MASTER | UP | ON | OK || localhost | 3331 | SLAVE | UP | ON | OK || localhost | 3333 | SLAVE | UP | ON | OK || localhost | 3334 | SLAVE | UP | ON | OK |+------------+-------+---------+--------+------------+---------+# ...done.
PERMISSIONS REQUIRED
The users on the master need the following privileges: SELECT and INSERT privileges on mysqldatabase, REPLICATION SLAVE, REPLICATION CLIENT and GRANT OPTION. The slave users needthe SUPER privilege. The repl user, used as the argument for the --rpl-user option, is either createdautomatically or if it exists, it needs the REPLICATION SLAVE privilege.
To run the mysqlrpladmin utility with the health command, the account used on the master needs anextra SUPER privilege.
mysqlrplcheck — Check Replication Prerequisites
190
As for the switchover command all the users need the following privileges: SUPER, GRANT OPTION,SELECT, RELOAD, DROP, CREATE and REPLICATION SLAVE
5.21 mysqlrplcheck — Check Replication PrerequisitesThis utility checks the prerequisites for replication between a master and a slave. These checks (calledtests) are designed to ensure a healthy replication setup. The utility performs the following tests:
1. Is the binary log enabled on the master?
2. Are there binary logging exceptions (such as *_do_db or *_ignore_db settings)? If so, display them.
3. Does the replication user exist on the master with the correct privileges?
4. Are there server_id conflicts?
5. Is the slave connected to this master? If not, display the master host and port.
6. Are there conflicts between the master.info file on the slave and the values shown in SHOWSLAVE STATUS on the master?
7. Are the InnoDB configurations compatible (plugin vs. native)?
8. Are the storage engines compatible (have same on slave as master)?
9. Are the lower_case_tables_names settings compatible? Warn if there are settings for lowercase/uppercase table names that can cause problems. See Bug #59240.
10. Is the slave behind the master?
The utility runs each test in turn unless there is a fatal error preventing further testing, such as a loss ofconnection to the servers.
Each test can complete with one of the following states: pass (the prerequisites are met), fail (theprerequisites were met but one or more errors occurred or there are exceptions to consider), or warn (thetest found some unusual settings that should be examined further but may not be in error).
Use the --verbose option to see additional information such as server IDs, lower_case_table_namesettings, and the contents of the master information file on the slave.
To see the values from the SHOW SLAVE STATUS statement, use the --show-slave-status option.
OPTIONS
mysqlrplcheck accepts the following command-line options:
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --master=source
Connection information for the master server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply this
OPTIONS
191
information. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --master-info-file=file
The name of the master information file on the slave. The default is master.info read from the datadirectory. Note: This option requires that you run the utility on the slave and that you have appropriateread access for the file.
• --quiet, -q
Turn off all messages for quiet execution. Note: Errors and warnings are not suppressed.
• --show-slave-status, -s
Display the values from SHOW SLAVE STATUS on the master.
• --slave=source
Connection information for the slave server. You may specify only one slave for this option.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --suppress
Suppress warning messages.
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
NOTES
192
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
• --width=number
Change the display width of the test report. The default is 75 characters.
NOTES
The login user must have the appropriate permissions to execute SHOW SLAVE STATUS, SHOWMASTER STATUS, and SHOW VARIABLES on the appropriate servers.
Mixing IP and hostnames is not recommended. The replication-specific utilities attempt to comparehostnames and IP addresses as aliases for checking slave connectivity to the master. However, if yourinstallation does not support reverse name lookup, the comparison could fail. Without the ability to do areverse name lookup, the replication utilities could report a false negative that the slave is (not) connectedto the master.
For example, if you setup replication using MASTER_HOST=ubuntu.net on the slave and later connectto the slave with mysqlrplcheck and have the master specified as --master=198.51.100.6 using the validIP address for ubuntu.net, you must have the ability to do a reverse name lookup to compare the IP(198.51.100.6) and the hostname (ubuntu.net) to determine if they are the same machine.
The path to the MySQL client tools should be included in the PATH environment variable in order to usethe authentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
EXAMPLES
To check the prerequisites of a master and slave that currently are actively performing replication, use thefollowing command:
shell> mysqlrplcheck --master=root@host1:3310 --slave=root@host2:3311# master on host1: ... connected.# slave on host2: ... connected.Test Description Status------------------------------------------------------------------------Checking for binary logging on master [pass]Are there binlog exceptions? [pass]Replication user exists? [pass]Checking server_id values [pass]Is slave connected to master? [pass]Check master information file [pass]Checking InnoDB compatibility [pass]Checking storage engines compatibility [pass]Checking lower_case_table_names settings [pass]Checking slave delay (seconds behind master) [pass]# ...done.
EXAMPLES
193
As shown in the example, you must provide valid login information for both the master and the slave.
To perform the same command but also display the contents of the master information file on the slave andthe values of SHOW SLAVE STATUS as well as additional details, use this command:
shell> mysqlrplcheck --master=root@host1:3310 --slave=root@host2:3311 \ --show-slave-status -vv# master on host1: ... connected.# slave on host2: ... connected.Test Description Status------------------------------------------------------------------------Checking for binary logging on master [pass]Are there binlog exceptions? [pass]Replication user exists? [pass]Checking server_id values [pass]
master id = 10 slave id = 11
Is slave connected to master? [pass]Check master information file [pass]
## Master information file:# Master_Log_File : clone-bin.000001 Read_Master_Log_Pos : 482 Master_Host : host1 Master_User : rpl Master_Password : XXXX Master_Port : 3310 Connect_Retry : 60 Master_SSL_Allowed : 0 Master_SSL_CA_File : Master_SSL_CA_Path : Master_SSL_Cert : Master_SSL_Cipher : Master_SSL_Key : Master_SSL_Verify_Server_Cert : 0
Checking InnoDB compatibility [pass]Checking storage engines compatibility [pass]Checking lower_case_table_names settings [pass]
Master lower_case_table_names: 2 Slave lower_case_table_names: 2
Checking slave delay (seconds behind master) [pass]
## Slave status:# Slave_IO_State : Waiting for master to send event Master_Host : host1 Master_User : rpl Master_Port : 3310 Connect_Retry : 60 Master_Log_File : clone-bin.000001 Read_Master_Log_Pos : 482 Relay_Log_File : clone-relay-bin.000006 Relay_Log_Pos : 251 Relay_Master_Log_File : clone-bin.000001 Slave_IO_Running : Yes Slave_SQL_Running : Yes Replicate_Do_DB : Replicate_Ignore_DB :
PERMISSIONS REQUIRED
194
Replicate_Do_Table : Replicate_Ignore_Table : Replicate_Wild_Do_Table : Replicate_Wild_Ignore_Table : Last_Errno : 0 Last_Error : Skip_Counter : 0 Exec_Master_Log_Pos : 482 Relay_Log_Space : 551 Until_Condition : None Until_Log_File : Until_Log_Pos : 0 Master_SSL_Allowed : No Master_SSL_CA_File : Master_SSL_CA_Path : Master_SSL_Cert : Master_SSL_Cipher : Master_SSL_Key : Seconds_Behind_Master : 0 Master_SSL_Verify_Server_Cert : No Last_IO_Errno : 0 Last_IO_Error : Last_SQL_Errno : 0 Last_SQL_Error :# ...done.
PERMISSIONS REQUIRED
The users on the master need the following privileges: SELECT and INSERT privileges on mysqldatabase, REPLICATION SLAVE, REPLICATION CLIENT and GRANT OPTION. The slave users needthe SUPER privilege.
Also, when using GTIDs, the slave users must also have SELECT privilege over the mysql database.
5.22 mysqlrplshow — Show Slaves for Master ServerThis utility shows the replication slaves for a master. It prints a graph of the master and the slavesconnected labeling each with the host name and port number.
You must specify the --discover-slaves-login option to provide the user name and password todiscover any slaves in the topology.
The discover slaves option requires all slaves use the --report-host and --report-portserver startup variables with the correct hostname and port. If these are missing or report the incorrectinformation, the slave may not be detected and thus not included in the operation of the utility. Thediscover slaves option ignores any slaves to which it cannot connect.
To explore the slaves for each client, use the --recurse option. This causes the utility to connect to eachslave found and attempt to determine whether it has any slaves. If slaves are found, the process continuesuntil the slave is found in the list of servers serving as masters (a circular topology). The graph displays thetopology with successive indents. A notation is made for circular topologies.
If you use the --recurse option, the utility attempts to connect to the slaves using the user name andpassword provided for the master. By default, if the connection attempt fails, the utility throws an error andstops. To change this behavior, use the --prompt option, which permits the utility to prompt for the username and password for each slave that fails to connect. You can also use the --num-retries=n optionto reattempt a failed connection 'n' times before the utility fails.
An example graph for a typical topology with relay slaves is shown here:
# Replication Topology Graph::
OPTIONS
195
localhost:3311 (MASTER) | +--- localhost:3310 - (SLAVE) | +--- localhost:3312 - (SLAVE + MASTER) | +--- localhost:3313 - (SLAVE)
MASTER, SLAVE, and SLAVE+MASTER indicate that a server is a master only, slave only, and both slaveand master, respectively.
A circular replication topology is shown like this, where <--> indicates circularity:
# Replication Topology Graph
localhost:3311 (MASTER) | +--- localhost:3312 - (SLAVE + MASTER) | +--- localhost:3313 - (SLAVE + MASTER) | +--- localhost:3311 <--> (SLAVE)
To produce a column list in addition to the graph, specify the --show-list option. In this case, to specifyhow to display the list, use one of the following values with the --format option:
• grid (default)
Display output in grid or table format like that of the mysql client command-line tool.
• csv
Display output in comma-separated values format.
• tab
Display output in tab-separated format.
• vertical
Display output in single-column format like that of the \G command for the mysql client command-linetool.
The utility uses of the SHOW SLAVE HOSTS statement to determine which slaves the master has. Ifyou want to use the --recurse option, slaves must have been started with the --report-host and--report-port options set to their actual host name and port number or the utility may not be able toconnect to the slaves to determine their own slaves.
OPTIONS
mysqlrplshow accepts the following command-line options:
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --discover-slaves-login=slave-login
OPTIONS
196
Supply the user and password in the form user[:passwd] or login-path for discovering slaves andrelay slaves in the topology. For example, --discover=joe:secret uses 'joe' as the user and 'secret' as thepassword for each discovered slave.
• --format=format, -fformat
Specify the display format for column list output. Permitted format values are grid, csv, tab, andvertical. The default is grid. This option applies only if --show-list is given.
• --master=source
Connection information for the master server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --max-depth=N
The maximum recursion depth. This option is valid only if --recurse is given.
• --num-retries=num_retries, -nnum_retries
The number of retries permitted for failed slave login attempts. This option is valid only if --prompt isgiven.
• --prompt, -p
Prompt for the slave user and password if different from the master user and password.
If you give this option, the utility sets --num-retries to 1 if that option is not set explicitly. This ensuresat least one attempt to retry and prompt for the user name and password should a connection fail.
• --quiet, -q
Turn off all messages for quiet execution. This option does not suppress errors or warnings.
• --recurse, -r
Traverse the list of slaves to find additional master/slave connections. User this option to map areplication topology.
• --show-list, -l
Display a column list of the topology.
• --ssl-ca
NOTES
197
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --verbose, -v
Specify how much information to display. If this option is used, the IO thread status of each slave isalso displayed. Use this option multiple times to increase the amount of information. For example, -v =verbose, -vv = more verbose, -vvv = debug. If you use -vvv, the output contains the state of the IO andSQL threads for each slave.
• --version
Display version information and exit.
NOTES
The login user must have the REPLICATE SLAVE and REPLICATE CLIENT privileges to successfullyexecute this utility. Specifically, the login user must have appropriate permissions to execute SHOWSLAVE STATUS, SHOW MASTER STATUS, and SHOW SLAVE HOSTS.
For the --format option, the permitted values are not case-sensitive. In addition, values may be specifiedas any unambiguous prefix of a valid value. For example, --format=g specifies the grid format. An erroroccurs if a prefix matches more than one valid value.
Mixing IP and hostnames is not recommended. The replication-specific utilities attempt to comparehostnames and IP addresses as aliases for checking slave connectivity to the master. However, if yourinstallation does not support reverse name lookup, the comparison could fail. Without the ability to do areverse name lookup, the replication utilities could report a false negative that the slave is (not) connectedto the master.
For example, if you setup replication using MASTER_HOST=ubuntu.net on the slave and later connectto the slave with mysqlrplcheck and have the master specified as --master=198.51.100.6 using the validIP address for ubuntu.net, you must have the ability to do a reverse name lookup to compare the IP(198.51.100.6) and the hostname (ubuntu.net) to determine if they are the same machine.
The path to the MySQL client tools should be included in the PATH environment variable in order to usethe authentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
EXAMPLES
To show the slaves for a master running on port 3311 on the local host, use the following command:
shell> mysqlrplshow --master=root@localhost:3311 --discover-slaves-login=root
EXAMPLES
198
# master on localhost: ... connected.# Finding slaves for master: localhost:3311
# Replication Topology Graphlocalhost:3311 (MASTER) | +--- localhost:3310 - (SLAVE) | +--- localhost:3312 - (SLAVE)
As shown in the example, you must provide valid login information for the master.
To show additional information about the IO thread status (to confirm if the slaves are really connected tothe master) use the option --verbose:
shell> mysqlrplshow --master=root@localhost:3311 --discover-slaves-login=root --verbose# master on localhost: ... connected.# Finding slaves for master: localhost:3311
# Replication Topology Graphlocalhost:3311 (MASTER) | +--- localhost:3310 [IO: Yes, SQL: Yes] - (SLAVE) | +--- localhost:3312 [IO: Yes, SQL: Yes] - (SLAVE)
To show the full replication topology of a master running on the local host, use the following command:
shell> mysqlrplshow --master=root@localhost:3311 --recurse --discover-slaves-login=root# master on localhost: ... connected.# Finding slaves for master: localhost:3311
# Replication Topology Graphlocalhost:3311 (MASTER) | +--- localhost:3310 - (SLAVE) | +--- localhost:3312 - (SLAVE + MASTER) | +--- localhost:3313 - (SLAVE)
To show the full replication topology of a master running on the local host, prompting for the user nameand password for slaves that do not have the same user name and password credentials as the master,use the following command:
shell> mysqlrplshow --recurse --prompt --num-retries=1 \ --master=root@localhost:3331 --discover-slaves-login=root
Server localhost:3331 is running on localhost.# master on localhost: ... connected.# Finding slaves for master: localhost:3331Server localhost:3332 is running on localhost.# master on localhost: ... FAILED.Connection to localhost:3332 has failed.Please enter the following information to connect to this server.User name: rootPassword:# master on localhost: ... connected.# Finding slaves for master: localhost:3332Server localhost:3333 is running on localhost.# master on localhost: ... FAILED.Connection to localhost:3333 has failed.Please enter the following information to connect to this server.
PERMISSIONS REQUIRED
199
User name: rootPassword:# master on localhost: ... connected.# Finding slaves for master: localhost:3333Server localhost:3334 is running on localhost.# master on localhost: ... FAILED.Connection to localhost:3334 has failed.Please enter the following information to connect to this server.User name: rootPassword:# master on localhost: ... connected.# Finding slaves for master: localhost:3334
# Replication Topology Graphlocalhost:3331 (MASTER) | +--- localhost:3332 - (SLAVE) | +--- localhost:3333 - (SLAVE + MASTER) | +--- localhost:3334 - (SLAVE)
PERMISSIONS REQUIRED
The user connected to the master must have the REPLICATION SLAVE privilege.
The user specified with the --discover-slaves-login option that logs into each slave must have theREPLICATION CLIENT privilege.
5.23 mysqlrplsync — Replication synchronization checker
This utility permits you to check replication servers for synchronization of replicated events. The utilitypermits users to check data consistency between a master and slaves or between two slaves. The utilityreports missing objects as well as missing data. The utility can also be used to synchronize the replicateddata on the servers.
The utility can operate on an active replication topology applying a synchronization process to check thedata. Those servers where replication is not active can still be checked but the synchronization process isskipped. In that case, it is up to the user to manually synchronize the servers.
The user must provide connection parameters for the servers. That is, the utility requires the master andslaves using the --master and --slaves options. To compare only slaves, the user need only providethe --slaves option.
The utility also provides a feature to discover slaves connected to the master using the --discover-slaves-login and --master options.
The discover slaves option requires all slaves use the --report-host and --report-portserver startup variables with the correct hostname and port. If these are missing or report the incorrectinformation, the slave may not be detected and thus not included in the operation of the utility. Thediscover slaves option ignores any slaves to which it cannot connect.
By default, all data is included in the comparison. To check specific databases or tables, list each elementas a separated argument for the utility using fully qualified names. The user can also choose to excludesome databases or tables from the check using the --exclude option.
The utility also provides some important features that allow users to adjust the execution of theconsistency check to their system. For example, the user may wish the utility to minimize execution of thesynchronization process. To do so, the user uses the --rpl-timeout to define the maximum time for
OPTIONS
200
each slave to synchronize. More specifically, allow slaves to catch up with the master in order to comparethe data. During this waiting step, the slaves status is periodically polled according to a predefined timeinterval. This polling interval to verify if the slaves are synced can be adjusted with the --intervaloption. A checksum query is used to compare the data of each table between servers. The checksumcalculation step is skipped if its execution exceeds a predefined time, avoiding undesirable performanceimpacts on the target system if it takes too long to execute. The user can change the checksum timeoutusing the --checksum-timeout option.
Users can also use the --verbose option to see additional information when the utility executes.
This utility is designed to work exclusively for servers that support global transaction identifiers (GTIDs)and have gtid_mode=ON. Servers with GTID disabled are skipped by the utility. See Replication withGlobal Transaction Identifiers, for more information about GTID.
The utility takes into consideration the use of replication filtering rules on the servers skipping the check forfiltered databases and tables according to the defined options. Nevertheless, the use of replication filterscan still lead to data consistency issues depending on how statements are evaluated. See How ServersEvaluate Replication Filtering Rules, for more information.
OPTIONS
mysqlrplsync accepts the following command-line options:
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --checksum-timeout=checksum_timeout_in_seconds
Maximum timeout in seconds to wait for the checksum query to complete.
Default = 3 seconds.
• --discover-slaves-login=user_login
Detect registered slaves at startup and use the user name and password specified to connect in theformat: user [:password] or login-path. For example, --discover-slaves-login=joe:secret uses 'joe'as the user and 'secret' as the password for each discovered slave.
• --exclude=databases_tables_to_exclude
Fully qualified name for the databases or tables to exclude: db_name [.tbl_name]. List multiple dataobjects in a comma-separated list.
• --interval=interval_in_seconds, -i interval_in_seconds
Interval in seconds for periodically polling the slaves sync status to verify if the sync point was reached.
Default = 3 seconds.
• --master=master_connection
Connection information for the master server.
OPTIONS
201
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --rpl-timeout=rpl_timeout_in_seconds
Maximum timeout in seconds to wait for synchronization. More precisely, the time to wait for thereplication process on a slave to reach a sync point (GTID set).
Default = 300 seconds.
• --slaves=slaves_connections
Connection information for slave servers . List multiple slaves in comma-separated list.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --verbose, -v
NOTES
202
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
NOTES
The data consistency check is performed per table using a checksum on the table. If the calculatedchecksum differs, it indicates the tables are not synchronized. Nevertheless, since the checksum operationis not collision free, there is a very small probability that two tables with differing data can produce thesame checksum.
Mixing IP and hostnames is not recommended. The replication-specific utilities attempt to comparehostnames and IP addresses as aliases for checking slave connectivity to the master. However, if yourinstallation does not support reverse name lookup, the comparison could fail. Without the ability to do areverse name lookup, the replication utilities could report a false negative that the slave is (not) connectedto the master.
For example, if you setup replication using MASTER_HOST=ubuntu.net on the slave and later connectto the slave with mysqlrplcheck and have the master specified as --master=198.51.100.6 using the validIP address for ubuntu.net, you must have the ability to do a reverse name lookup to compare the IP(198.51.100.6) and the hostname (ubuntu.net) to determine if they are the same machine.
Similarly, in order to avoid issues mixing local IP '127.0.0.1' with 'localhost', the addresse '127.0.0.1' isconverted to 'localhost' by the utility.
The path to the MySQL client tools should be included in the PATH environment variable in order to usethe authentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
LIMITATIONS
This utility is designed to work exclusively for servers that support global transaction identifiers(GTIDs) and have gtid_mode=ON. Due to known server issues with some operations required for thesynchronization process, only MySQL Server versions 5.6.14 and higher are supported by this utility.
Some replication filtering options are not supported by this utility due to known issues on the server side,namely: replicate_do_db, replicate_ignore_db, and replicate_wild_do_table. In case a non supportedreplication filtering option is detected on a server, the utility issues an appropriate error and exits. Thischeck is performed at the beginning when the utility starts.
EXAMPLES
To check the data consistency on an active replication system explicitly specifying the master and slaves:
shell> mysqlrplsync --master=user:pass@localhost:3310 \ --slaves=rpl:pass@localhost:3311,rpl:pass@localhost:3312## GTID differences between Master and Slaves:# - Slave 'localhost@3311' is 15 transactions behind Master.# - Slave 'localhost@3312' is 12 transactions behind Master.## Checking data consistency.
EXAMPLES
203
## Using Master 'localhost@3310' as base server for comparison.# Checking 'test_rplsync_db' database...# - Checking 't0' table data...# [OK] `test_rplsync_db`.`t0` checksum for server 'localhost@3311'.# [OK] `test_rplsync_db`.`t0` checksum for server 'localhost@3312'.# - Checking 't1' table data...# [OK] `test_rplsync_db`.`t1` checksum for server 'localhost@3311'.# [OK] `test_rplsync_db`.`t1` checksum for server 'localhost@3312'.# Checking 'test_db' database...# - Checking 't0' table data...# [OK] `test_db`.`t0` checksum for server 'localhost@3311'.# [OK] `test_db`.`t0` checksum for server 'localhost@3312'.# - Checking 't1' table data...# [OK] `test_db`.`t1` checksum for server 'localhost@3311'.# [OK] `test_db`.`t1` checksum for server 'localhost@3312'.##...done.## SUMMARY: No data consistency issue found.#
To check the data consistency on an active replication system using slave discovery:
shell> mysqlrplsync --master=user:pass@localhost:3310 \ --discover-slaves-login=rpl:pass# Discovering slaves for master at localhost:3310# Discovering slave at localhost:3311# Found slave: localhost:3311# Discovering slave at localhost:3312# Found slave: localhost:3312## GTID differences between Master and Slaves:# - Slave 'localhost@3311' is 15 transactions behind Master.# - Slave 'localhost@3312' is 15 transactions behind Master.## Checking data consistency.## Using Master 'localhost@3310' as base server for comparison.# Checking 'test_rplsync_db' database...# - Checking 't0' table data...# [OK] `test_rplsync_db`.`t0` checksum for server 'localhost@3311'.# [OK] `test_rplsync_db`.`t0` checksum for server 'localhost@3312'.# - Checking 't1' table data...# [OK] `test_rplsync_db`.`t1` checksum for server 'localhost@3311'.# [OK] `test_rplsync_db`.`t1` checksum for server 'localhost@3312'.# Checking 'test_db' database...# - Checking 't0' table data...# [OK] `test_db`.`t0` checksum for server 'localhost@3311'.# [OK] `test_db`.`t0` checksum for server 'localhost@3312'.# - Checking 't1' table data...# [OK] `test_db`.`t1` checksum for server 'localhost@3311'.# [OK] `test_db`.`t1` checksum for server 'localhost@3312'.##...done.## SUMMARY: No data consistency issue found.#
To check the data consistency on an active replication system, but only between specific slaves:
shell> mysqlrplsync --slaves=rpl:pass@localhost:3311,rpl:pass@localhost:3312## Checking data consistency.#
EXAMPLES
204
# Using Slave 'localhost@3311' as base server for comparison.# Checking 'test_rplsync_db' database...# - Checking 't0' table data...# [OK] `test_rplsync_db`.`t0` checksum for server 'localhost@3312'.# - Checking 't1' table data...# [OK] `test_rplsync_db`.`t1` checksum for server 'localhost@3312'.# Checking 'test_db' database...# - Checking 't0' table data...# [OK] `test_db`.`t0` checksum for server 'localhost@3312'.# - Checking 't1' table data...# [OK] `test_db`.`t1` checksum for server 'localhost@3312'.##...done.## SUMMARY: No data consistency issue found.#
To check the data consistency of a specific database and table on an active replication system:
shell> mysqlrplsync --master=user:pass@localhost:3310 \ --slaves=rpl:pass@localhost:3311,rpl:pass@localhost:3312 \ test_rplsync_db test_db.t1## GTID differences between Master and Slaves:# - Slave 'localhost@3311' is 15 transactions behind Master.# - Slave 'localhost@3312' is 12 transactions behind Master.## Checking data consistency.## Using Master 'localhost@3310' as base server for comparison.# Checking 'test_rplsync_db' database...# - Checking 't0' table data...# [OK] `test_rplsync_db`.`t0` checksum for server 'localhost@3311'.# [OK] `test_rplsync_db`.`t0` checksum for server 'localhost@3312'.# - Checking 't1' table data...# [OK] `test_rplsync_db`.`t1` checksum for server 'localhost@3311'.# [OK] `test_rplsync_db`.`t1` checksum for server 'localhost@3312'.# Checking 'test_db' database...# - Checking 't1' table data...# [OK] `test_db`.`t1` checksum for server 'localhost@3311'.# [OK] `test_db`.`t1` checksum for server 'localhost@3312'.##...done.## SUMMARY: No data consistency issue found.#
To check the data consistency on an active replication system excluding a specific database and table:
shell> mysqlrplsync --master=user:pass@localhost:3310 \ --slaves=rpl:pass@localhost:3311,rpl:pass@localhost:3312 \ --exclude=test_rplsync_db,test_db.t1## GTID differences between Master and Slaves:# - Slave 'localhost@3311' is 15 transactions behind Master.# - Slave 'localhost@3312' is 12 transactions behind Master.## Checking data consistency.## Using Master 'localhost@3310' as base server for comparison.# Checking 'test_db' database...# - Checking 't0' table data...# [OK] `test_db`.`t0` checksum for server 'localhost@3311'.# [OK] `test_db`.`t0` checksum for server 'localhost@3312'.#
EXAMPLES
205
#...done.## SUMMARY: No data consistency issue found.#
The following is an example of a replication check that has data inconsistencies:
shell> mysqlrplsync --master=user:pass@localhost:3310 \ --slaves=rpl:pass@localhost:3311,rpl:pass@localhost:3312## GTID differences between Master and Slaves:# - Slave 'localhost@3311' is up-to-date.# - Slave 'localhost@3312' is up-to-date.## Checking data consistency.## Using Master 'localhost@3310' as base server for comparison.# [DIFF] Database NOT on base server but found on 'localhost@3311': only_on_slave_db# Checking 'test_rplsync_db' database...# [DIFF] Table NOT on base server but found on 'localhost@3311': t3# [DIFF] Table NOT on base server but found on 'localhost@3312': t3# [DIFF] Table 'test_rplsync_db.t0' NOT on server 'localhost@3311'.# - Checking 't0' table data...# [DIFF] `test_rplsync_db`.`t0` checksum for server 'localhost@3312'.# - Checking 't1' table data...# WARNING: Slave not active 'localhost@3311' - Sync skipped.# [DIFF] `test_rplsync_db`.`t1` checksum for server 'localhost@3311'.# [OK] `test_rplsync_db`.`t1` checksum for server 'localhost@3312'.# - Checking 't2' table data...# WARNING: Slave not active 'localhost@3311' - Sync skipped.# [OK] `test_rplsync_db`.`t2` checksum for server 'localhost@3311'.# [OK] `test_rplsync_db`.`t2` checksum for server 'localhost@3312'.# Checking 'only_on_master_db' database...# [DIFF] Database 'only_on_master_db' NOT on server 'localhost@3311'.# [DIFF] Database 'only_on_master_db' NOT on server 'localhost@3312'.##...done.## SUMMARY: 8 data consistency issues found.#
Check a replication topology with filtering:
shell> mysqlrplsync --master=user:pass@localhost:3310 \ --slaves=rpl:pass@localhost:3311,rpl:pass@localhost:3312 \ --verbose# Checking users permission to perform consistency check.## WARNING: Replication filters found on checked servers. This can lead data consistency issues depending on how statements are evaluated.# More information: http://dev.mysql.com/doc/en/replication-rules.html# Master 'localhost@3310':# - binlog_do_db: test_rplsync_db1# Slave 'localhost@3311':# - replicate_do_table: test_rplsync_db1.t1# Slave 'localhost@3312':# - replicate_ignore_table: test_rplsync_db1.t2# - replicate_wild_ignore_table: test\_rplsync\_db1.%3## GTID differences between Master and Slaves:# - Slave 'localhost@3311' is up-to-date.# - Slave 'localhost@3312' is up-to-date.## Checking data consistency.## Using Master 'localhost@3310' as base server for comparison.
PERMISSIONS REQUIRED
206
# Checking 'test_rplsync_db1' database...# [SKIP] Table 't0' check for 'localhost@3311' - filtered by replication rule.# - Checking 't0' table data...# Setting data synchronization point for slaves.# Compute checksum on slaves (wait to catch up and resume replication).# [OK] `test_rplsync_db1`.`t0` checksum for server 'localhost@3312'.# - Checking 't1' table data...# Setting data synchronization point for slaves.# Compute checksum on slaves (wait to catch up and resume replication).# [OK] `test_rplsync_db1`.`t1` checksum for server 'localhost@3311'.# [OK] `test_rplsync_db1`.`t1` checksum for server 'localhost@3312'.# [SKIP] Table 't2' check for 'localhost@3311' - filtered by replication rule.# [SKIP] Table 't2' check for 'localhost@3312' - filtered by replication rule.# [SKIP] Table 't3' check for 'localhost@3311' - filtered by replication rule.# [SKIP] Table 't3' check for 'localhost@3312' - filtered by replication rule.# [SKIP] Database 'test_rplsync_db0' check - filtered by replication rule.# [SKIP] Database 'test_rplsync_db2' check - filtered by replication rule.# [SKIP] Database 'test_rplsync_db3' check - filtered by replication rule.##...done.## SUMMARY: No data consistency issue found.#
PERMISSIONS REQUIRED
The user for the master must have permissions to lock tables, perform the checksum, and get informationabout the master status. Specifically, the user used to connect to the master requires the followingprivileges: SUPER or REPLICATION CLIENT, LOCK TABLES and SELECT.
The user for the slaves must have permissions to start/stop the slave, perform the checksum, and getinformation about the slave status. More specifically, the login user to connect to slaves requires thefollowing privileges: SUPER and SELECT.
5.24 mysqlserverclone — Clone Existing Server to Create NewServer
This utility enables you to clone an existing MySQL server instance to create a new server instance on thesame host. The utility creates a new datadir (--new-data), and, on Unix systems, starts the server with asocket file. You can optionally add a password for the login user account on the new instance.
If the user does not have read and write access to the folder specified by the --new-data option, theutility issues an error.
Similarly, if the folder specified by --new-data exists and is not empty, the utility does not delete thefolder and issues an error message. Users must specify the --delete-data option to permit the utility toremove the folder prior to starting the cloned server.
The utility does not copy any data. It merely creates a new running instance of the cloned server with thesame options (or additional options if specified). Thus, to create a copy of a server, you must copy the dataafter the server is cloned.
OPTIONS
mysqlserverclone accepts the following command-line options:
• --help
Display a help message and exit.
OPTIONS
207
• --license
Display license information and exit.
• --delete-data
Delete the folder specified by --new-data if it exists and is not empty.
• --basedir
The base directory for the MySQL server source, as an alternative to the --server option.
shell> mysqlserverclone --basedir=/source/mysql-5.6 \--new-data=/source/temp_3007 --new-port=3007 --new-id=101 \--root=root --mysqld="--log-bin --gtid-mode=on --log-slave-updates \--enforce-gtid-consistency --master-info-repository=table \--report-host=localhost --report-port=3007" --delete
• --force
Ignore the maximum path length and the low space checks for the --new-data option.
• --mysqld=options
Additional options for mysqld. To specify multiple options, separate them by spaces. Use appropriatequoting as necessary. For example, to specify --log-bin=binlog and --general-log-file="mylogfile", use:
If the option --skip-innodb is included when connecting to a MySQL server version 5.7.5 or higher, theoption is ignored and a warning is issued.
--mysqld="--log-bin=binlog --general-log-file='my log file'"
• --new-data=path_to_new_datadir
The full path to the location of the data directory for the new instance. The path size must be 200characters or less and it requires at least 120 MB of free space.
• --new-id=server_id
The server_id value for the new server instance. The default is 2.
• --new-port=port
The port number for the new server instance. The default is 3307.
• --quiet, -q
Turn off all messages for quiet execution.
• --root-password=password
The password for the root user of the new server instance.
• --server=source
Connection information for the server to be cloned.
EXAMPLES
208
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --start-timeout=timeout_in_seconds
Number of seconds to wait for server to start. Default = 10 seconds.
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
• --write-command=file_name, -wfile_name
Path name of file in which to write the command used to launch the new server instance.
EXAMPLES
The following command demonstrates how to create a new instance of a running server, set the root userpassword and enable binary logging:
shell> mkdir /source/test123shell> mysqlserverclone --server=root:pass@localhost \ --new-data=/Users/cbell/source/test123 --new-port=3310 \ --root-password=pass --mysqld=--log-bin=mysql-bin
NOTES
209
# Cloning the MySQL server running on localhost.# Creating new data directory...# Configuring new instance...# Locating mysql tools...# Setting up empty database and mysql tables...# Starting new instance of the server...# Testing connection to new instance...# Success!# Setting the root password...# ...done.
NOTES
Should the server fail to start due to an error in the server startup sequence, the utility presents an errormessage along with suggestions for how to identify the error. The best way to find the error is to run theutility again with verbosity turned on (using the -vvv option). This displays all of the messages from theserver setup. Examine this list to find the exact error/reason why the server did not start.
PERMISSIONS REQUIRED
The user must have permission to read all databases. Since we are using the root account for theseexamples (and you typically would), permissions are not generally a problem.
You also need permissions to create the new data directory and write data to it.
5.25 mysqlserverinfo — Display Common Diagnostic Informationfrom a Server
This utility displays critical information about a server for use in diagnosing problems. The informationdisplayed includes the following:
• Server connection information
• Server version number
• Data directory path name
• Base directory path name
• Plugin directory path name
• Configuration file location and name
• Current binary log coordinates (filename and position)
• Current relay log coordinates (filename and position)
This utility can be used to see the diagnostic information for servers that are running or offline. If you wantto see information about an offline server, the utility starts the server in read-only mode. In this case, youmust specify the --basedir, --datadir, and --start options to prevent the utility from starting anoffline server accidentally. Note: Be sure to consider the ramifications of starting an offline server on theerror and similar logs. It is best to save this information prior to running this utility.
To specify how to display output, use one of the following values with the --format option:
• grid (default)
OPTIONS
210
Display output in grid or table format like that of the mysql client command-line tool.
• csv
Display output in comma-separated values format.
• tab
Display output in tab-separated format.
• vertical
Display output in single-column format like that of the \G command for the mysql client command-linetool.
To turn off the headers for grid, csv, or tab display format, specify the --no-headers option.
To see the common default settings for the local server's configuration file, use the --show-defaultsoption. This option reads the configuration file on the machine where the utility is run, not the machine forthe host that the --server option specifies.
To run the utility against several servers, specify the --server option multiple times. In this case, theutility attempts to connect to each server and read the information.
To see the MySQL servers running on the local machine, use the --show-servers option. This shows allthe servers with their process ID and data directory. On Windows, the utility shows only the process ID andport.
OPTIONS
mysqlserverinfo accepts the following command-line options:
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --basedir=basedir
The base directory for the server. This option is required for starting an offline server.
Is also used to access server tools, such as my_print_defaults that is required to read the login-pathvalues from the login configuration file (.mylogin.cnf).
• --datadir=datadir
The data directory for the server. This option is required for starting an offline server.
• --format=format, -fformat
Specify the output display format. Permitted format values are grid, csv, tab, and vertical. The default isgrid.
• --no-headers, -h
OPTIONS
211
Do not display column headers. This option applies only for grid, csv, and tab output.
• --port-range=start:end
The port range to check for finding running servers. This option applies only to Windows and is ignoredunless --show-servers is given. The default range is 3306:3333.
• --server=server
Connection information for a server. Use this option multiple times to see information for multipleservers.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --show-defaults, -d
Display default settings for mysqld from the local configuration file. It uses my_print_defaults toobtain the options.
• --show-servers
Display information about servers running on the local host. The utility examines the host process list todetermine which servers are running.
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --start, -s
Start the server in read-only mode if it is offline. With this option, you must also give the --basedir and--datadir options.
EXAMPLES
212
• --start-timeout
Number of seconds to wait for the server to be online when started in read-only mode using the --start option. The default value is 10 seconds.
The --start-timeout option is available as of MySQL Utilities 1.2.4 / 1.3.3.
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
For the --format option, the permitted values are not case-sensitive. In addition, values may be specifiedas any unambiguous prefix of a valid value. For example, --format=g specifies the grid format. An erroroccurs if a prefix matches more than one valid value.
The path to the MySQL client tools should be included in the PATH environment variable in order to usethe authentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
EXAMPLES
To display the server information for the local server and the settings for mysqld in the configuration filewith the output in a vertical list, use this command:
shell> mysqlserverinfo --server=root:pass@localhost -d --format=vertical# Source on localhost: ... connected.************************* 1. row ************************* server: localhost:3306 version: 5.1.50-log datadir: /usr/local/mysql/data/ basedir: /usr/local/mysql-5.1.50-osx10.6-x86_64/ plugin_dir: /usr/local/mysql-5.1.50-osx10.6-x86_64/lib/plugin config_file: /etc/my.cnf binary_log: my_log.000068 binary_log_pos: 212383 relay_log: None relay_log_pos: None1 rows.
Defaults for server localhost:3306 --port=3306 --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data --server_id=5 --log-bin=my_log --general_log --slow_query_log --innodb_data_file_path=ibdata1:778M;ibdata2:50M:autoextend#...done.
PERMISSIONS REQUIRED
The permissions required include the ability to read the mysql database and to have read access to thedata directory.
mysqlslavetrx — Slave transaction skip utility
213
The user must have permissions to read the data directory or use an administrator or super user (sudo)account to obtain access to the data directory.
5.26 mysqlslavetrx — Slave transaction skip utility
This utility allows users to skip multiple transactions on slaves in a single step for gtid-enabled servers. Inparticular, it injects empty transactions on all specified slaves for each GTID in the specified GTID set.
Note
Skipping transactions can be useful to recover from erroneous situations that canoccur during the replication process. However, this technique must be applied withextreme caution and full knowledge of its consequences because it might lead todata inconsistencies between the replication servers.
For example, let's consider that a transaction that inserts some data 'row1' into table't1' fails on 'slave1'. If that transaction is simply skipped to quickly resume replicationon 'slave1' without any additional intervention, then 'row1' is missing from that slave.Moreover, 'row1' is no longer replicated from the master since the GTID for theskipped transaction is associated to an empty transaction. As a consequence, thedata for table 't1' on 'slave1' is inconsistent with the one on the master and otherslaves because 'row1' is missing. For this reason, we should make sure that thetechnique to skip transactions is applied in the right situations and that all additionaloperations to keep the data consistent are also taken.
Skipping transactions is also useful to ignore errant transactions on slaves in order to avoid thosetransactions from being replicated if a failover occurs. For example, consider that some transactions withcustom data changes were accidentally committed on a slave without turning off binary logging, and thatthose changes are specific to that slave and should not be replicated (e.g., additional data for reportingpurposes, data mining, or local administrative commands). If that slave becomes the new master as aresult of a failover or switchover, then those errant transactions start being replicated across the topology.In order to avoid this situation, errant transactions should be skipped on all slaves.
Note
An errant transaction is a transaction that exists on a slave but not on all of theslaves connected to the master. An errant transaction has a GTID associated withthe UUID of the slave to which it was committed. These type of transactions canresult from write operations performed on the slave while binary logging is enabled.By nature, these transactions should not be replicated.
It is considered poor practice to execute write operation on slave with binary loggingenabled because it creates errant transactions that can lead to unstable topologiesin failover scenarios. The best way to deal with errant transactions is to avoidwriting or applying query statements to the slave directly without turning off binarylogging first.
There are other situations like provisioning and scale out where injecting empty transaction can be a usefultechnique. See Using GTIDs for Failover and Scaleout, for more information about this scenario.
Users must specify the set of GTIDs for the transactions to skip with the --gtid-set option, and theserver connection parameters for the list of target slaves using the --slaves option.
The utility displays the GTID set that is effectively skipped for each slave. If any of the specified GTIDscorrespond to an already committed transaction on a slave, then those GTIDs are ignored for that slave
OPTIONS
214
(not skipped) because no other transaction (empty or not) can be applied with the same GTID. Users canexecute the utility in dry run mode using the --dryrun option to confirm which transactions would beskipped with the provided input values without effectively skipping them.
The utility does not require replication to be stopped. However, in some situations it is recommended. Forexample, in order to skip a transaction from the master on a slave, that slave should be stopped otherwisethe target transaction might be replicated before the execution of the skip operation and therefore notskipped as expected.
Users can also use the --verbose option to see additional information when the utility executes. Thisincludes a list of slaves not supporting GTIDs and the GTIDs of the injected transactions.
OPTIONS
mysqlslavetrx accepts the following command-line options:
• --dryrun
Execute the utility in dry-run mode, show the transactions (GTID) that would have been skipped for eachslave but without effectively skipping them. This option is useful to verify if the correct transactions areskipped.
• --gtid-set=gtid-set
Set of Global Transaction Identifiers (GTID) to skip.
• --help
Display a help message and exit.
• --license
Display license information and exit.
• --slaves=slaves_connections
Connection information for slave servers. List multiple slaves in comma-separated list.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
NOTES
215
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
NOTES
The path to the MySQL client tools should be included in the PATH environment variable in order to usethe authentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
LIMITATIONS
The utility requires all target slaves to support global transaction identifiers (GTIDs) and havegtid_mode=ON.
EXAMPLES
Skip multiple GTIDs on the specified slaves:
shell> mysqlslavetrx --gtid-set=af6b22ee-7b0b-11e4-aa8d-606720440b68:7-9 \ --slaves=user:pass@localhost:3311,user:pass@localhost:3312WARNING: Using a password on the command line interface can be insecure.## GTID set to be skipped for each server:# - localhost@3311: af6b22ee-7b0b-11e4-aa8d-606720440b68:7-9# - localhost@3312: af6b22ee-7b0b-11e4-aa8d-606720440b68:7-9## Injecting empty transactions for 'localhost:3311'...# Injecting empty transactions for 'localhost:3312'...##...done.#
Execute the utility in dryrun mode to verify which GTIDs would have been skipped on all specified slaves:
shell> mysqlslavetrx --gtid-set=af6b22ee-7b0b-11e4-aa8d-606720440b68:6-12 \ --slaves=user:pass@localhost:3311,user:pass@localhost:3312 --dryrunWARNING: Using a password on the command line interface can be insecure.#
PERMISSIONS REQUIRED
216
# WARNING: Executing utility in dry run mode (read only).## GTID set to be skipped for each server:# - localhost@3311: af6b22ee-7b0b-11e4-aa8d-606720440b68:6:10-12# - localhost@3312: af6b22ee-7b0b-11e4-aa8d-606720440b68:6:10-12## (dry run) Injecting empty transactions for 'localhost:3311'...# (dry run) Injecting empty transactions for 'localhost:3312'...##...done.#
Skip multiple GTIDs on the specified slaves using the verbose mode:
shell> mysqlslavetrx --gtid-set=af6b22ee-7b0b-11e4-aa8d-606720440b68:6-12 \ --slaves=user:pass@localhost:3311,user:pass@localhost:3312 --verboseWARNING: Using a password on the command line interface can be insecure.## GTID set to be skipped for each server:# - localhost@3311: af6b22ee-7b0b-11e4-aa8d-606720440b68:6:10-12# - localhost@3312: af6b22ee-7b0b-11e4-aa8d-606720440b68:6:10-12## Injecting empty transactions for 'localhost:3311'...# - af6b22ee-7b0b-11e4-aa8d-606720440b68:6# - af6b22ee-7b0b-11e4-aa8d-606720440b68:10# - af6b22ee-7b0b-11e4-aa8d-606720440b68:11# - af6b22ee-7b0b-11e4-aa8d-606720440b68:12# Injecting empty transactions for 'localhost:3312'...# - af6b22ee-7b0b-11e4-aa8d-606720440b68:6# - af6b22ee-7b0b-11e4-aa8d-606720440b68:10# - af6b22ee-7b0b-11e4-aa8d-606720440b68:11# - af6b22ee-7b0b-11e4-aa8d-606720440b68:12##...done.#
PERMISSIONS REQUIRED
The user used to connect to each slave must have the required permissions to inject empty transactions,more precisely the SUPER privilege is required to set the gtid_next variable.
5.27 mysqluc — Command line client for running MySQL Utilities
This utility provides a command line environment for running MySQL Utilities.
The mysqluc utility, hence console, allows users to execute any of the currently installed MySQL Utilitiescommands (the MySQL Utility scripts such as mysqluserclone). The option --utildir is used to providea path to the MySQL Utilities scripts if the location is different from where the utility is executed.
The console has a list of console or base commands. These allow the user to interact with the features ofthe console itself. The list of base commands is shown below along with a brief description.
Command Description---------------------- ---------------------------------------------------help utilities Display list of all utilities supported.help <utility> Display help for a specific utility.help | help commands Show this list.exit | quit Exit the console.set <variable>=<value> Store a variable for recall in commands.show options Display list of options specified by the user on
mysqluc — Command line client for running MySQL Utilities
217
launch.show variables Display list of variables.<ENTER> Press ENTER to execute command.<ESCAPE> Press ESCAPE to clear the command entry.<DOWN> Press DOWN to retrieve the previous command.<UP> Press UP to retrieve the next command in history.<TAB> Press TAB for type completion of utility, option, or variable names.<TAB><TAB> Press TAB twice for list of matching type completion (context sensitive).
One of the most helpful base commands is the ability to see the options for a given utility by typing 'helputility'. When the user enters this command, the console displays a list of all of the options for theutility.
The console provides tab completion for all commands, options for utilities, and user-defined variables.Tab completion for commands allows users to specify the starting N characters of a command and pressTAB to complete the command. If there are more than one command that matches the prefix, and the userpresses TAB twice, a list of all possible matches is displayed.
Tab completion for options is similar. The user must first type a valid MySQL Utility command then typesthe first N characters of a command and presses TAB, for example --verbTAB. In this case, the consolecompletes the option. For the cases where an option requires a value, the console completes the optionname and append the '=' character. Tab completion for options works for both the full name and the alias(if available). If the user presses TAB twice, the console displays a list of matching options. Pressing TABtwice immediately after typing the name of a MySQL Utility displays a list of all options for that utility.
Tab completion for variables works the same as that for options. In this case, the user must first type the'$' character then press TAB. For example, if a variable $SERVER1 exists, when the user types --server=$SERTAB, the console completes the $SERVER variable name. For cases where there are multiplevariables, pressing TAB twice displays a list of all matches to the first $+N characters. Pressing TAB twiceafter typing only the $ character displays a list of all variables.
Note
The 'mysql' prefix is optional in the console. For example, typing 'diskuTAB' in theconsole completes the command as 'diskusage '.
Executing utilities is accomplished by typing the complete command and pressing ENTER. The user doesnot have to type 'python' or provide the '.py' file extension. The console adds these if needed when thecommand is executed.
The user can also run commands using the option --execute. The value for this option is a semi-colonseparated list of commands to execute. These can be base commands or MySQL Utility commands. Theconsole executes each command and display the output. All commands to be run by the console mustappear inside a quoted string and separated by semi-colons. Commands outside of the quoted string aretreated as arguments for the mysqluc utility itself and thus ignored for execution.
Note
In the console, an error in the console or related code stop sexecuting commandsat the point of failure. Commands may also be piped into the console using amechanism such as 'echo "commands" | mysqluc'.
The console also allows users to set user-defined variables for commonly used values in options. Thesyntax is simply 'set VARNAME=VALUE'. The user can see a list of all variables by entering the 'showvariables' command. To use the values of these variables in utility commands, the user must prefix the
OPTIONS
218
value with a '$'. For example, --server=$SERVER1 substitutes the value of the SERVER1 user-definedvariable when the utility is executed.
Note
User-defined variables have a session lifetime. They are not saved from oneexecution to another in the users console.
User-defined variables may also be set by passing them as arguments to the mysqluc command. Forexample, to set the SERVER1 variable and launch the console, the user can launch the console using thiscommand.:
shell> mysqluc SERVER1=root@localhost
The user can provide any number of user-defined variables but they must contain a value and no spacesaround the '=' character. Once the console is launched, the user can see all variables using the 'showvariables' command.
OPTIONS
• --version
show program's version number and exit
• --help
show the program's help page
• --license
Display license information and exit.
• --verbose, -v
control how much information is displayed. For example, -v = verbose, -vv = more verbose, -vvv =debug
• --quiet
suppress all informational messages
• --execute commands, -e commands
Execute commands and exit. Multiple commands are separated with semi-colons.
Note
Some platforms may require double quotes around the command list.
• --utildir path
location of utilities
• --width number
Display width
NOTES
219
NOTES
Using the --execute option or piping commands to the console may require quotes or double quotes (forexample, on Windows).
EXAMPLES
To launch the console, use this command:
shell> mysqluc
The following demonstrates launching the console and running the console command 'help utilities' to seea list of all utilities supported. The console executes the command then exits.:
shell> mysqluc -e "help utilities"
Utility Description---------------- ---------------------------------------------------------mysqlindexcheck check for duplicate or redundant indexesmysqlrplcheck check replicationmysqluserclone clone a MySQL user account to one or more new usersmysqldbcompare compare databases for consistencymysqldiff compare object definitions among objects where the difference is how db1.obj1 differs from db2.obj2mysqldbcopy copy databases from one server to anothermysqlreplicate establish replication with a mastermysqldbexport export metadata and data from databasesmysqldbimport import metadata and data from filesmysqlmetagrep search metadatamysqlprocgrep search process informationmysqldiskusage show disk usage for databasesmysqlserverinfo show server informationmysqlserverclone start another instance of a running server
The following demonstrates launching the console to run several commands using the --execute option toincluding setting a variable for a server connection and executing a utility using variable substitution.
Note
It may be necessary to escape the '$' on some platforms, such as Linux.
The output below is an excerpt and is representational only:
shell> mysqluc -e "set SERVER=root@host123; mysqldiskusage --server=\$SERVER"
# Source on host123: ... connected.
NOTICE: Your user account does not have read access to the datadir. Datasizes will be calculated and actual file sizes may be omitted. Some featuresmay be unavailable.
# Database totals:+--------------------+--------------+| db_name | total |+--------------------+--------------+...| world | 0 |...+--------------------+--------------+
PERMISSIONS REQUIRED
220
Total database disk usage = 1,072,359,052 bytes or 1022.00 MB
#...done.
The following demonstrates launching the console using the commands shown above but piped into theconsole on the command line. The results are the same as above.:
shell> echo "set SERVER=root@host123; mysqldiskusage --server=\$SERVER" | mysqluc
The following demonstrates launching the console and setting variables via the command line.:
shell> mysqluc SERVER=root@host123 VAR_A=57 -e "show variables"
Variable Value-------- -----------------------------------------------------------------SERVER root@host123VAR_A 57
PERMISSIONS REQUIRED
There are no special permissions required to run mysqluc however, you must have the necessaryprivileges to execute the desired utilities. See the PERMISSIONS REQUIRED section for each commandyou wish to execute.
5.28 mysqluserclone — Clone Existing User to Create New UserThis utility uses an existing MySQL user account on one server as a template, and clones it to create oneor more new user accounts with the same privileges as the original user. The new users can be created onthe original server or a different server.
To list users for a server, specify the --list option. This prints a list of the users on the source (nodestination is needed). To control how to display list output, use one of the following values with the --format option:
• grid (default)
Display output in grid or table format like that of the mysql client command-line tool.
• csv
Display output in comma-separated values format.
• tab
Display output in tab-separated format.
• vertical
Display output in single-column format like that of the \G command for the mysql client command-linetool.
OPTIONS
mysqluserclone accepts the following command-line options:
• --help
OPTIONS
221
Display a help message and exit.
• --license
Display license information and exit.
• --destination=destination
Connection information for the destination server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --dump, -d
Display the GRANT statements to create the account rather than executing them. In this case, the utilitydoes not connect to the destination server and no --destination option is needed.
• --format=list_format, -flist_format
Specify the user display format. Permitted format values are grid, csv, tab, and vertical. The default isgrid. This option is valid only if --list is given.
• --force
Drop the new user account if it exists before creating the new account. Without this option, it is an errorto try to create an account that already exists.
• --include-global-privileges
Include privileges that match base_user@% as well as base_user@host.
• --list
List all users on the source server. With this option, a destination server need not be specified.
• --quiet, -q
Turn off all messages for quiet execution.
• --source=source
Connection information for the source server.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply this
NOTES
222
information. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --ssl-ca
The path to a file that contains a list of trusted SSL CAs.
• --ssl-cert
The name of the SSL certificate file to use for establishing a secure connection.
• --ssl-key
The name of the SSL key file to use for establishing a secure connection.
• --ssl
Specifies if the server connection requires use of SSL. If an encrypted connection cannot be established,the connection attempt fails. Default setting is 0 (SSL not required).
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug.
• --version
Display version information and exit.
NOTES
For the --format option, the permitted values are not case-sensitive. In addition, values may be specifiedas any unambiguous prefix of a valid value. For example, --format=g specifies the grid format. An erroroccurs if a prefix matches more than one valid value.
The path to the MySQL client tools should be included in the PATH environment variable in order to usethe authentication mechanism with login-paths. This permits the utility to use the my_print_defaults toolswhich is required to read the login-path values from the login configuration file (.mylogin.cnf).
When cloning users that are defined with an authentication plugin, the utility attempts to use theauthentication plugin for the destination user(s). The utility issues an error if the plugin is not on thedestination machine or is inactive and the operation is aborted. A warning is issued if a password isassigned to a new user when the source user has an authentication plugin. In this case, the utility uses thepassword and not the authentication plugin for the new user.
EXAMPLES
To clone joe as sam and sally with passwords and logging in as root on the local machine, use thiscommand:
PERMISSIONS REQUIRED
223
shell> mysqluserclone --source=root@localhost \ --destination=root@localhost \ joe@localhost sam:secret1@localhost sally:secret2@localhost# Source on localhost: ... connected.# Destination on localhost: ... connected.# Cloning 2 users...# Cloning joe@localhost to user sam:secret1@localhost# Cloning joe@localhost to user sally:secret2@localhost# ...done.
The following command shows all users on the local server in the most verbose output in CSV format:
shell> mysqluserclone --source=root@localhost --list --format=csv -vvv# Source on localhost: ... connected.user,host,databasejoe,localhost,util_testrpl,localhost,sally,localhost,util_testsam,localhost,util_testjoe,user,util_test
PERMISSIONS REQUIRED
The account used on the source server must have privileges to read the mysql database. The accountused to connect to the destination server must have privileges to execute CREATE USER (and DROPUSER if the --force option is given), and privileges to execute GRANT for all privileges to be granted tothe new accounts.
224
225
Chapter 6 Extending MySQL Utilities
Table of Contents6.1 Introduction to extending the MySQL Utilities ............................................................................. 2256.2 MySQL Utilities copy_server.py sample ..................................................................................... 2316.3 Specialized Operations ............................................................................................................. 234
6.3.1 mysql.utilities.command.grep — Search Databases for Objects ........................... 2346.3.2 mysql.utilities.command.proc — Search Processes on Servers ............................ 235
6.4 Parsers .................................................................................................................................... 2376.4.1 mysql.utilities.parser — Parse MySQL Log Files .............................................................. 237
This chapter introduces the architecture for the MySQL Utilities library and demonstrates how to get startedbuilding your own utilities.
6.1 Introduction to extending the MySQL UtilitiesAdministration and maintenance on the MySQL server can at times be complicated. Sometimes tasksrequire tedious or even repetitive operations that can be time consuming to type and re-type. For thesereasons and more, the MySQL Utilities were created to help both beginners and experienced databaseadministrators perform common tasks.
What are the internals of the MySQL Utilities?
MySQL Utilities are designed as a collection of easy to use Python scripts that can be combined to providemore powerful features. Internally, the scripts use the mysql.utilities module library to perform its varioustasks. Since a library of common functions is available, it is easy for a database administrator to createscripts for common tasks. These utilities are located in the /scripts folder of the installation or sourcetree.
If you have a task that is not met by these utilities or one that can be met by combining one or more ofthe utilities or even parts of the utilities, you can easily form your own custom solution. The followingsections present an example of a custom utility, discussing first the anatomy of a utility and then what themysql.utilities module library has available.
Anatomy of a MySQL Utility
MySQL Utilities use a three-tier module organization. At the top is the command script, which resides in the/scripts folder of the installation or source tree. Included in the script is a command module designed toencapsulate and isolate the bulk of the work performed by the utility. The command module resides in the/mysql/utilities/command folder of the source tree. Command modules have names similar to thescript. A command module includes classes and methods from one or more common modules where theabstract objects and method groups are kept. The common modules reside in the /mysql/utilities/common folder of the source tree. The following illustrates this arrangement using the mysqlserverinfoutility:
/scripts/mysqlserverinfo.py | +--- /mysql/utilities/command/serverinfo.py | +--- /mysql/utilities/common/options.py | +--- /mysql/utilities/common/server.py | +--- /mysql/utilities/common/tools.py
The MySQL Utilities Library
226
| +--- /mysql/utilities/common/format.py
Each utility script is designed to process the user input and option settings and pass them on to thecommand module. Thus, the script contains only such logic for managing and validating options. The workof the operation resides in the command module.
Command modules are designed to be used from other Python applications. For example, one couldcall the methods in the serverinfo.py module from another Python script. This enables developers tocreate their own interfaces to the utilities. It also permits developers to combine several utilities to form amacro-level utility tailored to a specified need. For example, if there is a need to gather server informationas well as disk usage, it is possible to import the serverinfo.py and diskusage.py modules andcreate a new utility that performs both operations.
Common modules are the heart of the MySQL Utilities library. These modules contain classes that abstractMySQL objects, devices, and mechanisms. For example, there is a server class that contains operations tobe performed on servers, such as connecting (logging in) and running queries.
The MySQL Utilities Library
Although the library is growing, the following lists the current common modules and the major classes andmethods as of the 1.0.1 release:
Module Class/Method Description---------- ------------------------- ----------------------------------------database Database Perform database-level operationsdbcompare get_create_object Retrieve object create statement diff_objects Diff definitions of two objects check_consistency Check data consistency of two tablesformat format_tabular_list Format list in either GRID or delimited format to a file format_vertical_list Format list in a vertical format to a file print_list Print list based on format (CSV, GRID, TAB, or VERTICAL)options setup_common_options Set up option parser and options common to all MySQL Utilities add_skip_options Add common --skip options check_skip_options Check skip options for validity check_format_option Check format option for validity add_verbosity Add verbosity and quiet options check_verbosity Check whether both verbosity and quiet options are being used add_difftype Add difftype option add_engines Add engine, default-storage-engine options check_engine_options Check whether storage engines listed in options exist parse_connection Parse connection valuesrpl Replication Establish replication connection between a master and a slave get_replication_tests Return list of replication test function pointersserver get_connection_dictionary Get connection dictionary find_running_servers Check whether any servers are running on the local host connect_servers Connect to source and destination server Server Connect to running MySQL server and perform server-level operationstable Index Encapsulate index for a given table as defined by SHOW INDEXES Table Encapsulate table for given database to perform table-level operationstools get_tool_path Search for MySQL tool and return its
General Interface Specifications and Code Practices
227
full path delete_directory Remove directory (folder) and contentsuser parse_user_host Parse user, passwd, host, port from user:passwd@host User Clone user and its grants to another user and perform user-level operations
General Interface Specifications and Code Practices
The MySQL Utilities are designed and coded using mainstream coding practices and techniques commonto the Python community. Effort has been made to adhere to the most widely accepted specifications andtechniques. This includes limiting the choice of libraries used to the default libraries found in the Pythondistributions. This ensures easier installation, enhanced portability, and fewer problems with missinglibraries. Similarly, external libraries that resort to platform-specific native code are also not used.
The class method and function signatures are designed to make use of a small number of requiredparameters and all optional parameters as a single dictionary. Consider the following method:
def do_something_wonderful(position, obj1, obj2, options={}): """Does something wonderful
A fictional method that does something to object 2 based on the location of something in object 1.
position[in] Position in obj1 obj1[in] First object to manipulate obj2[in] Second object to manipulate options[in] Option dictionary width width of printout (default 75) iter max iterations (default 2) ok_to_fail if True, do not throw exception (default True)
Returns bool - True = success, Fail = failed """
This example is typical of the methods and classes in the library. Notice that this method has threerequired parameters and a dictionary of options that may exist.
Each method and function that uses this mechanism defines its own default values for the items in thedictionary. A quick look at the method documentation shows the key names for the dictionary. This can beseen in the preceding example where the dictionary contains three keys and the documentation lists theirdefaults.
To call this method and pass different values for one or more of the options, the code may look like this:
opt_dictionary = { 'width' : 100, 'iter' : 10, 'ok_to_fail' : False,}result = do_something_wonderful(1, obj_1, obj_2, opt_dictionary)
The documentation block for the preceding method is the style used throughout the library.
Example
Now that you are familiar with the MySQL utilities and the supporting library modules, let us take a look atan example that combines some of these modules to solve a problem.
Suppose that you want to develop a new database solution and need to use real world data and useraccounts for testing. The mysqlserverclone MySQL utility looks like a possibility but it makes only an
Example
228
instance of a running server. It does not copy data. However, mysqldbcopy makes a copy of the dataand mysqluserclone clones the users. You could run each of these utilities in sequence, and that wouldwork, but we are lazy at heart and want something that not only copies everything but also finds it for us.That is, we want a one-command solution.
The good news is that this is indeed possible and very easy to do. Let us start by breaking the problemdown into its smaller components. In a nutshell, we must perform these tasks:
• Connect to the original server
• Find all of the databases
• Find all of the users
• Make a clone of the original server
• Copy all of the databases
• Copy all of the users
If you look at the utilities and the modules just listed, you see that we have solutions and primitives for eachof these operations. So you need not even call the MySQL utilities directly (although you could). Now let usdive into the code for this example.
The first task is to connect to the original server. We use the same connection mechanism as the otherMySQL utilities by specifying a --server option like this:
parser.add_option("--server", action="store", dest="server", type="string", default="root@localhost:3306", help="connection information for original server in " + \ "the form: user:password@host:port:socket")
Once we process the options and arguments, connecting to the server is easy: Use theparse_connection method to take the server option values and get a dictionary with the connectionvalues. All of the heavy diagnosis and error handling is done for us, so we just need to check forexceptions:
from mysql.utilities.common.options import parse_connection
try: conn = parse_connection(opt.server)except: parser.error("Server connection values invalid or cannot be parsed.")
Now that we have the connection parameters, we create a class instance of the server using the Serverclass from the server module and then connect. Once again, we check for exceptions:
from mysql.utilities.common.server import Server
server_options = { 'conn_info' : conn, 'role' : "source",}server1 = Server(server_options)try: server1.connect()except UtilError, e: print "ERROR:", e.errmsg
The next item is to get a list of all of the databases on the server. We use the new server class instance toretrieve all of the databases on the server:
db_list = []
Example
229
for db in server1.get_all_databases(): db_list.append((db[0], None))
If you wanted to supply your own list of databases, you could use an option like the following. You couldalso add an else clause which would enable you to either get all of the databases by omitting the --databases option or supply your own list of databases (for example, --databases=db1,db2,db3):
parser.add_option("-d", "--databases", action="store", dest="dbs_to_copy", type="string", help="comma-separated list of databases " "to include in the copy (omit for all databases)", default=None)
if opt.dbs_to_copy is None: for db in server1.get_all_databases(): db_list.append((db[0], None))else: for db in opt.dbs_to_copy.split(","): db_list.append((db, None))
Notice we are creating a list of tuples. This is because the dbcopy module uses a list of tuples in the form(old_db, new_db) to enable you to copy a database to a new name. For our purposes, we do not want arename so we leave the new name value set to None.
Next, we want a list of all of the users. Once again, you could construct the new solution to be flexible bypermitting the user to specify the users to copy. We leave this as an exercise.
In this case, we do not have a primitive for getting all users created on a server. But we do have the abilityto run a query and process the results. Fortunately, there is a simple SQL statement that can retrieve all ofthe users on a server. For our purposes, we get all of the users except the root and anonymous users, thenadd each to a list for processing later:
users = server1.exec_query("SELECT user, host " "FROM mysql.user " "WHERE user != 'root' and user != ''")for user in users: user_list.append(user[0]+'@'+user[1])
Now we must clone the original server and create a viable running instance. When you examinethe mysqlserverclone utility code, you see that it calls another module located in the /mysql/utilities/command sub folder. These modules are where all of the work done by the utilities take place.This enables you to create new combinations of the utilities by calling the actual operations directly. Let'sdo that now to clone the server.
The first thing you notice in examining the serverclone module is that it takes a number of parametersfor the new server instance. We supply those in a similar way as options:
parser.add_option("--new-data", action="store", dest="new_data", type="string", help="the full path to the location " "of the data directory for the new instance")parser.add_option("--new-port", action="store", dest="new_port", type="string", default="3307", help="the new port " "for the new instance - default=%default")parser.add_option("--new-id", action="store", dest="new_id", type="string", default="2", help="the server_id for " "the new instance - default=%default")
from mysql.utilities.command import serverclone
try: res = serverclone.clone_server(conn, opt.new_data, opt.new_port, opt.new_id, "root", None, False, True)except exception.UtilError, e: print "ERROR:", e.errmsg sys.exit()
Example
230
As you can see, the operation is very simple. We just added a few options we needed like --new-data,--new-port, and --new-id (much like mysqlserverclone) and supplied some default values for theother parameters.
Next, we need to copy the databases. Once again, we use the command module for mysqldbcopy to doall of the work for us. First, we need the connection parameters for the new instance. This is provided inthe form of a dictionary. We know the instance is a clone, so some of the values are going to be the sameand we use a default root password, so that is also known. Likewise, we specified the data directory and,since we are running on a Linux machine, we know what the socket path is. (For Windows machines, youcan leave the socket value None.) We pass this dictionary to the copy method:
dest_values = { "user" : conn.get("user"), "passwd" : "root", "host" : conn.get("host"), "port" : opt.new_port, "unix_socket" : os.path.join(opt.new_data, "mysql.sock")}
In this case, a number of options are needed to control how the copy works (for example, if any objects areskipped). For our purposes, we want all objects to be copied so we supply only the minimal settings and letthe library use the defaults. This example shows how you can 'fine tune' the scripts to meet your specificneeds without having to specify a lot of additional options in your script. We enable the quiet option on soas not to clutter the screen with messages, and tell the copy to skip databases that do not exist (in case wesupply the --databases option and provide a database that does not exist):
options = { "quiet" : True, "force" : True}
The actual copy of the databases is easy. Just call the method and supply the list of databases:
from mysql.utilities.command import dbcopy
try: dbcopy.copy_db(conn, dest_values, db_list, options)except exception.UtilError, e: print "ERROR:", e.errmsg sys.exit()
Lastly, we copy the user accounts. Once again, we must provide a dictionary of options and call thecommand module directly. In this case, the userclone module provides a method that clones one user toone or more users so we must loop through the users and clone them one at a time:
from mysql.utilities.command import userclone
options = { "overwrite" : True, "quiet" : True, "globals" : True}
for user in user_list: try: res = userclone.clone_user(conn, dest_values, user, (user,), options) except exception.UtilError, e: print "ERROR:", e.errmsg sys.exit()
We are done. As you can see, constructing new solutions from the MySQL utility command and commonmodules is easy and is limited only by your imagination.
Enhancing the Example
231
Enhancing the Example
A complete solution for the example named copy_server.py is located in the appendix. It is completein so far as this document explains, but it can be enhanced in a number of ways. The following briefly listssome of the things to consider adding to make this example utility more robust.
• Table locking: Currently, databases are not locked when copied. To achieve a consistent copy of thedata on an active server, you may want to add table locking or use transactions (for example, if you areusing InnoDB) for a more consistent copy.
• Skip users not associated with the databases being copied.
• Do not copy users with only global privileges.
• Start replication after all of the users are copied (makes this example a clone and replicate scale outsolution).
• Stop new client connections to the server during the copy.
Conclusion
If you find some primitives missing or would like to see more specific functionality in the library or scripts,please contact us with your ideas or better still, write them yourselves! We welcome all suggestions incode or text. To file a feature request or bug report, visit http://bugs.mysql.com. For discussions, visit http://forums.mysql.com/list.php?155.
6.2 MySQL Utilities copy_server.py sample
## Copyright (c) 2010, 2013, Oracle and/or its affiliates. All rights reserved.## This program is free software; you can redistribute it and/or modify# it under the terms of the GNU General Public License as published by# the Free Software Foundation; version 2 of the License.## This program is distributed in the hope that it will be useful,# but WITHOUT ANY WARRANTY; without even the implied warranty of# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the# GNU General Public License for more details.## You should have received a copy of the GNU General Public License# along with this program; if not, write to the Free Software# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA#
"""This file contains an example of how to build a customized utility usingthe MySQL Utilities scripts and libraries."""
import optparseimport osimport sys
from mysql.utilities import VERSION_FRMfrom mysql.utilities.command import dbcopyfrom mysql.utilities.command import serverclonefrom mysql.utilities.command import userclonefrom mysql.utilities.common.server import Serverfrom mysql.utilities.common.options import parse_connection
MySQL Utilities copy_server.py sample
232
from mysql.utilities.exception import UtilError
# ConstantsNAME = "example - copy_server "DESCRIPTION = "copy_server - copy an existing server"USAGE = "%prog --server=user:pass@host:port:socket " \ "--new-dir=<path> --new-id=<server_id> " \ "--new-port=<port> --databases=<db list> " \ "--users=<user list>"
# Setup the command parserparser = optparse.OptionParser( version=VERSION_FRM.format(program=os.path.basename(sys.argv[0])), description=DESCRIPTION, usage=USAGE, add_help_option=False)parser.add_option("--help", action="help")
# Setup utility-specific options:
# Connection information for the source serverparser.add_option("--server", action="store", dest="server", type="string", default="root@localhost:3306", help="connection information for original server in " + \ "the form: <user>:<password>@<host>:<port>:<socket>")
# Data directory for new instanceparser.add_option("--new-data", action="store", dest="new_data", type="string", help="the full path to the location " "of the data directory for the new instance")
# Port for the new instanceparser.add_option("--new-port", action="store", dest="new_port", type="string", default="3307", help="the new port " "for the new instance - default=%default")
# Server id for the new instanceparser.add_option("--new-id", action="store", dest="new_id", type="string", default="2", help="the server_id for " "the new instance - default=%default")
# List of databasesparser.add_option("-d", "--databases", action="store", dest="dbs_to_copy", type="string", help="comma-separated list of databases " "to include in the copy (omit for all databases)", default=None)
# List of usersparser.add_option("-u", "--users", action="store", dest="users_to_copy", type="string", help="comma-separated list of users " "to include in the copy (omit for all users)", default=None)
# Now we process the rest of the arguments.opt, args = parser.parse_args()
# Parse source connection valuestry: conn = parse_connection(opt.server)except: parser.error("Server connection values invalid or cannot be parsed.")
# Get a server class instanceprint "# Connecting to server..."server_options = { 'conn_info' : conn, 'role' : "source",
MySQL Utilities copy_server.py sample
233
}server1 = Server(server_options)try: server1.connect()except UtilError, e: print "ERROR:", e.errmsg
# Get list of databases from the server if not specified in optionsprint "# Getting databases..."db_list = []if opt.dbs_to_copy is None: for db in server1.get_all_databases(): db_list.append((db[0], None))else: for db in opt.dbs_to_copy.split(","): db_list.append((db, None))
# Get list of all users from the serverprint "# Getting users..."user_list=[]if opt.users_to_copy is None: users = server1.exec_query("SELECT user, host " "FROM mysql.user " "WHERE user != 'root' and user != ''") for user in users: user_list.append(user[0]+'@'+user[1])else: for user in opt.users_to_copy.split(","): user_list.append(user)
# Build optionsoptions = { 'new_data' : opt.new_data, 'new_port' : opt.new_port, 'new_id' : opt.new_id, 'root_pass' : 'root', 'mysqld_options' : '--report-host=localhost --report-port=%s' % opt.new_port,}
# Clone the serverprint "# Cloning server instance..."try: res = serverclone.clone_server(conn, options)except UtilError, e: print "ERROR:", e.errmsg sys.exit()
# Set connection valuesdest_values = { "user" : conn.get("user"), "passwd" : "root", "host" : conn.get("host"), "port" : opt.new_port, "unix_socket" : os.path.join(opt.new_data, "mysql.sock")}
# Build dictionary of optionsoptions = { "quiet" : True, "force" : True}
print "# Copying databases..."try: dbcopy.copy_db(conn, dest_values, db_list, options)except UtilError, e: print "ERROR:", e.errmsg
Specialized Operations
234
sys.exit()
# Build dictionary of optionsoptions = { "overwrite" : True, "quiet" : True, "globals" : True}
print "# Cloning the users..."for user in user_list: try: res = userclone.clone_user(conn, dest_values, user, (user,), options) except UtilError, e: print "ERROR:", e.errmsg sys.exit()
print "# ...done."
6.3 Specialized Operations
6.3.1 mysql.utilities.command.grep — Search Databases for Objects
This module provides utilities to search for objects on a server. The module defines a set of object types tobe searched. Searches target the fields of each object. The notion of an object field is very loosely definedand means any names occurring as part of the object definition. For example, the fields of a table includethe table name, the column names, and the partition names (if it is a partitioned table).
Constants
The following constants denote the object types that can be searched.
• mysql.utilities.command.grep.ROUTINE
• mysql.utilities.command.grep.EVENT
• mysql.utilities.command.grep.TRIGGER
• mysql.utilities.command.grep.TABLE
• mysql.utilities.command.grep.DATABASE
• mysql.utilities.command.grep.VIEW
• mysql.utilities.command.grep.USER
The following constant is a sequence of all the object types that are available. It can be used to generate aversion-independent list of object types that can be searched; for example, options and help texts.
• mysql.utilities.command.grep.OBJECT_TYPES
Classes
class mysql.utilities.command.grep.ObjectGrep(pattern[, database_pattern=None,types=OBJECT_TYPES, check_body=False, use_regexp=False])
Search MySQL server instances for objects where the name (or content, for routines, triggers, or events)matches a given pattern.
mysql.utilities.command.proc — Search Processes on Servers
235
sql() - string
Return the SQL code for executing the search in the form of a SELECT statement.
Returns:
SQL code for executing the operation specified by the options.
Return type:
string
execute(connections[, output=sys.output, connector=mysql.connector])
Execute the search on each of the connections in turn and print an aggregate of the result as a grid table.
Parameters:
• connections
Sequence of connection specifiers to send the query to
• output
File object to use for writing the result
• connector
Connector to use for connecting to the servers
6.3.2 mysql.utilities.command.proc — Search Processes on Servers
This module searches processes on a server and optionally kills either the query or the connection for allmatches.
Processes are matched by searching the fields of the INFORMATION_SCHEMA.PROCESSLIST table.Internally, the module operates by constructing a SELECT statement for finding matching processes, andthen sending it to the server. Instead of performing the search, the module can return the SQL code thatperforms the query. This can be useful if you want to execute the query later or feed it to some otherprogram that processes SQL queries further.
Constants
The following constants correspond to fields in the INFORMATION_SCHEMA.PROCESSLIST table. Theyindicate which columns to examine when searching for processes matching the search conditions.
• mysql.utilities.command.proc.ID
• mysql.utilities.command.proc.USER
• mysql.utilities.command.proc.HOST
• mysql.utilities.command.proc.DB
• mysql.utilities.command.proc.COMMAND
• mysql.utilities.command.proc.TIME
mysql.utilities.command.proc — Search Processes on Servers
236
• mysql.utilities.command.proc.STATE
• mysql.utilities.command.proc.INFO
The following constants indicate actions to perform on processes that match the search conditions.
• mysql.utilities.command.proc.KILL_QUERY
Kill the process query
• mysql.utilities.command.proc.KILL_CONNECTION
Kill the process connection
• mysql.utilities.command.proc.PRINT_PROCESS
Print the processes
Classes
class mysql.utilities.command.proc.ProcessGrep(matches, actions=[], use_regexp=False)
This class searches the INFORMATION_SCHEMA.PROCESSLIST table for processes on MySQL serversand optionally kills them. It can be used to perform a search (and optionally kill), or to generate the SQLstatement for doing the same.
For example, to kill all queries with user 'mats', use the following code:
>>> from mysql.utilities.command.proc import *>>> grep = ProcessGrep(matches=[(USER, "mats")], actions=[KILL_QUERY])>>> grep.execute("[email protected]", "[email protected]")
Parameters:
• matches (List of (var, pat) pairs)
Sequence of field comparison conditions. In each condition, var is one of the constants listed earlier thatspecify PROCESSLIST table fields and pat is a pattern. For a process to match, all field conditions mustmatch.
sql([only_body=False])
Return the SQL code for executing the search (and optionally, the kill).
If only_body is True, only the body of the function is shown. This is useful if the SQL code is to be usedwith other utilities that generate the routine declaration. If only_body is False, a complete procedure isgenerated if there is any kill action supplied, and just a SELECT statement if it is a plain search.
Parameters:
• only_body (boolean)
Show only the body of the procedure. If this is False, a complete procedure is returned.
Returns:
SQL code for executing the operation specified by the options.
Return type:
Parsers
237
string
execute(connections, ...[, output=sys.stdout, connector=mysql.connector])
Execute the search on each of the connections supplied. If output is not None, the value is treated as afile object and the result of the execution is printed on that stream. Note that the output and connectorarguments must be supplied as keyword arguments. All other arguments are treated as connectionspecifiers.
Parameters:
• connections
Sequence of connection specifiers to send the search to
• output
File object to use for writing the result
• connector
Connector to use for connecting to the servers
6.4 Parsers
6.4.1 mysql.utilities.parser — Parse MySQL Log Files
This module provides classes for parsing MySQL log files. Currently, Slow Query Log and General QueryLog are supported.
Classes
class mysql.utilities.parser.GeneralQueryLog(stream)
This class parses the MySQL General Query Log. Instances support iteration, but the class does notprovide multiple independent iterators.
For example, to read the log and print the entries:
>>> general_log = open("/var/lib/mysql/mysql.log")>>> log = GeneralQueryLog(general_log)>>> for entry in log:... print entry
Parameters:
• stream (file type)
A valid file type; for example, the result of the built-in Python function open().
version
Returns:
Version of the MySQL server that produced the log
Return type:
mysql.utilities.parser — Parse MySQL Log Files
238
tuple
program
Returns:
Full path of the MySQL server executable
Return type:
str
port
Returns:
TCP/IP port on which the MySQL server was listening
Return type:
int
socket
Returns:
Full path of the MySQL server Unix socket
Return type:
str
start_datetime
Returns:
Date and time of the first read log entry
Return type:
datetime.datetime
lastseen_datetime
Returns:
Date and time of the last read log entry
Return type:
datetime.datetime
class mysql.utilities.parser.SlowQueryLog(stream)
This class parses the MySQL Slow Query Log. Instances support iteration, but the class does not providemultiple independent iterators.
For example, to read the log and print the entries:
mysql.utilities.parser — Parse MySQL Log Files
239
>>> slow_log = open("/var/lib/mysql/mysql-slow.log")>>> log = SlowQueryLog(slow_log)>>> for entry in log:... print entry
Parameters:
• stream (file type)
A valid file type; for example, the result of the built-in Python function open().
version
Returns:
Version of the MySQL server that produced the log
Return type:
tuple
program
Returns:
Full path of the MySQL server executable
Return type:
str
port
Returns:
TCP/IP port on which the MySQL server was listening
Return type:
int
socket
Returns:
Full path of the MySQL server Unix socket
Return type:
str
start_datetime
Returns:
Date and time of the first read log entry
Return type:
datetime.datetime
mysql.utilities.parser — Parse MySQL Log Files
240
lastseen_datetime
Returns:
Date and time of the last read log entry
Return type:
datetime.datetime
241
Chapter 7 MySQL Utilities Testing (MUT)
Table of Contents7.1 mut — MySQL Utilities Testing ................................................................................................. 241
7.1 mut — MySQL Utilities TestingThis utility executes predefined tests to test the MySQL Utilities. The tests are located under the /mysql-test directory with the default tests located in the /t folder. The utility supports dividing tests into suites,which are stored as folders with their own /t folder for the test files. Those tests located in the base /tfolder are considered the 'main' test suite.
You can select any number of tests to run, select one or more suites to restrict the tests, exclude suitesand tests, and specify the location of the utilities and tests. The utility attempts to locate the tests basedon name in any of the suites in the /suites folder with the exception of a special test suite named'performance' where performance-related tests are placed. This suite is not included by default and mustbe specified with the --suite option to execute the performance tests.
The utility requires the existence of at least one server to clone for testing purposes. You must specify atleast one server, but you may specify multiple servers for tests designed to use additional servers.
OPTIONS
mut accepts the following command-line options:
• --help
Display a help message and exit.
• --do-tests=prefix
Execute all tests that begin with prefix.
• --force
Do not abort when a test fails.
• --record
Record the output of the specified test if successful. With this option, you must specify exactly one test torun.
• --server=server
Connection information for the server to use in the tests. Use this option multiple times to specify multipleservers.
To connect to a server, it is necessary to specify connection parameters such as the user name, hostname, password, and either a port or socket. MySQL Utilities provides a number of ways to supply thisinformation. All of the methods require specifying your choice via a command-line option such as --server, --master, --slave, etc. The methods include the following in order of most secure to least secure.
• Use login-paths from your .mylogin.cnf file (encrypted, not visible). Example : login-path[:port][:socket]
OPTIONS
242
• Use a configuration file (unencrypted, not visible) Note: available in release-1.5.0. Example :configuration-file-path[:section]
• Specify the data on the command-line (unencrypted, visible). Example : user[:passwd]@host[:port][:socket]
• --skip-long
Exclude tests that require greater resources or take a long time to run.
• --skip-suite=name
Exclude the named test suite. Use this option multiple times to specify multiple suites.
• --skip-test=name
Exclude the named test. Use this option multiple times to specify multiple tests.
• --skip-tests=prefix
Exclude all tests that begin with prefix.
• --sort
Execute tests sorted by suite.name either ascending (asc) or descending (desc). Default is ascending(asc).
• --start-port=port
The first port to use for spawned servers. If you run the entire test suite, you may see up to 12 newinstances created. The default is to use ports 3310 to 3321.
• --start-test=prefix
Start executing tests that begin with prefix.
• --stop-test=prefix
Stop executing tests at the first test that begins with prefix.
• --suite=name
Execute the named test suite. Use this option multiple times to specify multiple suites.
• --testdir=path
The path to the test directory. Note that the path is appended with a folder named 't' and result files areexpected to reside in a folder named 'r', both are sub folders of the path specified for this option.
• --utildir=path
The location of the utilities.
• --verbose, -v
Specify how much information to display. Use this option multiple times to increase the amount ofinformation. For example, -v = verbose, -vv = more verbose, -vvv = debug. To diagnose testexecution problems, use -vvv to display the actual results of test cases and ignore result processing.
NOTES
243
• --version
Display version information and exit.
• --width=number
Specify the display width. The default is 75 characters.
NOTES
The connection specifier must name a valid account for the server.
Any test named ???_template.py is skipped. This enables the developer to create a base class to importfor a collection of tests based on a common code base.
EXAMPLES
The following example demonstrates how to invoke mut to execute a subset of the tests using an existingserver which is cloned. The example displays the test name, status, and relative time:
shell> mut --server=root@localhost --do-tests=clone_user --width=70
MySQL Utilities Testing - MUT
Parameters used: Display Width = 70 Sorted = True Force = False Test directory = './t' Utilities directory = '../scripts' Starting port = 3310 Test wildcard = 'clone_user%'
Servers: Connecting to localhost as user root on port 3306: CONNECTED
----------------------------------------------------------------------TEST NAME STATUS TIME======================================================================main.clone_user [pass] 54main.clone_user_errors [pass] 27main.clone_user_parameters [pass] 17----------------------------------------------------------------------Testing completed: Friday 03 December 2010 09:50:06
All 3 tests passed.
PERMISSIONS REQUIRED
There are no special permissions required to run mut however, you must have the necessary privileges toexecute the desired utilities in the tests.
244
245
Chapter 8 Appendix
Table of Contents8.1 MySQL Utilities Frequently Asked Questions .............................................................................. 245
This chapter includes additional information about MySQL Utilities including a list of frequently askedquestions.
Licensing information. This product may include third-party software, used under license. If you areusing a Commercial release of MySQL Utilities, see the MySQL Utilities Commercial License InformationUser Manual for licensing information, including licensing information relating to third-party software thatmay be included in this Commercial release. If you are using a Community release of MySQL Utilities,see the MySQL Utilities Community License Information User Manual for licensing information, includinglicensing information relating to third-party software that may be included in this Community release.
8.1 MySQL Utilities Frequently Asked Questions
FAQ Categories
• General Questions
• Storage Engine Questions
• The mysqlfrm Utility: .frm File Reader Questions
General
8.1.1 Are these utilities present in the community version of MySQL? ............................................... 245
8.1.1. Are these utilities present in the community version of MySQL?
Yes, see Chapter 1, How to Install MySQL Utilities.
Storage Engines
8.1.1 Can the utilities be used with MyISAM or CSV? ...................................................................... 245
8.1.1. Can the utilities be used with MyISAM or CSV?
Yes. There are no storage engine specific limitations in using the utilities. There are some featureswritten specifically for InnoDB so those may not apply but in general no utility is storage enginespecific. For example, the mysqldiskusage utility shows exact sizes for MyISAM and InnoDB filesbut uses estimated sizes for any other storage engine based on number of rows and row size.
The mysqlfrm Utility: .frm File Reader
8.1.1 Can the .frm reader read a .frm file without the associated data files? ....................................... 2468.1.2 Will the .frm reader modify my original .frm file? ...................................................................... 2468.1.3 What is diagnostic mode and why doesn't it produce the same output as the default mode? ........ 2468.1.4 If the diagnostic mode is only a best-effort compilation, why use it? .......................................... 2468.1.5 Why does the default mode require a server? ......................................................................... 2468.1.6 Can the .frm reader read any .frm file? ................................................................................... 246
MySQL Utilities Frequently Asked Questions
246
8.1.7 My .frm files are tucked away in a restricted folder. How do I get access to them to run the .frmreader without copying or modifying file privileges? ................................................................ 246
8.1.8 Will the default mode display a 100% accurate CREATE statement? ........................................ 246
8.1.1. Can the .frm reader read a .frm file without the associated data files?
Yes! The .frm reader was designed to read the contents of an .frm file without requiring the datafiles.
8.1.2. Will the .frm reader modify my original .frm file?
No, it does not modify the original .frm file in either default or diagnostic mode.
8.1.3. What is diagnostic mode and why doesn't it produce the same output as the default mode?
The diagnostic mode does not use a spawned server to read the .frm file. Instead, it attempts toread the contents of the file byte-by-byte and forms a best-effort approximation of the CREATEstatement. Due to the many complexities of the server code, the diagnostic mode does not currentlyprocess all features of a table. Future revisions will improve the accuracy of the diagnostic mode.
8.1.4. If the diagnostic mode is only a best-effort compilation, why use it?
The diagnostic mode is used to attempt to read corrupt or otherwise damaged .frm files. You wouldalso use it if you had no access to a server installation on the local machine.
8.1.5. Why does the default mode require a server?
The default mode uses a server to create a temporary working copy of the server instance. It doesnot access the donor server in any way other than to execute the mysqld[.exe] process.
8.1.6. Can the .frm reader read any .frm file?
Although it can read most .frm files, there are known limits to which storage engines it can processcorrectly. Currently, tables with storage engines partition and performance_schema cannot be read.However, these .frm files can be read by the diagnostic mode,
8.1.7. My .frm files are tucked away in a restricted folder. How do I get access to them to run the .frmreader without copying or modifying file privileges?
You can use elevated privileges such as su or sudo to execute the .frm reader. You must use the --user option to specify a user to launch the spawned server, however. This will permit the .frm readerto read the original .frm file and copy it to the spawned server and access the copy without requiringadditional privileges.
8.1.8. Will the default mode display a 100% accurate CREATE statement?
For most tables and all views, yes. However, there are at least two features that are not stored inthe .frm file and therefore will not be included. These are autoincrement values and foreign keys.That being said, the CREATE statement produced will be syntactically correct.
247
Index
Ccommands, 234, 235
FFAQs, 245
Mmut, 241mysql.utilities.command.grep, 234mysql.utilities.command.proc, 235mysqlauditadmin, 69mysqlauditgrep, 75mysqlbinlogmove, 82mysqlbinlogpurge, 89mysqlbinlogrotate, 92mysqldbcompare, 94mysqldbcopy, 103mysqldbexport, 110mysqldbimport, 119mysqldiff, 125mysqldiskusage, 131mysqlfailover, 134mysqlfrm, 146mysqlgrants, 150mysqlindexcheck, 157mysqlmetagrep, 160mysqlprocgrep, 165mysqlreplicate, 169mysqlrpladmin, 178mysqlrplcheck, 190mysqlrplms, 173mysqlrplshow, 194mysqlrplsync, 199mysqlserverclone, 206mysqlserverinfo, 209mysqlslavetrx, 213mysqluc, 216mysqluserclone, 220
Sscripts, 69, 75, 82, 89, 92, 94, 103, 110, 119, 125, 131,135, 146, 150, 157, 160, 165, 169, 173, 178, 190, 194,199, 206, 209, 213, 216, 220, 241
Uutilities
mut, 241mysql.utilities.command.grep, 234mysql.utilities.command.proc, 235mysqlauditadmin, 69
mysqlauditgrep, 75mysqlbinlogmove, 82mysqlbinlogpurge, 89mysqlbinlogrotate, 92mysqldbcompare, 94mysqldbcopy, 103mysqldbexport, 110mysqldbimport, 119mysqldiff, 125mysqldiskusage, 131mysqlfailover, 135mysqlfrm, 146mysqlgrants, 150mysqlindexcheck, 157mysqlmetagrep, 160mysqlprocgrep, 165mysqlreplicate, 169mysqlrpladmin, 178mysqlrplcheck, 190mysqlrplms, 173mysqlrplshow, 194mysqlrplsync, 199mysqlserverclone, 206mysqlserverinfo, 209mysqlslavetrx, 213mysqluc, 216mysqluserclone, 220
248
