After installing MySQL, you must initialize the data directory,
including the tables in the
database. For some MySQL installation methods, data directory
initialization may be done automatically, as described in
Section 2.10, “Postinstallation Setup and Testing”. For other installation
methods, including installation from generic binary and source
distributions, you must initialize the data directory yourself.
This section describes how to initialize the data directory on Unix and Unix-like systems. (For Windows, see Section 2.3.7, “Windows Postinstallation Procedures”.) For some suggested commands that you can use to test whether the server is accessible and working properly, see Section 2.10.3, “Testing the Server”.
In the examples shown here, the server runs under the user ID of
mysql login account. This assumes that such
an account exists. Either create the account if it does not exist,
or substitute the name of a different existing login account that
you plan to use for running the server. For information about
creating the account, see
mysql System User and Group, in
Section 2.2, “Installing MySQL on Unix/Linux Using Generic Binaries”.
Change location into the top-level directory of your MySQL installation, represented here by
shell> cd BASEDIR
BASEDIRis likely to be something like
/usr/bin(for installation wtih MySQL Yum repository, or other means). The following steps assume that you have changed location to this directory.
You will find several files and subdirectories in the
BASEDIRdirectory. The most important for installation purposes are the
scriptssubdirectories, which contain the server as well as client and utility programs.
If necessary, ensure that the distribution contents are accessible to
mysql. If you installed the distribution as
mysql, no further action is required. If you installed the distribution as
root, its contents will be owned by
root. Change its ownership to
mysqlby executing the following commands as
rootin the installation directory. The first command changes the owner attribute of the files to the
mysqluser. The second changes the group attribute to the
shell> chown -R mysql . shell> chgrp -R mysql .
If necessary, initialize the data directory, including the
mysqldatabase containing the initial MySQL grant tables that determine how users are permitted to connect to the server.
Typically, data directory initialization need be done only the first time you install MySQL. If you are upgrading an existing installation, you should run mysql_upgrade instead (see Section 4.4.7, “mysql_upgrade — Check and Upgrade MySQL Tables”). However, the command that initializes the data directory does not overwrite any existing privilege tables, so it should be safe to run in any circumstances.
shell> scripts/mysql_install_db --user=mysql
It is important to make sure that the database directories and files are owned by the
mysqllogin account so that the server has read and write access to them when you run it later. To ensure this if you run mysql_install_db as
root, include the
--useroption as shown. Otherwise, you should execute the program while logged in as
mysql, in which case you can omit the
--useroption from the command.
The mysql_install_db command creates the server's data directory. Under the data directory, it creates directories for the
mysqldatabase that holds the grant tables and the
testdatabase that you can use to test MySQL. The program also creates privilege table entries for the initial account or accounts.
test_. For a complete listing and description of the grant tables, see Section 6.2, “The MySQL Access Privilege System”.
It might be necessary to specify other options such as
--datadirif mysql_install_db does not identify the correct locations for the installation directory or data directory. For example:
shell> scripts/mysql_install_db --user=mysql \ --basedir=/opt/mysql/mysql \ --datadir=/opt/mysql/mysql/data
For a more secure installation, invoke mysql_install_db with the
--random-passwordsoption. This causes it to assign a random password to the MySQL
rootaccounts, set the “password expired” flag for those accounts, and remove the anonymous-user MySQL accounts. For additional details, see Section 4.4.3, “mysql_install_db — Initialize MySQL Data Directory”. (Install operations using RPMs for Unbreakable Linux Network are unaffected because they do not use mysql_install_db.)
If you do not want to have the
testdatabase, you can remove it after starting the server, using the instructions in Section 2.10.4, “Securing the Initial MySQL Accounts”.
If you have trouble with mysql_install_db at this point, see Section 18.104.22.168, “Problems Running mysql_install_db”.
After initializing the data directory, you can establish the final installation ownership settings. To leave the installation owned by
mysql, no action is required here. Otherwise, most of the MySQL installation can be owned by
rootif you like. The exception is that the data directory must be owned by
mysql. To accomplish this, run the following commands as
rootin the installation directory. For some distribution types, the data directory might be named
data; adjust the second command accordingly.
shell> chown -R root . shell> chown -R mysql data
If the plugin directory (the directory named by the
plugin_dirsystem variable) is writable by the server, it may be possible for a user to write executable code to a file in the directory using
SELECT ... INTO DUMPFILE. This can be prevented by making the plugin directory read only to the server or by setting the
secure_file_privsystem variable at server startup to a directory where
SELECTwrites can be performed safely.
To specify options that the MySQL server should use at startup, put them in a
/etc/mysql/my.cnffile. See Section 5.1.2, “Server Configuration Defaults”. If you do not do this, the server starts with its default settings.
If you want MySQL to start automatically when you boot your machine, see Section 2.10.5, “Starting and Stopping MySQL Automatically”.
Data directory initialization creates time zone tables in the
mysql database but does not populate them. To
do so, use the instructions in
Section 10.6, “MySQL Server Time Zone Support”.