Starting with mysql linux

MySQL distributions on Unix and Unix-like system include a script named mysql.server , which starts the MySQL server using mysqld_safe . It can be used on systems such as Linux and Solaris that use System V-style run directories to start and stop system services. It is also used by the macOS Startup Item for MySQL.

mysql.server is the script name as used within the MySQL source tree. The installed name might be different (for example, mysqld or mysql ). In the following discussion, adjust the name mysql.server as appropriate for your system.

For some Linux platforms, MySQL installation from RPM or Debian packages includes systemd support for managing MySQL server startup and shutdown. On these platforms, mysql.server and mysqld_safe are not installed because they are unnecessary. For more information, see Managing MySQL Server with systemd.

To start or stop the server manually using the mysql.server script, invoke it from the command line with start or stop arguments:

mysql.server changes location to the MySQL installation directory, then invokes mysqld_safe . To run the server as some specific user, add an appropriate user option to the [mysqld] group of the global /etc/my.cnf option file, as shown later in this section. (It is possible that you must edit mysql.server if you’ve installed a binary distribution of MySQL in a nonstandard location. Modify it to change location into the proper directory before it runs mysqld_safe . If you do this, your modified version of mysql.server may be overwritten if you upgrade MySQL in the future; make a copy of your edited version that you can reinstall.)

mysql.server stop stops the server by sending a signal to it. You can also stop the server manually by executing mysqladmin shutdown .

To start and stop MySQL automatically on your server, you must add start and stop commands to the appropriate places in your /etc/rc* files:

If you use the Linux server RPM package ( MySQL-server- VERSION .rpm ), or a native Linux package installation, the mysql.server script may be installed in the /etc/init.d directory with the name mysqld or mysql . See Installing MySQL on Linux Using RPM Packages from Oracle, for more information on the Linux RPM packages.

If you install MySQL from a source distribution or using a binary distribution format that does not install mysql.server automatically, you can install the script manually. It can be found in the support-files directory under the MySQL installation directory or in a MySQL source tree. Copy the script to the /etc/init.d directory with the name mysql and make it executable:

After installing the script, the commands needed to activate it to run at system startup depend on your operating system. On Linux, you can use chkconfig :

On some Linux systems, the following command also seems to be necessary to fully enable the mysql script:

On FreeBSD, startup scripts generally should go in /usr/local/etc/rc.d/ . Install the mysql.server script as /usr/local/etc/rc.d/mysql.server.sh to enable automatic startup. The rc(8) manual page states that scripts in this directory are executed only if their base name matches the *.sh shell file name pattern. Any other files or directories present within the directory are silently ignored.

As an alternative to the preceding setup, some operating systems also use /etc/rc.local or /etc/init.d/boot.local to start additional services on startup. To start up MySQL using this method, append a command like the one following to the appropriate startup file:

For other systems, consult your operating system documentation to see how to install startup scripts.

mysql.server reads options from the [mysql.server] and [mysqld] sections of option files. For backward compatibility, it also reads [mysql_server] sections, but to be current you should rename such sections to [mysql.server] .

You can add options for mysql.server in a global /etc/my.cnf file. A typical my.cnf file might look like this:

The mysql.server script supports the options shown in the following table. If specified, they must be placed in an option file, not on the command line. mysql.server supports only start and stop as command-line arguments.

Table 4.2 mysql.server Option-File Options

Option Name	Description	Type
basedir	Path to MySQL installation directory	Directory name
datadir	Path to MySQL data directory	Directory name
pid-file	File in which server should write its process ID	File name
service-startup-timeout	How long to wait for server startup	Integer

The path to the MySQL installation directory.

The path to the MySQL data directory.

The path name of the file in which the server should write its process ID. The server creates the file in the data directory unless an absolute path name is given to specify a different directory.

Источник

Getting Started with MySQL

MySQL is the world’s most popular open-source database. Despite its powerful features, MySQL is simple to set up and easy to use. Below are some instructions to help you get MySQL up and running in a few easy steps. We also explain how to perform some basic operations with MySQL using the mysql client.

The following instructions do not necessarily apply to versions of MySQL older than MySQL 5.7.

These are instructions for a fresh installation only. If you are already using MySQL and want to upgrade to a newer version, see Upgrading MySQL.

For legal information, see the Legal Notices.

For help with using MySQL, please visit the MySQL Forums, where you can discuss your issues with other MySQL users.

Document generated on: 2021-09-23 (revision: 70881)

Table of Contents

Installing and Starting MySQL

