Table of Contents

3.1 Installing MySQL on Solaris Using a Solaris PKG

MySQL 8.0 supports Solaris 11.4 and higher

• For information on installing using the native Solaris PKG format, seeSection 3.1, “Installing MySQL on Solaris Using a Solaris PKG”.

• To use a standardtar binary installation, use the notes provided inChapter 1,Installing MySQL on Unix/Linux Using Generic Binaries. Check the notes and hints at the end of this section for Solaris specific notes that you may need before or after installation.

MySQL 5.7 has a dependency on the Oracle Developer Studio Runtime Libraries; but this does not apply to MySQL 8.0.

• If you want to use MySQL with themysql user and group, use thegroupadd anduseradd commands:

  groupadd mysqluseradd -g mysql -s /bin/false mysql

• If you install MySQL using a binary tarball distribution on Solaris, because the Solaristar cannot handle long file names, use GNUtar (gtar) to unpack the distribution. If you do not have GNUtar on your system, install it with the following command:

  pkg install archiver/gnu-tar

• You should mount any file systems on which you intend to storeInnoDB files with theforcedirectio option. (By default mounting is done without this option.) Failing to do so causes a significant drop in performance when using theInnoDB storage engine on this platform.

• If you would like MySQL to start automatically, you can copysupport-files/mysql.server to/etc/init.d and create a symbolic link to it named/etc/rc3.d/S99mysql.server.

• If too many processes try to connect very rapidly tomysqld, you should see this error in the MySQL log:

  Error in accept: Protocol error

  You might try starting the server with the--back_log=50 option as a workaround for this.

• To configure the generation of core files on Solaris you should use thecoreadm command. Because of the security implications of generating a core on asetuid() application, by default, Solaris does not support core files onsetuid() programs. However, you can modify this behavior usingcoreadm. If you enablesetuid() core files for the current user, they are generated using mode 600 and are owned by the superuser.