- Install Rpm Package On Arch Linux Operating System
- Install Rpm Package On Arch Linux Command
- Install Rpm Package On Arch Linux Download
- Install Rpm Package On Arch Linux Download
2.5.4 Installing MySQL on Linux Using RPM Packages from Oracle
How To Install Rpm Package On Arch Linux Readkit 2 6 3 X 5 Calendarique 1 3 1 Download Free Free Antivirus For Mac Os X 10.8.5 Warcraft 3 Frozen Throne Free For Mac Pc 98 Iso Download Cfs Software Crack Goodtask 2 2 3 Download Free Minecraft: Story Mode 1 0 Wirecast Pro 6 0 3 Download Free Itube Studio 7 4 0 5 Cc. Mar 03, 2019 Install RPM on Fedora. To install an.rpm package on Fedora Linux, enter the following: sudo rpm -i samplefile.rpm. Just as in CentOS, the -i switch tells RPM to install the software. Another method is to use the dnf utility to install the package: sudo dnf localinstall samplefile.rpm. Unlike many Linux tools, DNF is not a set of initials.
The recommended way to install MySQL on RPM-based Linux distributions is by using the RPM packages provided by Oracle. There are two sources for obtaining them, for the Community Edition of MySQL:
From the MySQL software repositories:
The MySQL Yum repository (see Section 2.5.1, “Installing MySQL on Linux Using the MySQL Yum Repository” for details).
The MySQL SLES repository (see Section 2.5.3, “Installing MySQL on Linux Using the MySQL SLES Repository” for details).
From the Download MySQL Community Server page in the MySQL Developer Zone.
RPM distributions of MySQL are also provided by other vendors. Be aware that they may differ from those built by Oracle in features, capabilities, and conventions (including communication setup), and that the installation instructions in this manual do not necessarily apply to them. The vendor's instructions should be consulted instead.
MySQL RPM Packages
Table 2.9 RPM Packages for MySQL Community Edition
Package Name | Summary |
---|---|
mysql-community-client | MySQL client applications and tools |
mysql-community-common | Common files for server and client libraries |
mysql-community-devel | Development header files and libraries for MySQL database client applications |
mysql-community-embedded-compat | MySQL server as an embedded library with compatibility for applications using version 18 of the library |
mysql-community-libs | Shared libraries for MySQL database client applications |
mysql-community-libs-compat | Shared compatibility libraries for previous MySQL installations |
mysql-community-server | Database server and related tools |
mysql-community-server-debug | Debug server and plugin binaries |
mysql-community-test | Test suite for the MySQL server |
mysql-community | The source code RPM looks similar to mysql-community-8.0.26-1.el7.src.rpm, depending on selected OS |
Additional *debuginfo* RPMs | There are several debuginfo packages: mysql-community-client-debuginfo, mysql-community-libs-debuginfo mysql-community-server-debug-debuginfo mysql-community-server-debuginfo, and mysql-community-test-debuginfo. |
Table 2.10 RPM Packages for the MySQL Enterprise Edition
Package Name | Summary |
---|---|
mysql-commercial-backup | MySQL Enterprise Backup (added in 8.0.11) |
mysql-commercial-client | MySQL client applications and tools |
mysql-commercial-common | Common files for server and client libraries |
mysql-commercial-devel | Development header files and libraries for MySQL database client applications |
mysql-commercial-embedded-compat | MySQL server as an embedded library with compatibility for applications using version 18 of the library |
mysql-commercial-libs | Shared libraries for MySQL database client applications |
mysql-commercial-libs-compat | Shared compatibility libraries for previous MySQL installations; the version of the libraries matches the version of the libraries installed by default by the distribution you are using |
mysql-commercial-server | Database server and related tools |
mysql-commercial-test | Test suite for the MySQL server |
Additional *debuginfo* RPMs | There are several debuginfo packages: mysql-commercial-client-debuginfo, mysql-commercial-libs-debuginfo mysql-commercial-server-debug-debuginfo mysql-commercial-server-debuginfo, and mysql-commercial-test-debuginfo. |
The full names for the RPMs have the following syntax:
The distribution
and arch
values indicate the Linux distribution and the processor type for which the package was built. See the table below for lists of the distribution identifiers:
Table 2.11 MySQL Linux RPM Package Distribution Identifiers
Distribution Value | Intended Use |
---|---|
el{version} where {version} is the major Enterprise Linux version, such as el8 | EL6, EL7, and EL8-based platforms (for example, the corresponding versions of Oracle Linux, Red Hat Enterprise Linux, and CentOS) |
fc{version} where {version} is the major Fedora version, such as fc34 | Fedora 33 and 34 |
sles12 | SUSE Linux Enterprise Server 12 |
To see all files in an RPM package (for example, mysql-community-server
), use the following command:
The discussion in the rest of this section applies only to an installation process using the RPM packages directly downloaded from Oracle, instead of through a MySQL repository.
Dependency relationships exist among some of the packages. If you plan to install many of the packages, you may wish to download the RPM bundle tar file instead, which contains all the RPM packages listed above, so that you need not download them separately.
In most cases, you need to install the mysql-community-server
, mysql-community-client
, mysql-community-libs
, mysql-community-common
, and mysql-community-libs-compat
packages to get a functional, standard MySQL installation. To perform such a standard, basic installation, go to the folder that contains all those packages (and, preferably, no other RPM packages with similar names), and issue the following command:
Replace yum with zypper for SLES, and with dnf for Fedora.
While it is much preferable to use a high-level package management tool like yum to install the packages, users who prefer direct rpm commands can replace the yum install command with the rpm -Uvh command; however, using rpm -Uvh instead makes the installation process more prone to failure, due to potential dependency issues the installation process might run into.
To install only the client programs, you can skip mysql-community-server
in your list of packages to install; issue the following command:
Replace yum with zypper for SLES, and with dnf for Fedora.
A standard installation of MySQL using the RPM packages result in files and resources created under the system directories, shown in the following table.
Table 2.12 MySQL Installation Layout for Linux RPM Packages from the MySQL Developer Zone
Files or Resources | Location |
---|---|
Client programs and scripts | /usr/bin |
mysqld server | /usr/sbin |
Configuration file | /etc/my.cnf |
Data directory | /var/lib/mysql |
Error log file | For RHEL, Oracle Linux, CentOS or Fedora platforms: For SLES: |
Value of secure_file_priv | /var/lib/mysql-files |
System V init script | For RHEL, Oracle Linux, CentOS or Fedora platforms: For SLES: |
Systemd service | For RHEL, Oracle Linux, CentOS or Fedora platforms: For SLES: |
Pid file | /var/run/mysql/mysqld.pid |
Socket | /var/lib/mysql/mysql.sock |
Keyring directory | /var/lib/mysql-keyring |
Unix manual pages | /usr/share/man |
Include (header) files | /usr/include/mysql |
Libraries | /usr/lib/mysql |
Miscellaneous support files (for example, error messages, and character set files) | /usr/share/mysql |
The installation also creates a user named mysql
and a group named mysql
on the system.
Installation of previous versions of MySQL using older packages might have created a configuration file named /usr/my.cnf
. It is highly recommended that you examine the contents of the file and migrate the desired settings inside to the file /etc/my.cnf
file, then remove /usr/my.cnf
.
MySQL is NOT automatically started at the end of the installation process. For Red Hat Enterprise Linux, Oracle Linux, CentOS, and Fedora systems, use the following command to start MySQL:
For SLES systems, the command is the same, but the service name is different:
If the operating system is systemd enabled, standard systemctl (or alternatively, service with the arguments reversed) commands such as stop, start, status, and restart should be used to manage the MySQL server service. The mysqld
service is enabled by default, and it starts at system reboot. Notice that certain things might work differently on systemd platforms: for example, changing the location of the data directory might cause issues. See Section 2.5.9, “Managing MySQL Server with systemd” for additional information.
During an upgrade installation using RPM and DEB packages, if the MySQL server is running when the upgrade occurs then the MySQL server is stopped, the upgrade occurs, and the MySQL server is restarted. One exception: if the edition also changes during an upgrade (such as community to commercial, or vice-versa), then MySQL server is not restarted.
At the initial start up of the server, the following happens, given that the data directory of the server is empty:
The server is initialized.
An SSL certificate and key files are generated in the data directory.
validate_password
is installed and enabled.A superuser account
'root'@'localhost'
is created. A password for the superuser is set and stored in the error log file. To reveal it, use the following command for RHEL, Oracle Linux, CentOS, and Fedora systems:Use the following command for SLES systems:
The next step is to log in with the generated, temporary password and set a custom password for the superuser account:
validate_password
is installed by default. The default password policy implemented by validate_password
requires that passwords contain at least one uppercase letter, one lowercase letter, one digit, and one special character, and that the total password length is at least 8 characters.
If something goes wrong during installation, you might find debug information in the error log file /var/log/mysqld.log
.
For some Linux distributions, it might be necessary to increase the limit on number of file descriptors available to mysqld. See Section B.3.2.16, “File Not Found and Similar Errors”
Installing Client Libraries from Multiple MySQL Versions. It is possible to install multiple client library versions, such as for the case that you want to maintain compatibility with older applications linked against previous libraries. To install an older client library, use the --oldpackage
option with rpm. For example, to install mysql-community-libs-5.5
on an EL6 system that has libmysqlclient.21
from MySQL 8.0, use a command like this:
Debug Package. A special variant of MySQL Server compiled with the debug package has been included in the server RPM packages. It performs debugging and memory allocation checks and produces a trace file when the server is running. To use that debug version, start MySQL with /usr/sbin/mysqld-debug
, instead of starting it as a service or with /usr/sbin/mysqld
. See Section 5.9.4, “The DBUG Package” for the debug options you can use.
The default plugin directory for debug builds changed from /usr/lib64/mysql/plugin
to /usr/lib64/mysql/plugin/debug
in MySQL 8.0.4. Previously, it was necessary to change plugin_dir
to /usr/lib64/mysql/plugin/debug
for debug builds.
Install Rpm Package On Arch Linux Operating System
Rebuilding RPMs from source SRPMs. Source code SRPM packages for MySQL are available for download. They can be used as-is to rebuild the MySQL RPMs with the standard rpmbuild tool chain.
Install Rpm Package On Arch Linux Command
2.5.5 Installing MySQL on Linux Using RPM Packages from Oracle
The recommended way to install MySQL on RPM-based Linux distributions is by using the RPM packages provided by Oracle. There are two sources for obtaining them, for the Community Edition of MySQL:
From the MySQL software repositories:
The MySQL Yum repository (see Section 2.5.1, “Installing MySQL on Linux Using the MySQL Yum Repository” for details).
The MySQL SLES repository (see Section 2.5.4, “Installing MySQL on Linux Using the MySQL SLES Repository” for details).
From the MySQL Downloads page in the MySQL Developer Zone.
RPM distributions of MySQL are also provided by other vendors. Be aware that they may differ from those built by Oracle in features, capabilities, and conventions (including communication setup), and that the installation instructions in this manual do not necessarily apply to them. The vendor's instructions should be consulted instead.
If you have such a third-party distribution of MySQL running on your system and now want to migrate to Oracle's distribution using the RPM packages downloaded from the MySQL Developer Zone, see Compatibility with RPM Packages from Other Vendors below. The preferred method of migration, however, is to use the MySQL Yum repository or MySQL SLES repository.
There are two kinds of RPM packages for installing MySQL 5.6 :
The older kind: Their package names started with
MYSQL-
. They are available from the MySQL Downloads page in the MySQL Developer Zone. The instructions given in this section are for using these packages.The newer kind: Their package names started with
mysql-community-
ormysql-commercial-
. They are available from the MySQL Yum repository and MySQL SLES repository. If, instead of configuring your system to install these RPM directly from the MySQL repositories (which is recommended), you are downloading the packages from the repositories and then installing them manually in separate steps, use the installation commands given for the MySQL 5.7 RPMs in Installing MySQL on Linux Using RPM Packages from Oracle, but consult this section for information like installation layout, server initialization, root password, and so on.
RPM packages for MySQL are listed in the following tables:
Table 2.9 RPM Packages for MySQL Community Edition
Package Name | Summary |
---|---|
MySQL-server | Database server and related tools |
MySQL-client | MySQL client applications and tools |
MySQL-devel | Development header files and libraries for MySQL database client applications |
MySQL-shared | Shared libraries for MySQL database client applications |
MySQL-shared-compat | Shared compatibility libraries for previous MySQL installations |
MySQL-embedded | MySQL embedded library |
MySQL-test | Test suite for the MySQL server |
Dependency relationships exist among some of the packages. If you plan to install many of the packages, you may wish to download the RPM bundle tar file instead, which contains all the RPM packages listed above, so that you need not download them separately.
The full names for the RPMs have the following syntax:
The distribution
and arch
values indicate the Linux distribution and the processor type for which the package was built. See the table below for lists of the distribution identifiers:
Table 2.10 MySQL Linux RPM Package Distribution Identifiers
distribution Value | Intended Use |
---|---|
el6 , el7 | Red Hat Enterprise Linux/Oracle Linux/CentOS 5, 6, or 7 |
sles11, sles12 | SUSE Linux Enterprise Server 11 or 12 |
linux_glibc2.5 | Distribution independent; run on any RPM-based Linux distribution |
To see all files in an RPM package (for example, MySQL-server
), use the following command:
In most cases, you need to install the MySQL-server
and MySQL-client
to get a functional, standard MySQL installation. To perform such a standard, minimal installation, go to the folder that contains all those packages (and, preferably, no other RPM packages with similar names), and issue the following command (replace yum with zypper for SLES systems):
While it is much preferable to use a high-level package management tool like yum to install the packages, users who prefer direct rpm commands can replace the yum install command with the rpm -Uvh command; however, using rpm -Uvh instead makes the installation process more prone to failure, due to potential dependency issues the installation process might run into.
To install only the client programs, you can skip installing the MySQL-server
package; issue the following command (replace yum with zypper for SLES systems):
A standard installation of MySQL using the RPM packages result in files and resources created under the system directories, shown in the following table.
Table 2.11 MySQL Installation Layout for Linux RPM Packages from the MySQLDeveloper Zone
Files or Resources | Location |
---|---|
Client programs and scripts | /usr/bin |
mysqld server | /usr/sbin |
Data directory | /var/lib/mysql |
Error log file | For RHEL, Oracle Linux, or CentOS: For SLES: |
System V init script |
|
Systemd service |
|
Pid file |
|
Unix manual pages | /usr/share/man |
Include (header) files | /usr/include/mysql |
Libraries | /usr/lib/mysql |
Socket | /var/lib/mysql/mysql.sock |
Miscellaneous support files (for example, error messages, and character set files) | /usr/share/mysql |
The installation also creates a user named mysql
and a group named mysql
on the system.
MySQL is not automatically started at the end of the installation process. Use the following command to start MySQL:
At the initial start up of the server, the server is initialized if the data directory of the server is empty. mysql_install_db is invoked with the --random-passwords
option, which assigns a random password to the MySQL root
accounts and sets the “password expired” flag for those accounts. It is necessary after installation to start the server, connect as root
using the initial random password, and assign a new root
password. Until this is done, root
cannot do anything else. This must be done for each root
account you intend to use. To change the password, you can use the SET PASSWORD
statement (for example, with the mysql client). You can also use mysqladmin or mysql_secure_installation. For additional details (including where to find the assigned random root
password), 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 run mysql_install_db.)
During an upgrade installation using RPM packages, if the MySQL server is running when the upgrade occurs then the MySQL server is stopped, the upgrade occurs, and the MySQL server is restarted. One exception: if the edition also changes during an upgrade (such as community to commercial, or vice-versa), then MySQL server is not restarted.
If something goes wrong during installation, you might find debug information in the error log file /var/lib/mysql/
. host_name
.err
Compatibility with RPM Packages from Other Vendors. If you have installed packages for MySQL from your Linux distribution's local software repository, it is much preferable to install the new, directly-downloaded packages from Oracle using the package management system of your platform (yum or zypper), as described above. The command replaces old packages with new ones to ensure compatibility of old applications with the new installation; for example, the old MySQL-shared
package is replaced with the MySQL-shared-compat
package, which provides a replacement-compatible client library for applications that were using your older MySQL installation. If there was an older version of MySQL-shared-compat
on the system, it also gets replaced.
If you have installed third-party packages for MySQL that are NOT from your Linux distribution's local software repository (for example, packages directly downloaded from a vendor other than Oracle), you should uninstall all those packages before installing the new, directly-downloaded packages from Oracle. This is because conflicts may arise between those vendor's RPM packages and Oracle's: for example, a vendor's convention about which files belong with the server and which belong with the client library may differ from that used for Oracle packages. Attempts to install an Oracle RPM may then result in messages saying that files in the RPM to be installed conflict with files from an installed package.
Debug Package. A special variant of MySQL Server compiled with the debug package has been included in the server RPM packages. It performs debugging and memory allocation checks and produces a trace file when the server is running. To use that debug version, start MySQL with /usr/sbin/mysqld-debug
, instead of starting it as a service or with /usr/sbin/mysqld
. See Section 5.8.3, “The DBUG Package” for the debug options you can use.
The default plugin directory for debug builds changed from /usr/lib64/mysql/plugin
to /usr/lib64/mysql/plugin/debug
in 5.6.39. Previously, it was necessary to change plugin_dir
to /usr/lib64/mysql/plugin/debug
for debug builds.
Install Rpm Package On Arch Linux Download
Rebuilding RPMs from source SRPMs. Source code SRPM packages for MySQL are available for download. They can be used as-is to rebuild the MySQL RPMs with the standard rpmbuild tool chain.
Install Rpm Package On Arch Linux Download
RPMs for NDB Cluster. Standard MySQL server RPMs built by MySQL do not provide support for the NDBCLUSTER
storage engine. For more information about installing NDB Cluster from RPMs, see Section 18.3, “NDB Cluster Installation”.