There are different ways to install MySQL. The following covers the easiest methods for installing and starting MySQL on different platforms.

Linux. The easiest way to install MySQL is to use the MySQL repositories:

For Yum-based Linux distributions like Oracle Linux, Red Hat Enterprise Linux, and Fedora, follow the instructions in A Quick Guide to Using the MySQL Yum Repository. If your system cannot use the MySQL Yum repository for some reason, follow the instructions in Installing MySQL on Linux Using RPM Packages from Oracle.

For APT-based distributions like Debian and Ubuntu, follow the instructions in A Quick Guide to Using the MySQL APT Repository. If your system cannot use the MySQL APT repository for some reason, follow the instructions in Installing MySQL on Linux Using Debian Packages from Oracle.

For SUSE Linux Enterprise, follow the instructions in A Quick Guide to Using the MySQL SLES Repository. If your system cannot use the MySQL SUSE repository for some reason, follow the instructions in Installing MySQL on Linux Using RPM Packages from Oracle.

For Linux distributions that do not support the MySQL repositories or the installation packages mentioned above, you can install MySQL using generic binaries:

Download the .tar or .tar.gz archive for the generic binaries for Linux from the Download MySQL Community Server page.

See Installing MySQL on Unix/Linux Using Generic Binaries for instructions on installing the binaries.

After installing the binaries, following the instructions given in Initializing the Data Directory. It is especially important to note the random root password generated for you during the initialization process; see Initializing the Data Directory for more detail.

Next, follow the instructions given in Starting the Server.

Detailed instructions, as well as other methods for installation, can be found in Installing MySQL on Linux.

Microsoft Windows. The recommended way to install MySQL on Microsoft Windows is to use the MySQL Installer; see MySQL Installer Method on how to download and run the MySQL Installer. For a detailed explanation for each step of the installation wizard, see MySQL Installer for Windows.

If you have chosen to configure MySQL as a Windows service during the installation process, which is the default option (see Windows Service for details), the MySQL server will start automatically after the installation process is completed.

Detailed information regarding Windows installation, including alternative installation methods and instructions for troubleshooting, can be found in Installing MySQL on Microsoft Windows.

macOS. The recommended way for installing MySQL on macOS is to use the macOS installer package. See Installing MySQL on macOS Using Native Packages on how to download and run the installer package, and how to start the MySQL server afterward.

Detailed information regarding installation on macOS can be found in Installing MySQL on macOS.

Other platforms. For installations on other platforms (for example, FreeBSD and Solaris), as well as installation methods not covered above, see Installing and Upgrading MySQL.

Connecting to the MySQL Server with the mysql Client

Once your MySQL server is up and running, you can connect to it as the superuser root with the mysql client.

On Linux, enter the following command at the command line terminal (for installation using generic binaries, you might need to go first to the bin folder under the base directory of your MySQL installation):

On Windows, click Start , All Programs , MySQL , MySQL 5.7 Command Line Client (or MySQL 8.0 Command Line Client , respectively). If you did not install MySQL with the MySQL Installer, open a command prompt, go to the bin folder under the base directory of your MySQL installation, and issue the following command:

You are then asked for the root password, which was assigned in different manners according to the way you installed MySQL. The installation and initialization instructions given above already explain the root password, but here is a quick summary:

For installations using the MySQL Yum repository, MySQL SUSE repository, or RPM packages directly downloaded from Oracle, the generated root password is in the error log. View it with, for example, the following command:

For installations using the MySQL APT repository or Debian packages directly downloaded from Oracle, you should have already assigned the root password yourself; if you have not done that for some reason, see the «Important» note here or How to Reset the Root Password.

For installations on Linux using the generic binaries followed by a data directory initialization using mysqld —initialize as discussed in Initializing the Data Directory, the generated root password is displayed in the standard error stream during the data directory’s initialization:

Depending on the configuration you used to initialize the MySQL server, the error output might have been directed to the MySQL error log; go there and check for the password if you do not see the above message on your screen. The error log is a file with a .err extension, usually found under the server’s data directory (the location of which depends on the server’s configuration, but is likely to be the data folder under the base directory of your MySQL installation, or the /var/lib/mysql folder).

If you have initialized the data directory with mysqld —initialize-insecure instead, the root password is empty.

For installations on Windows using the MySQL Installer and OS X using the installer package, you should have assigned a root password yourself.

If you have forgotten the root password you have chosen or have problems finding the temporary root password generated for you, see How to Reset the Root Password.

