Linux 支持多种不同的 MySQL 安装解决方案，已在第 2.5 节，“在 Linux 上安装 MySQL”中介绍。本节介绍的方法之一是从 Oracle 的不可破坏 Linux 网络（ULN）进行安装。您可以在http://linux.oracle.com/.Linux supports a number of different solutions for installing MySQL, covered in Section 2.5, “Installing MySQL on Linux”. One of the methods, covered in this section, is installing from Oracle's Unbreakable Linux Network (ULN). You can find information about Oracle Linux and ULN under http://linux.oracle.com/.

要使用 ULN，您需要获取 ULN 登录名并使用 ULN 注册用于安装的计算机。 ULN 常见问题解答对此进行了详细描述。该页面还介绍了如何安装和更新软件包。To use ULN, you need to obtain a ULN login and register the machine used for installation with ULN. This is described in detail in the ULN FAQ. The page also describes how to install and update packages.

支持社区版和商业版软件包，每个软件包都提供三个 MySQL 通道：Both Community and Commercial packages are supported, and each offers three MySQL channels:

社区频道可供所有 ULN 用户使用。The Community channels are available to all ULN users.

要访问 oracle.linux.com 上的商业 MySQL ULN 软件包，您需要提供具有有效的 MySQL 商业许可证（企业版或标准版）的 CSI。截至撰写本文时，有效购买数量为 60944、60945、64911 和 64912。相应的 CSI 使您可以在 ULN GUI 界面中使用商业 MySQL 订阅频道。Accessing commercial MySQL ULN packages at oracle.linux.com requires you to provide a CSI with a valid commercial license for MySQL (Enterprise or Standard). As of this writing, valid purchases are 60944, 60945, 64911, and 64912. The appropriate CSI makes commercial MySQL subscription channels available in your ULN GUI interface.

使用 ULN 安装 MySQL 后，您可以在 第 2.5.7 节“从本机软件存储库在 Linux 上安装 MySQL”，特别是在 第 2.5.4 节“使用 Oracle 的 RPM 软件包在 Linux 上安装 MySQL”。Once MySQL has been installed using ULN, you can find information on starting and stopping the server, and more, at Section 2.5.7, “Installing MySQL on Linux from the Native Software Repositories”, particularly under Section 2.5.4, “Installing MySQL on Linux Using RPM Packages from Oracle”.

如果您要更改包源以使用 ULN，而不更改您正在使用的 MySQL 版本，请备份您的数据，删除现有的二进制文件，并将其替换为来自 ULN 的二进制文件。如果涉及构建更改，我们建议备份为转储（来自 mysqldump 或 MySQL Shell 的备份实用程序）以防万一您需要在新二进制文件就位后重建数据。如果向 ULN 的转换跨越了版本边界，请在继续操作之前查阅本节：第 3 章，升级 MySQL。If you are changing your package source to use ULN and not changing which build of MySQL you are using, then back up your data, remove your existing binaries, and replace them with those from ULN. If a change of build is involved, we recommend the backup be a dump (from mysqldump or MySQL Shell's backup utility) just in case you need to rebuild your data after the new binaries are in place. If this shift to ULN crosses a version boundary, consult this section before proceeding: Chapter 3, Upgrading MySQL.