Once you are connected to the MySQL server, a welcome message is displayed and the mysql> prompt appears, which looks like this:

At this point, if you have logged in using a temporary root password that was generated during the installation or initialization process (which will be the case if you installed MySQL using the MySQL Yum repository, or using RPM packages or generic binaries from Oracle), change your root password by typing the following statement at the prompt:

Until you change your root password, you will not be able to exercise any of the superuser privileges, even if you are logged in as root .

Here are a few useful things to remember when using the mysql client:

Client commands (for example, help , quit , and clear ) and keywords in SQL statements (for example, SELECT, CREATE TABLE, and INSERT) are not case-sensitive.

Column names are case-sensitive. Table names are case-sensitive on most Unix-like platforms, but not case-sensitive on Windows platforms. Case-sensitivity during string comparison depends on the character collation you use. In general, it is a good idea to treat all identifiers (database names, table names, column names, etc.) and strings as case-sensitive. See Identifier Case Sensitivity and Case Sensitivity in String Searches for details.

You can type your SQL statements on multiple lines by pressing Enter in the middle of it. Typing a semicolon ( ; ) followed by an Enter ends an SQL statement and sends it to the server for execution; the same happens when a statement is ended with \g or \G (with the latter, returned results are displayed vertically). However, client commands (for example, help , quit , and clear ) do not require a terminator.

To disconnect from the MySQL server, type QUIT or \q at the client:

Some Basic Operations with MySQL

Here are some basic operations with the MySQL server. SQL Statements explains in detail the rich syntax and functionality of the SQL statements that are illustrated below.

Showing existing databases. Use a SHOW DATABASES statement:

Creating a new database. Use a CREATE DATABASE statement:

Check if the database has been created:

Creating a table inside a database. First, pick the database in which you want to create the table with a USE statement:

The USE statement tells MySQL to use pets as the default database for subsequent statements. Next, create a table with a CREATE TABLE statement:

Data types you can use in each column are explained in Data Types. Primary Key Optimization explains the concept of a primary key. What follows a # on each line is a comment, which is ignored by the mysql client; see Comments for other comment styles.

Check if the table has been created with a SHOW TABLES statement:

DESCRIBE shows information on all columns of a table:

Adding records into a table. Use, for example, an INSERT. VALUES statement:

See Literal Values for how to write string, date, and other kinds of literals in MySQL.

Retrieving records from a table. Use a SELECT statement, and “ * ” to match all columns:

To select specific columns and rows by a certain condition using the WHERE clause:

Deleting a record from a table. Use a DELETE statement to delete a record from a table, specifying the criterion for deletion with the WHERE clause:

Adding or deleting a column from a table. Use an ALTER TABLE. ADD statement to add a column. You can use, for example, an AFTER clause to specify the location of the new column:

Use DESCRIBE to check the result:

SHOW CREATE TABLE shows a CREATE TABLE statement, which provides even more details on the table:

Use ALTER TABLE. DROP to delete a column:

See the Tutorial for more instructions on how to work with the MySQL server.

Other Important Tasks to Perform

Create more user accounts. root is a superuser account for administration of the MySQL server which should not be used for general operations. On how to create user accounts of various kinds, see Adding Accounts, Assigning Privileges, and Dropping Accounts.

Configure MySQL to be managed with systemd. If you have installed MySQL on a systemd platform using generic binaries and want it to be managed with systemd, see Managing MySQL Server with systemd.

Troubleshooting

The following are resources for troubleshooting some problems you might run into:

Other Helpful Resources

MySQL Reference Manual (select the version with the version switch)

Tutorial on using the mysql client program to work with MySQL

Legal Notices

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in 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 any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, 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 it on 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 embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are «commercial computer software» or «commercial computer software documentation» pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused 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 trademarks of their respective owners.

Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro 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 and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

This documentation is NOT distributed under a GPL license. Use of this documentation is subject to the following terms:

You may create a printed copy of this documentation solely for your own personal use. Conversion to other formats is allowed as long as the actual content is not altered or edited in any way. You shall not publish or distribute this documentation in any form or on any media, except if you distribute the documentation in a manner similar to how Oracle disseminates it (that is, electronically for download on a Web site with the software) or on a CD-ROM or similar medium, provided however that the documentation is disseminated together with the software on the same medium. Any other use, such as any dissemination of printed copies or use of this documentation, in whole or in part, in another publication, requires the prior written consent from an authorized representative of Oracle. Oracle and/or its affiliates reserve any and all rights to this documentation not expressly granted above.

Источник