diff options
| author | unknown <knielsen@knielsen-hq.org> | 2009-12-01 08:24:05 +0100 |
|---|---|---|
| committer | unknown <knielsen@knielsen-hq.org> | 2009-12-01 08:24:05 +0100 |
| commit | 4b69d0ee5245b26a3bd7bd5dfd3bd066cd38ea4c (patch) | |
| tree | 7df2e0cd76e4b8f382ba3c2441bdae45e410f438 /INSTALL-SOURCE | |
| parent | 36f3cbfdc6188d63416b2fbd5a88fe2f8faa2425 (diff) | |
| download | mariadb-git-4b69d0ee5245b26a3bd7bd5dfd3bd066cd38ea4c.tar.gz | |
Imported MySQL documentation files from MySQL 5.1.41 source tarball
Diffstat (limited to 'INSTALL-SOURCE')
| -rw-r--r-- | INSTALL-SOURCE | 10213 |
1 files changed, 4595 insertions, 5618 deletions
diff --git a/INSTALL-SOURCE b/INSTALL-SOURCE index b38f884d98c..4e91825917b 100644 --- a/INSTALL-SOURCE +++ b/INSTALL-SOURCE @@ -5,9 +5,8 @@ Chapter 2. Installing and Upgrading MySQL of the procedure follows and later sections provide the details. If you plan to upgrade an existing version of MySQL to a newer version rather than install MySQL for the first time, see Section - 2.12.1, "Upgrading MySQL," for information about upgrade - procedures and about issues that you should consider before - upgrading. + 2.4.1, "Upgrading MySQL," for information about upgrade procedures + and about issues that you should consider before upgrading. If you are interested in migrating to MySQL from another database system, you may wish to read Section A.8, "MySQL 5.1 FAQ --- @@ -15,96 +14,61 @@ Chapter 2. Installing and Upgrading MySQL concerning migration issues. 1. Determine whether MySQL runs and is supported on your - platform. Please note that not all platforms are equally - suitable for running MySQL, and that not all platforms on - which MySQL is known to run are officially supported by Sun - Microsystems, Inc.: - - + For MySQL Enterprise Server, the officially supported - platforms are listed at - http://www.mysql.com/support/supportedplatforms.html. - - + MySQL Community Server runs on the platforms listed at - Section 2.1.1, "Operating Systems Supported by MySQL - Community Server." - - 2. Choose which distribution to install. Several versions of - MySQL are available, and most are available in several - distribution formats. You can choose from pre-packaged - distributions containing binary (precompiled) programs or - source code. When in doubt, use a binary distribution. We also - provide public access to our current source tree for those who - want to see our most recent developments and help us test new - code. To determine which version and type of distribution you - should use, see Section 2.1.2, "Choosing Which MySQL - Distribution to Install." - - 3. Download the distribution that you want to install. For - instructions, see Section 2.1.3, "How to Get MySQL." To verify - the integrity of the distribution, use the instructions in - Section 2.1.4, "Verifying Package Integrity Using MD5 + platform. + Please note that not all platforms are equally suitable for + running MySQL, and that not all platforms on which MySQL is + known to run are officially supported by Sun Microsystems, + Inc.: + + 2. Choose which distribution to install. + Several versions of MySQL are available, and most are + available in several distribution formats. You can choose from + pre-packaged distributions containing binary (precompiled) + programs or source code. When in doubt, use a binary + distribution. We also provide public access to our current + source tree for those who want to see our most recent + developments and help us test new code. To determine which + version and type of distribution you should use, see Section + 2.1.2, "Choosing Which MySQL Distribution to Install." + + 3. Download the distribution that you want to install. + For instructions, see Section 2.1.3, "How to Get MySQL." To + verify the integrity of the distribution, use the instructions + in Section 2.1.4, "Verifying Package Integrity Using MD5 Checksums or GnuPG." - 4. Install the distribution. To install MySQL from a binary - distribution, use the instructions in Section 2.2, "Standard - MySQL Installation Using a Binary Distribution." To install - MySQL from a source distribution or from the current - development source tree, use the instructions in Section 2.10, - "MySQL Installation Using a Source Distribution." - If you encounter installation difficulties, see Section 2.13, - "Operating System-Specific Notes," for information on solving - problems for particular platforms. - - 5. Perform any necessary post-installation setup. After - installing MySQL, read Section 2.11, "Post-Installation Setup - and Testing." This section contains important information - about making sure the MySQL server is working properly. It - also describes how to secure the initial MySQL user accounts, - which have no passwords until you assign passwords. The - section applies whether you install MySQL using a binary or - source distribution. + 4. Install the distribution. + To install MySQL from a binary distribution, use the + instructions in Section 2.2, "Installing MySQL from Generic + Binaries on Unix/Linux." + To install MySQL from a source distribution or from the + current development source tree, use the instructions in + Section 2.3, "MySQL Installation Using a Source Distribution." + + 5. Perform any necessary post-installation setup. + After installing MySQL, read Section 2.13, "Post-Installation + Setup and Testing." This section contains important + information about making sure the MySQL server is working + properly. It also describes how to secure the initial MySQL + user accounts, which have no passwords until you assign + passwords. The section applies whether you install MySQL using + a binary or source distribution. 6. If you want to run the MySQL benchmark scripts, Perl support for MySQL must be available. See Section 2.15, "Perl Installation Notes." -2.1. General Installation Issues - - The MySQL installation procedure depends on whether you will - install MySQL Enterprise Server or MySQL Community Server. The set - of applicable platforms depends on which distribution you will - install: - - * For MySQL Enterprise Server, the officially supported - platforms are listed at - http://www.mysql.com/support/supportedplatforms.html. - - * MySQL Community Server runs on the platforms listed at Section - 2.1.1, "Operating Systems Supported by MySQL Community - Server." - - For MySQL Enterprise Server, install the main distribution plus - any service packs or hotfixes that you wish to apply using the - Enterprise Installer. For platforms that do not yet have an - Enterprise Installer, use the Community Server instructions. - - For MySQL Community Server, install the main distribution plus any - hotfixes and updates: - - * Download a binary release, or download a source release and - build MySQL yourself from the source code. - - * Retrieve MySQL from the Bazaar tree and build it from source. - The Bazaar tree contains the latest developer code. +2.1. General Installation Guidance The immediately following sections contain the information necessary to choose, download, and verify your distribution. The instructions in later sections of the chapter describe how to install the distribution that you choose. For binary - distributions, see the instructions at Section 2.2, "Standard - MySQL Installation Using a Binary Distribution." To build MySQL - from source, use the instructions at Section 2.10, "MySQL - Installation Using a Source Distribution." + distributions, see the instructions at Section 2.2, "Installing + MySQL from Generic Binaries on Unix/Linux" or the corresponding + section for your platform if available. To build MySQL from + source, use the instructions in Section 2.3, "MySQL Installation + Using a Source Distribution." 2.1.1. Operating Systems Supported by MySQL Community Server @@ -129,58 +93,31 @@ Important MySQL has been reported to compile successfully on the following combinations of operating system and thread package. - * AIX 4.x, 5.x with native threads. See Section 2.13.5.3, - "IBM-AIX notes." - - * Amiga. + * AIX 4.x, 5.x with native threads. See Section 2.12, + "Installing MySQL on AIX." AIX 5.3 should be upgraded to + technology level 7 (5300-07). - * FreeBSD 5.x and up with native threads. + * FreeBSD 5.x and up with native threads. See Section 2.10, + "Installing MySQL on FreeBSD." - * HP-UX 11.x with the native threads. See Section 2.13.5.2, - "HP-UX Version 11.x Notes." + * HP-UX 11.x with the native threads. See Section 2.11, + "Installing MySQL on HP-UX." * Linux, builds on all fairly recent Linux distributions with - glibc 2.3. See Section 2.13.1, "Linux Notes." - - * Mac OS X. See Section 2.13.2, "Mac OS X Notes." - - * NetBSD 1.3/1.4 Intel and NetBSD 1.3 Alpha. See Section - 2.13.4.2, "NetBSD Notes." - - * Novell NetWare 6.0 and 6.5. See Section 2.8, "Installing MySQL - on NetWare." - - * OpenBSD 2.5 and with native threads. OpenBSD earlier than 2.5 - with the MIT-pthreads package. See Section 2.13.4.3, "OpenBSD - 2.5 Notes." + glibc 2.3. See Section 2.6, "Installing MySQL on Linux." - * SCO OpenServer 5.0.X with a recent port of the FSU Pthreads - package. See Section 2.13.5.8, "SCO UNIX and OpenServer 5.0.x - Notes." + * Mac OS X. See Section 2.7, "Installing MySQL on Mac OS X." - * SCO Openserver 6.0.x. See Section 2.13.5.9, "SCO OpenServer - 6.0.x Notes." - - * SCO UnixWare 7.1.x. See Section 2.13.5.10, "SCO UnixWare 7.1.x - and OpenUNIX 8.0.0 Notes." - - * SGI Irix 6.x with native threads. See Section 2.13.5.7, "SGI - Irix Notes." - - * Solaris 2.5 and above with native threads on SPARC and x86. - See Section 2.13.3, "Solaris Notes." - - * Tru64 Unix. See Section 2.13.5.5, "Alpha-DEC-UNIX Notes - (Tru64)." + * Solaris 2.8 on SPARC and x86, including support for native + threads. See Section 2.8.1, "Solaris Notes." * Windows 2000, Windows XP, Windows Vista, Windows Server 2003, - and Windows Server 2008. See Section 2.3, "Installing MySQL on + and Windows Server 2008. See Section 2.5, "Installing MySQL on Windows." MySQL has also been known to run on other systems in the past. See - Section 2.13, "Operating System-Specific Notes." Some porting - effort might be required for current versions of MySQL on these - systems. + Section 2.1, "General Installation Guidance." Some porting effort + might be required for current versions of MySQL on these systems. Not all platforms are equally well-suited for running MySQL. How well a certain platform is suited for a high-load mission-critical @@ -208,8 +145,8 @@ Important * General file system stability and performance. * Table size. If your tables are large, performance is affected - by the ability of the file system to deal with large files at - all and to deal with them efficiently. + by the ability of the file system to deal with large files and + dealing with them efficiently. * Our level of expertise here at Sun Microsystems, Inc. with the platform. If we know a platform well, we enable @@ -240,7 +177,7 @@ Important development process, multiple release series co-exist, each at a different stage of maturity: - * MySQL 5.4 and 6.0 are the current development release series. + * MySQL 5.5 is the current development release series. * MySQL 5.1 is the current General Availability (Production) release series. New releases are issued for bugfixes only; no @@ -255,9 +192,9 @@ Important has ended. Extended support for MySQL 4.1 remains available. According to the MySQL Lifecycle Policy - (http://www.mysql.com/company/legal/lifecycle/#policy), only - Security and Severity Level 1 issues are still being fixed for - MySQL 4.1. + (http://www.mysql.com/about/legal/lifecycle/), only Security + and Severity Level 1 issues are still being fixed for MySQL + 4.1. We do not believe in a complete code freeze because this prevents us from making bugfixes and other fixes that must be done. By @@ -367,13 +304,13 @@ Important * The MySQL benchmark suite This suite runs a range of common queries. It is also a test to determine whether the latest batch of optimizations - actually made the code faster. See Section 7.1.4, "The MySQL + actually made the code faster. See Section 7.1.3, "The MySQL Benchmark Suite." * The crash-me test This test tries to determine what features the database supports and what its capabilities and limitations are. See - Section 7.1.4, "The MySQL Benchmark Suite." + Section 7.1.3, "The MySQL Benchmark Suite." We also test the newest MySQL version in our internal production environment, on at least one machine. We have more than 100GB of @@ -492,21 +429,6 @@ Important as soon as possible. (We would like other companies to do this, too!) -2.1.2.4. MySQL Binaries Compiled by Sun Microsystems, Inc. - - Sun Microsystems, Inc. provides a set of binary distributions of - MySQL. In addition to binaries provided in platform-specific - package formats, we offer binary distributions for a number of - platforms in the form of compressed tar files (.tar.gz files). See - Section 2.2, "Standard MySQL Installation Using a Binary - Distribution." For Windows distributions, see Section 2.3, - "Installing MySQL on Windows." - - If you want to compile a debug version of MySQL from a source - distribution, you should add --with-debug or --with-debug=full to - the configure command used to configure the distribution and - remove any -fomit-frame-pointer options. - 2.1.3. How to Get MySQL Check our downloads page at http://dev.mysql.com/downloads/ for @@ -553,8 +475,8 @@ Important shell> md5sum package_name Example: -shell> md5sum mysql-standard-5.1.39-linux-i686.tar.gz -aaab65abbec64d5e907dcd41b8699945 mysql-standard-5.1.39-linux-i686.ta +shell> md5sum mysql-standard-5.1.41-linux-i686.tar.gz +aaab65abbec64d5e907dcd41b8699945 mysql-standard-5.1.41-linux-i686.ta r.gz You should verify that the resulting checksum (the string of @@ -728,8 +650,8 @@ pg-signature.html signature, which also is available from the download page. The signature file has the same name as the distribution file with an .asc extension, as shown by the examples in the following table. - Distribution file mysql-standard-5.1.39-linux-i686.tar.gz - Signature file mysql-standard-5.1.39-linux-i686.tar.gz.asc + Distribution file mysql-standard-5.1.41-linux-i686.tar.gz + Signature file mysql-standard-5.1.41-linux-i686.tar.gz.asc Make sure that both files are stored in the same directory and then run the following command to verify the signature for the @@ -737,7 +659,7 @@ pg-signature.html shell> gpg --verify package_name.asc Example: -shell> gpg --verify mysql-standard-5.1.39-linux-i686.tar.gz.asc +shell> gpg --verify mysql-standard-5.1.41-linux-i686.tar.gz.asc gpg: Signature made Tue 12 Jul 2005 23:35:41 EST using DSA key ID 507 2E1F5 gpg: Good signature from "MySQL Package signing key (www.mysql.com) < @@ -757,8 +679,8 @@ build@mysql.com>" shell> rpm --checksig package_name.rpm Example: -shell> rpm --checksig MySQL-server-5.1.39-0.glibc23.i386.rpm -MySQL-server-5.1.39-0.glibc23.i386.rpm: md5 gpg OK +shell> rpm --checksig MySQL-server-5.1.41-0.glibc23.i386.rpm +MySQL-server-5.1.41-0.glibc23.i386.rpm: md5 gpg OK Note @@ -786,22 +708,6 @@ shell> rpm --import mysql_pubkey.asc Sun Microsystems, Inc. A distribution provided by another vendor might use a layout different from those shown here. - For MySQL 5.1 on Windows, the default installation directory is - C:\Program Files\MySQL\MySQL Server 5.1. (Some Windows users - prefer to install in C:\mysql, the directory that formerly was - used as the default. However, the layout of the subdirectories - remains the same.) The installation directory has the following - subdirectories. - Directory Contents of Directory - bin Client programs and the mysqld server - data Log files, databases - Docs Manual in CHM format - examples Example programs and scripts - include Include (header) files - lib Libraries - scripts Utility scripts - share Error message files - Installations created from our Linux RPM distributions result in files under the following system directories. Directory Contents of Directory @@ -863,2399 +769,37 @@ shell> rpm --import mysql_pubkey.asc distribution by executing the scripts/make_binary_distribution script from the top directory of the source distribution. -2.2. Standard MySQL Installation Using a Binary Distribution - - The next several sections cover the installation of MySQL on - platforms where we offer packages using the native packaging - format of the respective platform. (This is also known as - performing a "binary install.") However, binary distributions of - MySQL are available for many other platforms as well. See Section - 2.9, "Installing MySQL from tar.gz Packages on Other Unix-Like - Systems," for generic installation instructions for these packages - that apply to all platforms. - - See Section 2.1, "General Installation Issues," for more - information on what other binary distributions are available and - how to obtain them. - -2.3. Installing MySQL on Windows - - A native Windows distribution of MySQL has been available since - version 3.21 and represents a sizable percentage of the daily - downloads of MySQL. This section describes the process for - installing MySQL on Windows. - -Note - - If you are upgrading MySQL from an existing installation older - than MySQL 4.1.5, you must first perform the procedure described - in Section 2.3.14, "Upgrading MySQL on Windows." - - To run MySQL on Windows, you need the following: - - * A Windows operating system such as Windows 2000, Windows XP, - Windows Vista, Windows Server 2003, or Windows Server 2008. - Both 32-bit and 64-bit versions are supported. - A Windows operating system permits you to run the MySQL server - as a service. See Section 2.3.11, "Starting MySQL as a Windows - Service." - Generally, you should install MySQL on Windows using an - account that has administrator rights. Otherwise, you may - encounter problems with certain operations such as editing the - PATH environment variable or accessing the Service Control - Manager. Once installed, MySQL does not need to be executed - using a user with Administrator privileges. - - * TCP/IP protocol support. - - * Enough space on the hard drive to unpack, install, and create - the databases in accordance with your requirements (generally - a minimum of 200 megabytes is recommended.) - - For a list of limitations within the Windows version of MySQL, see - Section D.7.3, "Windows Platform Limitations." - - There may also be other requirements, depending on how you plan to - use MySQL: - - * If you plan to connect to the MySQL server via ODBC, you need - a Connector/ODBC driver. See Section 21.1, "MySQL - Connector/ODBC." - - * If you plan to use MySQL server with ADO.NET applications, you - need the Connector/NET driver. See Section 21.2, "MySQL - Connector/NET." - - * If you need tables with a size larger than 4GB, install MySQL - on an NTFS or newer file system. Don't forget to use MAX_ROWS - and AVG_ROW_LENGTH when you create tables. See Section - 12.1.17, "CREATE TABLE Syntax." - - MySQL for Windows is available in several distribution formats: - - * Binary distributions are available that contain a setup - program that installs everything you need so that you can - start the server immediately. Another binary distribution - format contains an archive that you simply unpack in the - installation location and then configure yourself. For - details, see Section 2.3.1, "Choosing An Installation - Package." - - * The source distribution contains all the code and support - files for building the executables using the Visual Studio - compiler system. - - Generally speaking, you should use a binary distribution that - includes an installer. It is simpler to use than the others, and - you need no additional tools to get MySQL up and running. The - installer for the Windows version of MySQL, combined with a GUI - Configuration Wizard, automatically installs MySQL, creates an - option file, starts the server, and secures the default user - accounts. - -Caution - - Using virus scanning software such as Norton/Symantec Anti-Virus - on directories containing MySQL data and temporary tables can - cause issues, both in terms of the performance of MySQL and the - virus-scanning software mis-identifying the contents of the files - as containing spam. This is because of the fingerprinting - mechanism used by the virus scanning software, and the way in - which MySQL rapidly updates different files, which may be - identified as a potential security risk. - - After installing MySQL Server, it is recommended that you disable - virus scanning on the main directory (datadir) being used to store - your MySQL table data. There is usually a system built into the - virus scanning software to allow certain directories to be - specifically ignored during virus scanning. - - In addition, by default, MySQL creates temporary files in the - standard Windows temporary directory. To prevent the temporary - files also being scanned, you should configure a separate - temporary directory for MySQL temporary files and add this to the - virus scanning exclusion list. To do this, add a configuration - option for the tmpdir parameter to your my.ini configuration file. - For more information, see Section 2.3.7, "Creating an Option - File." - - The following section describes how to install MySQL on Windows - using a binary distribution. To use an installation package that - does not include an installer, follow the procedure described in - Section 2.3.5, "Installing MySQL from a Noinstall Zip Archive." To - install using a source distribution, see Section 2.10.6, - "Installing MySQL from Source on Windows." - - MySQL distributions for Windows can be downloaded from - http://dev.mysql.com/downloads/. See Section 2.1.3, "How to Get - MySQL." - -2.3.1. Choosing An Installation Package - - For MySQL 5.1, there are three installation packages to choose - from when installing MySQL on Windows: - - * The Essentials Package: This package has a file name similar - to mysql-essential-5.1.39-win32.msi and contains the minimum - set of files needed to install MySQL on Windows, including the - Configuration Wizard. This package does not include optional - components such as the embedded server and benchmark suite. - - * The Complete Package: This package has a file name similar to - mysql-5.1.39-win32.zip and contains all files needed for a - complete Windows installation, including the Configuration - Wizard. This package includes optional components such as the - embedded server and benchmark suite. - - * The Noinstall Archive: This package has a file name similar to - mysql-noinstall-5.1.39-win32.zip and contains all the files - found in the Complete install package, with the exception of - the Configuration Wizard. This package does not include an - automated installer, and must be manually installed and - configured. - - The Essentials package is recommended for most users. It is - provided as an .msi file for use with the Windows Installer. The - Complete and Noinstall distributions are packaged as Zip archives. - To use them, you must have a tool that can unpack .zip files. - - Your choice of install package affects the installation process - you must follow. If you choose to install either the Essentials or - Complete install packages, see Section 2.3.2, "Installing MySQL - with the Automated Installer." If you choose to install MySQL from - the Noinstall archive, see Section 2.3.5, "Installing MySQL from a - Noinstall Zip Archive." - -2.3.2. Installing MySQL with the Automated Installer - - New MySQL users can use the MySQL Installation Wizard and MySQL - Configuration Wizard to install MySQL on Windows. These are - designed to install and configure MySQL in such a way that new - users can immediately get started using MySQL. - - The MySQL Installation Wizard and MySQL Configuration Wizard are - available in the Essentials and Complete install packages. They - are recommended for most standard MySQL installations. Exceptions - include users who need to install multiple instances of MySQL on a - single server host and advanced users who want complete control of - server configuration. - -2.3.3. Using the MySQL Installation Wizard - - MySQL Installation Wizard is an installer for the MySQL server - that uses the latest installer technologies for Microsoft Windows. - The MySQL Installation Wizard, in combination with the MySQL - Configuration Wizard, allows a user to install and configure a - MySQL server that is ready for use immediately after installation. - - The MySQL Installation Wizard is the standard installer for all - MySQL server distributions, version 4.1.5 and higher. Users of - previous versions of MySQL need to shut down and remove their - existing MySQL installations manually before installing MySQL with - the MySQL Installation Wizard. See Section 2.3.3.6, "Upgrading - MySQL with the Installation Wizard," for more information on - upgrading from a previous version. - - Microsoft has included an improved version of their Microsoft - Windows Installer (MSI) in the recent versions of Windows. MSI has - become the de-facto standard for application installations on - Windows 2000, Windows XP, and Windows Server 2003. The MySQL - Installation Wizard makes use of this technology to provide a - smoother and more flexible installation process. - - The Microsoft Windows Installer Engine was updated with the - release of Windows XP; those using a previous version of Windows - can reference this Microsoft Knowledge Base article - (http://support.microsoft.com/default.aspx?scid=kb;EN-US;292539) - for information on upgrading to the latest version of the Windows - Installer Engine. - - In addition, Microsoft has introduced the WiX (Windows Installer - XML) toolkit recently. This is the first highly acknowledged Open - Source project from Microsoft. We have switched to WiX because it - is an Open Source project and it allows us to handle the complete - Windows installation process in a flexible manner using scripts. - - Improving the MySQL Installation Wizard depends on the support and - feedback of users like you. If you find that the MySQL - Installation Wizard is lacking some feature important to you, or - if you discover a bug, please report it in our bugs database using - the instructions given in Section 1.6, "How to Report Bugs or - Problems." - -2.3.3.1. Downloading and Starting the MySQL Installation Wizard - - The MySQL installation packages can be downloaded from - http://dev.mysql.com/downloads/. If the package you download is - contained within a Zip archive, you need to extract the archive - first. - -Note - - If you are installing on Windows Vista it is best to open a - network port before beginning the installation. To do this, first - ensure that you are logged in as an Administrator, go to the - Control Panel, and double click the Windows Firewall icon. Choose - the Allow a program through Windows Firewall option and click the - Add port button. Enter MySQL into the Name text box and 3306 (or - the port of your choice) into the Port number text box. Also - ensure that the TCP protocol radio button is selected. If you - wish, you can also limit access to the MySQL server by choosing - the Change scope button. Confirm your choices by clicking the OK - button. If you do not open a port prior to installation, you - cannot configure the MySQL server immediately after installation. - Additionally, when running the MySQL Installation Wizard on - Windows Vista, ensure that you are logged in as a user with - administrative rights. - - The process for starting the wizard depends on the contents of the - installation package you download. If there is a setup.exe file - present, double-click it to start the installation process. If - there is an .msi file present, double-click it to start the - installation process. - -2.3.3.2. Choosing an Install Type - - There are three installation types available: Typical, Complete, - and Custom. - - The Typical installation type installs the MySQL server, the mysql - command-line client, and the command-line utilities. The - command-line clients and utilities include mysqldump, myisamchk, - and several other tools to help you manage the MySQL server. - - The Complete installation type installs all components included in - the installation package. The full installation package includes - components such as the embedded server library, the benchmark - suite, support scripts, and documentation. - - The Custom installation type gives you complete control over which - packages you wish to install and the installation path that is - used. See Section 2.3.3.3, "The Custom Install Dialog," for more - information on performing a custom install. - - If you choose the Typical or Complete installation types and click - the Next button, you advance to the confirmation screen to verify - your choices and begin the installation. If you choose the Custom - installation type and click the Next button, you advance to the - custom installation dialog, described in Section 2.3.3.3, "The - Custom Install Dialog." - -2.3.3.3. The Custom Install Dialog - - If you wish to change the installation path or the specific - components that are installed by the MySQL Installation Wizard, - choose the Custom installation type. - - A tree view on the left side of the custom install dialog lists - all available components. Components that are not installed have a - red X icon; components that are installed have a gray icon. To - change whether a component is installed, click on that component's - icon and choose a new option from the drop-down list that appears. - - You can change the default installation path by clicking the - Change... button to the right of the displayed installation path. - - After choosing your installation components and installation path, - click the Next button to advance to the confirmation dialog. - -2.3.3.4. The Confirmation Dialog - - Once you choose an installation type and optionally choose your - installation components, you advance to the confirmation dialog. - Your installation type and installation path are displayed for you - to review. - - To install MySQL if you are satisfied with your settings, click - the Install button. To change your settings, click the Back - button. To exit the MySQL Installation Wizard without installing - MySQL, click the Cancel button. - - After installation is complete, you have the option of registering - with the MySQL web site. Registration gives you access to post in - the MySQL forums at forums.mysql.com (http://forums.mysql.com), - along with the ability to report bugs at bugs.mysql.com - (http://bugs.mysql.com) and to subscribe to our newsletter. The - final screen of the installer provides a summary of the - installation and gives you the option to launch the MySQL - Configuration Wizard, which you can use to create a configuration - file, install the MySQL service, and configure security settings. - -2.3.3.5. Changes Made by MySQL Installation Wizard - - Once you click the Install button, the MySQL Installation Wizard - begins the installation process and makes certain changes to your - system which are described in the sections that follow. - - Changes to the Registry - - The MySQL Installation Wizard creates one Windows registry key in - a typical install situation, located in - HKEY_LOCAL_MACHINE\SOFTWARE\MySQL AB. - - The MySQL Installation Wizard creates a key named after the major - version of the server that is being installed, such as MySQL - Server 5.1. It contains two string values, Location and Version. - The Location string contains the path to the installation - directory. In a default installation it contains C:\Program - Files\MySQL\MySQL Server 5.1\. The Version string contains the - release number. For example, for an installation of MySQL Server - 5.1.39, the key contains a value of 5.1.39. - - These registry keys are used to help external tools identify the - installed location of the MySQL server, preventing a complete scan - of the hard-disk to determine the installation path of the MySQL - server. The registry keys are not required to run the server, and - if you install MySQL using the noinstall Zip archive, the registry - keys are not created. - - Changes to the Start Menu - - The MySQL Installation Wizard creates a new entry in the Windows - Start menu under a common MySQL menu heading named after the major - version of MySQL that you have installed. For example, if you - install MySQL 5.1, the MySQL Installation Wizard creates a MySQL - Server 5.1 section in the Start menu. - - The following entries are created within the new Start menu - section: - - * MySQL Command Line Client: This is a shortcut to the mysql - command-line client and is configured to connect as the root - user. The shortcut prompts for a root user password when you - connect. - - * MySQL Server Instance Config Wizard: This is a shortcut to the - MySQL Configuration Wizard. Use this shortcut to configure a - newly installed server, or to reconfigure an existing server. - - * MySQL Documentation: This is a link to the MySQL server - documentation that is stored locally in the MySQL server - installation directory. This option is not available when the - MySQL server is installed using the Essentials installation - package. - - Changes to the File System - - The MySQL Installation Wizard by default installs the MySQL 5.1 - server to C:\Program Files\MySQL\MySQL Server 5.1, where Program - Files is the default location for applications in your system, and - 5.1 is the major version of your MySQL server. This is the - recommended location for the MySQL server, replacing the former - default location C:\mysql. - - By default, all MySQL applications are stored in a common - directory at C:\Program Files\MySQL, where Program Files is the - default location for applications in your Windows installation. A - typical MySQL installation on a developer machine might look like - this: -C:\Program Files\MySQL\MySQL Server 5.1 -C:\Program Files\MySQL\MySQL Workbench 5.1 OSS - - This approach makes it easier to manage and maintain all MySQL - applications installed on a particular system. - - In MySQL 5.1.23 and earlier, the default location for the data - files used by MySQL is located within the corresponding MySQL - Server installation directory. For MySQL 5.1.24 and later, the - default location of the data directory is the AppData directory - configured for the user that installed the MySQL application. - -2.3.3.6. Upgrading MySQL with the Installation Wizard - - The MySQL Installation Wizard can perform server upgrades - automatically using the upgrade capabilities of MSI. That means - you do not need to remove a previous installation manually before - installing a new release. The installer automatically shuts down - and removes the previous MySQL service before installing the new - version. - - Automatic upgrades are available only when upgrading between - installations that have the same major and minor version numbers. - For example, you can upgrade automatically from MySQL 4.1.5 to - MySQL 4.1.6, but not from MySQL 5.0 to MySQL 5.1. - - See Section 2.3.14, "Upgrading MySQL on Windows." - -2.3.4. MySQL Server Instance Configuration Wizard - - The MySQL Server Instance Configuration Wizard helps automate the - process of configuring your server. It creates a custom MySQL - configuration file (my.ini or my.cnf) by asking you a series of - questions and then applying your responses to a template to - generate the configuration file that is tuned to your - installation. - - The MySQL Server Instance Configuration Wizard is included with - the MySQL 5.1 server. The MySQL Server Instance Configuration - Wizard is only available for Windows. - -2.3.4.1. Starting the MySQL Server Instance Configuration Wizard - - The MySQL Server Instance Configuration Wizard is normally started - as part of the installation process. You should only need to run - the MySQL Server Instance Configuration Wizard again when you need - to change the configuration parameters of your server. - - If you chose not to open a port prior to installing MySQL on - Windows Vista, you can choose to use the MySQL Server - Configuration Wizard after installation. However, you must open a - port in the Windows Firewall. To do this see the instructions - given in Section 2.3.3.1, "Downloading and Starting the MySQL - Installation Wizard." Rather than opening a port, you also have - the option of adding MySQL as a program that bypasses the Windows - Firewall. One or the other option is sufficient --- you need not - do both. Additionally, when running the MySQL Server Configuration - Wizard on Windows Vista ensure that you are logged in as a user - with administrative rights. - MySQL Server Instance Configuration Wizard - - You can launch the MySQL Configuration Wizard by clicking the - MySQL Server Instance Config Wizard entry in the MySQL section of - the Windows Start menu. - - Alternatively, you can navigate to the bin directory of your MySQL - installation and launch the MySQLInstanceConfig.exe file directly. - - The MySQL Server Instance Configuration Wizard places the my.ini - file in the installation directory for the MySQL server. This - helps associate configuration files with particular server - instances. - - To ensure that the MySQL server knows where to look for the my.ini - file, an argument similar to this is passed to the MySQL server as - part of the service installation: ---defaults-file="C:\Program Files\MySQL\MySQL Server 5.1\my.ini" - - Here, C:\Program Files\MySQL\MySQL Server 5.1 is replaced with the - installation path to the MySQL Server. The --defaults-file option - instructs the MySQL server to read the specified file for - configuration options when it starts. - - Apart from making changes to the my.ini file by running the MySQL - Server Instance Configuration Wizard again, you can modify it by - opening it with a text editor and making any necessary changes. - You can also modify the server configuration with the MySQL - Administrator (http://www.mysql.com/products/administrator/) - utility. For more information about server configuration, see - Section 5.1.2, "Server Command Options." - - MySQL clients and utilities such as the mysql and mysqldump - command-line clients are not able to locate the my.ini file - located in the server installation directory. To configure the - client and utility applications, create a new my.ini file in the - Windows installation directory (for example, C:\WINDOWS). - - Under Windows Server 2003, Windows Server 2000, Windows XP, and - Windows Vista MySQL Server Instance Configuration Wizard will - configure MySQL to work as a Windows service. To start and stop - MySQL you use the Services application that is supplied as part of - the Windows Administrator Tools. - -2.3.4.2. Choosing a Maintenance Option - - If the MySQL Server Instance Configuration Wizard detects an - existing configuration file, you have the option of either - reconfiguring your existing server, or removing the server - instance by deleting the configuration file and stopping and - removing the MySQL service. - - To reconfigure an existing server, choose the Re-configure - Instance option and click the Next button. Any existing - configuration file is not overwritten, but renamed (within the - same directory) using a timestamp (Windows) or sequential number - (Linux). To remove the existing server instance, choose the Remove - Instance option and click the Next button. - - If you choose the Remove Instance option, you advance to a - confirmation window. Click the Execute button. The MySQL Server - Configuration Wizard stops and removes the MySQL service, and then - deletes the configuration file. The server installation and its - data folder are not removed. - - If you choose the Re-configure Instance option, you advance to the - Configuration Type dialog where you can choose the type of - installation that you wish to configure. - -2.3.4.3. Choosing a Configuration Type - - When you start the MySQL Server Instance Configuration Wizard for - a new MySQL installation, or choose the Re-configure Instance - option for an existing installation, you advance to the - Configuration Type dialog. - MySQL Server Instance Configuration Wizard: Configuration Type - - There are two configuration types available: Detailed - Configuration and Standard Configuration. The Standard - Configuration option is intended for new users who want to get - started with MySQL quickly without having to make many decisions - about server configuration. The Detailed Configuration option is - intended for advanced users who want more fine-grained control - over server configuration. - - If you are new to MySQL and need a server configured as a - single-user developer machine, the Standard Configuration should - suit your needs. Choosing the Standard Configuration option causes - the MySQL Configuration Wizard to set all configuration options - automatically with the exception of Service Options and Security - Options. - - The Standard Configuration sets options that may be incompatible - with systems where there are existing MySQL installations. If you - have an existing MySQL installation on your system in addition to - the installation you wish to configure, the Detailed Configuration - option is recommended. - - To complete the Standard Configuration, please refer to the - sections on Service Options and Security Options in Section - 2.3.4.10, "The Service Options Dialog," and Section 2.3.4.11, "The - Security Options Dialog," respectively. - -2.3.4.4. The Server Type Dialog - - There are three different server types available to choose from. - The server type that you choose affects the decisions that the - MySQL Server Instance Configuration Wizard makes with regard to - memory, disk, and processor usage. - MySQL Server Instance Configuration Wizard: Server Type - - * Developer Machine: Choose this option for a typical desktop - workstation where MySQL is intended only for personal use. It - is assumed that many other desktop applications are running. - The MySQL server is configured to use minimal system - resources. - - * Server Machine: Choose this option for a server machine where - the MySQL server is running alongside other server - applications such as FTP, email, and Web servers. The MySQL - server is configured to use a moderate portion of the system - resources. - - * Dedicated MySQL Server Machine: Choose this option for a - server machine that is intended to run only the MySQL server. - It is assumed that no other applications are running. The - MySQL server is configured to use all available system - resources. - -Note - - By selecting one of the preconfigured configurations, the values - and settings of various options in your my.cnf or my.ini will be - altered accordingly. The default values and options as described - in the reference manual may therefore be different to the options - and values that were created during the execution of the - configuration wizard. - -2.3.4.5. The Database Usage Dialog - - The Database Usage dialog allows you to indicate the storage - engines that you expect to use when creating MySQL tables. The - option you choose determines whether the InnoDB storage engine is - available and what percentage of the server resources are - available to InnoDB. - MySQL Server Instance Configuration Wizard: Usage Dialog - - * Multifunctional Database: This option enables both the InnoDB - and MyISAM storage engines and divides resources evenly - between the two. This option is recommended for users who use - both storage engines on a regular basis. - - * Transactional Database Only: This option enables both the - InnoDB and MyISAM storage engines, but dedicates most server - resources to the InnoDB storage engine. This option is - recommended for users who use InnoDB almost exclusively and - make only minimal use of MyISAM. - - * Non-Transactional Database Only: This option disables the - InnoDB storage engine completely and dedicates all server - resources to the MyISAM storage engine. This option is - recommended for users who do not use InnoDB. - - The Configuration Wizard uses a template to generate the server - configuration file. The Database Usage dialog sets one of the - following option strings: -Multifunctional Database: MIXED -Transactional Database Only: INNODB -Non-Transactional Database Only: MYISAM - - When these options are processed through the default template - (my-template.ini) the result is: -Multifunctional Database: -default-storage-engine=InnoDB -_myisam_pct=50 - -Transactional Database Only: -default-storage-engine=InnoDB -_myisam_pct=5 - -Non-Transactional Database Only: -default-storage-engine=MyISAM -_myisam_pct=100 -skip-innodb - - The _myisam_pct value is used to calculate the percentage of - resources dedicated to MyISAM. The remaining resources are - allocated to InnoDB. - -2.3.4.6. The InnoDB Tablespace Dialog - - Some users may want to locate the InnoDB tablespace files in a - different location than the MySQL server data directory. Placing - the tablespace files in a separate location can be desirable if - your system has a higher capacity or higher performance storage - device available, such as a RAID storage system. - MySQL Server Instance Configuration Wizard: InnoDB Data Tablespace - - To change the default location for the InnoDB tablespace files, - choose a new drive from the drop-down list of drive letters and - choose a new path from the drop-down list of paths. To create a - custom path, click the ... button. - - If you are modifying the configuration of an existing server, you - must click the Modify button before you change the path. In this - situation you must move the existing tablespace files to the new - location manually before starting the server. - -2.3.4.7. The Concurrent Connections Dialog - - To prevent the server from running out of resources, it is - important to limit the number of concurrent connections to the - MySQL server that can be established. The Concurrent Connections - dialog allows you to choose the expected usage of your server, and - sets the limit for concurrent connections accordingly. It is also - possible to set the concurrent connection limit manually. - MySQL Server Instance Configuration Wizard: Connections - - * Decision Support (DSS)/OLAP: Choose this option if your server - does not require a large number of concurrent connections. The - maximum number of connections is set at 100, with an average - of 20 concurrent connections assumed. - - * Online Transaction Processing (OLTP): Choose this option if - your server requires a large number of concurrent connections. - The maximum number of connections is set at 500. - - * Manual Setting: Choose this option to set the maximum number - of concurrent connections to the server manually. Choose the - number of concurrent connections from the drop-down box - provided, or enter the maximum number of connections into the - drop-down box if the number you desire is not listed. - -2.3.4.8. The Networking and Strict Mode Options Dialog - - Use the Networking Options dialog to enable or disable TCP/IP - networking and to configure the port number that is used to - connect to the MySQL server. - MySQL Server Instance Configuration Wizard: Network Configuration - - TCP/IP networking is enabled by default. To disable TCP/IP - networking, uncheck the box next to the Enable TCP/IP Networking - option. - - Port 3306 is used by default. To change the port used to access - MySQL, choose a new port number from the drop-down box or type a - new port number directly into the drop-down box. If the port - number you choose is in use, you are prompted to confirm your - choice of port number. - - Set the Server SQL Mode to either enable or disable strict mode. - Enabling strict mode (default) makes MySQL behave more like other - database management systems. If you run applications that rely on - MySQL's old "forgiving" behavior, make sure to either adapt those - applications or to disable strict mode. For more information about - strict mode, see Section 5.1.8, "Server SQL Modes." - -2.3.4.9. The Character Set Dialog - - The MySQL server supports multiple character sets and it is - possible to set a default server character set that is applied to - all tables, columns, and databases unless overridden. Use the - Character Set dialog to change the default character set of the - MySQL server. - MySQL Server Instance Configuration Wizard: Character Set - - * Standard Character Set: Choose this option if you want to use - latin1 as the default server character set. latin1 is used for - English and many Western European languages. - - * Best Support For Multilingualism: Choose this option if you - want to use utf8 as the default server character set. This is - a Unicode character set that can store characters from many - different languages. - - * Manual Selected Default Character Set / Collation: Choose this - option if you want to pick the server's default character set - manually. Choose the desired character set from the provided - drop-down list. - -2.3.4.10. The Service Options Dialog - - On Windows platforms, the MySQL server can be installed as a - Windows service. When installed this way, the MySQL server can be - started automatically during system startup, and even restarted - automatically by Windows in the event of a service failure. - - The MySQL Server Instance Configuration Wizard installs the MySQL - server as a service by default, using the service name MySQL. If - you do not wish to install the service, uncheck the box next to - the Install As Windows Service option. You can change the service - name by picking a new service name from the drop-down box provided - or by entering a new service name into the drop-down box. - -Note - - Service names can include any legal character except forward (/) - or backward (\) slashes, and must be less than 256 characters - long. - -Warning - - If you are installing multiple versions of MySQL onto the same - machine, you must choose a different service name for each version - that you install. If you do not choose a different service for - each installed version then the service manager information will - be inconsistent and this will cause problems when you try to - uninstall a previous version. - - If you have already installed multiple versions using the same - service name, you must manually edit the contents of the - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services parameters - within the Windows registry to update the association of the - service name with the correct server version. - - Typically, when installing multiple versions you create a service - name based on the version information. For example, you might - install MySQL 5.x as mysql5, or specific versions such as MySQL - 5.1.30 as mysql50130. - - To install the MySQL server as a service but not have it started - automatically at startup, uncheck the box next to the Launch the - MySQL Server Automatically option. - -2.3.4.11. The Security Options Dialog - - It is strongly recommended that you set a root password for your - MySQL server, and the MySQL Server Instance Configuration Wizard - requires by default that you do so. If you do not wish to set a - root password, uncheck the box next to the Modify Security - Settings option. - MySQL Server Instance Configuration Wizard: Security - - To set the root password, enter the desired password into both the - New root password and Confirm boxes. If you are reconfiguring an - existing server, you need to enter the existing root password into - the Current root password box. - - To prevent root logins from across the network, check the box next - to the Root may only connect from localhost option. This increases - the security of your root account. - - To create an anonymous user account, check the box next to the - Create An Anonymous Account option. Creating an anonymous account - can decrease server security and cause login and permission - difficulties. For this reason, it is not recommended. - -2.3.4.12. The Confirmation Dialog - - The final dialog in the MySQL Server Instance Configuration Wizard - is the Confirmation Dialog. To start the configuration process, - click the Execute button. To return to a previous dialog, click - the Back button. To exit the MySQL Server Instance Configuration - Wizard without configuring the server, click the Cancel button. - MySQL Server Instance Configuration Wizard: Confirmation - - After you click the Execute button, the MySQL Server Instance - Configuration Wizard performs a series of tasks and displays the - progress onscreen as the tasks are performed. - - The MySQL Server Instance Configuration Wizard first determines - configuration file options based on your choices using a template - prepared by MySQL developers and engineers. This template is named - my-template.ini and is located in your server installation - directory. - - The MySQL Configuration Wizard then writes these options to the - corresponding configuration file. - - If you chose to create a service for the MySQL server, the MySQL - Server Instance Configuration Wizard creates and starts the - service. If you are reconfiguring an existing service, the MySQL - Server Instance Configuration Wizard restarts the service to apply - your configuration changes. - - If you chose to set a root password, the MySQL Configuration - Wizard connects to the server, sets your new root password, and - applies any other security settings you may have selected. - - After the MySQL Server Instance Configuration Wizard has completed - its tasks, it displays a summary. Click the Finish button to exit - the MySQL Server Configuration Wizard. - -2.3.5. Installing MySQL from a Noinstall Zip Archive - - Users who are installing from the Noinstall package can use the - instructions in this section to manually install MySQL. The - process for installing MySQL from a Zip archive is as follows: - - 1. Extract the archive to the desired install directory - - 2. Create an option file - - 3. Choose a MySQL server type - - 4. Start the MySQL server - - 5. Secure the default user accounts - - This process is described in the sections that follow. - -2.3.6. Extracting the Install Archive - - To install MySQL manually, do the following: - - 1. If you are upgrading from a previous version please refer to - Section 2.3.14, "Upgrading MySQL on Windows," before beginning - the upgrade process. - - 2. Make sure that you are logged in as a user with administrator - privileges. - - 3. Choose an installation location. Traditionally, the MySQL - server is installed in C:\mysql. The MySQL Installation Wizard - installs MySQL under C:\Program Files\MySQL. If you do not - install MySQL at C:\mysql, you must specify the path to the - install directory during startup or in an option file. See - Section 2.3.7, "Creating an Option File." - - 4. Extract the install archive to the chosen installation - location using your preferred Zip archive tool. Some tools may - extract the archive to a folder within your chosen - installation location. If this occurs, you can move the - contents of the subfolder into the chosen installation - location. - -2.3.7. Creating an Option File - - If you need to specify startup options when you run the server, - you can indicate them on the command line or place them in an - option file. For options that are used every time the server - starts, you may find it most convenient to use an option file to - specify your MySQL configuration. This is particularly true under - the following circumstances: - - * The installation or data directory locations are different - from the default locations (C:\Program Files\MySQL\MySQL - Server 5.1 and C:\Program Files\MySQL\MySQL Server 5.1\data). - - * You need to tune the server settings, such as memory, cache, - or InnoDB configuration information. - - When the MySQL server starts on Windows, it looks for options in - two files: the my.ini file in the Windows directory, and the - C:\my.cnf file. The Windows directory typically is named something - like C:\WINDOWS. You can determine its exact location from the - value of the WINDIR environment variable using the following - command: -C:\> echo %WINDIR% - - MySQL looks for options first in the my.ini file, and then in the - my.cnf file. However, to avoid confusion, it is best if you use - only one file. If your PC uses a boot loader where C: is not the - boot drive, your only option is to use the my.ini file. Whichever - option file you use, it must be a plain text file. - - You can also make use of the example option files included with - your MySQL distribution; see Section 4.2.3.3.2, "Preconfigured - Option Files." - - An option file can be created and modified with any text editor, - such as Notepad. For example, if MySQL is installed in E:\mysql - and the data directory is in E:\mydata\data, you can create an - option file containing a [mysqld] section to specify values for - the basedir and datadir options: -[mysqld] -# set basedir to your installation path -basedir=E:/mysql -# set datadir to the location of your data directory -datadir=E:/mydata/data - - Note that Windows path names are specified in option files using - (forward) slashes rather than backslashes. If you do use - backslashes, you must double them: -[mysqld] -# set basedir to your installation path -basedir=E:\\mysql -# set datadir to the location of your data directory -datadir=E:\\mydata\\data - - MySQL Enterprise For expert advice on the start-up options - appropriate to your circumstances, subscribe to the MySQL - Enterprise Monitor. For more information, see - http://www.mysql.com/products/enterprise/advisors.html. - - In MySQL 5.1.23 and earlier, the MySQL installer places the data - directory directly under the directory where you install MySQL. On - MySQL 5.1.24 and later, the data directory is located within the - AppData directory for the user running MySQL. - - If you would like to use a data directory in a different location, - you should copy the entire contents of the data directory to the - new location. For example, if you want to use E:\mydata as the - data directory instead, you must do two things: - - 1. Move the entire data directory and all of its contents from - the default location (for example C:\Program Files\MySQL\MySQL - Server 5.1\data) to E:\mydata. - - 2. Use a --datadir option to specify the new data directory - location each time you start the server. - -2.3.8. Selecting a MySQL Server Type - - The following table shows the available servers for Windows in - MySQL 5.1.20 and earlier. - Binary Description - mysqld-nt Optimized binary with named-pipe support - mysqld Optimized binary without named-pipe support - mysqld-debug Like mysqld-nt, but compiled with full debugging and - automatic memory allocation checking - - The following table shows the available servers for Windows in - MySQL 5.1.21 and later. - Binary Description - mysqld Optimized binary with named-pipe support - mysqld-debug Like mysqld, but compiled with full debugging and - automatic memory allocation checking - - All of the preceding binaries are optimized for modern Intel - processors, but should work on any Intel i386-class or higher - processor. - - Each of the servers in a distribution support the same set of - storage engines. The SHOW ENGINES statement displays which engines - a given server supports. - - All Windows MySQL 5.1 servers have support for symbolic linking of - database directories. - - MySQL supports TCP/IP on all Windows platforms. MySQL servers on - Windows support named pipes as indicated in the following list. - However, the default is to use TCP/IP regardless of platform. - (Named pipes are slower than TCP/IP in many Windows - configurations.) - - Use of named pipes is subject to these conditions: - - * Named pipes are enabled only if you start the server with the - --enable-named-pipe option. It is necessary to use this option - explicitly because some users have experienced problems with - shutting down the MySQL server when named pipes were used. - - * For MySQL 5.1.20 and earlier, named-pipe connections are - allowed only by the mysqld-nt and mysqld-debug servers. For - MySQL 5.1.21 and later, the mysqld and mysqld-debug servers - both contain support for named-pipe connections. - -Note - - Most of the examples in this manual use mysqld as the server name. - If you choose to use a different server, such as mysqld-nt or - mysqld-debug, make the appropriate substitutions in the commands - that are shown in the examples. - -2.3.9. Starting the Server for the First Time - - This section gives a general overview of starting the MySQL - server. The following sections provide more specific information - for starting the MySQL server from the command line or as a - Windows service. - - The information here applies primarily if you installed MySQL - using the Noinstall version, or if you wish to configure and test - MySQL manually rather than with the GUI tools. - - The examples in these sections assume that MySQL is installed - under the default location of C:\Program Files\MySQL\MySQL Server - 5.1. Adjust the path names shown in the examples if you have MySQL - installed in a different location. - - Clients have two options. They can use TCP/IP, or they can use a - named pipe if the server supports named-pipe connections. - - MySQL for Windows also supports shared-memory connections if the - server is started with the --shared-memory option. Clients can - connect through shared memory by using the --protocol=MEMORY - option. - - For information about which server binary to run, see Section - 2.3.8, "Selecting a MySQL Server Type." - - Testing is best done from a command prompt in a console window (or - "DOS window"). In this way you can have the server display status - messages in the window where they are easy to see. If something is - wrong with your configuration, these messages make it easier for - you to identify and fix any problems. - - To start the server, enter this command: -C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld" --console - - For a server that includes InnoDB support, you should see the - messages similar to those following as it starts (the path names - and sizes may differ): -InnoDB: The first specified datafile c:\ibdata\ibdata1 did not exist: -InnoDB: a new database to be created! -InnoDB: Setting file c:\ibdata\ibdata1 size to 209715200 -InnoDB: Database physically writes the file full: wait... -InnoDB: Log file c:\iblogs\ib_logfile0 did not exist: new to be creat -ed -InnoDB: Setting log file c:\iblogs\ib_logfile0 size to 31457280 -InnoDB: Log file c:\iblogs\ib_logfile1 did not exist: new to be creat -ed -InnoDB: Setting log file c:\iblogs\ib_logfile1 size to 31457280 -InnoDB: Log file c:\iblogs\ib_logfile2 did not exist: new to be creat -ed -InnoDB: Setting log file c:\iblogs\ib_logfile2 size to 31457280 -InnoDB: Doublewrite buffer not found: creating new -InnoDB: Doublewrite buffer created -InnoDB: creating foreign key constraint system tables -InnoDB: foreign key constraint system tables created -011024 10:58:25 InnoDB: Started - - When the server finishes its startup sequence, you should see - something like this, which indicates that the server is ready to - service client connections: -mysqld: ready for connections -Version: '5.1.39' socket: '' port: 3306 - - The server continues to write to the console any further - diagnostic output it produces. You can open a new console window - in which to run client programs. - - If you omit the --console option, the server writes diagnostic - output to the error log in the data directory (C:\Program - Files\MySQL\MySQL Server 5.1\data by default). The error log is - the file with the .err extension. - -Note - - The accounts that are listed in the MySQL grant tables initially - have no passwords. After starting the server, you should set up - passwords for them using the instructions in Section 2.11, - "Post-Installation Setup and Testing." - -2.3.10. Starting MySQL from the Windows Command Line - - The MySQL server can be started manually from the command line. - This can be done on any version of Windows. - - To start the mysqld server from the command line, you should start - a console window (or "DOS window") and enter this command: -C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld" - - The path to mysqld may vary depending on the install location of - MySQL on your system. - - You can stop the MySQL server by executing this command: -C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqladmin" -u root - shutdown - -Note - - If the MySQL root user account has a password, you need to invoke - mysqladmin with the -p option and supply the password when - prompted. - - This command invokes the MySQL administrative utility mysqladmin - to connect to the server and tell it to shut down. The command - connects as the MySQL root user, which is the default - administrative account in the MySQL grant system. Note that users - in the MySQL grant system are wholly independent from any login - users under Windows. - - If mysqld doesn't start, check the error log to see whether the - server wrote any messages there to indicate the cause of the - problem. The error log is located in the C:\Program - Files\MySQL\MySQL Server 5.1\data directory. It is the file with a - suffix of .err. You can also try to start the server as mysqld - --console; in this case, you may get some useful information on - the screen that may help solve the problem. - - The last option is to start mysqld with the --standalone and - --debug options. In this case, mysqld writes a log file - C:\mysqld.trace that should contain the reason why mysqld doesn't - start. See MySQL Internals: Porting - (http://forge.mysql.com/wiki/MySQL_Internals_Porting). - - Use mysqld --verbose --help to display all the options that mysqld - supports. - -2.3.11. Starting MySQL as a Windows Service - - On Windows, the recommended way to run MySQL is to install it as a - Windows service, whereby MySQL starts and stops automatically when - Windows starts and stops. A MySQL server installed as a service - can also be controlled from the command line using NET commands, - or with the graphical Services utility. Generally, to install - MySQL as a Windows service you should be logged in using an - account that has administrator rights. - - The Services utility (the Windows Service Control Manager) can be - found in the Windows Control Panel (under Administrative Tools on - Windows 2000, XP, Vista and Server 2003). To avoid conflicts, it - is advisable to close the Services utility while performing server - installation or removal operations from the command line. - - Before installing MySQL as a Windows service, you should first - stop the current server if it is running by using the following - command: -C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqladmin" - -u root shutdown - -Note - - If the MySQL root user account has a password, you need to invoke - mysqladmin with the -p option and supply the password when - prompted. - - This command invokes the MySQL administrative utility mysqladmin - to connect to the server and tell it to shut down. The command - connects as the MySQL root user, which is the default - administrative account in the MySQL grant system. Note that users - in the MySQL grant system are wholly independent from any login - users under Windows. - - Install the server as a service using this command: -C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld" --install - - The service-installation command does not start the server. - Instructions for that are given later in this section. - - To make it easier to invoke MySQL programs, you can add the path - name of the MySQL bin directory to your Windows system PATH - environment variable: - - * On the Windows desktop, right-click on the My Computer icon, - and select Properties. - - * Next select the Advanced tab from the System Properties menu - that appears, and click the Environment Variables button. - - * Under System Variables, select Path, and then click the Edit - button. The Edit System Variable dialogue should appear. - - * Place your cursor at the end of the text appearing in the - space marked Variable Value. (Use the End key to ensure that - your cursor is positioned at the very end of the text in this - space.) Then enter the complete path name of your MySQL bin - directory (for example, C:\Program Files\MySQL\MySQL Server - 5.1\bin), Note that there should be a semicolon separating - this path from any values present in this field. Dismiss this - dialogue, and each dialogue in turn, by clicking OK until all - of the dialogues that were opened have been dismissed. You - should now be able to invoke any MySQL executable program by - typing its name at the DOS prompt from any directory on the - system, without having to supply the path. This includes the - servers, the mysql client, and all MySQL command-line - utilities such as mysqladmin and mysqldump. - You should not add the MySQL bin directory to your Windows - PATH if you are running multiple MySQL servers on the same - machine. - -Warning - - You must exercise great care when editing your system PATH by - hand; accidental deletion or modification of any portion of the - existing PATH value can leave you with a malfunctioning or even - unusable system. - - The following additional arguments can be used in MySQL 5.1 when - installing the service: - - * You can specify a service name immediately following the - --install option. The default service name is MySQL. - - * If a service name is given, it can be followed by a single - option. By convention, this should be - --defaults-file=file_name to specify the name of an option - file from which the server should read options when it starts. - The use of a single option other than --defaults-file is - possible but discouraged. --defaults-file is more flexible - because it enables you to specify multiple startup options for - the server by placing them in the named option file. - - * You can also specify a --local-service option following the - service name. This causes the server to run using the - LocalService Windows account that has limited system - privileges. This account is available only for Windows XP or - newer. If both --defaults-file and --local-service are given - following the service name, they can be in any order. - - For a MySQL server that is installed as a Windows service, the - following rules determine the service name and option files that - the server uses: - - * If the service-installation command specifies no service name - or the default service name (MySQL) following the --install - option, the server uses the a service name of MySQL and reads - options from the [mysqld] group in the standard option files. - - * If the service-installation command specifies a service name - other than MySQL following the --install option, the server - uses that service name. It reads options from the [mysqld] - group and the group that has the same name as the service in - the standard option files. This allows you to use the [mysqld] - group for options that should be used by all MySQL services, - and an option group with the service name for use by the - server installed with that service name. - - * If the service-installation command specifies a - --defaults-file option after the service name, the server - reads options only from the [mysqld] group of the named file - and ignores the standard option files. - - As a more complex example, consider the following command: -C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld" - --install MySQL --defaults-file=C:\my-opts.cnf - - Here, the default service name (MySQL) is given after the - --install option. If no --defaults-file option had been given, - this command would have the effect of causing the server to read - the [mysqld] group from the standard option files. However, - because the --defaults-file option is present, the server reads - options from the [mysqld] option group, and only from the named - file. - - You can also specify options as Start parameters in the Windows - Services utility before you start the MySQL service. - - Once a MySQL server has been installed as a service, Windows - starts the service automatically whenever Windows starts. The - service also can be started immediately from the Services utility, - or by using a NET START MySQL command. The NET command is not case - sensitive. - - When run as a service, mysqld has no access to a console window, - so no messages can be seen there. If mysqld does not start, check - the error log to see whether the server wrote any messages there - to indicate the cause of the problem. The error log is located in - the MySQL data directory (for example, C:\Program - Files\MySQL\MySQL Server 5.1\data). It is the file with a suffix - of .err. - - When a MySQL server has been installed as a service, and the - service is running, Windows stops the service automatically when - Windows shuts down. The server also can be stopped manually by - using the Services utility, the NET STOP MySQL command, or the - mysqladmin shutdown command. - - You also have the choice of installing the server as a manual - service if you do not wish for the service to be started - automatically during the boot process. To do this, use the - --install-manual option rather than the --install option: -C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld" --install-m -anual - - To remove a server that is installed as a service, first stop it - if it is running by executing NET STOP MySQL. Then use the - --remove option to remove it: -C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld" --remove - - If mysqld is not running as a service, you can start it from the - command line. For instructions, see Section 2.3.10, "Starting - MySQL from the Windows Command Line." - - Please see Section 2.3.13, "Troubleshooting a MySQL Installation - Under Windows," if you encounter difficulties during installation. - -2.3.12. Testing The MySQL Installation - - You can test whether the MySQL server is working by executing any - of the following commands: -C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqlshow" -C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqlshow" -u root -mysql -C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqladmin" version - status proc -C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysql" test - - If mysqld is slow to respond to TCP/IP connections from client - programs, there is probably a problem with your DNS. In this case, - start mysqld with the --skip-name-resolve option and use only - localhost and IP numbers in the Host column of the MySQL grant - tables. - - You can force a MySQL client to use a named-pipe connection rather - than TCP/IP by specifying the --pipe or --protocol=PIPE option, or - by specifying . (period) as the host name. Use the --socket option - to specify the name of the pipe if you do not want to use the - default pipe name. - - Note that if you have set a password for the root account, deleted - the anonymous account, or created a new user account, then you - must use the appropriate -u and -p options with the commands shown - above in order to connect with the MySQL Server. See Section - 4.2.2, "Connecting to the MySQL Server." - - For more information about mysqlshow, see Section 4.5.6, - "mysqlshow --- Display Database, Table, and Column Information." - -2.3.13. Troubleshooting a MySQL Installation Under Windows - - When installing and running MySQL for the first time, you may - encounter certain errors that prevent the MySQL server from - starting. The purpose of this section is to help you diagnose and - correct some of these errors. - - Your first resource when troubleshooting server issues is the - error log. The MySQL server uses the error log to record - information relevant to the error that prevents the server from - starting. The error log is located in the data directory specified - in your my.ini file. The default data directory location is - C:\Program Files\MySQL\MySQL Server 5.1\data. See Section 5.2.2, - "The Error Log." - - Another source of information regarding possible errors is the - console messages displayed when the MySQL service is starting. Use - the NET START MySQL command from the command line after installing - mysqld as a service to see any error messages regarding the - starting of the MySQL server as a service. See Section 2.3.11, - "Starting MySQL as a Windows Service." - - The following examples show other common error messages you may - encounter when installing MySQL and starting the server for the - first time: - - * If the MySQL server cannot find the mysql privileges database - or other critical files, you may see these messages: -System error 1067 has occurred. -Fatal error: Can't open privilege tables: Table 'mysql.host' doesn't -exist - These messages often occur when the MySQL base or data - directories are installed in different locations than the - default locations (C:\Program Files\MySQL\MySQL Server 5.1 and - C:\Program Files\MySQL\MySQL Server 5.1\data, respectively). - This situation may occur when MySQL is upgraded and installed - to a new location, but the configuration file is not updated - to reflect the new location. In addition, there may be old and - new configuration files that conflict. Be sure to delete or - rename any old configuration files when upgrading MySQL. - If you have installed MySQL to a directory other than - C:\Program Files\MySQL\MySQL Server 5.1, you need to ensure - that the MySQL server is aware of this through the use of a - configuration (my.ini) file. The my.ini file needs to be - located in your Windows directory, typically C:\WINDOWS. You - can determine its exact location from the value of the WINDIR - environment variable by issuing the following command from the - command prompt: -C:\> echo %WINDIR% - An option file can be created and modified with any text - editor, such as Notepad. For example, if MySQL is installed in - E:\mysql and the data directory is D:\MySQLdata, you can - create the option file and set up a [mysqld] section to - specify values for the basedir and datadir options: -[mysqld] -# set basedir to your installation path -basedir=E:/mysql -# set datadir to the location of your data directory -datadir=D:/MySQLdata - Note that Windows path names are specified in option files - using (forward) slashes rather than backslashes. If you do use - backslashes, you must double them: -[mysqld] -# set basedir to your installation path -basedir=C:\\Program Files\\MySQL\\MySQL Server 5.1 -# set datadir to the location of your data directory -datadir=D:\\MySQLdata - If you change the datadir value in your MySQL configuration - file, you must move the contents of the existing MySQL data - directory before restarting the MySQL server. - See Section 2.3.7, "Creating an Option File." - - * If you reinstall or upgrade MySQL without first stopping and - removing the existing MySQL service and install MySQL using - the MySQL Configuration Wizard, you may see this error: -Error: Cannot create Windows service for MySql. Error: 0 - This occurs when the Configuration Wizard tries to install the - service and finds an existing service with the same name. - One solution to this problem is to choose a service name other - than mysql when using the configuration wizard. This allows - the new service to be installed correctly, but leaves the - outdated service in place. Although this is harmless, it is - best to remove old services that are no longer in use. - To permanently remove the old mysql service, execute the - following command as a user with administrative privileges, on - the command-line: -C:\> sc delete mysql -[SC] DeleteService SUCCESS - If the sc utility is not available for your version of - Windows, download the delsrv utility from - http://www.microsoft.com/windows2000/techinfo/reskit/tools/exi - sting/delsrv-o.asp and use the delsrv mysql syntax. - -2.3.14. Upgrading MySQL on Windows - - This section lists some of the steps you should take when - upgrading MySQL on Windows. - - 1. Review Section 2.12.1, "Upgrading MySQL," for additional - information on upgrading MySQL that is not specific to - Windows. - - 2. You should always back up your current MySQL installation - before performing an upgrade. See Section 6.1, "Database - Backups." - - 3. Download the latest Windows distribution of MySQL from - http://dev.mysql.com/downloads/. - - 4. Before upgrading MySQL, you must stop the server. If the - server is installed as a service, stop the service with the - following command from the command prompt: -C:\> NET STOP MySQL - If you are not running the MySQL server as a service, use the - following command to stop it: -C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqladmin" -u root - shutdown - -Note - If the MySQL root user account has a password, you need to - invoke mysqladmin with the -p option and supply the password - when prompted. - - 5. When upgrading to MySQL 5.1 from a version previous to 4.1.5, - or when upgrading from a version of MySQL installed from a Zip - archive to a version of MySQL installed with the MySQL - Installation Wizard, you must manually remove the previous - installation and MySQL service (if the server is installed as - a service). - To remove the MySQL service, use the following command: -C:\> C:\mysql\bin\mysqld --remove - If you do not remove the existing service, the MySQL - Installation Wizard may fail to properly install the new MySQL - service. - - 6. When upgrading from MySQL 5.1.23 to MySQL 5.1.24, the change - in the default location of the data directory from a directory - within the MySQL installation to the AppData folder means that - you must manually copy the data files from your old - installation to the new location. - - 7. If you are using the MySQL Installation Wizard, start the - wizard as described in Section 2.3.3, "Using the MySQL - Installation Wizard." - - 8. If you are installing MySQL from a Zip archive, extract the - archive. You may either overwrite your existing MySQL - installation (usually located at C:\mysql), or install it into - a different directory, such as C:\mysql5. Overwriting the - existing installation is recommended. - - 9. If you were running MySQL as a Windows service and you had to - remove the service earlier in this procedure, reinstall the - service. (See Section 2.3.11, "Starting MySQL as a Windows - Service.") - 10. Restart the server. For example, use NET START MySQL if you - run MySQL as a service, or invoke mysqld directly otherwise. - 11. If you encounter errors, see Section 2.3.13, "Troubleshooting - a MySQL Installation Under Windows." - -2.3.15. MySQL on Windows Compared to MySQL on Unix - - MySQL for Windows has proven itself to be very stable. The Windows - version of MySQL has the same features as the corresponding Unix - version, with the following exceptions: - - * Limited number of ports - Windows systems have about 4,000 ports available for client - connections, and after a connection on a port closes, it takes - two to four minutes before the port can be reused. In - situations where clients connect to and disconnect from the - server at a high rate, it is possible for all available ports - to be used up before closed ports become available again. If - this happens, the MySQL server appears to be unresponsive even - though it is running. Note that ports may be used by other - applications running on the machine as well, in which case the - number of ports available to MySQL is lower. - For more information about this problem, see - http://support.microsoft.com/default.aspx?scid=kb;en-us;196271 - . - - * Concurrent reads - MySQL depends on the pread() and pwrite() system calls to be - able to mix INSERT and SELECT. Currently, we use mutexes to - emulate pread() and pwrite(). We intend to replace the file - level interface with a virtual interface in the future so that - we can use the readfile()/writefile() interface to get more - speed. The current implementation limits the number of open - files that MySQL 5.1 can use to 2,048, which means that you - cannot run as many concurrent threads on Windows as on Unix. - - * Blocking read - MySQL uses a blocking read for each connection. That has the - following implications if named-pipe connections are enabled: - - + A connection is not disconnected automatically after - eight hours, as happens with the Unix version of MySQL. - - + If a connection hangs, it is not possible to break it - without killing MySQL. - - + mysqladmin kill does not work on a sleeping connection. - - + mysqladmin shutdown cannot abort as long as there are - sleeping connections. - We plan to fix this problem in the future. - - * ALTER TABLE - While you are executing an ALTER TABLE statement, the table is - locked from being used by other threads. This has to do with - the fact that on Windows, you can't delete a file that is in - use by another thread. In the future, we may find some way to - work around this problem. - - * DROP TABLE - DROP TABLE on a table that is in use by a MERGE table does not - work on Windows because the MERGE handler does the table - mapping hidden from the upper layer of MySQL. Because Windows - does not allow dropping files that are open, you first must - flush all MERGE tables (with FLUSH TABLES) or drop the MERGE - table before dropping the table. - - * DATA DIRECTORY and INDEX DIRECTORY - The DATA DIRECTORY and INDEX DIRECTORY options for CREATE - TABLE are ignored on Windows, because Windows doesn't support - symbolic links. These options also are ignored on systems that - have a nonfunctional realpath() call. - - * DROP DATABASE - You cannot drop a database that is in use by some thread. - - * Case-insensitive names - File names are not case sensitive on Windows, so MySQL - database and table names are also not case sensitive on - Windows. The only restriction is that database and table names - must be specified using the same case throughout a given - statement. See Section 8.2.2, "Identifier Case Sensitivity." - - * Directory and file names - On Windows, MySQL Server supports only directory and file - names that are compatible with the current ANSI code pages. - For example, the following Japanese directory name will not - work in the Western locale (code page 1252): -datadir="C:/维基百科关于ä¸æ–‡ç»´åŸºç™¾ç§‘" - The same limitation applies to directory and file names - referred to in SQL statements, such as the data file path name - in LOAD DATA INFILE. - - * The "\" path name separator character - Path name components in Windows are separated by the "\" - character, which is also the escape character in MySQL. If you - are using LOAD DATA INFILE or SELECT ... INTO OUTFILE, use - Unix-style file names with "/" characters: -mysql> LOAD DATA INFILE 'C:/tmp/skr.txt' INTO TABLE skr; -mysql> SELECT * INTO OUTFILE 'C:/tmp/skr.txt' FROM skr; - Alternatively, you must double the "\" character: -mysql> LOAD DATA INFILE 'C:\\tmp\\skr.txt' INTO TABLE skr; -mysql> SELECT * INTO OUTFILE 'C:\\tmp\\skr.txt' FROM skr; - - * Problems with pipes - Pipes do not work reliably from the Windows command-line - prompt. If the pipe includes the character ^Z / CHAR(24), - Windows thinks that it has encountered end-of-file and aborts - the program. - This is mainly a problem when you try to apply a binary log as - follows: -C:\> mysqlbinlog binary_log_file | mysql --user=root - If you have a problem applying the log and suspect that it is - because of a ^Z / CHAR(24) character, you can use the - following workaround: -C:\> mysqlbinlog binary_log_file --result-file=/tmp/bin.sql -C:\> mysql --user=root --execute "source /tmp/bin.sql" - The latter command also can be used to reliably read in any - SQL file that may contain binary data. - - * Access denied for user error - If MySQL cannot resolve your host name properly, you may get - the following error when you attempt to run a MySQL client - program to connect to a server running on the same machine: -Access denied for user 'some_user'@'unknown' -to database 'mysql' - To fix this problem, you should create a file named - \windows\hosts containing the following information: -127.0.0.1 localhost - - Here are some open issues for anyone who might want to help us - improve MySQL on Windows: - - * Add macros to use the faster thread-safe increment/decrement - methods provided by Windows. - -2.4. Installing MySQL from RPM Packages on Linux - - The recommended way to install MySQL on RPM-based Linux - distributions is by using the RPM packages. The RPMs that we - provide to the community should work on all versions of Linux that - support RPM packages and use glibc 2.3. To obtain RPM packages, - see Section 2.1.3, "How to Get MySQL." - - For non-RPM Linux distributions, you can install MySQL using a - .tar.gz package. See Section 2.9, "Installing MySQL from tar.gz - Packages on Other Unix-Like Systems." - - We do provide some platform-specific RPMs; the difference between - a platform-specific RPM and a generic RPM is that a - platform-specific RPM is built on the targeted platform and is - linked dynamically whereas a generic RPM is linked statically with - LinuxThreads. - -Note - - RPM distributions of MySQL often are provided by other vendors. Be - aware that they may differ in features and capabilities from those - built by us, and that the instructions in this manual do not - necessarily apply to installing them. The vendor's instructions - should be consulted instead. - - If you have problems with an RPM file (for example, if you receive - the error Sorry, the host 'xxxx' could not be looked up), see - Section 2.13.1.2, "Linux Binary Distribution Notes." - - In most cases, you need to install only the MySQL-server and - MySQL-client packages to get a functional MySQL installation. The - other packages are not required for a standard installation. - - RPMs for MySQL Cluster. Beginning with MySQL 5.1.24, standard - MySQL server RPMs built by MySQL no longer provide support for the - NDBCLUSTER storage engine. MySQL Cluster users wanting to upgrade - MySQL 5.1.23 or earlier installations from RPMs built by MySQL - should upgrade to MySQL Cluster NDB 6.2 or MySQL Cluster NDB 6.3; - RPMs that should work with most Linux distributions are available - for both of these release series. - -Important - - When upgrading a MySQL Cluster RPM installation, you must upgrade - all installed RPMs, including the Server and Client RPMs. - - For more information about installing MySQL Cluster from RPMs, see - Section 17.2.2, "MySQL Cluster Multi-Computer Installation." - - For upgrades, if your installation was originally produced by - installing multiple RPM packages, it is best to upgrade all the - packages, not just some. For example, if you previously installed - the server and client RPMs, do not upgrade just the server RPM. - - If you get a dependency failure when trying to install MySQL - packages (for example, error: removing these packages would break - dependencies: libmysqlclient.so.10 is needed by ...), you should - also install the MySQL-shared-compat package, which includes both - the shared libraries for backward compatibility - (libmysqlclient.so.12 for MySQL 4.0 and libmysqlclient.so.10 for - MySQL 3.23). - - Some Linux distributions still ship with MySQL 3.23 and they - usually link applications dynamically to save disk space. If these - shared libraries are in a separate package (for example, - MySQL-shared), it is sufficient to simply leave this package - installed and just upgrade the MySQL server and client packages - (which are statically linked and do not depend on the shared - libraries). For distributions that include the shared libraries in - the same package as the MySQL server (for example, Red Hat Linux), - you could either install our 3.23 MySQL-shared RPM, or use the - MySQL-shared-compat package instead. (Do not install both.) - - The RPM packages shown in the following list are available. The - names shown here use a suffix of .glibc23.i386.rpm, but particular - packages can have different suffixes, as described later. - - * MySQL-server-VERSION.glibc23.i386.rpm - The MySQL server. You need this unless you only want to - connect to a MySQL server running on another machine. - - * MySQL-client-VERSION.glibc23.i386.rpm - The standard MySQL client programs. You probably always want - to install this package. - - * MySQL-devel-VERSION.glibc23.i386.rpm - The libraries and include files that are needed if you want to - compile other MySQL clients, such as the Perl modules. - - * MySQL-debuginfo-VERSION.glibc23.i386.rpm - This package contains debugging information. debuginfo RPMs - are never needed to use MySQL software; this is true both for - the server and for client programs. However, they contain - additional information that might be needed by a debugger to - analyze a crash. - - * MySQL-shared-VERSION.glibc23.i386.rpm - This package contains the shared libraries - (libmysqlclient.so*) that certain languages and applications - need to dynamically load and use MySQL. It contains - single-threaded and thread-safe libraries. If you install this - package, do not install the MySQL-shared-compat package. - - * MySQL-shared-compat-VERSION.glibc23.i386.rpm - This package includes the shared libraries for MySQL 3.23, - 4.0, and so on, up to the current release. It contains - single-threaded and thread-safe libraries. Install this - package instead of MySQL-shared if you have applications - installed that are dynamically linked against older versions - of MySQL but you want to upgrade to the current version - without breaking the library dependencies. - - * MySQL-embedded-VERSION.glibc23.i386.rpm - The embedded MySQL server library. - - * MySQL-ndb-management-VERSION.glibc23.i386.rpm, - MySQL-ndb-storage-VERSION.glibc23.i386.rpm, - MySQL-ndb-tools-VERSION.glibc23.i386.rpm, - MySQL-ndb-extra-VERSION.glibc23.i386.rpm - Packages that contain additional files for MySQL Cluster - installations. - -Note - The MySQL-ndb-tools RPM requires a working installation of - perl. Prior to MySQL 5.1.18, the DBI and HTML::Template - packages were also required. See Section 2.15, "Perl - Installation Notes," and Section 17.6.21, "ndb_size.pl --- - NDBCLUSTER Size Requirement Estimator," for more information. - - * MySQL-test-VERSION.glibc23.i386.rpm - This package includes the MySQL test suite. - - * MySQL-VERSION.src.rpm - This contains the source code for all of the previous - packages. It can also be used to rebuild the RPMs on other - architectures (for example, Alpha or SPARC). - - The suffix of RPM package names (following the VERSION value) has - the following syntax: -.PLATFORM.CPU.rpm - - The PLATFORM and CPU values indicate the type of system for which - the package is built. PLATFORM indicates the platform and CPU - indicates the processor type or family. - - All packages are dynamically linked against glibc 2.3. The - PLATFORM value indicates whether the package is platform - independent or intended for a specific platform, as shown in the - following table. - glibc23 Platform independent, should run on any Linux distribution - that supports glibc 2.3 - rhel3, rhel4 Red Hat Enterprise Linux 3 or 4 - sles9, sles10 SuSE Linux Enterprise Server 9 or 10 - - In MySQL 5.1, only glibc23 packages are available currently. - - The CPU value indicates the processor type or family for which the - package is built. - i386 x86 processor, 386 and up - i586 x86 processor, Pentium and up - x86_64 64-bit x86 processor - ia64 Itanium (IA-64) processor - - To see all files in an RPM package (for example, a MySQL-server - RPM), run a command like this: -shell> rpm -qpl MySQL-server-VERSION.glibc23.i386.rpm - - To perform a standard minimal installation, install the server and - client RPMs: -shell> rpm -i MySQL-server-VERSION.glibc23.i386.rpm -shell> rpm -i MySQL-client-VERSION.glibc23.i386.rpm - - To install only the client programs, install just the client RPM: -shell> rpm -i MySQL-client-VERSION.glibc23.i386.rpm - - RPM provides a feature to verify the integrity and authenticity of - packages before installing them. If you would like to learn more - about this feature, see Section 2.1.4, "Verifying Package - Integrity Using MD5 Checksums or GnuPG." - - The server RPM places data under the /var/lib/mysql directory. The - RPM also creates a login account for a user named mysql (if one - does not exist) to use for running the MySQL server, and creates - the appropriate entries in /etc/init.d/ to start the server - automatically at boot time. (This means that if you have performed - a previous installation and have made changes to its startup - script, you may want to make a copy of the script so that you - don't lose it when you install a newer RPM.) See Section 2.11.2.2, - "Starting and Stopping MySQL Automatically," for more information - on how MySQL can be started automatically on system startup. - - If you want to install the MySQL RPM on older Linux distributions - that do not support initialization scripts in /etc/init.d - (directly or via a symlink), you should create a symbolic link - that points to the location where your initialization scripts - actually are installed. For example, if that location is - /etc/rc.d/init.d, use these commands before installing the RPM to - create /etc/init.d as a symbolic link that points there: -shell> cd /etc -shell> ln -s rc.d/init.d . - - However, all current major Linux distributions should support the - new directory layout that uses /etc/init.d, because it is required - for LSB (Linux Standard Base) compliance. - - If the RPM files that you install include MySQL-server, the mysqld - server should be up and running after installation. You should be - able to start using MySQL. - - If something goes wrong, you can find more information in the - binary installation section. See Section 2.9, "Installing MySQL - from tar.gz Packages on Other Unix-Like Systems." - -Note - - The accounts that are listed in the MySQL grant tables initially - have no passwords. After starting the server, you should set up - passwords for them using the instructions in Section 2.11, - "Post-Installation Setup and Testing." - - During RPM installation, a user named mysql and a group named - mysql are created on the system. This is done using the useradd, - groupadd, and usermod commands. Those commands require appropriate - administrative privileges, which is ensured for locally managed - users and groups (as listed in the /etc/passwd and /etc/group - files) by the RPM installation process being run by root. - - For nonlocal user management (LDAP, NIS, and so forth), the - administrative tools may require additional authentication (such - as a password), and will fail if the installing user does not - provide this authentication. Even if they fail, the RPM - installation will not abort but succeed, and this is intentional. - If they failed, some of the intended transfer of ownership may be - missing, and it is recommended that the system administrator then - manually ensures some appropriate user andgroup exists and - manually transfers ownership following the actions in the RPM spec - file. - -2.5. Installing MySQL on Mac OS X - - You can install MySQL on Mac OS X 10.3.x ("Panther") or newer - using a Mac OS X binary package in PKG format instead of the - binary tarball distribution. Please note that older versions of - Mac OS X (for example, 10.1.x or 10.2.x) are not supported by this - package. - - The package is located inside a disk image (.dmg) file that you - first need to mount by double-clicking its icon in the Finder. It - should then mount the image and display its contents. - - To obtain MySQL, see Section 2.1.3, "How to Get MySQL." - -Note - - Before proceeding with the installation, be sure to shut down all - running MySQL server instances by either using the MySQL Manager - Application (on Mac OS X Server) or via mysqladmin shutdown on the - command line. - - To actually install the MySQL PKG file, double-click on the - package icon. This launches the Mac OS X Package Installer, which - guides you through the installation of MySQL. - - Due to a bug in the Mac OS X package installer, you may see this - error message in the destination disk selection dialog: -You cannot install this software on this disk. (null) - - If this error occurs, simply click the Go Back button once to - return to the previous screen. Then click Continue to advance to - the destination disk selection again, and you should be able to - choose the destination disk correctly. We have reported this bug - to Apple and it is investigating this problem. - - The Mac OS X PKG of MySQL installs itself into - /usr/local/mysql-VERSION and also installs a symbolic link, - /usr/local/mysql, that points to the new location. If a directory - named /usr/local/mysql exists, it is renamed to - /usr/local/mysql.bak first. Additionally, the installer creates - the grant tables in the mysql database by executing - mysql_install_db. - - The installation layout is similar to that of a tar file binary - distribution; all MySQL binaries are located in the directory - /usr/local/mysql/bin. The MySQL socket file is created as - /tmp/mysql.sock by default. See Section 2.1.5, "Installation - Layouts." - - MySQL installation requires a Mac OS X user account named mysql. A - user account with this name should exist by default on Mac OS X - 10.2 and up. - - If you are running Mac OS X Server, a version of MySQL should - already be installed. The following table shows the versions of - MySQL that ship with Mac OS X Server versions. - Mac OS X Server Version MySQL Version - 10.2-10.2.2 3.23.51 - 10.2.3-10.2.6 3.23.53 - 10.3 4.0.14 - 10.3.2 4.0.16 - 10.4.0 4.1.10a - - This manual section covers the installation of the official MySQL - Mac OS X PKG only. Make sure to read Apple's help information - about installing MySQL: Run the "Help View" application, select - "Mac OS X Server" help, do a search for "MySQL," and read the item - entitled "Installing MySQL." - - If you previously used Marc Liyanage's MySQL packages for Mac OS X - from http://www.entropy.ch, you can simply follow the update - instructions for packages using the binary installation layout as - given on his pages. - - If you are upgrading from Marc's 3.23.x versions or from the Mac - OS X Server version of MySQL to the official MySQL PKG, you also - need to convert the existing MySQL privilege tables to the current - format, because some new security privileges have been added. See - Section 4.4.8, "mysql_upgrade --- Check Tables for MySQL Upgrade." - - If you want MySQL to start automatically during system startup, - you also need to install the MySQL Startup Item. It is part of the - Mac OS X installation disk images as a separate installation - package. Simply double-click the MySQLStartupItem.pkg icon and - follow the instructions to install it. The Startup Item need be - installed only once. There is no need to install it each time you - upgrade the MySQL package later. - - The Startup Item for MySQL is installed into - /Library/StartupItems/MySQLCOM. (Before MySQL 4.1.2, the location - was /Library/StartupItems/MySQL, but that collided with the MySQL - Startup Item installed by Mac OS X Server.) Startup Item - installation adds a variable MYSQLCOM=-YES- to the system - configuration file /etc/hostconfig. If you want to disable the - automatic startup of MySQL, simply change this variable to - MYSQLCOM=-NO-. - - On Mac OS X Server, the default MySQL installation uses the - variable MYSQL in the /etc/hostconfig file. The MySQL Startup Item - installer disables this variable by setting it to MYSQL=-NO-. This - avoids boot time conflicts with the MYSQLCOM variable used by the - MySQL Startup Item. However, it does not shut down a running MySQL - server. You should do that yourself. - - After the installation, you can start up MySQL by running the - following commands in a terminal window. You must have - administrator privileges to perform this task. - - If you have installed the Startup Item, use this command: -shell> sudo /Library/StartupItems/MySQLCOM/MySQLCOM start -(Enter your password, if necessary) -(Press Control-D or enter "exit" to exit the shell) - - If you don't use the Startup Item, enter the following command - sequence: -shell> cd /usr/local/mysql -shell> sudo ./bin/mysqld_safe -(Enter your password, if necessary) -(Press Control-Z) -shell> bg -(Press Control-D or enter "exit" to exit the shell) - - You should be able to connect to the MySQL server, for example, by - running /usr/local/mysql/bin/mysql. - -Note - - The accounts that are listed in the MySQL grant tables initially - have no passwords. After starting the server, you should set up - passwords for them using the instructions in Section 2.11, - "Post-Installation Setup and Testing." - - You might want to add aliases to your shell's resource file to - make it easier to access commonly used programs such as mysql and - mysqladmin from the command line. The syntax for bash is: -alias mysql=/usr/local/mysql/bin/mysql -alias mysqladmin=/usr/local/mysql/bin/mysqladmin - - For tcsh, use: -alias mysql /usr/local/mysql/bin/mysql -alias mysqladmin /usr/local/mysql/bin/mysqladmin - - Even better, add /usr/local/mysql/bin to your PATH environment - variable. You can do this by modifying the appropriate startup - file for your shell. For more information, see Section 4.2.1, - "Invoking MySQL Programs." - - If you are upgrading an existing installation, note that - installing a new MySQL PKG does not remove the directory of an - older installation. Unfortunately, the Mac OS X Installer does not - yet offer the functionality required to properly upgrade - previously installed packages. - - To use your existing databases with the new installation, you'll - need to copy the contents of the old data directory to the new - data directory. Make sure that neither the old server nor the new - one is running when you do this. After you have copied over the - MySQL database files from the previous installation and have - successfully started the new server, you should consider removing - the old installation files to save disk space. Additionally, you - should also remove older versions of the Package Receipt - directories located in /Library/Receipts/mysql-VERSION.pkg. - -2.6. Installing MySQL on Solaris - - To obtain a binary MySQL distribution for Solaris in tarball or - PKG format, http://dev.mysql.com/downloads/mysql/5.1.html. - - If you install MySQL using a binary tarball distribution on - Solaris, you may run into trouble even before you get the MySQL - distribution unpacked, as the Solaris tar cannot handle long file - names. This means that you may see errors when you try to unpack - MySQL. - - If this occurs, you must use GNU tar (gtar) to unpack the - distribution. - - You can install MySQL on Solaris using a binary package in PKG - format instead of the binary tarball distribution. Before - installing using the binary PKG format, you should create the - mysql user and group, for example: -groupadd mysql -useradd -g mysql mysql - - Some basic PKG-handling commands follow: - - * To add a package: -pkgadd -d package_name.pkg - - * To remove a package: -pkgrm package_name - - * To get a full list of installed packages: -pkginfo - - * To get detailed information for a package: -pkginfo -l package_name - - * To list the files belonging to a package: -pkgchk -v package_name - - * To get packaging information for an arbitrary file: -pkgchk -l -p file_name - - For additional information about installing MySQL on Solaris, see - Section 2.13.3, "Solaris Notes." - -2.7. Installing MySQL on i5/OS - - The i5/OS POWER MySQL package was created in cooperation with IBM. - MySQL works within the Portable Application Solution Environment - (PASE) on the System i series of hardware and will also provide - database services for the Zend Core for i5/OS. - - MySQL for i5/OS is provided as a save file (.savf) package that - can be downloaded and installed directly without any additional - installation steps required. - - MySQL is only supported on i5/OS V5R4 or later releases. The i5/OS - PASE must be installed for MySQL to operate. You must be able to - login as a user in *SECOFR class. - - You should the installation notes and tips for i5/OS before - starting installation. See i5/OS Installation Notes. - -Note - - The installation package will use an existing configuration if you - have previously installed MySQL (which is identified by looking - for the file /etc/my.cnf). The values for the data directory - (DATADIR) and owner of the MySQL files (USRPRF) specified during - the installation will be ignored, and the values determined from - the /etc/my.cnf will be used instead. - - If you want to change these parameters during a new install, you - should temporarily rename /etc/my.cnf, install MySQL using the new - parameters you want to use, and then merge your previous - /etc/my.cnf configuration settings with the new /etc/my.cnf file - that is created during installation. - - To install MySQL on i5/OS, follow these steps: - - 1. Create a user profile MYSQL. The MYSQL user profile will own - all the MySQL files and databases and be the active user used - when the MySQL server is running. The profile should be - disabled so that you cannot log in as the MySQL user. To - create a user profile, use CRTUSRPRF: -CRTUSRPRF USRPRF(MYSQL) STATUS(*DISABLED) TEXT('MySQL user id') - - 2. On the System i machine, create a save file that will be used - to receive the downloaded installation save file. The file - should be located within the General Purpose Library (QGPL): -CRTSAVF FILE(QGPL/MYSQLINST) - - 3. Download the MySQL installation save file in 32-bit - (mysql-5.0.42-i5os-power-32bit.savf) or 64-bit - (mysql-5.0.42-i5os-power-64bit.savf) from MySQL Downloads - (http://dev.mysql.com/downloads). - - 4. You need to FTP the downloaded .savf file directly into the - QGPL/MYSQLINST file on the System i server. You can do this - through FTP using the following steps after logging in to the - System i machine: -ftp> bin -ftp> cd qgpl -ftp> put mysql-5.0.42-i5os-power.savf mysqlinst - - 5. Log into the System i server using a user in the *SECOFR - class, such as the QSECOFR user ID. - - 6. You need to restore the installation library stored in the - .savf save file: -RSTLIB MYSQLINST DEV(*SAVF) SAVF(QGPL/MYSQLINST) - - 7. You need to execute the installation command, - MYSQLINST/INSMYSQL. You can specify three parameter settings - during installation: - - + DIR('/opt/mysql') sets the installation location for the - MySQL files. The directory will be created if it does not - already exist. - - + DATADIR('/QOpenSys/mysal/data') sets the location of the - directory that will be used to store the database files - and binary logs. The default setting is - /QOpenSys/mysql/data. Note that if the installer detects - an existing installation (due to the existence of - /etc/my.cnf), then this parameter will be ignored. - - + USRPRF(MYSQL) sets the user profile that will own the - files that are installed. The profile will be created if - it does not already exist. - MySQL can be installed anywhere, for this example we will - assume MySQL has been installed into /opt/mysql. The MYSQL - user profile that was created earlier in this sequence should - be used for the profile: -MYSQLINST/INSMYSQL DIR('/opt/mysql') DATADIR('/opt/mysqldata') USRPRF -(MYSQL) - If you are updating an installation over an existing MySQL - installation, you should use the same parameter values that - were used when MySQL was originally installed. - The installation copies all the necessary files into a - directory matching the package version (for example - mysql-5.0.42-i5os-power-32bit), sets the ownership on those - files, sets up the MySQL environment and creates the MySQL - configuration file (in /etc/my.cnf) completing all the steps - in a typical binary installation process automatically. If - this is a new installation of MySQL, or if the installer - detects that this is a new version (because the /etc/my.cnf - file does not exist), then the initial core MySQL databases - will also be created during installation. - - 8. Once the installation has completed, you can delete the - installation file: -DLTLIB LIB(MYSQLINST) - - To start MySQL: - - 1. Log into the System i server using a user within the *SECOFR - class, such as the QSECOFR user ID. - -Note - You should start mysqld_safe using a user that in the PASE - environment has the id=0 (the equivalent of the standard Unix - root user). If you do not use a user with this ID then the - system will be unable to change the user when executing mysqld - as set using --user option. If this happens, mysqld may be - unable to read the files located within the MySQL data - directory and the execution will fail. - - 2. Enter the PASE environment using call qp2term. - - 3. Start the MySQL server by changing to the installation - directory and running mysqld_safe, specifying the user name - used to install the server. The installer conveniently - installs a symbolic link to the installation directory - (mysql-5.0.42-i5os-power-32bit) as /opt/mysql/mysql: -> cd /opt/mysql/mysql -> bin/mysqld_safe --user=mysql & - You should see a message similar to the following: -Starting mysqld daemon with databases » - from /opt/mysql/mysql-enterprise-5.0.42-i5os-power-32bit/data - - If you are having problems starting MySQL server, see Section - 2.11.2.3, "Starting and Troubleshooting the MySQL Server." - - To stop MySQL: - - 1. Log into the System i server using the *SECOFR class, such as - the QSECOFR user ID. - - 2. Enter the PASE environment using call qp2term. - - 3. Stop the MySQL server by changing into the installation - directory and running mysqladmin, specifying the user name - used to install the server: -> cd /opt/mysql/mysql -> bin/mysqladmin -u root shutdown - If the session that you started and stopped MySQL are the - same, you may get the log output from mysqld: - STOPPING server from pid file » - /opt/mysql/mysql-enterprise-5.0.42-i5os-power-32bit/data/I5DBX.R -CHLAND.IBM.COM.pid - 070718 10:34:20 mysqld ended - If the sessions used to start and stop MySQL are different, - you will not receive any confirmation of the shutdown. - - Note and tips - - * A problem has been identified with the installation process on - DBCS systems. If you are having problems install MySQL on a - DBCS system, you need to change your job's coded character set - identifier (CSSID) to 37 (EBCDIC) before executing the install - command, INSMYSQL. To do this, determine your existing CSSID - (using DSPJOB and selecting option 2), execute CHGJOB - CSSID(37), run INSMYSQL to install MySQL and then execute - CHGJOB again with your original CSSID. - - * If you want to use the Perl scripts that are included with - MySQL, you need to download the iSeries Tools for Developers - (5799-PTL). See - http://www-03.ibm.com/servers/enable/site/porting/tools/. - -2.8. Installing MySQL on NetWare - - Porting MySQL to NetWare was an effort spearheaded by Novell. - Novell customers should be pleased to note that NetWare 6.5 ships - with bundled MySQL binaries, complete with an automatic commercial - use license for all servers running that version of NetWare. - - MySQL for NetWare is compiled using a combination of Metrowerks - CodeWarrior for NetWare and special cross-compilation versions of - the GNU autotools. - - The latest binary packages for NetWare can be obtained at - http://dev.mysql.com/downloads/. See Section 2.1.3, "How to Get - MySQL." - - To host MySQL, the NetWare server must meet these requirements: - - * The latest Support Pack of NetWare 6.5 - (http://support.novell.com/filefinder/18197/index.html) must - be installed. - - * The system must meet Novell's minimum requirements to run the - respective version of NetWare. - - * MySQL data and the program binaries must be installed on an - NSS volume; traditional volumes are not supported. - - To install MySQL for NetWare, use the following procedure: - - 1. If you are upgrading from a prior installation, stop the MySQL - server. This is done from the server console, using the - following command: -SERVER: mysqladmin -u root shutdown - -Note - If the MySQL root user account has a password, you need to - invoke mysqladmin with the -p option and supply the password - when prompted. - - 2. Log on to the target server from a client machine with access - to the location where you are installing MySQL. - - 3. Extract the binary package Zip file onto the server. Be sure - to allow the paths in the Zip file to be used. It is safe to - simply extract the file to SYS:\. - If you are upgrading from a prior installation, you may need - to copy the data directory (for example, SYS:MYSQL\DATA), as - well as my.cnf, if you have customized it. You can then delete - the old copy of MySQL. - - 4. You might want to rename the directory to something more - consistent and easy to use. The examples in this manual use - SYS:MYSQL to refer to the installation directory. - Note that MySQL installation on NetWare does not detect if a - version of MySQL is already installed outside the NetWare - release. Therefore, if you have installed the latest MySQL - version from the Web (for example, MySQL 4.1 or later) in - SYS:\MYSQL, you must rename the folder before upgrading the - NetWare server; otherwise, files in SYS:\MySQL are overwritten - by the MySQL version present in NetWare Support Pack. - - 5. At the server console, add a search path for the directory - containing the MySQL NLMs. For example: -SERVER: SEARCH ADD SYS:MYSQL\BIN - - 6. Initialize the data directory and the grant tables, if - necessary, by executing mysql_install_db at the server - console. - - 7. Start the MySQL server using mysqld_safe at the server - console. - - 8. To finish the installation, you should also add the following - commands to autoexec.ncf. For example, if your MySQL - installation is in SYS:MYSQL and you want MySQL to start - automatically, you could add these lines: -#Starts the MySQL 5.1.x database server -SEARCH ADD SYS:MYSQL\BIN -MYSQLD_SAFE - If you are running MySQL on NetWare 6.0, we strongly suggest - that you use the --skip-external-locking option on the command - line: -#Starts the MySQL 5.1.x database server -SEARCH ADD SYS:MYSQL\BIN -MYSQLD_SAFE --skip-external-locking - It is also necessary to use CHECK TABLE and REPAIR TABLE - instead of myisamchk, because myisamchk makes use of external - locking. External locking is known to have problems on NetWare - 6.0; the problem has been eliminated in NetWare 6.5. Note that - the use of MySQL on Netware 6.0 is not officially supported. - mysqld_safe on NetWare provides a screen presence. When you - unload (shut down) the mysqld_safe NLM, the screen does not go - away by default. Instead, it prompts for user input: -*<NLM has terminated; Press any key to close the screen>* - If you want NetWare to close the screen automatically instead, - use the --autoclose option to mysqld_safe. For example: -#Starts the MySQL 5.1.x database server -SEARCH ADD SYS:MYSQL\BIN -MYSQLD_SAFE --autoclose - The behavior of mysqld_safe on NetWare is described further in - Section 4.3.2, "mysqld_safe --- MySQL Server Startup Script." - - 9. When installing MySQL, either for the first time or upgrading - from a previous version, download and install the latest and - appropriate Perl module and PHP extensions for NetWare: - - + Perl: - http://forge.novell.com/modules/xfcontent/downloads.php/p - erl/Modules/ - - + PHP: - http://forge.novell.com/modules/xfcontent/downloads.php/p - hp/Modules/ - - If there was an existing installation of MySQL on the NetWare - server, be sure to check for existing MySQL startup commands in - autoexec.ncf, and edit or delete them as necessary. - -Note - - The accounts that are listed in the MySQL grant tables initially - have no passwords. After starting the server, you should set up - passwords for them using the instructions in Section 2.11, - "Post-Installation Setup and Testing." - -2.9. Installing MySQL from tar.gz Packages on Other Unix-Like Systems +2.2. Installing MySQL from Generic Binaries on Unix/Linux This section covers the installation of MySQL binary distributions that are provided for various platforms in the form of compressed - tar files (files with a .tar.gz extension). See Section 2.1.2.4, - "MySQL Binaries Compiled by Sun Microsystems, Inc.," for a + tar files (files with a .tar.gz extension). See Section 2.2, + "Installing MySQL from Generic Binaries on Unix/Linux," for a detailed list. To obtain MySQL, see Section 2.1.3, "How to Get MySQL." + Sun Microsystems, Inc. provides a set of binary distributions of + MySQL. In addition to binaries provided in platform-specific + package formats, we offer binary distributions for a number of + platforms in the form of compressed tar files (.tar.gz files). For + Windows distributions, see Section 2.5, "Installing MySQL on + Windows." + + If you want to compile a debug version of MySQL from a source + distribution, you should add --with-debug or --with-debug=full to + the configure command used to configure the distribution and + remove any -fomit-frame-pointer options. + MySQL tar file binary distributions have names of the form mysql-VERSION-OS.tar.gz, where VERSION is a number (for example, - 5.1.39), and OS indicates the type of operating system for which + 5.1.41), and OS indicates the type of operating system for which the distribution is intended (for example, pc-linux-i686). In addition to these generic packages, we also offer binaries in - platform-specific package formats for selected platforms. See - Section 2.2, "Standard MySQL Installation Using a Binary - Distribution," for more information on how to install these. + platform-specific package formats for selected platforms. See the + platform specific sections for more information, for more + information on how to install these. You need the following tools to install a MySQL tar file binary distribution: @@ -3265,11 +809,13 @@ Note * A reasonable tar to unpack the distribution. GNU tar is known to work. Some operating systems come with a preinstalled version of tar that is known to have problems. For example, - the tar provided with early versions of Mac OS X, SunOS 4.x - and Solaris 8 and earlier are known to have problems with long - file names. On Mac OS X, you can use the preinstalled gnutar - program. On other systems with a deficient tar, you should - install GNU tar first. + the tar provided with early versions of Mac OS X, SunOS 4.x, + Solaris 8, Solaris 9, Solaris 10 and OpenSolaris, and HP-UX + are known to have problems with long file names. On Mac OS X, + you can use the preinstalled gnutar program. On Solaris 10 and + OpenSolaris you can use the preinstalled gtar. On other + systems with a deficient tar, you should install GNU tar + first. If you run into problems and need to file a bug report, please use the instructions in Section 1.6, "How to Report Bugs or Problems." @@ -3292,7 +838,7 @@ shell> bin/mysqld_safe --user=mysql & Note This procedure does not set up any passwords for MySQL accounts. - After following the procedure, proceed to Section 2.11, + After following the procedure, proceed to Section 2.13, "Post-Installation Setup and Testing." A more detailed version of the preceding description for @@ -3386,7 +932,7 @@ shell> chown -R mysql data machine, you can copy support-files/mysql.server to the location where your system has its startup files. More information can be found in the support-files/mysql.server - script itself and in Section 2.11.2.2, "Starting and Stopping + script itself and in Section 2.13.1.2, "Starting and Stopping MySQL Automatically." 10. You can set up new accounts using the bin/mysql_setpermission script if you install the DBI and DBD::mysql Perl modules. See @@ -3425,10 +971,10 @@ Note The accounts that are listed in the MySQL grant tables initially have no passwords. After starting the server, you should set up - passwords for them using the instructions in Section 2.11, + passwords for them using the instructions in Section 2.13, "Post-Installation Setup and Testing." -2.10. MySQL Installation Using a Source Distribution +2.3. MySQL Installation Using a Source Distribution Before you proceed with an installation from source, first check whether our binary is available for your platform and whether it @@ -3437,11 +983,11 @@ Note To obtain a source distribution for MySQL, Section 2.1.3, "How to Get MySQL." If you want to build MySQL from source on Windows, see - Section 2.10.6, "Installing MySQL from Source on Windows." + Section 2.5.10, "Installing MySQL from Source on Windows." MySQL source distributions are provided as compressed tar archives and have names of the form mysql-VERSION.tar.gz, where VERSION is - a number like 5.1.39. + a number like 5.1.41. You need the following tools to build and install MySQL from source: @@ -3451,11 +997,13 @@ Note * A reasonable tar to unpack the distribution. GNU tar is known to work. Some operating systems come with a preinstalled version of tar that is known to have problems. For example, - the tar provided with early versions of Mac OS X, SunOS 4.x - and Solaris 8 and earlier are known to have problems with long - file names. On Mac OS X, you can use the preinstalled gnutar - program. On other systems with a deficient tar, you should - install GNU tar first. + the tar provided with early versions of Mac OS X, SunOS 4.x, + Solaris 8, Solaris 9, Solaris 10 and OpenSolaris, and HP-UX + are known to have problems with long file names. On Mac OS X, + you can use the preinstalled gnutar program. On Solaris 10 and + OpenSolaris you can use the preinstalled gtar. On other + systems with a deficient tar, you should install GNU tar + first. * A working ANSI C++ compiler. gcc 2.95.2 or later, SGI C++, and SunPro C++ are some of the compilers that are known to work. @@ -3489,7 +1037,7 @@ CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors \ If you run into problems and need to file a bug report, please use the instructions in Section 1.6, "How to Report Bugs or Problems." -2.10.1. Source Installation Overview +2.3.1. Source Installation Overview The basic commands that you must execute to install a MySQL source distribution are: @@ -3519,7 +1067,7 @@ shell> rpmbuild --rebuild --clean MySQL-VERSION.src.rpm Note This procedure does not set up any passwords for MySQL accounts. - After following the procedure, proceed to Section 2.11, + After following the procedure, proceed to Section 2.13, "Post-Installation Setup and Testing," for post-installation setup and testing. @@ -3566,15 +1114,15 @@ shell> ./configure --prefix=/usr/local/mysql shell> make When you run configure, you might want to specify other options. Run ./configure --help for a list of options. Section - 2.10.2, "Typical configure Options," discusses some of the - more useful options. + 2.3.2, "Typical configure Options," discusses some of the more + useful options. If configure fails and you are going to send mail to a MySQL mailing list to ask for assistance, please include any lines from config.log that you think can help solve the problem. Also include the last couple of lines of output from configure. To file a bug report, please use the instructions in Section 1.6, "How to Report Bugs or Problems." - If the compile fails, see Section 2.10.4, "Dealing with + If the compile fails, see Section 2.3.4, "Dealing with Problems Compiling MySQL," for help. 8. Install the distribution: @@ -3622,7 +1170,7 @@ shell> chown -R mysql var machine, you can copy support-files/mysql.server to the location where your system has its startup files. More information can be found in the support-files/mysql.server - script itself; see also Section 2.11.2.2, "Starting and + script itself; see also Section 2.13.1.2, "Starting and Stopping MySQL Automatically." 14. You can set up new accounts using the bin/mysql_setpermission script if you install the DBI and DBD::mysql Perl modules. See @@ -3652,10 +1200,10 @@ Note The accounts that are listed in the MySQL grant tables initially have no passwords. After starting the server, you should set up - passwords for them using the instructions in Section 2.11, + passwords for them using the instructions in Section 2.13, "Post-Installation Setup and Testing." -2.10.2. Typical configure Options +2.3.2. Typical configure Options The configure script gives you a great deal of control over how you configure a MySQL source distribution. Typically you do this @@ -3687,6 +1235,7 @@ shell> ./configure --help --enable-FEATURE Enable FEATURE --enable-assembler Use assembler versions of some string functions if available + --enable-debug-sync Compile in Debug Sync facility 5.1.41 --enable-dependency-tracking Do not reject slow dependency extractors --enable-fast-install Optimize for fast installation yes @@ -3833,8 +1382,7 @@ shell> ./configure --help Some of the configure options available are described here. For options that may be of use if you have difficulties building - MySQL, see Section 2.10.4, "Dealing with Problems Compiling - MySQL." + MySQL, see Section 2.3.4, "Dealing with Problems Compiling MySQL." * To compile just the MySQL client libraries and client programs and not the server, use the --without-server option: @@ -3870,6 +1418,11 @@ shell> ./configure --prefix=/usr/local \ common to use an option file. See Section 4.2.3.3, "Using Option Files." + * This option specifies the port number on which the server + listens for TCP/IP connections. The default is port 3306. To + listen on a different port, use a configure command like this: +shell> ./configure --with-tcp-port=3307 + * If you are using Unix and you want the MySQL socket file location to be somewhere other than the default location (normally in the directory /tmp or /var/run), use a configure @@ -3878,7 +1431,7 @@ shell> ./configure \ --with-unix-socket-path=/usr/local/mysql/tmp/mysql.sock The socket file name must be an absolute path name. You can also change the location of mysql.sock at server startup by - using a MySQL option file. See Section B.1.4.5, "How to + using a MySQL option file. See Section B.5.4.5, "How to Protect or Change the MySQL Unix Socket File." * If you want to compile statically linked programs (for @@ -3924,7 +1477,7 @@ CFLAGS="-O3 -mpentiumpro" CXX=gcc CXXFLAGS="-O3 -mpentiumpro \ The binaries we provide on the MySQL Web site at http://dev.mysql.com/downloads/ are all compiled with full optimization and should be perfect for most users. See Section - 2.1.2.4, "MySQL Binaries Compiled by Sun Microsystems, Inc.." + 2.2, "Installing MySQL from Generic Binaries on Unix/Linux." There are some configuration settings you can tweak to build an even faster binary, but these are only for advanced users. See Section 7.5.1, "How Compiling and Linking Affects the @@ -3987,22 +1540,41 @@ shell> ./configure --with-debug error output. Typically, this output is written to the error log. + * To cause the Debug Sync facility to be compiled into the + server, use the --enable-debug-sync option. This facility is + used for testing and debugging. When compiled in, Debug Sync + is disabled by default. To enable it, start mysqld with the + --debug-sync-timeout=N option, where N is a timeout value + greater than 0. (The default value is 0, which disables Debug + Sync.) N becomes the default timeout for individual + synchronization points. + Debug Sync is also compiled in if you configure with the + --with-debug option (which implies --enable-debug-sync), + unless you also use the --disable-debug-sync option. + For a description of the Debug Sync facility and how to use + synchronization points, see MySQL Internals: Test + Synchronization + (http://forge.mysql.com/wiki/MySQL_Internals_Test_Synchronizat + ion). + The --enable-debug-sync and --disable-debug-sync options were + added in MySQL 5.1.41. + * If your client programs are using threads, you must compile a thread-safe version of the MySQL client library with the --enable-thread-safe-client configure option. This creates a libmysqlclient_r library with which you should link your - threaded applications. See Section 21.10.17, "How to Make a + threaded applications. See Section 21.9.16.2, "How to Make a Threaded Client." * Some features require that the server be built with compression library support, such as the COMPRESS() and UNCOMPRESS() functions, and compression of the client/server protocol. The --with-zlib-dir=no|bundled|DIR option provides - control for compression library support. The value no + control over compression library support. The value no explicitly disables compression support. bundled causes the zlib library bundled in the MySQL sources to be used. A DIR - path name specifies where to find the compression library - sources. + path name specifies the directory in which to find the + compression library sources. * It is possible to build MySQL with large table support using the --with-big-tables option. @@ -4035,8 +1607,8 @@ shell> ./configure --with-debug default as of MySQL 5.1.28; to disable it, use --disable-profiling. - * See Section 2.13, "Operating System-Specific Notes," for - options that pertain to particular operating systems. + * See Section 2.1, "General Installation Guidance," for options + that pertain to particular operating systems. * See Section 5.5.7.2, "Using SSL Connections," for options that pertain to configuring MySQL to support secure (encrypted) @@ -4082,7 +1654,7 @@ shell> ./configure --with-debug dynamic plugins. Plugins that do not support dynamic build are not built.) -2.10.3. Installing from the Development Source Tree +2.3.3. Installing from the Development Source Tree Caution @@ -4091,17 +1663,17 @@ Caution on your system, you should use a standard release distribution (either a binary or source distribution). - To obtain the most recent development source tree, you first need - to download and install Bazaar. You can obtain Bazaar from the - Bazaar VCS Website (http://bazaar-vcs.org). Bazaar is supported by - any platform that supports Python, and is therefore compatible - with any Linux, Unix, Windows or Mac OS X host. Instructions for + To obtain the most recent development source tree, you must have + Bazaar installed. You can obtain Bazaar from the Bazaar VCS + Website (http://bazaar-vcs.org). Bazaar is supported by any + platform that supports Python, and is therefore compatible with + any Linux, Unix, Windows or Mac OS X host. Instructions for downloading and installing Bazaar on the different platforms are available on the Bazaar website. All MySQL projects are hosted on Launchpad (http://launchpad.net/). MySQL projects, including MySQL server, - MySQL Workbench and others are available from the Sun/MySQL + MySQL Workbench, and others are available from the Sun/MySQL Engineering (http://launchpad.net/~mysql) page. For the repositories related only to MySQL server, see the MySQL Server (http://launchpad.net/mysql-server) page. @@ -4135,12 +1707,12 @@ sql_yacc.yy:#####: fatal error: maximum table size (32767) exceeded The maximum table size is not actually exceeded; the error is caused by bugs in older versions of bison. - To build under Windows you will need a copy of Microsoft Visual - C++ 2005 Express Edition, Visual Studio .Net 2003 (7.1), or Visual - Studio 2005 (8.0) compiler system. + To build under Windows you must have Microsoft Visual C++ 2005 + Express Edition, Visual Studio .Net 2003 (7.1), or Visual Studio + 2005 (8.0) compiler system. - Once you have the necessary tools installed, you first need to - create a local branch of the MySQL source code on your machine: + Once the necessary tools are installed, you must create a local + branch of the MySQL source code on your machine: 1. To obtain a copy of the MySQL source code, you must create a new Bazaar branch. If you do not already have a Bazaar @@ -4150,8 +1722,8 @@ shell> mkdir mysql-server shell> bzr init-repo --trees mysql-server 2. Once you have an initialized directory, you can branch from - the public MySQL server repositories. To create a branch of a - specific version: + the public MySQL server repositories to create a local source + tree. To create a branch of a specific version: shell> cd mysql-server shell> bzr branch lp:mysql-server/5.1 mysql-5.1 @@ -4167,46 +1739,60 @@ shell> bzr branch lp:mysql-server/5.1 mysql-5.1 branch: shell> bzr branch mysql-5.1 mysql-5.1-build - Once you have the local branch, you can start to build MySQL - server from the source code. On Windows, the build process is - different from Unix/Linux. To continue building MySQL on Windows, - see Section 2.10.6, "Installing MySQL from Source on Windows." + 5. To obtain changes made after you have set up the branch + initially, update it using the pull option periodically. Use + this command in the top-level directory of the local copy: +shell> bzr pull + You can examine the changeset comments for the tree by using + the log option to bzr: +shell> bzr log + You can also browse changesets, comments, and source code + online. To browse this information for MySQL 5.1, go to the + Launchpad MySQL Server (http://launchpad.net/mysql-server) + page. + If you see diffs (changes) or code that you have a question + about, do not hesitate to send email to the MySQL internals + mailing list. See Section 1.5.1, "MySQL Mailing Lists." Also, + if you think you have a better idea on how to do something, + send an email message to the list with a patch. + + After you have the local branch, you can build MySQL server from + the source code. On Windows, the build process is different from + Unix/Linux: see Section 2.5.10, "Installing MySQL from Source on + Windows." - On Unix/Linux you need to use the autoconf system to create the - configure script so that you can configure the build environment - before building. + On Unix/Linux, use the autoconf system to create the configure + script so that you can configure the build environment before + building. The following example shows the typical commands + required to build MySQL from a source tree. - 1. The following example shows the typical commands required to - configure a source tree. The first cd command changes location - into the top-level directory of the tree; replace mysql-5.1 - with the appropriate directory name. + 1. Change location to the top-level directory of the source tree; + replace mysql-5.1 with the appropriate directory name. +shell> cd mysql-5.1 -Note - For MySQL 5.1.12 and earlier, you must separately configure - the INNODB storage engine. You can do this by running the - following command from the main source directory: + 2. Prepare the source tree for configuration. + Prior to MySQL 5.1.12, you must separately configure the + InnoDB storage engine. Run the following command from the main + source directory: shell> (cd storage/innobase; autoreconf --force --install) -shell> cd mysql-5.1 + You can omit the previous command for MySQL 5.1.12 and later, + or if you do not require InnoDB support. + Prepare the remainder of the source tree: shell> autoreconf --force --install -shell> ./configure # Add your favorite options here -shell> make - Or you can use BUILD/autorun.sh as a shortcut for the + As an alternative to the preceding autoreconf command, you can + use BUILD/autorun.sh, which acts as a shortcut for the following sequence of commands: shell> aclocal; autoheader shell> libtoolize --automake --force shell> automake --force --add-missing; autoconf - The command line that changes directory into the - storage/innobase directory is used to configure the InnoDB - storage engine. You can omit this lines if you do not require - InnoDB support. - -Note - Beginning with MySQL 5.1, code specific to storage engines has - been moved under a storage directory. For example, InnoDB code - is now found in storage/innobase and NDBCLUSTER code is in - storage/ndb. If you get some strange errors during this stage, verify that - you have the correct version of the libtool installed. + you have the correct version of libtool installed. + + 3. Configure the source tree and compile MySQL: +shell> ./configure # Add your favorite options here +shell> make + For a description of some configure options, see Section + 2.3.2, "Typical configure Options." A collection of our standard configuration scripts is located in the BUILD/ subdirectory. For example, you may find it more convenient to use the BUILD/compile-pentium-debug script than @@ -4217,52 +1803,34 @@ Note They are not officially maintained and their contents may change from release to release. - 2. When the build is done, run make install. Be careful with this + 4. When the build is done, run make install. Be careful with this on a production machine; the command may overwrite your live - release installation. If you have another installation of - MySQL, run ./configure with different values for the --prefix, - --with-tcp-port, and --with-unix-socket-path options than - those used for your production server. + release installation. If you already have MySQL installed and + do not want to overwrite it, run ./configure with values for + the --prefix, --with-tcp-port, and --with-unix-socket-path + options different from those used for your production server. - 3. Play hard with your new installation and try to make the new + 5. Play hard with your new installation and try to make the new features crash. Start by running make test. See Section 22.1.2, "MySQL Test Suite." - 4. If you have gotten to the make stage, but the distribution + 6. If you have gotten to the make stage, but the distribution does not compile, please enter the problem into our bugs database using the instructions given in Section 1.6, "How to Report Bugs or Problems." If you have installed the latest versions of the required GNU tools, and they crash trying to process our configuration files, please report that also. - However, if you execute aclocal and get a command not found - error or a similar problem, do not report it. Instead, make - sure that all the necessary tools are installed and that your - PATH variable is set correctly so that your shell can find - them. - - 5. After initially copying the repository with bzr to obtain the - source tree, you should use pull option to periodically update - your local copy. To do this any time after you have set up the - repository, use this command: -shell> bzr pull - - 6. You can examine the changeset comments for the tree by using - the log option to bzr: -shell> bzr log - You can also browse changesets, comments, and source code - online. To browse this information for MySQL 5.1, go to - http://launchpad.net/mysql-server/. - If you see diffs or code that you have a question about, do - not hesitate to send email to the MySQL internals mailing - list. See Section 1.5.1, "MySQL Mailing Lists." Also, if you - think you have a better idea on how to do something, send an - email message to the list with a patch. + However, if you get a command not found error or a similar + problem for aclocal, configure, or other required tools, do + not report it. Instead, make sure that all the required tools + are installed and that your PATH variable is set correctly so + that your shell can find them. -2.10.4. Dealing with Problems Compiling MySQL +2.3.4. Dealing with Problems Compiling MySQL All MySQL programs compile cleanly for us with no warnings on Solaris or Linux using gcc. On other systems, warnings may occur - due to differences in system include files. See Section 2.10.5, + due to differences in system include files. See Section 2.3.5, "MIT-pthreads Notes," for warnings that may occur when using MIT-pthreads. For other problems, check the following list. @@ -4355,9 +1923,9 @@ shell> CFLAGS=-O3 shell> CXX=gcc shell> CXXFLAGS=-O3 shell> export CC CFLAGS CXX CXXFLAGS - See Section 2.1.2.4, "MySQL Binaries Compiled by Sun - Microsystems, Inc.," for a list of flag definitions that have - been found to be useful on various systems. + See Section 2.2, "Installing MySQL from Generic Binaries on + Unix/Linux," for a list of flag definitions that have been + found to be useful on various systems. * If you get errors such as those shown here when compiling mysqld, configure did not correctly detect the type of the @@ -4415,20 +1983,19 @@ export CXX="gcc" You must run configure again after making either of those changes. -2.10.5. MIT-pthreads Notes +2.3.5. MIT-pthreads Notes This section describes some of the issues involved in using MIT-pthreads. On Linux, you should not use MIT-pthreads. Use the installed - LinuxThreads implementation instead. See Section 2.13.1, "Linux - Notes." + LinuxThreads implementation instead. See Section 2.6, "Installing + MySQL on Linux." If your system does not provide native thread support, you should build MySQL using the MIT-pthreads package. This includes older FreeBSD systems, SunOS 4.x, Solaris 2.4 and earlier, and some - others. See Section 2.1.1, "Operating Systems Supported by MySQL - Community Server." + others. See Section 2.1, "General Installation Guidance." MIT-pthreads is not part of the MySQL 5.1 source distribution. If you require this package, you need to download it separately from @@ -4497,1322 +2064,9 @@ implicit declaration of function `int strtoul(...)' * We have not been able to make readline work with MIT-pthreads. (This is not necessary, but may be of interest to some.) -2.10.6. Installing MySQL from Source on Windows - - These instructions describe how to build binaries from source for - MySQL 5.1 on Windows. Instructions are provided for building - binaries from a standard source distribution or from the Bazaar - tree that contains the latest development source. - -Note - - The instructions here are strictly for users who want to test - MySQL on Microsoft Windows from the latest source distribution or - from the Bazaar tree. For production use, we do not advise using a - MySQL server built by yourself from source. Normally, it is best - to use precompiled binary distributions of MySQL that are built - specifically for optimal performance on Windows by Sun - Microsystems, Inc. Instructions for installing binary - distributions are available in Section 2.3, "Installing MySQL on - Windows." - - To build MySQL on Windows from source, you must satisfy the - following system, compiler, and resource requirements: - - * Windows 2000, Windows XP, or newer version. - Windows Vista is supported when using Visual Studio 2005 - provided you have installed the following updates: - - + Microsoft Visual Studio 2005 Professional Edition - ENU - Service Pack 1 (KB926601) - (http://support.microsoft.com/?kbid=926601) - - + Security Update for Microsoft Visual Studio 2005 - Professional Edition - ENU (KB937061) - (http://support.microsoft.com/?kbid=937061) - - + Update for Microsoft Visual Studio 2005 Professional - Edition - ENU (KB932232) - (http://support.microsoft.com/?kbid=932232) - - * CMake, which can be downloaded from http://www.cmake.org. - After installing, modify your path to include the cmake - binary. - - * Microsoft Visual C++ 2005 Express Edition, Visual Studio .Net - 2003 (7.1), or Visual Studio 2005 (8.0) compiler system. - - * If you are using Visual C++ 2005 Express Edition, you must - also install an appropriate Platform SDK. More information and - links to downloads for various Windows platforms is available - from - http://www.microsoft.com/downloads/details.aspx?familyid=0baf2 - b35-c656-4969-ace8-e4c0c0716adb. - - * If you are compiling from a Bazaar tree or making changes to - the parser, you need bison for Windows, which can be - downloaded from - http://gnuwin32.sourceforge.net/packages/bison.htm. Download - the package labeled "Complete package, excluding sources". - After installing the package, modify your path to include the - bison binary and ensure that this binary is accessible from - Visual Studio. - - * Cygwin might be necessary if you want to run the test script - or package the compiled binaries and support files into a Zip - archive. (Cygwin is needed only to test or package the - distribution, not to build it.) Cygwin is available from - http://cygwin.com. - - * 3GB to 5GB of disk space. - - The exact system requirements can be found here: - http://msdn.microsoft.com/vstudio/Previous/2003/sysreqs/default.as - px and - http://msdn.microsoft.com/vstudio/products/sysreqs/default.aspx - - You also need a MySQL source distribution for Windows, which can - be obtained two ways: - - * Obtain a source distribution packaged by Sun Microsystems, - Inc. These are available from http://dev.mysql.com/downloads/. - - * Package a source distribution yourself from the latest Bazaar - developer source tree. For instructions on pulling the latest - source files, see Section 2.10.3, "Installing from the - Development Source Tree." - - If you find something not working as expected, or you have - suggestions about ways to improve the current build process on - Windows, please send a message to the win32 mailing list. See - Section 1.5.1, "MySQL Mailing Lists." - -2.10.6.1. Building MySQL from Source Using CMake and Visual Studio - - You can build MySQL on Windows by using a combination of cmake and - Microsoft Visual Studio .NET 2003 (7.1), Microsoft Visual Studio - 2005 (8.0) or Microsoft Visual C++ 2005 Express Edition. You must - have the appropriate Microsoft Platform SDK installed. - -Note - - To compile from the source code on Windows you must use the - standard source distribution (for example, mysql-5.0.45.tar.gz). - You build from the same distribution as used to build MySQL on - Unix, Linux and other platforms. Do not use the Windows Source - distributions as they do not contain the necessary configuration - script and other files. - - Follow this procedure to build MySQL: - - 1. If you are installing from a packaged source distribution, - create a work directory (for example, C:\workdir), and unpack - the source distribution there using WinZip or another Windows - tool that can read .zip files. This directory is the work - directory in the following instructions. - - 2. Using a command shell, navigate to the work directory and run - the following command: -C:\workdir>win\configure.js options - If you have associated the .js file extension with an - application such as a text editor, then you may need to use - the following command to force configure.js to be executed as - a script: -C:\workdir>cscript win\configure.js options - These options are available for configure.js: - - + WITH_INNOBASE_STORAGE_ENGINE: Enable the InnoDB storage - engine. - - + WITH_PARTITION_STORAGE_ENGINE: Enable user-defined - partitioning. - - + WITH_ARCHIVE_STORAGE_ENGINE: Enable the ARCHIVE storage - engine. - - + WITH_BLACKHOLE_STORAGE_ENGINE: Enable the BLACKHOLE - storage engine. - - + WITH_EXAMPLE_STORAGE_ENGINE: Enable the EXAMPLE storage - engine. - - + WITH_FEDERATED_STORAGE_ENGINE: Enable the FEDERATED - storage engine. - - + WITH_NDBCLUSTER_STORAGE_ENGINE (experimental): Enable the - NDBCLUSTER storage engine in the MySQL server; cause - binaries for the MySQL Cluster management and data node, - management client, and other programs to be built. - This option is supported only in MySQL Cluster NDB 7.0 - (NDBCLUSTER storage engine versions 6.4.0 and later) - using the MySQL Cluster sources. It cannot be used to - enable clustering support in other MySQL source trees or - distributions. +2.4. Upgrading or Downgrading MySQL - + MYSQL_SERVER_SUFFIX=suffix: Server suffix, default none. - - + COMPILATION_COMMENT=comment: Server comment, default - "Source distribution". - - + MYSQL_TCP_PORT=port: Server port, default 3306. - - + DISABLE_GRANT_OPTIONS: Disables the --bootstrap, - --skip-grant-tables, and --init-file options for mysqld. - This option is available as of MySQL 5.1.15. - For example (type the command on one line): -C:\workdir>win\configure.js WITH_INNOBASE_STORAGE_ENGINE - WITH_PARTITION_STORAGE_ENGINE MYSQL_SERVER_SUFFIX=-pro - - 3. From the work directory, execute the win\build-vs8.bat or - win\build-vs71.bat file, depending on the version of Visual - Studio you have installed. The script invokes CMake, which - generates the mysql.sln solution file. - You can also use win\build-vs8_x64.bat to build the 64-bit - version of MySQL. However, you cannot build the 64-bit version - with Visual Studio Express Edition. You must use Visual Studio - 2005 (8.0) or higher. - - 4. From the work directory, open the generated mysql.sln file - with Visual Studio and select the proper configuration using - the Configuration menu. The menu provides Debug, Release, - RelwithDebInfo, MinRelInfo options. Then select Solution > - Build to build the solution. - Remember the configuration that you use in this step. It is - important later when you run the test script because that - script needs to know which configuration you used. - - 5. Test the server. The server built using the preceding - instructions expects that the MySQL base directory and data - directory are C:\mysql and C:\mysql\data by default. If you - want to test your server using the source tree root directory - and its data directory as the base directory and data - directory, you need to tell the server their path names. You - can either do this on the command line with the --basedir and - --datadir options, or by placing appropriate options in an - option file. (See Section 4.2.3.3, "Using Option Files.") If - you have an existing data directory elsewhere that you want to - use, you can specify its path name instead. - When the server is running in standalone fashion or as a - service based on your configuration, try to connect to it from - the mysql interactive command-line utility. - You can also run the standard test script, mysql-test-run.pl. - This script is written in Perl, so you'll need either Cygwin - or ActiveState Perl to run it. You may also need to install - the modules required by the script. To run the test script, - change location into the mysql-test directory under the work - directory, set the MTR_VS_CONFIG environment variable to the - configuration you selected earlier (or use the --vs-config - option), and invoke mysql-test-run.pl. For example (using - Cygwin and the bash shell): -shell> cd mysql-test -shell> export MTR_VS_CONFIG=debug -shell> ./mysql-test-run.pl --force --timer -shell> ./mysql-test-run.pl --force --timer --ps-protocol - - When you are satisfied that the programs you have built are - working correctly, stop the server. Now you can install the - distribution. One way to do this is to use the make_win_bin_dist - script in the scripts directory of the MySQL source distribution - (see Section 4.4.2, "make_win_bin_dist --- Package MySQL - Distribution as ZIP Archive"). This is a shell script, so you must - have Cygwin installed if you want to use it. It creates a Zip - archive of the built executables and support files that you can - unpack in the location at which you want to install MySQL. - - It is also possible to install MySQL by copying directories and - files directly: - - 1. Create the directories where you want to install MySQL. For - example, to install into C:\mysql, use these commands: -C:\> mkdir C:\mysql -C:\> mkdir C:\mysql\bin -C:\> mkdir C:\mysql\data -C:\> mkdir C:\mysql\share -C:\> mkdir C:\mysql\scripts - If you want to compile other clients and link them to MySQL, - you should also create several additional directories: -C:\> mkdir C:\mysql\include -C:\> mkdir C:\mysql\lib -C:\> mkdir C:\mysql\lib\debug -C:\> mkdir C:\mysql\lib\opt - If you want to benchmark MySQL, create this directory: -C:\> mkdir C:\mysql\sql-bench - Benchmarking requires Perl support. See Section 2.15, "Perl - Installation Notes." - - 2. From the work directory, copy into the C:\mysql directory the - following directories: -C:\> cd \workdir -C:\workdir> copy client_release\*.exe C:\mysql\bin -C:\workdir> copy client_debug\mysqld.exe C:\mysql\bin\mysqld-debug.ex -e -C:\workdir> xcopy scripts\*.* C:\mysql\scripts /E -C:\workdir> xcopy share\*.* C:\mysql\share /E - If you want to compile other clients and link them to MySQL, - you should also copy several libraries and header files: -C:\workdir> copy lib_debug\mysqlclient.lib C:\mysql\lib\debug -C:\workdir> copy lib_debug\libmysql.* C:\mysql\lib\debug -C:\workdir> copy lib_debug\zlib.* C:\mysql\lib\debug -C:\workdir> copy lib_release\mysqlclient.lib C:\mysql\lib\opt -C:\workdir> copy lib_release\libmysql.* C:\mysql\lib\opt -C:\workdir> copy lib_release\zlib.* C:\mysql\lib\opt -C:\workdir> copy include\*.h C:\mysql\include -C:\workdir> copy libmysql\libmysql.def C:\mysql\include - If you want to benchmark MySQL, you should also do this: -C:\workdir> xcopy sql-bench\*.* C:\mysql\bench /E - - After installation, set up and start the server in the same way as - for binary Windows distributions. See Section 2.3, "Installing - MySQL on Windows." - -2.10.7. Compiling MySQL Clients on Windows - - In your source files, you should include my_global.h before - mysql.h: -#include <my_global.h> -#include <mysql.h> - - my_global.h includes any other files needed for Windows - compatibility (such as windows.h) if you compile your program on - Windows. - - You can either link your code with the dynamic libmysql.lib - library, which is just a wrapper to load in libmysql.dll on - demand, or link with the static mysqlclient.lib library. - - The MySQL client libraries are compiled as threaded libraries, so - you should also compile your code to be multi-threaded. - -2.11. Post-Installation Setup and Testing - - After installing MySQL, there are some issues that you should - address. For example, on Unix, you should initialize the data - directory and create the MySQL grant tables. On all platforms, an - important security concern is that the initial accounts in the - grant tables have no passwords. You should assign passwords to - prevent unauthorized access to the MySQL server. Optionally, you - can create time zone tables to enable recognition of named time - zones. - - The following sections include post-installation procedures that - are specific to Windows systems and to Unix systems. Another - section, Section 2.11.2.3, "Starting and Troubleshooting the MySQL - Server," applies to all platforms; it describes what to do if you - have trouble getting the server to start. Section 2.11.3, - "Securing the Initial MySQL Accounts," also applies to all - platforms. You should follow its instructions to make sure that - you have properly protected your MySQL accounts by assigning - passwords to them. - - When you are ready to create additional user accounts, you can - find information on the MySQL access control system and account - management in Section 5.4, "The MySQL Access Privilege System," - and Section 5.5, "MySQL User Account Management." - -2.11.1. Windows Post-Installation Procedures - - On Windows, the data directory and the grant tables do not have to - be created. MySQL Windows distributions include the grant tables - with a set of preinitialized accounts in the mysql database under - the data directory. It is unnecessary to run the mysql_install_db - script that is used on Unix. Regarding passwords, if you installed - MySQL using the Windows Installation Wizard, you may have already - assigned passwords to the accounts. (See Section 2.3.3, "Using the - MySQL Installation Wizard.") Otherwise, use the - password-assignment procedure given in Section 2.11.3, "Securing - the Initial MySQL Accounts." - - Before setting up passwords, you might want to try running some - client programs to make sure that you can connect to the server - and that it is operating properly. Make sure that the server is - running (see Section 2.3.9, "Starting the Server for the First - Time"), and then issue the following commands to verify that you - can retrieve information from the server. The output should be - similar to what is shown here: -C:\> C:\mysql\bin\mysqlshow -+--------------------+ -| Databases | -+--------------------+ -| information_schema | -| mysql | -| test | -+--------------------+ - -C:\> C:\mysql\bin\mysqlshow mysql -Database: mysql -+---------------------------+ -| Tables | -+---------------------------+ -| columns_priv | -| db | -| event | -| func | -| general_log | -| help_category | -| help_keyword | -| help_relation | -| help_topic | -| host | -| plugin | -| proc | -| procs_priv | -| servers | -| slow_log | -| tables_priv | -| time_zone | -| time_zone_leap_second | -| time_zone_name | -| time_zone_transition | -| time_zone_transition_type | -| user | -+---------------------------+ - - -C:\> C:\mysql\bin\mysql -e "SELECT Host,Db,User FROM db" mysql -+------+-------+------+ -| host | db | user | -+------+-------+------+ -| % | test% | | -+------+-------+------+ - - You may need to specify a different directory from the one shown; - if you used the Windows Installation Wizard, then the default - directory is C:\Program Files\MySQL\MySQL Server 5.1, and the - mysql and mysqlshow client programs are in C:\Program - Files\MySQL\MySQL Server 5.1\bin. See Section 2.3.3, "Using the - MySQL Installation Wizard," for more information. - - If you have already secured the initial MySQL accounts, you may - need to use the -u and -p options to supply a user name and - password to the mysqlshow and mysql client programs; otherwise the - programs may fail with an error, or you may not be able to view - all databases. For example, if you have assigned the password - "secretpass" to the MySQL root account, then you can invoke - mysqlshow and mysql as shown here: -C:\> C:\mysql\bin\mysqlshow -uroot -psecretpass -+--------------------+ -| Databases | -+--------------------+ -| information_schema | -| mysql | -| test | -+--------------------+ - -C:\> C:\mysql\bin\mysqlshow -uroot -psecretpass mysql -Database: mysql -+---------------------------+ -| Tables | -+---------------------------+ -| columns_priv | -| db | -| event | -| func | -| general_log | -| help_category | -| help_keyword | -| help_relation | -| help_topic | -| host | -| plugin | -| proc | -| procs_priv | -| servers | -| slow_log | -| tables_priv | -| time_zone | -| time_zone_leap_second | -| time_zone_name | -| time_zone_transition | -| time_zone_transition_type | -| user | -+---------------------------+ - - -C:\> C:\mysql\bin\mysql -uroot -psecretpass -e "SELECT Host,Db,User F -ROM db" mysql -+------+-------+------+ -| host | db | user | -+------+-------+------+ -| % | test% | | -+------+-------+------+ - - For more information about these programs, see Section 4.5.6, - "mysqlshow --- Display Database, Table, and Column Information," - and Section 4.5.1, "mysql --- The MySQL Command-Line Tool." - - If you are running a version of Windows that supports services and - you want the MySQL server to run automatically when Windows - starts, see Section 2.3.11, "Starting MySQL as a Windows Service." - -2.11.2. Unix Post-Installation Procedures - - After installing MySQL on Unix, you need to initialize the grant - tables, start the server, and make sure that the server works - satisfactorily. You may also wish to arrange for the server to be - started and stopped automatically when your system starts and - stops. You should also assign passwords to the accounts in the - grant tables. - - On Unix, the grant tables are set up by the mysql_install_db - program. For some installation methods, this program is run for - you automatically: - - * If you install MySQL on Linux using RPM distributions, the - server RPM runs mysql_install_db. - - * If you install MySQL on Mac OS X using a PKG distribution, the - installer runs mysql_install_db. - - Otherwise, you'll need to run mysql_install_db yourself. - - The following procedure describes how to initialize the grant - tables (if that has not previously been done) and then start the - server. It also suggests some commands that you can use to test - whether the server is accessible and working properly. For - information about starting and stopping the server automatically, - see Section 2.11.2.2, "Starting and Stopping MySQL Automatically." - - After you complete the procedure and have the server running, you - should assign passwords to the accounts created by - mysql_install_db. Instructions for doing so are given in Section - 2.11.3, "Securing the Initial MySQL Accounts." - - In the examples shown here, the server runs under the user ID of - the 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. - - 1. Change location into the top-level directory of your MySQL - installation, represented here by BASEDIR: -shell> cd BASEDIR - BASEDIR is likely to be something like /usr/local/mysql or - /usr/local. The following steps assume that you are located in - this directory. - - 2. If necessary, run the mysql_install_db program to set up the - initial MySQL grant tables containing the privileges that - determine how users are allowed to connect to the server. - You'll need to do this if you used a distribution type for - which the installation procedure doesn't run the program for - you. - Typically, mysql_install_db needs to be run only the first - time you install MySQL, so you can skip this step if you are - upgrading an existing installation, However, mysql_install_db - does not overwrite any existing privilege tables, so it should - be safe to run in any circumstances. - To initialize the grant tables, use one of the following - commands, depending on whether mysql_install_db is located in - the bin or scripts directory: -shell> bin/mysql_install_db --user=mysql -shell> scripts/mysql_install_db --user=mysql - It might be necessary to specify other options such as - --basedir or --datadir if mysql_install_db does not use the - correct locations for the installation directory or data - directory. For example: -shell> bin/mysql_install_db --user=mysql \ - --basedir=/opt/mysql/mysql \ - --datadir=/opt/mysql/mysql/data - The mysql_install_db script creates the server's data - directory. Under the data directory, it creates directories - for the mysql database that holds all database privileges and - the test database that you can use to test MySQL. The script - also creates privilege table entries for root and - anonymous-user accounts. The accounts have no passwords - initially. A description of their initial privileges is given - in Section 2.11.3, "Securing the Initial MySQL Accounts." - Briefly, these privileges allow the MySQL root user to do - anything, and allow anybody to create or use databases with a - name of test or starting with test_. - It is important to make sure that the database directories and - files are owned by the mysql login account so that the server - has read and write access to them when you run it later. To - ensure this, the --user option should be used as shown if you - run mysql_install_db as root. Otherwise, you should execute - the script while logged in as mysql, in which case you can - omit the --user option from the command. - mysql_install_db creates several tables in the mysql database, - including user, db, host, tables_priv, columns_priv, func, and - others. See Section 5.4, "The MySQL Access Privilege System," - for a complete listing and description of these tables. - If you don't want to have the test database, you can remove it - with mysqladmin -u root drop test after starting the server. - If you have trouble with mysql_install_db at this point, see - Section 2.11.2.1, "Problems Running mysql_install_db." - - 3. Start the MySQL server: -shell> bin/mysqld_safe --user=mysql & - It is important that the MySQL server be run using an - unprivileged (non-root) login account. To ensure this, the - --user option should be used as shown if you run mysqld_safe - as system root. Otherwise, you should execute the script while - logged in to the system as mysql, in which case you can omit - the --user option from the command. - Further instructions for running MySQL as an unprivileged user - are given in Section 5.3.5, "How to Run MySQL as a Normal - User." - If you neglected to create the grant tables before proceeding - to this step, the following message appears in the error log - file when you start the server: -mysqld: Can't find file: 'host.frm' - If you have other problems starting the server, see Section - 2.11.2.3, "Starting and Troubleshooting the MySQL Server." - - 4. Use mysqladmin to verify that the server is running. The - following commands provide simple tests to check whether the - server is up and responding to connections: -shell> bin/mysqladmin version -shell> bin/mysqladmin variables - The output from mysqladmin version varies slightly depending - on your platform and version of MySQL, but should be similar - to that shown here: -shell> bin/mysqladmin version -mysqladmin Ver 14.12 Distrib 5.1.39, for pc-linux-gnu on i686 -... - -Server version 5.1.39 -Protocol version 10 -Connection Localhost via UNIX socket -UNIX socket /var/lib/mysql/mysql.sock -Uptime: 14 days 5 hours 5 min 21 sec - -Threads: 1 Questions: 366 Slow queries: 0 -Opens: 0 Flush tables: 1 Open tables: 19 -Queries per second avg: 0.000 - To see what else you can do with mysqladmin, invoke it with - the --help option. - - 5. Verify that you can shut down the server: -shell> bin/mysqladmin -u root shutdown - - 6. Verify that you can start the server again. Do this by using - mysqld_safe or by invoking mysqld directly. For example: -shell> bin/mysqld_safe --user=mysql --log & - If mysqld_safe fails, see Section 2.11.2.3, "Starting and - Troubleshooting the MySQL Server." - - 7. Run some simple tests to verify that you can retrieve - information from the server. The output should be similar to - what is shown here: -shell> bin/mysqlshow -+-----------+ -| Databases | -+-----------+ -| mysql | -| test | -+-----------+ - -shell> bin/mysqlshow mysql -Database: mysql -+---------------------------+ -| Tables | -+---------------------------+ -| columns_priv | -| db | -| func | -| help_category | -| help_keyword | -| help_relation | -| help_topic | -| host | -| proc | -| procs_priv | -| tables_priv | -| time_zone | -| time_zone_leap_second | -| time_zone_name | -| time_zone_transition | -| time_zone_transition_type | -| user | -+---------------------------+ - -shell> bin/mysql -e "SELECT Host,Db,User FROM db" mysql -+------+--------+------+ -| host | db | user | -+------+--------+------+ -| % | test | | -| % | test_% | | -+------+--------+------+ - - 8. There is a benchmark suite in the sql-bench directory (under - the MySQL installation directory) that you can use to compare - how MySQL performs on different platforms. The benchmark suite - is written in Perl. It requires the Perl DBI module that - provides a database-independent interface to the various - databases, and some other additional Perl modules: -DBI -DBD::mysql -Data::Dumper -Data::ShowTable - These modules can be obtained from CPAN - (http://www.cpan.org/). See also Section 2.15.1, "Installing - Perl on Unix." - The sql-bench/Results directory contains the results from many - runs against different databases and platforms. To run all - tests, execute these commands: -shell> cd sql-bench -shell> perl run-all-tests - If you don't have the sql-bench directory, you probably - installed MySQL using RPM files other than the source RPM. - (The source RPM includes the sql-bench benchmark directory.) - In this case, you must first install the benchmark suite - before you can use it. There are separate benchmark RPM files - named mysql-bench-VERSION.i386.rpm that contain benchmark code - and data. - If you have a source distribution, there are also tests in its - tests subdirectory that you can run. For example, to run - auto_increment.tst, execute this command from the top-level - directory of your source distribution: -shell> mysql -vvf test < ./tests/auto_increment.tst - The expected result of the test can be found in the - ./tests/auto_increment.res file. - - 9. At this point, you should have the server running. However, - none of the initial MySQL accounts have a password, so you - should assign passwords using the instructions found in - Section 2.11.3, "Securing the Initial MySQL Accounts." - - The MySQL 5.1 installation procedure creates time zone tables in - the mysql database. However, you must populate the tables manually - using the instructions in Section 9.7, "MySQL Server Time Zone - Support." - -2.11.2.1. Problems Running mysql_install_db - - The purpose of the mysql_install_db script is to generate new - MySQL privilege tables. It does not overwrite existing MySQL - privilege tables, and it does not affect any other data. - - If you want to re-create your privilege tables, first stop the - mysqld server if it is running. Then rename the mysql directory - under the data directory to save it, and then run - mysql_install_db. Suppose that your current directory is the MySQL - installation directory and that mysql_install_db is located in the - bin directory and the data directory is named data. To rename the - mysql database and re-run mysql_install_db, use these commands. -shell> mv data/mysql data/mysql.old -shell> bin/mysql_install_db --user=mysql - - When you run mysql_install_db, you might encounter the following - problems: - - * mysql_install_db fails to install the grant tables - You may find that mysql_install_db fails to install the grant - tables and terminates after displaying the following messages: -Starting mysqld daemon with databases from XXXXXX -mysqld ended - In this case, you should examine the error log file very - carefully. The log should be located in the directory XXXXXX - named by the error message and should indicate why mysqld - didn't start. If you do not understand what happened, include - the log when you post a bug report. See Section 1.6, "How to - Report Bugs or Problems." - - * There is a mysqld process running - This indicates that the server is running, in which case the - grant tables have probably been created already. If so, there - is no need to run mysql_install_db at all because it needs to - be run only once (when you install MySQL the first time). - - * Installing a second mysqld server does not work when one - server is running - This can happen when you have an existing MySQL installation, - but want to put a new installation in a different location. - For example, you might have a production installation, but you - want to create a second installation for testing purposes. - Generally the problem that occurs when you try to run a second - server is that it tries to use a network interface that is in - use by the first server. In this case, you should see one of - the following error messages: -Can't start server: Bind on TCP/IP port: -Address already in use -Can't start server: Bind on unix socket... - For instructions on setting up multiple servers, see Section - 5.6, "Running Multiple MySQL Servers on the Same Machine." - - * You do not have write access to the /tmp directory - If you do not have write access to create temporary files or a - Unix socket file in the default location (the /tmp directory), - an error occurs when you run mysql_install_db or the mysqld - server. - You can specify different locations for the temporary - directory and Unix socket file by executing these commands - prior to starting mysql_install_db or mysqld, where - some_tmp_dir is the full path name to some directory for which - you have write permission: -shell> TMPDIR=/some_tmp_dir/ -shell> MYSQL_UNIX_PORT=/some_tmp_dir/mysql.sock -shell> export TMPDIR MYSQL_UNIX_PORT - Then you should be able to run mysql_install_db and start the - server with these commands: -shell> bin/mysql_install_db --user=mysql -shell> bin/mysqld_safe --user=mysql & - If mysql_install_db is located in the scripts directory, - modify the first command to scripts/mysql_install_db. - See Section B.1.4.5, "How to Protect or Change the MySQL Unix - Socket File," and Section 2.14, "Environment Variables." - - There are some alternatives to running the mysql_install_db script - provided in the MySQL distribution: - - * If you want the initial privileges to be different from the - standard defaults, you can modify mysql_install_db before you - run it. However, it is preferable to use GRANT and REVOKE to - change the privileges after the grant tables have been set up. - In other words, you can run mysql_install_db, and then use - mysql -u root mysql to connect to the server as the MySQL root - user so that you can issue the necessary GRANT and REVOKE - statements. - If you want to install MySQL on several machines with the same - privileges, you can put the GRANT and REVOKE statements in a - file and execute the file as a script using mysql after - running mysql_install_db. For example: -shell> bin/mysql_install_db --user=mysql -shell> bin/mysql -u root < your_script_file - By doing this, you can avoid having to issue the statements - manually on each machine. - - * It is possible to re-create the grant tables completely after - they have previously been created. You might want to do this - if you're just learning how to use GRANT and REVOKE and have - made so many modifications after running mysql_install_db that - you want to wipe out the tables and start over. - To re-create the grant tables, remove all the .frm, .MYI, and - .MYD files in the mysql database directory. Then run the - mysql_install_db script again. - - * You can start mysqld manually using the --skip-grant-tables - option and add the privilege information yourself using mysql: -shell> bin/mysqld_safe --user=mysql --skip-grant-tables & -shell> bin/mysql mysql - From mysql, manually execute the SQL commands contained in - mysql_install_db. Make sure that you run mysqladmin - flush-privileges or mysqladmin reload afterward to tell the - server to reload the grant tables. - Note that by not using mysql_install_db, you not only have to - populate the grant tables manually, you also have to create - them first. - -2.11.2.2. Starting and Stopping MySQL Automatically - - Generally, you start the mysqld server in one of these ways: - - * Invoke mysqld directly. This works on any platform. - - * Run the MySQL server as a Windows service. The service can be - set to start the server automatically when Windows starts, or - as a manual service that you start on request. For - instructions, see Section 2.3.11, "Starting MySQL as a Windows - Service." - - * Invoke mysqld_safe, which tries to determine the proper - options for mysqld and then runs it with those options. This - script is used on Unix and Unix-like systems. See Section - 4.3.2, "mysqld_safe --- MySQL Server Startup Script." - - * Invoke mysql.server. This script is used primarily at system - startup and shutdown on systems that use System V-style run - directories, where it usually is installed under the name - mysql. The mysql.server script starts the server by invoking - mysqld_safe. See Section 4.3.3, "mysql.server --- MySQL Server - Startup Script." - - * On Mac OS X, install a separate MySQL Startup Item package to - enable the automatic startup of MySQL on system startup. The - Startup Item starts the server by invoking mysql.server. See - Section 2.5, "Installing MySQL on Mac OS X," for details. - - The mysqld_safe and mysql.server scripts and the Mac OS X Startup - Item can be used to start the server manually, or automatically at - system startup time. mysql.server and the Startup Item also can be - used to stop the server. - - To start or stop the server manually using the mysql.server - script, invoke it with start or stop arguments: -shell> mysql.server start -shell> mysql.server stop - - Before mysql.server starts the server, it changes location to the - MySQL installation directory, and then invokes mysqld_safe. If you - want the server to run as some specific user, add an appropriate - user option to the [mysqld] group of the /etc/my.cnf option file, - as shown later in this section. (It is possible that you will need - to 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, so you should 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 need to - 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), the mysql.server script is installed - in the /etc/init.d directory with the name mysql. You need not - install it manually. See Section 2.4, "Installing MySQL from RPM - Packages on Linux," for more information on the Linux RPM - packages. - - Some vendors provide RPM packages that install a startup script - under a different name such as mysqld. - - If you install MySQL from a source distribution or using a binary - distribution format that does not install mysql.server - automatically, you can install it manually. The script can be - found in the support-files directory under the MySQL installation - directory or in a MySQL source tree. - - To install mysql.server manually, copy it to the /etc/init.d - directory with the name mysql, and then make it executable. Do - this by changing location into the appropriate directory where - mysql.server is located and executing these commands: -shell> cp mysql.server /etc/init.d/mysql -shell> chmod +x /etc/init.d/mysql - - Older Red Hat systems use the /etc/rc.d/init.d directory rather - than /etc/init.d. Adjust the preceding commands accordingly. - Alternatively, first create /etc/init.d as a symbolic link that - points to /etc/rc.d/init.d: -shell> cd /etc -shell> ln -s rc.d/init.d . - - 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: -shell> chkconfig --add mysql - - On some Linux systems, the following command also seems to be - necessary to fully enable the mysql script: -shell> chkconfig --level 345 mysql on - - On FreeBSD, startup scripts generally should go in - /usr/local/etc/rc.d/. The rc(8) manual page states that scripts in - this directory are executed only if their basename matches the - *.sh shell file name pattern. Any other files or directories - present within the directory are silently ignored. In other words, - on FreeBSD, you should install the mysql.server script as - /usr/local/etc/rc.d/mysql.server.sh to enable automatic startup. - - 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, you could append a command like the one following to the - appropriate startup file: -/bin/sh -c 'cd /usr/local/mysql; ./bin/mysqld_safe --user=mysql &' - - For other systems, consult your operating system documentation to - see how to install startup scripts. - - You can add options for mysql.server in a global /etc/my.cnf file. - A typical /etc/my.cnf file might look like this: -[mysqld] -datadir=/usr/local/mysql/var -socket=/var/tmp/mysql.sock -port=3306 -user=mysql - -[mysql.server] -basedir=/usr/local/mysql - - The mysql.server script supports the following options: basedir, - datadir, and pid-file. 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. - - The following table shows which option groups the server and each - startup script read from option files. - Script Option Groups - mysqld [mysqld], [server], [mysqld-major_version] - mysqld_safe [mysqld], [server], [mysqld_safe] - mysql.server [mysqld], [mysql.server], [server] - - [mysqld-major_version] means that groups with names like - [mysqld-5.0] and [mysqld-5.1] are read by servers having versions - 5.0.x, 5.1.x, and so forth. This feature can be used to specify - options that can be read only by servers within a given release - series. - - For backward compatibility, mysql.server also reads the - [mysql_server] group and mysqld_safe also reads the [safe_mysqld] - group. However, you should update your option files to use the - [mysql.server] and [mysqld_safe] groups instead when using MySQL - 5.1. - - See Section 4.2.3.3, "Using Option Files." - -2.11.2.3. Starting and Troubleshooting the MySQL Server - - This section provides troubleshooting suggestions for problems - starting the server on Unix. If you are using Windows, see Section - 2.3.13, "Troubleshooting a MySQL Installation Under Windows." - - If you have problems starting the server, here are some things to - try: - - * Check the error log to see why the server does not start. - - * Specify any special options needed by the storage engines you - are using. - - * Make sure that the server knows where to find the data - directory. - - * Make sure that the server can access the data directory. The - ownership and permissions of the data directory and its - contents must be set such that the server can read and modify - them. - - * Verify that the network interfaces the server wants to use are - available. - - Some storage engines have options that control their behavior. You - can create a my.cnf file and specify startup options for the - engines that you plan to use. If you are going to use storage - engines that support transactional tables (InnoDB, NDB), be sure - that you have them configured the way you want before starting the - server: - - * If you are using InnoDB tables, see Section 13.6.2, "InnoDB - Configuration." - - * If you are using MySQL Cluster, see Section 17.3, "MySQL - Cluster Configuration." - - MySQL Enterprise For expert advice on start-up options appropriate - to your circumstances, subscribe to The MySQL Enterprise Monitor. - For more information, see - http://www.mysql.com/products/enterprise/advisors.html. - - Storage engines will use default option values if you specify - none, but it is recommended that you review the available options - and specify explicit values for those for which the defaults are - not appropriate for your installation. - - When the mysqld server starts, it changes location to the data - directory. This is where it expects to find databases and where it - expects to write log files. The server also writes the pid - (process ID) file in the data directory. - - The data directory location is hardwired in when the server is - compiled. This is where the server looks for the data directory by - default. If the data directory is located somewhere else on your - system, the server will not work properly. You can determine what - the default path settings are by invoking mysqld with the - --verbose and --help options. - - If the default locations don't match the MySQL installation layout - on your system, you can override them by specifying options to - mysqld or mysqld_safe on the command line or in an option file. - - To specify the location of the data directory explicitly, use the - --datadir option. However, normally you can tell mysqld the - location of the base directory under which MySQL is installed and - it looks for the data directory there. You can do this with the - --basedir option. - - To check the effect of specifying path options, invoke mysqld with - those options followed by the --verbose and --help options. For - example, if you change location into the directory where mysqld is - installed and then run the following command, it shows the effect - of starting the server with a base directory of /usr/local: -shell> ./mysqld --basedir=/usr/local --verbose --help - - You can specify other options such as --datadir as well, but - --verbose and --help must be the last options. - - Once you determine the path settings you want, start the server - without --verbose and --help. - - If mysqld is currently running, you can find out what path - settings it is using by executing this command: -shell> mysqladmin variables - - Or: -shell> mysqladmin -h host_name variables - - host_name is the name of the MySQL server host. - - If you get Errcode 13 (which means Permission denied) when - starting mysqld, this means that the privileges of the data - directory or its contents do not allow the server access. In this - case, you change the permissions for the involved files and - directories so that the server has the right to use them. You can - also start the server as root, but this raises security issues and - should be avoided. - - On Unix, change location into the data directory and check the - ownership of the data directory and its contents to make sure the - server has access. For example, if the data directory is - /usr/local/mysql/var, use this command: -shell> ls -la /usr/local/mysql/var - - If the data directory or its files or subdirectories are not owned - by the login account that you use for running the server, change - their ownership to that account. If the account is named mysql, - use these commands: -shell> chown -R mysql /usr/local/mysql/var -shell> chgrp -R mysql /usr/local/mysql/var - - If the server fails to start up correctly, check the error log. - Log files are located in the data directory (typically C:\Program - Files\MySQL\MySQL Server 5.1\data on Windows, - /usr/local/mysql/data for a Unix binary distribution, and - /usr/local/var for a Unix source distribution). Look in the data - directory for files with names of the form host_name.err and - host_name.log, where host_name is the name of your server host. - Then examine the last few lines of these files. On Unix, you can - use tail to display them: -shell> tail host_name.err -shell> tail host_name.log - - The error log should contain information that indicates why the - server couldn't start. - - If either of the following errors occur, it means that some other - program (perhaps another mysqld server) is using the TCP/IP port - or Unix socket file that mysqld is trying to use: -Can't start server: Bind on TCP/IP port: Address already in use -Can't start server: Bind on unix socket... - - Use ps to determine whether you have another mysqld server - running. If so, shut down the server before starting mysqld again. - (If another server is running, and you really want to run multiple - servers, you can find information about how to do so in Section - 5.6, "Running Multiple MySQL Servers on the Same Machine.") - - If no other server is running, try to execute the command telnet - your_host_name tcp_ip_port_number. (The default MySQL port number - is 3306.) Then press Enter a couple of times. If you don't get an - error message like telnet: Unable to connect to remote host: - Connection refused, some other program is using the TCP/IP port - that mysqld is trying to use. You'll need to track down what - program this is and disable it, or else tell mysqld to listen to a - different port with the --port option. In this case, you'll also - need to specify the port number for client programs when - connecting to the server via TCP/IP. - - Another reason the port might be inaccessible is that you have a - firewall running that blocks connections to it. If so, modify the - firewall settings to allow access to the port. - - If the server starts but you can't connect to it, you should make - sure that you have an entry in /etc/hosts that looks like this: -127.0.0.1 localhost - - This problem occurs only on systems that do not have a working - thread library and for which MySQL must be configured to use - MIT-pthreads. - - If you cannot get mysqld to start, you can try to make a trace - file to find the problem by using the --debug option. See MySQL - Internals: Porting - (http://forge.mysql.com/wiki/MySQL_Internals_Porting). - -2.11.3. Securing the Initial MySQL Accounts - - Part of the MySQL installation process is to set up the mysql - database that contains the grant tables: - - * Windows distributions contain preinitialized grant tables that - are installed automatically. - - * On Unix, the grant tables are populated by the - mysql_install_db program. Some installation methods run this - program for you. Others require that you execute it manually. - For details, see Section 2.11.2, "Unix Post-Installation - Procedures." - - The grant tables define the initial MySQL user accounts and their - access privileges. These accounts are set up as follows: - - * Accounts with the user name root are created. These are - superuser accounts that can do anything. The initial root - account passwords are empty, so anyone can connect to the - MySQL server as root --- without a password --- and be granted - all privileges. - - + On Windows, one root account is created; this account - allows connecting from the local host only. The Windows - installer will optionally create an account allowing for - connections from any host only if the user selects the - Enable root access from remote machines option during - installation. - - + On Unix, both root accounts are for connections from the - local host. Connections must be made from the local host - by specifying a host name of localhost for one of the - accounts, or the actual host name or IP number for the - other. - - * Two anonymous-user accounts are created, each with an empty - user name. The anonymous accounts have no password, so anyone - can use them to connect to the MySQL server. - - + On Windows, one anonymous account is for connections from - the local host. It has no global privileges. (Before - MySQL 5.1.16, it has all global privileges, just like the - root accounts.) The other is for connections from any - host and has all privileges for the test database and for - other databases with names that start with test. - - + On Unix, both anonymous accounts are for connections from - the local host. Connections must be made from the local - host by specifying a host name of localhost for one of - the accounts, or the actual host name or IP number for - the other. These accounts have all privileges for the - test database and for other databases with names that - start with test_. - - As noted, none of the initial accounts have passwords. This means - that your MySQL installation is unprotected until you do something - about it: - - * If you want to prevent clients from connecting as anonymous - users without a password, you should either assign a password - to each anonymous account or else remove the accounts. - - * You should assign a password to each MySQL root account. - - The following instructions describe how to set up passwords for - the initial MySQL accounts, first for the anonymous accounts and - then for the root accounts. Replace "newpwd" in the examples with - the actual password that you want to use. The instructions also - cover how to remove the anonymous accounts, should you prefer not - to allow anonymous access at all. - - You might want to defer setting the passwords until later, so that - you don't need to specify them while you perform additional setup - or testing. However, be sure to set them before using your - installation for production purposes. - - Anonymous Account Password Assignment - - To assign passwords to the anonymous accounts, connect to the - server as root and then use either SET PASSWORD or UPDATE. In - either case, be sure to encrypt the password using the PASSWORD() - function. - - To use SET PASSWORD on Windows, do this: -shell> mysql -u root -mysql> SET PASSWORD FOR ''@'localhost' = PASSWORD('newpwd'); -mysql> SET PASSWORD FOR ''@'%' = PASSWORD('newpwd'); - - To use SET PASSWORD on Unix, do this: -shell> mysql -u root -mysql> SET PASSWORD FOR ''@'localhost' = PASSWORD('newpwd'); -mysql> SET PASSWORD FOR ''@'host_name' = PASSWORD('newpwd'); - - In the second SET PASSWORD statement, replace host_name with the - name of the server host. This is the name that is specified in the - Host column of the non-localhost record for root in the user - table. If you don't know what host name this is, issue the - following statement before using SET PASSWORD: -mysql> SELECT Host, User FROM mysql.user; - - Look for the record that has root in the User column and something - other than localhost in the Host column. Then use that Host value - in the second SET PASSWORD statement. - - Anonymous Account Removal - - If you prefer to remove the anonymous accounts instead, do so as - follows: -shell> mysql -u root -mysql> DROP USER ''; - - The DROP statement applies both to Windows and to Unix. On - Windows, if you want to remove only the anonymous account that has - the same privileges as root, do this instead: -shell> mysql -u root -mysql> DROP USER ''@'localhost'; - - That account allows anonymous access but has full privileges, so - removing it improves security. - - root Account Password Assignment - - You can assign passwords to the root accounts in several ways. The - following discussion demonstrates three methods: - - * Use the SET PASSWORD statement - - * Use the mysqladmin command-line client program - - * Use the UPDATE statement - - To assign passwords using SET PASSWORD, connect to the server as - root and issue SET PASSWORD statements. Be sure to encrypt the - password using the PASSWORD() function. - - For Windows, do this: -shell> mysql -u root -mysql> SET PASSWORD FOR 'root'@'localhost' = PASSWORD('newpwd'); -mysql> SET PASSWORD FOR 'root'@'%' = PASSWORD('newpwd'); - - For Unix, do this: -shell> mysql -u root -mysql> SET PASSWORD FOR 'root'@'localhost' = PASSWORD('newpwd'); -mysql> SET PASSWORD FOR 'root'@'host_name' = PASSWORD('newpwd'); - - In the second SET PASSWORD statement, replace host_name with the - name of the server host. This is the same host name that you used - when you assigned the anonymous account passwords. - - If the user table contains an account with User and Host values of - 'root' and '127.0.0.1', use an additional SET PASSWORD statement - to set that account's password: -mysql> SET PASSWORD FOR 'root'@'127.0.0.1' = PASSWORD('newpwd'); - - To assign passwords to the root accounts using mysqladmin, execute - the following commands: -shell> mysqladmin -u root password "newpwd" -shell> mysqladmin -u root -h host_name password "newpwd" - - These commands apply both to Windows and to Unix. In the second - command, replace host_name with the name of the server host. The - double quotes around the password are not always necessary, but - you should use them if the password contains spaces or other - characters that are special to your command interpreter. - - The mysqladmin method of setting the root account passwords does - not set the password for the 'root'@'127.0.0.1' account. To do so, - use SET PASSWORD as shown earlier. - - You can also use UPDATE to modify the user table directly. The - following UPDATE statement assigns a password to all root - accounts: -shell> mysql -u root -mysql> UPDATE mysql.user SET Password = PASSWORD('newpwd') - -> WHERE User = 'root'; -mysql> FLUSH PRIVILEGES; - - The UPDATE statement applies both to Windows and to Unix. - - After the passwords have been set, you must supply the appropriate - password whenever you connect to the server. For example, if you - want to use mysqladmin to shut down the server, you can do so - using this command: -shell> mysqladmin -u root -p shutdown -Enter password: (enter root password here) - -Note - - If you forget your root password after setting it up, Section - B.1.4.1, "How to Reset the Root Password," covers the procedure - for resetting it. - - To set up additional accounts, you can use the GRANT statement. - For instructions, see Section 5.5.2, "Adding User Accounts." - -2.12. Upgrading or Downgrading MySQL - -2.12.1. Upgrading MySQL +2.4.1. Upgrading MySQL As a general rule, to upgrade from one release series to another, you should go to the next series rather than skipping a series. To @@ -5825,14 +2079,22 @@ Note MySQL 5.0, see the MySQL 5.0 Reference Manual; for earlier releases, see the MySQL 3.23, 4.0, 4.1 Reference Manual. + If you perform a binary (in-place) upgrade without dumping and + reloading tables, you cannot upgrade directly from MySQL 4.1 to + 5.1. This occurs due to an incompatible change in the MyISAM table + index format in MySQL 5.0. Upgrade from MySQL 4.1 to 5.0 and + repair all MyISAM tables (see Section 2.4.4, "Rebuilding or + Repairing Tables or Indexes"). Then upgrade from MySQL 5.0 to 5.1 + and check and repair your tables. + To upgrade from MySQL 5.0 to 5.1, use the items in the following checklist as a guide: * Before any upgrade, back up your databases, including the mysql database that contains the grant tables. See Section - 6.1, "Database Backups." + 6.1, "Database Backup Methods." - * Read all the notes in Section 2.12.1.1, "Upgrading from MySQL + * Read all the notes in Section 2.4.1.1, "Upgrading from MySQL 5.0 to 5.1." These notes enable you to identify upgrade issues that apply to your current MySQL installation. Some incompatibilities discussed in that section require your @@ -5852,8 +2114,8 @@ Note MySQL introduce changes to the structure of the grant tables to add new privileges or features.) - * If you are running MySQL Server on Windows, see Section - 2.3.14, "Upgrading MySQL on Windows." + * If you are running MySQL Server on Windows, see Section 2.5.7, + "Upgrading MySQL on Windows." * If you are using replication, see Section 16.3.3, "Upgrading a Replication Setup," for information on upgrading your @@ -5926,7 +2188,7 @@ Note applies to other MySQL interfaces as well, such as PHP mysql extensions and the Python MySQLdb module. -2.12.1.1. Upgrading from MySQL 5.0 to 5.1 +2.4.1.1. Upgrading from MySQL 5.0 to 5.1 After upgrading a 5.0 installation to 5.0.10 or above, it is necessary to upgrade your grant tables. Otherwise, creating stored @@ -5944,13 +2206,21 @@ Note you dump your tables with mysqldump before upgrading and reload the dump file after upgrading. + If you perform a binary (in-place) upgrade without dumping and + reloading tables, you cannot upgrade directly from MySQL 4.1 to + 5.1. This occurs due to an incompatible change in the MyISAM table + index format in MySQL 5.0. Upgrade from MySQL 4.1 to 5.0 and + repair all MyISAM tables (see Section 2.4.4, "Rebuilding or + Repairing Tables or Indexes"). Then upgrade from MySQL 5.0 to 5.1 + and check and repair your tables. + In general, you should do the following when upgrading from MySQL 5.0 to 5.1: * Read all the items in the following sections to see whether any of them might affect your applications: - + Section 2.12.1, "Upgrading MySQL," has general update + + Section 2.4.1, "Upgrading MySQL," has general update information. + The items in the change lists found later in this section @@ -5975,7 +2245,7 @@ Note in the incompatibility description. Often this will involve a dump and reload, or use of a statement such as CHECK TABLE or REPAIR TABLE. - For dump and reload instructions, see Section 2.12.4, + For dump and reload instructions, see Section 2.4.4, "Rebuilding or Repairing Tables or Indexes." Any procedure that involves REPAIR TABLE with the USE_FRM option must be done before upgrading. Use of this statement with a version of @@ -5992,15 +2262,17 @@ Note MySQL introduce changes to the structure of the grant tables to add new privileges or features.) - * Check Section 2.12.3, "Checking Whether Table Indexes Must Be - Rebuilt," to see whether changes to character sets or - collations were made that affect your table indexes. If so, - you will need to rebuild the affected indexes using the - instructions in Section 2.12.4, "Rebuilding or Repairing - Tables or Indexes." + * Check Section 2.4.3, "Checking Whether Tables or Indexes Must + Be Rebuilt," to see whether changes to table formats or to + character sets or collations were made between your current + version of MySQL and the version to which you are upgrading. + If so and these changes result in an incompatibility between + MySQL versions, you will need to upgrade the affected tables + using the instructions in Section 2.4.4, "Rebuilding or + Repairing Tables or Indexes." - * If you are running MySQL Server on Windows, see Section - 2.3.14, "Upgrading MySQL on Windows." + * If you are running MySQL Server on Windows, see Section 2.5.7, + "Upgrading MySQL on Windows." * If you are using replication, see Section 16.3.3, "Upgrading a Replication Setup," for information on upgrading your @@ -6042,6 +2314,22 @@ Note Server Changes: + * Known issue: After a binary upgrade to MySQL 5.1 from a MySQL + 5.0 installation that contains ARCHIVE tables, accessing those + tables will cause the server to crash, even if you have run + mysql_upgrade or CHECK TABLE ... FOR UPGRADE. To work around + this problem, use mysqldump to dump all ARCHIVE tables before + upgrading, and reload them into MySQL 5.1 after upgrading. + + * Known issue: The fix for + Bug#23491: http://bugs.mysql.com/23491 introduced a problem + with SHOW CREATE VIEW, which is used by mysqldump. This causes + an incompatibility when upgrading from versions affected by + that bug fix (MySQL 5.0.40 through 5.0.43, MySQL 5.1.18 + through 5.1.19): If you use mysqldump before upgrading from an + affected version and reload the data after upgrading to a + higher version, you must drop and recreate your views. + * Known issue: Dumps performed by using mysqldump to generate a dump file before the upgrade and reloading the file after upgrading are subject to the following problem: @@ -6162,8 +2450,28 @@ RENAME TABLE table_b TO `table b`; * Incompatible change: Character set or collation changes were made in MySQL 5.1.21, 5.1.23, and 5.1.24 that may require - table indexes to be rebuilt. For details, see Section 2.12.3, - "Checking Whether Table Indexes Must Be Rebuilt." + table indexes to be rebuilt. For details, see Section 2.4.3, + "Checking Whether Tables or Indexes Must Be Rebuilt." + + * Incompatible change: MySQL 5.1 implements support for a plugin + API that allows the loading and unloading of components at + runtime, without restarting the server. Section 22.2, "The + MySQL Plugin Interface." The plugin API requires the + mysql.plugin table. After upgrading from an older version of + MySQL, you should run the mysql_upgrade command to create this + table. See Section 4.4.8, "mysql_upgrade --- Check Tables for + MySQL Upgrade." + Plugins are installed in the directory named by the plugin_dir + system variable. This variable also controls the location from + which the server loads user-defined functions (UDFs), which is + a change from earlier versions of MySQL. That is, all UDF + library files now must be installed in the plugin directory. + When upgrading from an older version of MySQL, you must + migrate your UDF files to the plugin directory. + + * Incompatible change: The table_cache system variable has been + renamed to table_open_cache. Any scripts that refer to + table_cache must be updated to use the new name. * Incompatible change: In MySQL 5.1.36, options for loading plugins such as pluggable storage engines were changed from @@ -6262,26 +2570,6 @@ RENAME TABLE table_b TO `table b`; information and workarounds, see Section D.4, "Restrictions on Views." - * Incompatible change: MySQL 5.1 implements support for a plugin - API that allows the loading and unloading of components at - runtime, without restarting the server. Section 22.2, "The - MySQL Plugin Interface." The plugin API requires the - mysql.plugin table. After upgrading from an older version of - MySQL, you should run the mysql_upgrade command to create this - table. See Section 4.4.8, "mysql_upgrade --- Check Tables for - MySQL Upgrade." - Plugins are installed in the directory named by the plugin_dir - system variable. This variable also controls the location from - which the server loads user-defined functions (UDFs), which is - a change from earlier versions of MySQL. That is, all UDF - library files now must be installed in the plugin directory. - When upgrading from an older version of MySQL, you must - migrate your UDF files to the plugin directory. - - * Incompatible change: The table_cache system variable has been - renamed to table_open_cache. Any scripts that refer to - table_cache must be updated to use the new name. - * Incompatible change: Several issues were identified for stored programs (stored procedures and functions, triggers, and events) and views containing non-ASCII symbols. These issues @@ -6314,6 +2602,19 @@ RENAME TABLE table_b TO `table b`; to 5.1.20. 2) Logging to syslog may fail to operate correctly in some cases. For these reasons, avoid using MySQL 5.1.20. + * Incompatible change: As of MySQL 5.1.18, the plugin interface + and its handling of system variables was changed. Command-line + options such as --skip-innodb now cause an error if InnoDB is + not built-in or plugin-loaded. You should use + --loose-skip-innodb if you do not want any error even if + InnoDB is not available. The --loose prefix modifier should be + used for all command-line options where you are uncertain + whether the plugin exists and when you want the operation to + proceed even if the option is necessarily ignored due to the + absence of the plugin. (For a desecription of how --loose + works, see Section 4.2.3.1, "Using Options on the Command + Line.") + * Incompatible change: As of MySQL 5.1.15, InnoDB rolls back only the last statement on a transaction timeout. A new option, --innodb_rollback_on_timeout, causes InnoDB to abort @@ -6479,7 +2780,7 @@ DELETE FROM t1 AS a2 USING t1 AS a1 INNER JOIN t2 AS a2; still accepted as a synonym for the ENGINE = engine_name table option but generates a warning. You should note that this option is not available in MySQL 5.1.7, and is removed - altogether as of MySQL 6.0 and produces a syntax error. + altogether as of MySQL 5.4 and produces a syntax error. TYPE has been deprecated since MySQL 4.0. * Incompatible change: The namespace for triggers changed in @@ -6543,8 +2844,11 @@ mysql> source /tmp/triggers.sql // SUPER privilege from those accounts that no longer otherwise require it. - * Some keywords are reserved in MySQL 5.1 that were not reserved - in MySQL 5.0. See Section 8.3, "Reserved Words." + * Some keywords may be reserved in MySQL 5.1 that were not + reserved in MySQL 5.0. See Section 8.3, "Reserved Words." + + * The BACKUP TABLE, and RESTORE TABLE statements are deprecated. + mysqldump or mysqlhotcopy can be used as alternatives. * The LOAD DATA FROM MASTER and LOAD TABLE FROM MASTER statements are deprecated. See Section 12.6.2.2, "LOAD DATA @@ -6563,7 +2867,7 @@ mysql> source /tmp/triggers.sql // than an unsigned int for STMT_ATTR_UPDATE_MAX_LENGTH. (Bug#16144: http://bugs.mysql.com/16144) -2.12.2. Downgrading MySQL +2.4.2. Downgrading MySQL This section describes what you should do to downgrade to an older MySQL version in the unlikely case that the previous version @@ -6580,7 +2884,7 @@ mysql> source /tmp/triggers.sql // * Read the upgrading section for the release series from which you are downgrading to be sure that it does not have any - features you really need. See Section 2.12.1, "Upgrading + features you really need. See Section 2.4.1, "Upgrading MySQL." * If there is a downgrading section for that version, you should @@ -6590,13 +2894,14 @@ mysql> source /tmp/triggers.sql // which you are downgrading and your current version, see the change logs (Appendix C, "MySQL Change History"). - * Check Section 2.12.3, "Checking Whether Table Indexes Must Be - Rebuilt," to see whether changes to character sets or - collations were made between your current version of MySQL and - the version to which you are downgrading. If so and these - changes affect your table indexes, you will need to rebuild - the affected indexes using the instructions in Section 2.12.4, - "Rebuilding or Repairing Tables or Indexes." + * Check Section 2.4.3, "Checking Whether Tables or Indexes Must + Be Rebuilt," to see whether changes to table formats or to + character sets or collations were made between your current + version of MySQL and the version to which you are downgrading. + If so and these changes result in an incompatibility between + MySQL versions, you will need to downgrade the affected tables + using the instructions in Section 2.4.4, "Rebuilding or + Repairing Tables or Indexes." In most cases, you can move the MySQL format files and data files between different versions on the same architecture as long as you @@ -6606,7 +2911,7 @@ mysql> source /tmp/triggers.sql // incompatibilities in table storage formats. In this case, use mysqldump to dump your tables before downgrading. After downgrading, reload the dump file using mysql or mysqlimport to - re-create your tables. For examples, see Section 2.12.5, "Copying + re-create your tables. For examples, see Section 2.4.5, "Copying MySQL Databases to Another Machine." A typical symptom of a downward-incompatible table format change @@ -6639,11 +2944,11 @@ mysql> source /tmp/triggers.sql // * Triggers were added in MySQL 5.0, so if you downgrade from 5.0 to 4.1, you cannot use triggers at all. -2.12.2.1. Downgrading to MySQL 5.0 +2.4.2.1. Downgrading to MySQL 5.0 - When downgrading to MySQL 5.0 from MySQL 5.1 or a later version, - you should keep in mind the following issues relating to features - found in MySQL 5.1 and later, but not in MySQL 5.0: + When downgrading to MySQL 5.0 from MySQL 5.1, you should keep in + mind the following issues relating to features found in MySQL 5.1, + but not in MySQL 5.0: * Partitioning. MySQL 5.0 does not support user-defined partitioning. If a table was created as a partitioned table in @@ -6684,7 +2989,7 @@ mysql> source /tmp/triggers.sql // 5.0, you will need to give the SUPER privilege to those accounts that had the TRIGGER privilege in 5.1. -2.12.3. Checking Whether Table Indexes Must Be Rebuilt +2.4.3. Checking Whether Tables or Indexes Must Be Rebuilt A binary upgrade or downgrade is one that installs one version of MySQL "in place" over an existing version, without dumping and @@ -6699,12 +3004,37 @@ mysql> source /tmp/triggers.sql // 3. Start the server for the new version. In many cases, the tables from the previous version of MySQL can - be used without change by the new version. However, sometimes - modifications are made to the handling of character sets or - collations that change the character sort order, which causes the - ordering of entries in any index that uses an affected character - set or collation to be incorrect. Such changes result in several - possible problems: + be used without problem by the new version. However, sometimes + changes occur that require tables or table indexes to be rebuilt, + as described in this section. If you have tables that are affected + by any of the issues described here, rebuild the tables or indexes + as necessary using the instructions given in Section 2.4.4, + "Rebuilding or Repairing Tables or Indexes." + + Table Incompatibilities + + After a binary upgrade to MySQL 5.1 from a MySQL 5.0 installation + that contains ARCHIVE tables, accessing those tables causes the + server to crash, even if you have run mysql_upgrade or CHECK TABLE + ... FOR UPGRADE. To work around this problem, use mysqldump to + dump all ARCHIVE tables before upgrading, and reload them into + MySQL 5.1 after upgrading. The same problem occurs for binary + downgrades from MySQL 5.1 to 5.0. + + Index Incompatibilities + + If you perform a binary upgrade without dumping and reloading + tables, you cannot upgrade directly from MySQL 4.1 to 5.1 or + higher. This occurs due to an incompatible change in the MyISAM + table index format in MySQL 5.0. Upgrade from MySQL 4.1 to 5.0 and + repair all MyISAM tables. Then upgrade from MySQL 5.0 to 5.1 and + check and repair your tables. + + Modifications to the handling of character sets or collations + might change the character sort order, which causes the ordering + of entries in any index that uses an affected character set or + collation to be incorrect. Such changes result in several possible + problems: * Comparison results that differ from previous results @@ -6719,7 +3049,7 @@ mysql> source /tmp/triggers.sql // an affected character set or collation, either by dropping and re-creating the indexes, or by dumping and reloading the entire table. For information about rebuilding indexes, see Section - 2.12.4, "Rebuilding or Repairing Tables or Indexes." + 2.4.4, "Rebuilding or Repairing Tables or Indexes." To check whether a table has indexes that must be rebuilt, consult the following list. It indicates which versions of MySQL @@ -6730,14 +3060,10 @@ mysql> source /tmp/triggers.sql // report, the bug number is given. The list applies both for binary upgrades and downgrades. For - example, Bug#29461: http://bugs.mysql.com/29461 was fixed in MySQL - 5.0.48, so it applies to upgrades from versions older than 5.0.48 - to 5.0.48 or newer, and also to downgrades from 5.0.48 or newer to - versions older than 5.0.48. - - If you have tables with indexes that are affected, rebuild the - indexes using the instructions given in Section 2.12.4, - "Rebuilding or Repairing Tables or Indexes." + example, Bug#27877: http://bugs.mysql.com/27877 was fixed in MySQL + 5.1.24 and 5.4.0, so it applies to upgrades from versions older + than 5.1.24 to 5.1.24 or newer, and to downgrades from 5.1.24 or + newer to versions older than 5.1.24. In many cases, you can use CHECK TABLE ... FOR UPGRADE to identify tables for which index rebuilding is required. (It will report: @@ -6751,76 +3077,31 @@ mysql> source /tmp/triggers.sql // Changes that cause index rebuilding to be necessary: - * MySQL 5.0.48 (Bug#29461: http://bugs.mysql.com/29461) + * MySQL 5.0.48, 5.1.21 (Bug#29461: http://bugs.mysql.com/29461) Affects indexes for columns that use any of these character sets: eucjpms, euc_kr, gb2312, latin7, macce, ujis Affected tables can be detected by CHECK TABLE ... FOR UPGRADE - as of MySQL 5.1.29, 6.0.8 (see + as of MySQL 5.1.29, 5.4.0 (see Bug#39585: http://bugs.mysql.com/39585). - * MySQL 5.0.48 (Bug#27562: http://bugs.mysql.com/27562) + * MySQL 5.0.48, 5.1.23 (Bug#27562: http://bugs.mysql.com/27562) Affects indexes that use the ascii_general_ci collation for columns that contain any of these characters: '`' GRAVE ACCENT, '[' LEFT SQUARE BRACKET, '\' REVERSE SOLIDUS, ']' RIGHT SQUARE BRACKET, '~' TILDE Affected tables can be detected by CHECK TABLE ... FOR UPGRADE - as of MySQL 5.1.29, 6.0.8 (see + as of MySQL 5.1.29, 5.4.0 (see Bug#39585: http://bugs.mysql.com/39585). - * MySQL 5.1.21 (Bug#29461: http://bugs.mysql.com/29461) - Affects indexes for columns that use any of these character - sets: eucjpms, euc_kr, gb2312, latin7, macce, ujis - Affected tables can be detected by CHECK TABLE ... FOR UPGRADE - as of MySQL 5.1.29, 6.0.8 (see - Bug#39585: http://bugs.mysql.com/39585). - - * MySQL 5.1.23 (Bug#27562: http://bugs.mysql.com/27562) - Affects indexes that use the ascii_general_ci collation for - columns that contain any of these characters: '`' GRAVE - ACCENT, '[' LEFT SQUARE BRACKET, '\' REVERSE SOLIDUS, ']' - RIGHT SQUARE BRACKET, '~' TILDE - Affected tables can be detected by CHECK TABLE ... FOR UPGRADE - as of MySQL 5.1.29, 6.0.8 (see - Bug#39585: http://bugs.mysql.com/39585). - - * MySQL 5.1.24 (Bug#27877: http://bugs.mysql.com/27877) + * MySQL 5.1.24, 5.4.0 (Bug#27877: http://bugs.mysql.com/27877) Affects indexes that use the utf8_general_ci or ucs2_general_ci collation for columns that contain 'ß' LATIN SMALL LETTER SHARP S (German). Affected tables can be detected by CHECK TABLE ... FOR UPGRADE - as of MySQL 5.1.30, 6.0.8 (see + as of MySQL 5.1.30, 5.4.0 (see Bug#40053: http://bugs.mysql.com/40053). - * * MySQL 6.0.1 (WL#3664) - Affects indexes that use the latin2_czech_cs collation. - Affected tables can be detected by CHECK TABLE ... FOR UPGRADE - as of MySQL 5.4.4, 6.0.9 (see - Bug#40054: http://bugs.mysql.com/40054). - MySQL 6.0.5 (Bug#33452: http://bugs.mysql.com/33452) - Affects indexes that use the latin2_czech_cs collation. - Affected tables can be detected by CHECK TABLE ... FOR UPGRADE - as of MySQL 5.4.4, 6.0.9 (see - Bug#40054: http://bugs.mysql.com/40054). - - * MySQL 6.0.5 (Bug#27877: http://bugs.mysql.com/27877) - Affects indexes that use the utf8_general_ci or - ucs2_general_ci collation for columns that contain 'ß' LATIN - SMALL LETTER SHARP S (German). - Affected tables can be detected by CHECK TABLE ... FOR UPGRADE - as of MySQL 6.0.8 (see - Bug#40053: http://bugs.mysql.com/40053). - - * MySQL 6.0.6 (Bug#25420: http://bugs.mysql.com/25420) - Affects indexes for columns that use the following collations, - if the columns contain the indicated characters: - big5_chinese_ci: '~' TILDE or '`' GRAVE ACCENT; - cp866_general_ci: j LATIN SMALL LETTER J; gb2312_chinese_ci: - '~' TILDE; gbk_chinese_ci: '~' TILDE - Affected tables can be detected by CHECK TABLE ... FOR UPGRADE - as of MySQL 5.4.4, 6.0.9 (see - Bug#40054: http://bugs.mysql.com/40054). - -2.12.4. Rebuilding or Repairing Tables or Indexes +2.4.4. Rebuilding or Repairing Tables or Indexes This section describes how to rebuild a table. This can be necessitated by changes to MySQL such as how data types are @@ -6837,11 +3118,11 @@ mysql> source /tmp/triggers.sql // Note If you are rebuilding tables because a different version of MySQL - will not handle them after a binary upgrade or downgrade, you must - use the dump-and-reload method. Dump the tables before upgrading - or downgrading (using your original version of MySQL), and reload - the tables after upgrading or downgrading (after installing the - new version). + will not handle them after a binary (in-place) upgrade or + downgrade, you must use the dump-and-reload method. Dump the + tables before upgrading or downgrading (using your original + version of MySQL), and reload the tables after upgrading or + downgrading (after installing the new version). If you use the dump-and-reload method of rebuilding tables only for the purpose of rebuilding indexes, you can perform the dump @@ -6863,9 +3144,10 @@ shell> mysql db_name < dump.sql shell> mysqldump --all-databases > dump.sql shell> mysql < dump.sql - To rebuild a table with ALTER TABLE, use a statement that - "changes" the table to use the storage engine that it already has. - For example, if t1 is a MyISAM table, use this statement: + To rebuild a table with ALTER TABLE, use a "null" alteration; that + is, an ALTER TABLE statement that "changes" the table to use the + storage engine that it already has. For example, if t1 is a MyISAM + table, use this statement: mysql> ALTER TABLE t1 ENGINE = MyISAM; If you are not sure which storage engine to specify in the ALTER @@ -6885,7 +3167,15 @@ mysql> REPAIR TABLE t1; For specifics about which storage engines REPAIR TABLE supports, see Section 12.5.2.6, "REPAIR TABLE Syntax." -2.12.5. Copying MySQL Databases to Another Machine + mysqlcheck --repair provides command-line access to the REPAIR + TABLE statement. This can be a more convenient means of repairing + tables because you can use the --databases or --all-databases + option to repair all tables in specific databases or all + databases, respectively: +shell> mysqlcheck --repair --databases db_name ... +shell> mysqlcheck --repair --all-databases + +2.4.5. Copying MySQL Databases to Another Machine You can copy the .frm, .MYI, and .MYD files for MyISAM tables between different architectures that support the same @@ -6950,553 +3240,3112 @@ shell> mysqlimport db_name DUMPDIR/*.txt # load data into tables mysqladmin flush-privileges so that the server reloads the grant table information. -2.13. Operating System-Specific Notes +2.5. Installing MySQL on Windows + + This section describes the process for installing MySQL on + Windows. + + To run MySQL on Windows, you need the following: + + * A Windows operating system such as Windows 2000, Windows XP, + Windows Vista, Windows Server 2003, or Windows Server 2008. + Both 32-bit and 64-bit versions are supported. + In addition to running MySQL as a standard application, you + can also run the MySQL server as a Windows service. By using a + service you can monitor and control the operation of the + server through the standard Windows service management tools. + For more information, see Section 2.5.5.6, "Starting MySQL as + a Windows Service." + Generally, you should install MySQL on Windows using an + account that has administrator rights. Otherwise, you may + encounter problems with certain operations such as editing the + PATH environment variable or accessing the Service Control + Manager. Once installed, MySQL does not need to be executed + using a user with Administrator privileges. + + * TCP/IP protocol support. + + * Enough space on the hard drive to unpack, install, and create + the databases in accordance with your requirements (generally + a minimum of 200 megabytes is recommended.) + + For a list of limitations within the Windows version of MySQL, see + Section D.7.3, "Windows Platform Limitations." + + In addition to the MySQL Server package, you may need or want + additional components to use MySQL with your application or + development environment. These include, but are not limited to: + + * If you plan to connect to the MySQL server via ODBC, you need + a Connector/ODBC driver. For more information, including + installation and configuration instructions, see Section 21.1, + "MySQL Connector/ODBC." + + * If you plan to use MySQL server with .NET applications, you + need the Connector/NET driver. For more information, including + installation and configuration instructions, see Section 21.2, + "MySQL Connector/NET." + + MySQL distributions for Windows can be downloaded from + http://dev.mysql.com/downloads/. See Section 2.1.3, "How to Get + MySQL." + + MySQL for Windows is available in several distribution formats, + detailed below. Generally speaking, you should use a binary + distribution that includes an installer. It is simpler to use than + the others, and you need no additional tools to get MySQL up and + running. The installer for the Windows version of MySQL, combined + with a GUI Config Wizard, automatically installs MySQL, creates an + option file, starts the server, and secures the default user + accounts. + + * Binary installer distribution. The installable distribution + comes packaged as a Microsoft Windows Installer (MSI) package + that you can install manually or automatically on your + systems. Two formats are available, an essentials package that + contains all the files you need to install and configure + MySQL, but no additional components, and a complete package + that includes MySQL, configuration tools, benchmarks and other + components. For more information on the specific differences, + see Section 2.5.2, "Choosing An Installation Package" + For instructions on installing MySQL using one of the MSI + installation packages, see Section 2.5.3, "Installing MySQL + with the MSI Package." + + * Standard binary distribution format packaged as a Zip file + containing all of the necessary files that you unpack into + your chosen location. This package contains all of the files + in the full Windows MSI Installer package, but does not + including an installation program. + For instructions on installing MySQL using the Zip file, see + Section 2.5.5, "Installing MySQL from a noinstall Zip + Archive." + + * The source distribution contains all the code and support + files for building the executables using the Visual Studio + compiler system. + For instructions on building MySQL from source on Windows, see + Section 2.5.10, "Installing MySQL from Source on Windows." + + MySQL on Windows considerations: + + * Large Table Support + If you need tables with a size larger than 4GB, install MySQL + on an NTFS or newer file system. Don't forget to use MAX_ROWS + and AVG_ROW_LENGTH when you create tables. See Section + 12.1.17, "CREATE TABLE Syntax." + + * MySQL and Virus Checking Software + Using virus scanning software such as Norton/Symantec + Anti-Virus on directories containing MySQL data and temporary + tables can cause issues, both in terms of the performance of + MySQL and the virus-scanning software mis-identifying the + contents of the files as containing spam. This is because of + the fingerprinting mechanism used by the virus scanning + software, and the way in which MySQL rapidly updates different + files, which may be identified as a potential security risk. + After installing MySQL Server, it is recommended that you + disable virus scanning on the main directory (datadir) being + used to store your MySQL table data. There is usually a system + built into the virus scanning software to allow certain + directories to be specifically ignored during virus scanning. + In addition, by default, MySQL creates temporary files in the + standard Windows temporary directory. To prevent the temporary + files also being scanned, you should configure a separate + temporary directory for MySQL temporary files and add this to + the virus scanning exclusion list. To do this, add a + configuration option for the tmpdir parameter to your my.ini + configuration file. For more information, see Section 2.5.5.2, + "Creating an Option File." + +2.5.1. Windows Installation Layout + + For MySQL 5.1 on Windows, the default installation directory is + C:\Program Files\MySQL\MySQL Server 5.1. Some Windows users prefer + to install in C:\mysql, the directory that formerly was used as + the default. However, the layout of the subdirectories remains the + same. + + For MySQL 5.1.23 and earlier, all of the files are located within + this parent directory, using the following structure: + + Table 2.2. Installation Layout for Windows using MySQL 5.1.23 and + earlier + Directory Contents of Directory + bin Client programs and the mysqld server + data Log files, databases + Docs Manual in CHM format + examples Example programs and scripts + include Include (header) files + lib Libraries + scripts Utility scripts + share Error message files + + For MySQL 5.1.24 and later, the default location of data directory + was changed. The remainder of the directory structure remains the + same: + + Table 2.3. Installation Layout for Windows using MySQL 5.1.24 and + later + Directory Contents of Directory + bin Client programs and the mysqld server + C:\Documents and Settings\All Users\Application Data\MySQL Log + files, databases + Docs Manual in CHM format + examples Example programs and scripts + include Include (header) files + lib Libraries + scripts Utility scripts + share Error message files + +2.5.2. Choosing An Installation Package + + For MySQL 5.1, there are three installation packages to choose + from when installing MySQL on Windows: + Packaging + Feature Essentials Complete Zip (No-install) + Installer Yes Yes No + Directory-only + MySQL Server Instance Config Wizard Yes Yes No + Test Suite No Yes Yes + MySQL Server Yes Yes Yes + MySQL Client Programs Yes Yes Yes + C Headers/Libraries Yes Yes Yes + Embedded Server No Optional Yes + Scripts and Examples No Optional Yes + + In the above table: + + * Yes indiciates that the component is installed by default. + + * No indicates that the component is not installed or included. + + * Optional indicates that the component is included with the + package, but not installed unless explicitly requested using + the Custom installation mode. + + The workflow for installing using the MSI installer is shown + below: + + Figure 2.1. Installation Workflow for Windows using MSI + Installation Workflow for Windows using MSI + + The workflow for installing using the MSI installer is shown + below: + + Figure 2.2. Installation Workflow for Windows using Zip + Installation Workflow for Windows using Zip + +Note + + For the Essentials and Complete packages in the MSI installer, you + can select individual components to be installed by using the + Custom mode, including disable the components confiurated for + installation by default. + + Full details on the components are suggested uses are provided + below for reference: + + * Windows Essentials --- this package has a file name similar to + mysql-essential-5.1.41-win32.msi and is supplied as a + Microsoft Installer (MSI) package. The package includes the + minimum set of files needed to install MySQL on Windows, + including the MySQL Server Instance Config Wizard. This + package does not include optional components such as the + embedded server, developer headers and libraries or benchmark + suite. + To install using this package, see Section 2.5.3, "Installing + MySQL with the MSI Package." + + * Windows MSI Installer (Complete) --- this package has a file + name similar to mysql-5.1.41-win32.zip and contains all files + needed for a complete Windows installation, including the + MySQL Server Instance Config Wizard. This package includes + optional components such as the embedded server and benchmark + suite. + To install using this package, see Section 2.5.3, "Installing + MySQL with the MSI Package." + + * Without installer --- this package has a file name similar to + mysql-noinstall-5.1.41-win32.zip and contains all the files + found in the Complete install package, with the exception of + the MySQL Server Instance Config Wizard. This package does not + include an automated installer, and must be manually installed + and configured. + + The Essentials package is recommended for most users. Both the + Essentials and Complete distributions are available as an .msi + file for use with the Windows Installer. The Noinstall + distribution is packaged as Zip archives. To use Zip archives, you + must have a tool that can unpack .zip files. + + When using the MSI installers you can automate the installation + process. For more information, see Section 2.5.3.2, "Installing + MySQL Automatically using MSI." To automate the creation of a + MySQL instance, see Section 2.5.4.13, "Creating an Instance from + the Command Line." + + Your choice of install package affects the installation process + you must follow. If you choose to install either the Essentials or + Complete install packages, see Section 2.5.3, "Installing MySQL + with the MSI Package." If you choose to install MySQL from the + Noinstall archive, see Section 2.5.5, "Installing MySQL from a + noinstall Zip Archive." + +2.5.3. Installing MySQL with the MSI Package + + The MSI package are designed to install and configure MySQL in + such a way that you can immediately get started using MySQL. + + The MySQL Installation Wizard and MySQL Config Wizard are + available in the Essentials and Complete install packages. They + are recommended for most standard MySQL installations. Exceptions + include users who need to install multiple instances of MySQL on a + single server host and advanced users who want complete control of + server configuration. + + * For information on installing using the GUI MSI installer + process, see Section 2.5.3, "Installing MySQL with the MSI + Package." + + * For information on installing using the command line using the + MSI package, see Section 2.5.3.2, "Installing MySQL + Automatically using MSI." + + * If you have previously installed MySQL using the MSI package + and want to remove MySQL, see Section 2.5.3.3, "Removing MySQL + Installed from the MSI Package." + + The workflow sequence for using the installer is shown in the + figure below: + + Figure 2.3. Installation Workflow for Windows using MSI Installer + Installation Workflow for Windows using MSI Installer + +Note + + Microsoft Windows XP and later include a firewall which + specifically blocks ports. If you plan on using MySQL through a + network port then you should open and create an exception for this + port before performing the installation. To check and if necessary + add an exception to the firewall settings: + + 1. First ensure that you are logged in as an Administrator or a + user with Administrator privileges. + + 2. Go to the Control Panel, and double click the Windows Firewall + icon. + + 3. Choose the Allow a program through Windows Firewall option and + click the Add port button. + + 4. Enter MySQL into the Name text box and 3306 (or the port of + your choice) into the Port number text box. + + 5. Also ensure that the TCP protocol radio button is selected. + + 6. If you wish, you can also limit access to the MySQL server by + choosing the Change scope button. + + 7. Confirm your choices by clicking the OK button. + + Additionally, when running the MySQL Installation Wizard on + Windows Vista, ensure that you are logged in as a user with + administrative rights. + +Note + + When using Windows Vista, you may want to disable User Account + Control (UAC) before performing the installation. If you do not do + so, then MySQL may be identified as a security risk, which will + mean that you need to enable MySQL. You can disable the security + checking by following these instructions: + + 1. Open Control Panel. + + 2. Under the User Accounts and Family Safety, select Add or + remove user accounts. + + 3. Click on the Got to the main User Accounts page link. + + 4. Click on Turn User Account Control on or off. You may be + prompted to provide permission to change this setting. Click + Continue. + + 5. Deselect or unceck the checkbox next to Use User Account + Control (UAC) to help protect your computer. Click OK to save + the setting. + + You will need to restart to complete the process. Click Restart + Now to reboot the machine and apply the changes. You can then + follow the instructions below for installing Windows. + +2.5.3.1. Using the MySQL Installation Wizard + + MySQL Installation Wizard is an installer for the MySQL server + that uses the latest installer technologies for Microsoft Windows. + The MySQL Installation Wizard, in combination with the MySQL + Config Wizard, allows a user to install and configure a MySQL + server that is ready for use immediately after installation. + + The MySQL Installation Wizard uses the standard Microsoft + Installer Engine (MSI) system is the standard installer for all + MySQL server distributions, version 4.1.5 and higher. Users of + previous versions of MySQL need to shut down and remove their + existing MySQL installations manually before installing MySQL with + the MySQL Installation Wizard. See Section 2.5.3.1.6, "Upgrading + MySQL with the Installation Wizard," for more information on + upgrading from a previous version. + + If you are upgrading an installation from MySQL 5.1.31 or earlier + to MySQL 5.1.32 or later, read the notes provided in Section + 2.5.3.1.6, "Upgrading MySQL with the Installation Wizard." + + The Microsoft Windows Installer Engine was updated with the + release of Windows XP; those using a previous version of Windows + can reference this Microsoft Knowledge Base article + (http://support.microsoft.com/default.aspx?scid=kb;EN-US;292539) + for information on upgrading to the latest version of the Windows + Installer Engine. + + In addition, Microsoft has introduced the WiX (Windows Installer + XML) toolkit. This is the first highly acknowledged Open Source + project from Microsoft. We have switched to WiX because it is an + Open Source project and it allows us to handle the complete + Windows installation process in a flexible manner using scripts. + + Improving the MySQL Installation Wizard depends on the support and + feedback of users like you. If you find that the MySQL + Installation Wizard is lacking some feature important to you, or + if you discover a bug, please report it in our bugs database using + the instructions given in Section 1.6, "How to Report Bugs or + Problems." + +2.5.3.1.1. Downloading and Starting the MySQL Installation Wizard + + The MySQL installation packages can be downloaded from + http://dev.mysql.com/downloads/. If the package you download is + contained within a Zip archive, you need to extract the archive + first. + + The process for starting the wizard depends on the contents of the + installation package you download. If there is a setup.exe file + present, double-click it to start the installation process. If + there is an .msi file present, double-click it to start the + installation process. + +2.5.3.1.2. Choosing an Install Type + + There are three installation types available: Typical, Complete, + and Custom. + + The Typical installation type installs the MySQL server, the mysql + command-line client, and the command-line utilities. The + command-line clients and utilities include mysqldump, myisamchk, + and several other tools to help you manage the MySQL server. + + The Complete installation type installs all components included in + the installation package. The full installation package includes + components such as the embedded server library, the benchmark + suite, support scripts, and documentation. + + The Custom installation type gives you complete control over which + packages you wish to install and the installation path that is + used. See Section 2.5.3.1.3, "The Custom Install Dialog," for more + information on performing a custom install. + + If you choose the Typical or Complete installation types and click + the Next button, you advance to the confirmation screen to verify + your choices and begin the installation. If you choose the Custom + installation type and click the Next button, you advance to the + custom installation dialog, described in Section 2.5.3.1.3, "The + Custom Install Dialog." + +2.5.3.1.3. The Custom Install Dialog + + If you wish to change the installation path or the specific + components that are installed by the MySQL Installation Wizard, + choose the Custom installation type. + + A tree view on the left side of the custom install dialog lists + all available components. Components that are not installed have a + red X icon; components that are installed have a gray icon. To + change whether a component is installed, click on that component's + icon and choose a new option from the drop-down list that appears. + + You can change the default installation path by clicking the + Change... button to the right of the displayed installation path. + + After choosing your installation components and installation path, + click the Next button to advance to the confirmation dialog. + +2.5.3.1.4. The Confirmation Dialog + + Once you choose an installation type and optionally choose your + installation components, you advance to the confirmation dialog. + Your installation type and installation path are displayed for you + to review. + + To install MySQL if you are satisfied with your settings, click + the Install button. To change your settings, click the Back + button. To exit the MySQL Installation Wizard without installing + MySQL, click the Cancel button. + + After installation is complete, you have the option of registering + with the MySQL web site. Registration gives you access to post in + the MySQL forums at forums.mysql.com (http://forums.mysql.com), + along with the ability to report bugs at bugs.mysql.com + (http://bugs.mysql.com) and to subscribe to our newsletter. The + final screen of the installer provides a summary of the + installation and gives you the option to launch the MySQL Config + Wizard, which you can use to create a configuration file, install + the MySQL service, and configure security settings. + +2.5.3.1.5. Changes Made by MySQL Installation Wizard + + Once you click the Install button, the MySQL Installation Wizard + begins the installation process and makes certain changes to your + system which are described in the sections that follow. + + Changes to the Registry + + The MySQL Installation Wizard creates one Windows registry key in + a typical install situation, located in + HKEY_LOCAL_MACHINE\SOFTWARE\MySQL AB. + + The MySQL Installation Wizard creates a key named after the major + version of the server that is being installed, such as MySQL + Server 5.1. It contains two string values, Location and Version. + The Location string contains the path to the installation + directory. In a default installation it contains C:\Program + Files\MySQL\MySQL Server 5.1\. The Version string contains the + release number. For example, for an installation of MySQL Server + 5.1.41, the key contains a value of 5.1.41. + + These registry keys are used to help external tools identify the + installed location of the MySQL server, preventing a complete scan + of the hard-disk to determine the installation path of the MySQL + server. The registry keys are not required to run the server, and + if you install MySQL using the noinstall Zip archive, the registry + keys are not created. + + Changes to the Start Menu + + The MySQL Installation Wizard creates a new entry in the Windows + Start menu under a common MySQL menu heading named after the major + version of MySQL that you have installed. For example, if you + install MySQL 5.1, the MySQL Installation Wizard creates a MySQL + Server 5.1 section in the Start menu. + + The following entries are created within the new Start menu + section: + + * MySQL Command Line Client: This is a shortcut to the mysql + command-line client and is configured to connect as the root + user. The shortcut prompts for a root user password when you + connect. + + * MySQL Server Instance Config Wizard: This is a shortcut to the + MySQL Config Wizard. Use this shortcut to configure a newly + installed server, or to reconfigure an existing server. + + * MySQL Documentation: This is a link to the MySQL server + documentation that is stored locally in the MySQL server + installation directory. This option is not available when the + MySQL server is installed using the Essentials installation + package. + + Changes to the File System + + The MySQL Installation Wizard by default installs the MySQL 5.1 + server to C:\Program Files\MySQL\MySQL Server 5.1, where Program + Files is the default location for applications in your system, and + 5.1 is the major version of your MySQL server. This is the + recommended location for the MySQL server, replacing the former + default location C:\mysql. + + By default, all MySQL applications are stored in a common + directory at C:\Program Files\MySQL, where Program Files is the + default location for applications in your Windows installation. A + typical MySQL installation on a developer machine might look like + this: +C:\Program Files\MySQL\MySQL Server 5.1 +C:\Program Files\MySQL\MySQL Workbench 5.1 OSS + + This approach makes it easier to manage and maintain all MySQL + applications installed on a particular system. + + In MySQL 5.1.23 and earlier, the default location for the data + files used by MySQL is located within the corresponding MySQL + Server installation directory. For MySQL 5.1.24 and later, the + default location of the data directory is the AppData directory + configured for the user that installed the MySQL application. + +2.5.3.1.6. Upgrading MySQL with the Installation Wizard + + The MySQL Installation Wizard can perform server upgrades + automatically using the upgrade capabilities of MSI. That means + you do not need to remove a previous installation manually before + installing a new release. The installer automatically shuts down + and removes the previous MySQL service before installing the new + version. + + Automatic upgrades are available only when upgrading between + installations that have the same major and minor version numbers. + For example, you can upgrade automatically from MySQL 5.1.34 to + MySQL 5.1.37, but not from MySQL 5.0 to MySQL 5.1. + + In MySQL 5.1.32 and later, the EXE version of the MSI installer + packages were removed. When upgrading an existing MySQL + installation from the old EXE based installer to the MSI based + installer, please keep the following notes in mind: + + * The MSI installer will not identify an existing installation + that was installed using the old EXE installer. This means + that the installer will not stop the existing server, or + detect that the existing password is required before + installing the new version. To work around this: + + 1. Stop the current server manually using net stop or + mysqladmin shutdown. + + 2. Remove the existing installation manually by using the + Add/Remove Programs control panel. This will keep the + existing configuration and data files, as these are not + removed automatically. + + 3. Install the new version of MySQL using the MSI installer. + When running the installation, skip updating the security + by deselecting the checkbox on the security screen. + + 4. Complete the installation, and then start the server + again. You should be able to login with your existing + user and password credentials. + + * You can only upgrade the version and release using the MSI + installer. For example, you can upgrade an open source + installation with an open source installer. You cannot upgrade + an open source installation using the enterprise installer. + + See Section 2.5.7, "Upgrading MySQL on Windows." + +2.5.3.2. Installing MySQL Automatically using MSI + + The Microsoft Installer (MSI) supports a both a quiet and a + passive mode that can be used to install MySQL automatically + without requireing intervention. You can use this either in + scripts to automatically install MySQL or through a terminal + connection such as Telnet where you do not have access to the + standard Windows user interface. The MSI packages can also be used + in combination with Microsoft's Group Policy system (part of + Windows Server 2003 and Windows Server 2008) to install MySQL + across multiple machines. + + To install MySQL from one of the MSI packages automatically from + the command line (or within a script), you need to use the + msiexec.exe tool. For example, to perform a quiet installation + (which shows no dialog boxes or progress): +shell> msiexec /i /quiet mysql-5.1.39.msi + + The /i indicates that you want to perform an installation. The + /quiet option indicates that you want no interactive elements. + + To provide a dialog box showing the progress during installation, + and the dialog boxes providing information on the installation and + registration of MySQL, use /passive mode instead of /quiet: +shell> msiexec /i /passive mysql-5.1.39.msi + + Regardless of the mode of the installation, installing the package + in this manner performs a 'Typical' installation, and installs the + default components into the standard location. + + You can also use this method to uninstall MySQL by using the + /uninstall or /x options: +shell> msiexec /x /quiet mysql-5.1.39.msi + + To install MySQL and configure a MySQL instance from the command + line, see Section 2.5.4.13, "Creating an Instance from the Command + Line." + + For information on using MSI packages to install software + automatically using Group Policy, see How to use Group Policy to + remotely install software in Windows Server 2003 + (http://support.microsoft.com/kb/816102). + +2.5.3.3. Removing MySQL Installed from the MSI Package + + To uninstall a MySQL where you have used the MSI packages, you + must use the Add/Remove Programs tool within Control Panel. To do + this: + + 1. Right click on the start menu and choose Control Panel. + + 2. If the Control Panel is set to category mode (you will see + Pick a category at the top of the Control Panel window), + double click on Add or Remove Programs. If the Control is set + to classic mode, doubgle click on the Add or Remove Programs + icon. + + 3. Find MySQL in the list of installed software. MySQL Server is + installed against major version numbers (MySQL 5.0, MySQL 5.1, + etc.). Select the version that you want to remove and click + Remove. + + 4. You will be prompted to confirm the removal. Click Yes to + remove MySQL. + + When MySQL is removed using this method, only the installed + components are removed. Any database information (including the + tables and data), import or export files, log files, and binary + logs produced during execution are kept in their configured + location. + +2.5.4. MySQL Server Instance Config Wizard + + The MySQL Server Instance Config Wizard helps automate the process + of configuring your server. It creates a custom MySQL + configuration file (my.ini or my.cnf) by asking you a series of + questions and then applying your responses to a template to + generate the configuration file that is tuned to your + installation. + + The complete and essential MSI installation packages include the + MySQL Server Instance Config Wizard in the MySQL 5.1 server. The + MySQL Server Instance Config Wizard is only available for Windows. + + The workflow sequence for using the MySQL Server Instance Config + Wizard is shown in the figure below: + + Figure 2.4. MySQL Server Instance Config Wizard Workflow + MySQL Server Instance Config Wizard Workflow + +2.5.4.1. Starting the MySQL Server Instance Config Wizard + + The MySQL Server Instance Config Wizard is normally started as + part of the installation process. You should only need to run the + MySQL Server Instance Config Wizard again when you need to change + the configuration parameters of your server. + + If you chose not to open a port prior to installing MySQL on + Windows Vista, you can choose to use the MySQL Server Instance + Config Wizard after installation. However, you must open a port in + the Windows Firewall. To do this see the instructions given in + Section 2.5.3.1.1, "Downloading and Starting the MySQL + Installation Wizard." Rather than opening a port, you also have + the option of adding MySQL as a program that bypasses the Windows + Firewall. One or the other option is sufficient --- you need not + do both. Additionally, when running the MySQL Server Config Wizard + on Windows Vista ensure that you are logged in as a user with + administrative rights. + MySQL Server Instance Config Wizard + + You can launch the MySQL Config Wizard by clicking the MySQL + Server Instance Config Wizard entry in the MySQL section of the + Windows Start menu. + + Alternatively, you can navigate to the bin directory of your MySQL + installation and launch the MySQLInstanceConfig.exe file directly. + + The MySQL Server Instance Config Wizard places the my.ini file in + the installation directory for the MySQL server. This helps + associate configuration files with particular server instances. + + To ensure that the MySQL server knows where to look for the my.ini + file, an argument similar to this is passed to the MySQL server as + part of the service installation: +--defaults-file="C:\Program Files\MySQL\MySQL Server 5.1\my.ini" + + Here, C:\Program Files\MySQL\MySQL Server 5.1 is replaced with the + installation path to the MySQL Server. The --defaults-file option + instructs the MySQL server to read the specified file for + configuration options when it starts. + + Apart from making changes to the my.ini file by running the MySQL + Server Instance Config Wizard again, you can modify it by opening + it with a text editor and making any necessary changes. You can + also modify the server configuration with the MySQL Administrator + (http://www.mysql.com/products/administrator/) utility. For more + information about server configuration, see Section 5.1.2, "Server + Command Options." + + MySQL clients and utilities such as the mysql and mysqldump + command-line clients are not able to locate the my.ini file + located in the server installation directory. To configure the + client and utility applications, create a new my.ini file in the + Windows installation directory (for example, C:\WINDOWS). + + Under Windows Server 2003, Windows Server 2000, Windows XP, and + Windows Vista MySQL Server Instance Config Wizard will configure + MySQL to work as a Windows service. To start and stop MySQL you + use the Services application that is supplied as part of the + Windows Administrator Tools. + +2.5.4.2. Choosing a Maintenance Option + + If the MySQL Server Instance Config Wizard detects an existing + configuration file, you have the option of either reconfiguring + your existing server, or removing the server instance by deleting + the configuration file and stopping and removing the MySQL + service. + + To reconfigure an existing server, choose the Re-configure + Instance option and click the Next button. Any existing + configuration file is not overwritten, but renamed (within the + same directory) using a timestamp (Windows) or sequential number + (Linux). To remove the existing server instance, choose the Remove + Instance option and click the Next button. + + If you choose the Remove Instance option, you advance to a + confirmation window. Click the Execute button. The MySQL Server + Config Wizard stops and removes the MySQL service, and then + deletes the configuration file. The server installation and its + data folder are not removed. -2.13.1. Linux Notes + If you choose the Re-configure Instance option, you advance to the + Configuration Type dialog where you can choose the type of + installation that you wish to configure. - This section discusses issues that have been found to occur on - Linux. The first few subsections describe general operating - system-related issues, problems that can occur when using binary - or source distributions, and post-installation issues. The - remaining subsections discuss problems that occur with Linux on - specific platforms. +2.5.4.3. Choosing a Configuration Type - Note that most of these problems occur on older versions of Linux. - If you are running a recent version, you may see none of them. + When you start the MySQL Server Instance Config Wizard for a new + MySQL installation, or choose the Re-configure Instance option for + an existing installation, you advance to the Configuration Type + dialog. + MySQL Server Instance Config Wizard: Configuration Type -2.13.1.1. Linux Operating System Notes + There are two configuration types available: Detailed + Configuration and Standard Configuration. The Standard + Configuration option is intended for new users who want to get + started with MySQL quickly without having to make many decisions + about server configuration. The Detailed Configuration option is + intended for advanced users who want more fine-grained control + over server configuration. + + If you are new to MySQL and need a server configured as a + single-user developer machine, the Standard Configuration should + suit your needs. Choosing the Standard Configuration option causes + the MySQL Config Wizard to set all configuration options + automatically with the exception of Service Options and Security + Options. + + The Standard Configuration sets options that may be incompatible + with systems where there are existing MySQL installations. If you + have an existing MySQL installation on your system in addition to + the installation you wish to configure, the Detailed Configuration + option is recommended. + + To complete the Standard Configuration, please refer to the + sections on Service Options and Security Options in Section + 2.5.4.10, "The Service Options Dialog," and Section 2.5.4.11, "The + Security Options Dialog," respectively. + +2.5.4.4. The Server Type Dialog + + There are three different server types available to choose from. + The server type that you choose affects the decisions that the + MySQL Server Instance Config Wizard makes with regard to memory, + disk, and processor usage. + MySQL Server Instance Config Wizard: Server Type + + * Developer Machine: Choose this option for a typical desktop + workstation where MySQL is intended only for personal use. It + is assumed that many other desktop applications are running. + The MySQL server is configured to use minimal system + resources. + + * Server Machine: Choose this option for a server machine where + the MySQL server is running alongside other server + applications such as FTP, email, and Web servers. The MySQL + server is configured to use a moderate portion of the system + resources. + + * Dedicated MySQL Server Machine: Choose this option for a + server machine that is intended to run only the MySQL server. + It is assumed that no other applications are running. The + MySQL server is configured to use all available system + resources. + +Note + + By selecting one of the preconfigured configurations, the values + and settings of various options in your my.cnf or my.ini will be + altered accordingly. The default values and options as described + in the reference manual may therefore be different to the options + and values that were created during the execution of the Config + Wizard. + +2.5.4.5. The Database Usage Dialog + + The Database Usage dialog allows you to indicate the storage + engines that you expect to use when creating MySQL tables. The + option you choose determines whether the InnoDB storage engine is + available and what percentage of the server resources are + available to InnoDB. + MySQL Server Instance Config Wizard: Usage Dialog + + * Multifunctional Database: This option enables both the InnoDB + and MyISAM storage engines and divides resources evenly + between the two. This option is recommended for users who use + both storage engines on a regular basis. + + * Transactional Database Only: This option enables both the + InnoDB and MyISAM storage engines, but dedicates most server + resources to the InnoDB storage engine. This option is + recommended for users who use InnoDB almost exclusively and + make only minimal use of MyISAM. + + * Non-Transactional Database Only: This option disables the + InnoDB storage engine completely and dedicates all server + resources to the MyISAM storage engine. This option is + recommended for users who do not use InnoDB. + + The Config Wizard uses a template to generate the server + configuration file. The Database Usage dialog sets one of the + following option strings: +Multifunctional Database: MIXED +Transactional Database Only: INNODB +Non-Transactional Database Only: MYISAM + + When these options are processed through the default template + (my-template.ini) the result is: +Multifunctional Database: +default-storage-engine=InnoDB +_myisam_pct=50 + +Transactional Database Only: +default-storage-engine=InnoDB +_myisam_pct=5 + +Non-Transactional Database Only: +default-storage-engine=MyISAM +_myisam_pct=100 +skip-innodb + + The _myisam_pct value is used to calculate the percentage of + resources dedicated to MyISAM. The remaining resources are + allocated to InnoDB. + +2.5.4.6. The InnoDB Tablespace Dialog + + Some users may want to locate the InnoDB tablespace files in a + different location than the MySQL server data directory. Placing + the tablespace files in a separate location can be desirable if + your system has a higher capacity or higher performance storage + device available, such as a RAID storage system. + MySQL Server Instance Config Wizard: InnoDB Data Tablespace + + To change the default location for the InnoDB tablespace files, + choose a new drive from the drop-down list of drive letters and + choose a new path from the drop-down list of paths. To create a + custom path, click the ... button. + + If you are modifying the configuration of an existing server, you + must click the Modify button before you change the path. In this + situation you must move the existing tablespace files to the new + location manually before starting the server. + +2.5.4.7. The Concurrent Connections Dialog + + To prevent the server from running out of resources, it is + important to limit the number of concurrent connections to the + MySQL server that can be established. The Concurrent Connections + dialog allows you to choose the expected usage of your server, and + sets the limit for concurrent connections accordingly. It is also + possible to set the concurrent connection limit manually. + MySQL Server Instance Config Wizard: Connections + + * Decision Support (DSS)/OLAP: Choose this option if your server + does not require a large number of concurrent connections. The + maximum number of connections is set at 100, with an average + of 20 concurrent connections assumed. + + * Online Transaction Processing (OLTP): Choose this option if + your server requires a large number of concurrent connections. + The maximum number of connections is set at 500. + + * Manual Setting: Choose this option to set the maximum number + of concurrent connections to the server manually. Choose the + number of concurrent connections from the drop-down box + provided, or enter the maximum number of connections into the + drop-down box if the number you desire is not listed. + +2.5.4.8. The Networking and Strict Mode Options Dialog + + Use the Networking Options dialog to enable or disable TCP/IP + networking and to configure the port number that is used to + connect to the MySQL server. + MySQL Server Instance Config Wizard: Network Configuration + + TCP/IP networking is enabled by default. To disable TCP/IP + networking, uncheck the box next to the Enable TCP/IP Networking + option. + + Port 3306 is used by default. To change the port used to access + MySQL, choose a new port number from the drop-down box or type a + new port number directly into the drop-down box. If the port + number you choose is in use, you are prompted to confirm your + choice of port number. + + Set the Server SQL Mode to either enable or disable strict mode. + Enabling strict mode (default) makes MySQL behave more like other + database management systems. If you run applications that rely on + MySQL's old "forgiving" behavior, make sure to either adapt those + applications or to disable strict mode. For more information about + strict mode, see Section 5.1.8, "Server SQL Modes." - MySQL needs at least Linux version 2.0. +2.5.4.9. The Character Set Dialog + + The MySQL server supports multiple character sets and it is + possible to set a default server character set that is applied to + all tables, columns, and databases unless overridden. Use the + Character Set dialog to change the default character set of the + MySQL server. + MySQL Server Instance Config Wizard: Character Set + + * Standard Character Set: Choose this option if you want to use + latin1 as the default server character set. latin1 is used for + English and many Western European languages. + + * Best Support For Multilingualism: Choose this option if you + want to use utf8 as the default server character set. This is + a Unicode character set that can store characters from many + different languages. + + * Manual Selected Default Character Set / Collation: Choose this + option if you want to pick the server's default character set + manually. Choose the desired character set from the provided + drop-down list. + +2.5.4.10. The Service Options Dialog + + On Windows platforms, the MySQL server can be installed as a + Windows service. When installed this way, the MySQL server can be + started automatically during system startup, and even restarted + automatically by Windows in the event of a service failure. + + The MySQL Server Instance Config Wizard installs the MySQL server + as a service by default, using the service name MySQL. If you do + not wish to install the service, uncheck the box next to the + Install As Windows Service option. You can change the service name + by picking a new service name from the drop-down box provided or + by entering a new service name into the drop-down box. + +Note + + Service names can include any legal character except forward (/) + or backward (\) slashes, and must be less than 256 characters + long. Warning - We have seen some strange problems with Linux 2.2.14 and MySQL on - SMP systems. We also have reports from some MySQL users that they - have encountered serious stability problems using MySQL with - kernel 2.2.14. If you are using this kernel, you should upgrade to - 2.2.19 (or newer) or to a 2.4 kernel. If you have a multiple-CPU - box, you should seriously consider using 2.4 because it gives you - a significant speed boost. Your system should be more stable. - - When using LinuxThreads, you should see a minimum of three mysqld - processes running. These are in fact threads. There is one thread - for the LinuxThreads manager, one thread to handle connections, - and one thread to handle alarms and signals. - -2.13.1.2. Linux Binary Distribution Notes - - The Linux-Intel binary and RPM releases of MySQL are configured - for the highest possible speed. We are always trying to use the - fastest stable compiler available. - - The binary release is linked with -static, which means you do not - normally need to worry about which version of the system libraries - you have. You need not install LinuxThreads, either. A program - linked with -static is slightly larger than a dynamically linked - program, but also slightly faster (3-5%). However, one problem - with a statically linked program is that you can't use - user-defined functions (UDFs). If you are going to write or use - UDFs (this is something for C or C++ programmers only), you must - compile MySQL yourself using dynamic linking. - - A known issue with binary distributions is that on older Linux - systems that use libc (such as Red Hat 4.x or Slackware), you get - some (nonfatal) issues with host name resolution. If your system - uses libc rather than glibc2, you probably will encounter some - difficulties with host name resolution and getpwnam(). This - happens because glibc (unfortunately) depends on some external - libraries to implement host name resolution and getpwent(), even - when compiled with -static. These problems manifest themselves in - two ways: - - * You may see the following error message when you run - mysql_install_db: -Sorry, the host 'xxxx' could not be looked up - You can deal with this by executing mysql_install_db --force, - which does not execute the resolveip test in mysql_install_db. - The downside is that you cannot use host names in the grant - tables: except for localhost, you must use IP numbers instead. - If you are using an old version of MySQL that does not support - --force, you must manually remove the resolveip test in - mysql_install_db using a text editor. - - * You also may see the following error when you try to run - mysqld with the --user option: -getpwnam: No such file or directory - To work around this problem, start mysqld by using the su - command rather than by specifying the --user option. This - causes the system itself to change the user ID of the mysqld - process so that mysqld need not do so. - - Another solution, which solves both problems, is not to use a - binary distribution. Obtain a MySQL source distribution (in RPM or - tar.gz format) and install that instead. - - On some Linux 2.2 versions, you may get the error Resource - temporarily unavailable when clients make a great many new - connections to a mysqld server over TCP/IP. The problem is that - Linux has a delay between the time that you close a TCP/IP socket - and the time that the system actually frees it. There is room for - only a finite number of TCP/IP slots, so you encounter the - resource-unavailable error if clients attempt too many new TCP/IP - connections over a short period of time. For example, you may see - the error when you run the MySQL test-connect benchmark over - TCP/IP. - - We have inquired about this problem a few times on different Linux - mailing lists but have never been able to find a suitable - resolution. The only known "fix" is for clients to use persistent - connections, or, if you are running the database server and - clients on the same machine, to use Unix socket file connections - rather than TCP/IP connections. - -2.13.1.3. Linux Source Distribution Notes - - The following notes regarding glibc apply only to the situation - when you build MySQL yourself. If you are running Linux on an x86 - machine, in most cases it is much better for you to use our - binary. We link our binaries against the best patched version of - glibc we can find and with the best compiler options, in an - attempt to make it suitable for a high-load server. For a typical - user, even for setups with a lot of concurrent connections or - tables exceeding the 2GB limit, our binary is the best choice in - most cases. After reading the following text, if you are in doubt - about what to do, try our binary first to determine whether it - meets your needs. If you discover that it is not good enough, you - may want to try your own build. In that case, we would appreciate - a note about it so that we can build a better binary next time. - - MySQL uses LinuxThreads on Linux. If you are using an old Linux - version that doesn't have glibc2, you must install LinuxThreads - before trying to compile MySQL. You can obtain LinuxThreads from - http://dev.mysql.com/downloads/os-linux.html. - - Note that glibc versions before and including version 2.1.1 have a - fatal bug in pthread_mutex_timedwait() handling, which is used - when INSERT DELAYED statements are issued. Do not use INSERT - DELAYED before upgrading glibc. - - Note that Linux kernel and the LinuxThread library can by default - handle a maximum of 1,024 threads. If you plan to have more than - 1,000 concurrent connections, you need to make some changes to - LinuxThreads, as follows: - - * Increase PTHREAD_THREADS_MAX in - sysdeps/unix/sysv/linux/bits/local_lim.h to 4096 and decrease - STACK_SIZE in linuxthreads/internals.h to 256KB. The paths are - relative to the root of glibc. (Note that MySQL is not stable - with 600-1000 connections if STACK_SIZE is the default of - 2MB.) - - * Recompile LinuxThreads to produce a new libpthread.a library, - and relink MySQL against it. - - There is another issue that greatly hurts MySQL performance, - especially on SMP systems. The mutex implementation in - LinuxThreads in glibc 2.1 is very poor for programs with many - threads that hold the mutex only for a short time. This produces a - paradoxical result: If you link MySQL against an unmodified - LinuxThreads, removing processors from an SMP actually improves - MySQL performance in many cases. We have made a patch available - for glibc 2.1.3 to correct this behavior - (http://dev.mysql.com/Downloads/Linux/linuxthreads-2.1-patch). - - With glibc 2.2.2, MySQL uses the adaptive mutex, which is much - better than even the patched one in glibc 2.1.3. Be warned, - however, that under some conditions, the current mutex code in - glibc 2.2.2 overspins, which hurts MySQL performance. The - likelihood that this condition occurs can be reduced by re-nicing - the mysqld process to the highest priority. We have also been able - to correct the overspin behavior with a patch, available at - http://dev.mysql.com/Downloads/Linux/linuxthreads-2.2.2.patch. It - combines the correction of overspin, maximum number of threads, - and stack spacing all in one. You need to apply it in the - linuxthreads directory with patch -p0 - </tmp/linuxthreads-2.2.2.patch. We hope it is included in some - form in future releases of glibc 2.2. In any case, if you link - against glibc 2.2.2, you still need to correct STACK_SIZE and - PTHREAD_THREADS_MAX. We hope that the defaults is corrected to - some more acceptable values for high-load MySQL setup in the - future, so that the commands needed to produce your own build can - be reduced to ./configure; make; make install. - - If you use these patches to build a special static version of - libpthread.a, use it only for statically linking against MySQL. We - know that these patches are safe for MySQL and significantly - improve its performance, but we cannot say anything about their - effects on other applications. If you link other applications that - require LinuxThreads against the patched static version of the - library, or build a patched shared version and install it on your - system, you do so at your own risk. - - If you experience any strange problems during the installation of - MySQL, or with some common utilities hanging, it is very likely - that they are either library or compiler related. If this is the - case, using our binary resolves them. + If you are installing multiple versions of MySQL onto the same + machine, you must choose a different service name for each version + that you install. If you do not choose a different service for + each installed version then the service manager information will + be inconsistent and this will cause problems when you try to + uninstall a previous version. - If you link your own MySQL client programs, you may see the - following error at runtime: -ld.so.1: fatal: libmysqlclient.so.#: -open failed: No such file or directory + If you have already installed multiple versions using the same + service name, you must manually edit the contents of the + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services parameters + within the Windows registry to update the association of the + service name with the correct server version. - This problem can be avoided by one of the following methods: + Typically, when installing multiple versions you create a service + name based on the version information. For example, you might + install MySQL 5.x as mysql5, or specific versions such as MySQL + 5.1.30 as mysql50130. - * Link clients with the -Wl,r/full/path/to/libmysqlclient.so - flag rather than with -Lpath). + To install the MySQL server as a service but not have it started + automatically at startup, uncheck the box next to the Launch the + MySQL Server Automatically option. - * Copy libmysqclient.so to /usr/lib. +2.5.4.11. The Security Options Dialog - * Add the path name of the directory where libmysqlclient.so is - located to the LD_RUN_PATH environment variable before running - your client. + It is strongly recommended that you set a root password for your + MySQL server, and the MySQL Server Instance Config Wizard requires + by default that you do so. If you do not wish to set a root + password, uncheck the box next to the Modify Security Settings + option. + MySQL Server Instance Config Wizard: Security - If you are using the Fujitsu compiler (fcc/FCC), you may have some - problems compiling MySQL because the Linux header files are very - gcc oriented. The following configure line should work with - fcc/FCC: -CC=fcc CFLAGS="-O -K fast -K lib -K omitfp -Kpreex -D_GNU_SOURCE \ - -DCONST=const -DNO_STRTOLL_PROTO" \ -CXX=FCC CXXFLAGS="-O -K fast -K lib \ - -K omitfp -K preex --no_exceptions --no_rtti -D_GNU_SOURCE \ - -DCONST=const -Dalloca=__builtin_alloca -DNO_STRTOLL_PROTO \ - '-D_EXTERN_INLINE=static __inline'" \ -./configure \ - --prefix=/usr/local/mysql --enable-assembler \ - --with-mysqld-ldflags=-all-static --disable-shared \ - --with-low-memory + To set the root password, enter the desired password into both the + New root password and Confirm boxes. If you are reconfiguring an + existing server, you need to enter the existing root password into + the Current root password box. + + To allow root logins from across the network, check the box next + to the Enable root access from remote machines option. This + decreases the security of your root account. + + To create an anonymous user account, check the box next to the + Create An Anonymous Account option. Creating an anonymous account + can decrease server security and cause login and permission + difficulties. For this reason, it is not recommended. + +2.5.4.12. The Confirmation Dialog + + The final dialog in the MySQL Server Instance Config Wizard is the + Confirmation Dialog. To start the configuration process, click the + Execute button. To return to a previous dialog, click the Back + button. To exit the MySQL Server Instance Config Wizard without + configuring the server, click the Cancel button. + MySQL Server Instance Config Wizard: Confirmation + + After you click the Execute button, the MySQL Server Instance + Config Wizard performs a series of tasks and displays the progress + onscreen as the tasks are performed. + + The MySQL Server Instance Config Wizard first determines + configuration file options based on your choices using a template + prepared by MySQL developers and engineers. This template is named + my-template.ini and is located in your server installation + directory. + + The MySQL Config Wizard then writes these options to the + corresponding configuration file. + + If you chose to create a service for the MySQL server, the MySQL + Server Instance Config Wizard creates and starts the service. If + you are reconfiguring an existing service, the MySQL Server + Instance Config Wizard restarts the service to apply your + configuration changes. + + If you chose to set a root password, the MySQL Config Wizard + connects to the server, sets your new root password, and applies + any other security settings you may have selected. + + After the MySQL Server Instance Config Wizard has completed its + tasks, it displays a summary. Click the Finish button to exit the + MySQL Server Config Wizard. + +2.5.4.13. Creating an Instance from the Command Line + + In addition to using the GUI interface to the MySQL Server + Instance Config Wizard, you can also create instances + automatically from the command line. + + To use the MySQL Server Instance Config Wizard on the command + line, you need to use the MySQLInstanceConfig.exe command that is + installed with MySQL in the bin directory within the installation + directory. MySQLInstanceConfig.exe takes a number of command-line + arguments the set the properties that would normally be selected + through the GUI interface, and then creates a new configuration + file (my.ini) by combining these selections with a template + configuration file to produce the working configuration file. + + The main command line options are provided in the table below. + Some of the options are required, while some options are optional. + + Table 2.4. MySQL Server Instance Config Wizard Command Line + Options + Option Description + Required Parameters + -nPRODUCTNAME The name of the instance when installed + -pPATH Path of the base directory for installation. This is + equivalent to the directory when using the basedir configuration + parameter + -vVERSION The version tag to use for this installation + Action to Perform + -i Install an instance + -r Remove an instance + -s Stop an existing instance + -q Perform the operation quietly + -lFILENAME Sae the installation progress in a logfile + Config File to Use + -tFILENAME Path to the template config file that will be used to + generate the installed configuration file + -cFILENAME Path to a config file to be generated + + The -t and -c options work together to set the configuration + parameters for a new instance. The -t option specifies the + template configuration file to use as the basic configuration, + which are then merged with the configuration parameters generated + by the MySQL Server Instance Config Wizard into the configuration + file specified by the -c option. + + A sample template file, my-template.ini is provided in the + toplevel MySQL installation directory. The file contains elements + are replaced automatically by the MySQL Server Instance Config + Wizard during configuration. + + If you specify a configuration file that already exists, the + existing configuration file will be saved in the file with the + original, with the date and time added. For example, the mysql.ini + will be copied to mysql 2009-10-27 1646.ini.bak. + + The parameters that you can specify on the command line are listed + in the table below. + + Table 2.5. MySQL Server Instance Config Wizard Parameters + Parameter Description + ServiceName=$ Specify the name of the service to be created + AddBinToPath={yes | no} Specifies whether to add the binary + directory of MySQL to the standard PATH environment variable + ServerType={DEVELOPMENT | SERVER | DEDICATED} Specify the server + type. For more information, see Section 2.5.4.4, "The Server Type + Dialog" + DatabaseType={MIXED | INNODB | MYISAM} Specify the default + database type. For more information, see Section 2.5.4.5, "The + Database Usage Dialog" + ConnectionUsage={DSS | OLTP} Specify the type of connection + support, this automates the setting for the number of concurrent + connections (see the ConnectionCount parameter). For more + information, see Section 2.5.4.7, "The Concurrent Connections + Dialog" + ConnectionCount=# Specify the number of concurrent connections to + support. For more information, see Section 2.5.4.4, "The Server + Type Dialog" + SkipNetworking={yes | no} Specify whether network support should + be supported. Specifying yes disables network access altogether + Port=# Specify the network port number to use for network + connections. For more information, see Section 2.5.4.8, "The + Networking and Strict Mode Options Dialog" + StrictMode={yes | no} Specify whether to use the strict SQL mode. + For more information, see Section 2.5.4.8, "The Networking and + Strict Mode Options Dialog" + Charset=$ Specify the default character set. For more information, + see Section 2.5.4.9, "The Character Set Dialog" + RootPassword=$ Specify the root password + RootCurrentPassword=$ Specify the current root password then + stopping and/or reconfiguring an existing service + +Note + + When specifying options on the command line, you can enclose the + entire command-line option and the value you are specifying using + double quotes. This enables you to use spaces in the options. For + example, "-cC:\mysql.ini". + + The following command installs a MySQL Server 5.1 instance from + the directory C:\Program Files\MySQL\MySQL Server 5.1 using the + service name MySQL51 and setting the root password to 1234. +shell> MySQLInstanceConfig.exe -i -q "-lC:\mysql_install_log.txt" » + "-nMySQL Server 5.1" "-pC:\Program Files\MySQL\MySQL Server 5.1" - +v5.1.39 » + "-tmy-template.ini" "-cC:\mytest.ini" ServerType=DEVELOPMENT Datab +aseType=MIXED » + ConnectionUsage=DSS Port=3311 ServiceName=MySQL51 RootPassword=123 +4 + + In the above example, a log file will be generated in + mysql_install_log.txt containing the information about the + instance creation process. The log file generated by the above + example is shown below: +Welcome to the MySQL Server Instance Configuration Wizard 1.0.16.0 +Date: 2009-10-27 17:07:21 + +Installing service ... + +Product Name: MySQL Server 5.1 +Version: 5.1.39 +Installation Path: C:\Program Files\MySQL\MySQL Server 5.1\ + +Creating configuration file C:\mytest.ini using template my-template. +ini. +Options: +DEVELOPMENT +MIXED +DSS +STRICTMODE + +Variables: +port: 3311 +default-character-set: latin1 +basedir: "C:/Program Files/MySQL/MySQL Server 5.1/" +datadir: "C:/Program Files/MySQL/MySQL Server 5.1/Data/" + + +Creating Windows service entry. +Service name: "MySQL51" +Parameters: "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld" -- +defaults-file="C:\mytest.ini" MySQL51. +Windows service MySQL51 installed. + + When using the command-line, the return values in the following + table indicate an error performing the specified option. + + Table 2.6. Return Value from MySQL Server Instance Config Wizard + Value Description + 2 Configuration template file cannot be found + 3 The Windows service entry cannot be created + 4 Could not connect to the Service Control Manager + 5 The MySQL service cannot be started + 6 The MySQL service cannot be stopped + 7 The security settings cannot be applied + 8 The configuration file cannot be written + 9 The Windows service entry cannot be removed + + You can perform an installation of MySQL automatically using the + MSI packe. For more information, see Section 2.5.3.2, "Installing + MySQL Automatically using MSI." + +2.5.5. Installing MySQL from a noinstall Zip Archive + + Users who are installing from the noinstall package can use the + instructions in this section to manually install MySQL. The + process for installing MySQL from a Zip archive is as follows: + + 1. Extract the archive to the desired install directory + + 2. Create an option file + + 3. Choose a MySQL server type + + 4. Start the MySQL server + + 5. Secure the default user accounts + + This process is described in the sections that follow. + +2.5.5.1. Extracting the Install Archive + + To install MySQL manually, do the following: + + 1. If you are upgrading from a previous version please refer to + Section 2.5.7, "Upgrading MySQL on Windows," before beginning + the upgrade process. + + 2. Make sure that you are logged in as a user with administrator + privileges. + + 3. Choose an installation location. Traditionally, the MySQL + server is installed in C:\mysql. The MySQL Installation Wizard + installs MySQL under C:\Program Files\MySQL. If you do not + install MySQL at C:\mysql, you must specify the path to the + install directory during startup or in an option file. See + Section 2.5.5.2, "Creating an Option File." + + 4. Extract the install archive to the chosen installation + location using your preferred Zip archive tool. Some tools may + extract the archive to a folder within your chosen + installation location. If this occurs, you can move the + contents of the subfolder into the chosen installation + location. + +2.5.5.2. Creating an Option File + + If you need to specify startup options when you run the server, + you can indicate them on the command line or place them in an + option file. For options that are used every time the server + starts, you may find it most convenient to use an option file to + specify your MySQL configuration. This is particularly true under + the following circumstances: + + * The installation or data directory locations are different + from the default locations (C:\Program Files\MySQL\MySQL + Server 5.1 and C:\Program Files\MySQL\MySQL Server 5.1\data). + + * You need to tune the server settings, such as memory, cache, + or InnoDB configuration information. + + When the MySQL server starts on Windows, it looks for option files + in several locations, such as the Windows directory, C:\, and the + MySQL installation directory (for the full list of locations, see + Section 4.2.3.3, "Using Option Files"). The Windows directory + typically is named something like C:\WINDOWS. You can determine + its exact location from the value of the WINDIR environment + variable using the following command: +C:\> echo %WINDIR% + + MySQL looks for options in each location first in the my.ini file, + and then in the my.cnf file. However, to avoid confusion, it is + best if you use only one file. If your PC uses a boot loader where + C: is not the boot drive, your only option is to use the my.ini + file. Whichever option file you use, it must be a plain text file. + + You can also make use of the example option files included with + your MySQL distribution; see Section 4.2.3.3.2, "Preconfigured + Option Files." + + An option file can be created and modified with any text editor, + such as Notepad. For example, if MySQL is installed in E:\mysql + and the data directory is in E:\mydata\data, you can create an + option file containing a [mysqld] section to specify values for + the basedir and datadir options: +[mysqld] +# set basedir to your installation path +basedir=E:/mysql +# set datadir to the location of your data directory +datadir=E:/mydata/data + + Note that Windows path names are specified in option files using + (forward) slashes rather than backslashes. If you do use + backslashes, double them: +[mysqld] +# set basedir to your installation path +basedir=E:\\mysql +# set datadir to the location of your data directory +datadir=E:\\mydata\\data + + The rules for use of backslash in option file values are given in + Section 4.2.3.3, "Using Option Files." + + MySQL Enterprise For expert advice on the start-up options + appropriate to your circumstances, subscribe to the MySQL + Enterprise Monitor. For more information, see + http://www.mysql.com/products/enterprise/advisors.html. + + In MySQL 5.1.23 and earlier, the MySQL installer places the data + directory directly under the directory where you install MySQL. On + MySQL 5.1.24 and later, the data directory is located within the + AppData directory for the user running MySQL. + + If you would like to use a data directory in a different location, + you should copy the entire contents of the data directory to the + new location. For example, if you want to use E:\mydata as the + data directory instead, you must do two things: + + 1. Move the entire data directory and all of its contents from + the default location (for example C:\Program Files\MySQL\MySQL + Server 5.1\data) to E:\mydata. + + 2. Use a --datadir option to specify the new data directory + location each time you start the server. + +2.5.5.3. Selecting a MySQL Server Type + + The following table shows the available servers for Windows in + MySQL 5.1.20 and earlier. + Binary Description + mysqld-nt Optimized binary with named-pipe support + mysqld Optimized binary without named-pipe support + mysqld-debug Like mysqld-nt, but compiled with full debugging and + automatic memory allocation checking + + The following table shows the available servers for Windows in + MySQL 5.1.21 and later. + Binary Description + mysqld Optimized binary with named-pipe support + mysqld-debug Like mysqld, but compiled with full debugging and + automatic memory allocation checking + + All of the preceding binaries are optimized for modern Intel + processors, but should work on any Intel i386-class or higher + processor. + + Each of the servers in a distribution support the same set of + storage engines. The SHOW ENGINES statement displays which engines + a given server supports. + + All Windows MySQL 5.1 servers have support for symbolic linking of + database directories. + + MySQL supports TCP/IP on all Windows platforms. MySQL servers on + Windows support named pipes as indicated in the following list. + However, the default is to use TCP/IP regardless of platform. + (Named pipes are slower than TCP/IP in many Windows + configurations.) + + Use of named pipes is subject to these conditions: + + * Named pipes are enabled only if you start the server with the + --enable-named-pipe option. It is necessary to use this option + explicitly because some users have experienced problems with + shutting down the MySQL server when named pipes were used. + + * For MySQL 5.1.20 and earlier, named-pipe connections are + allowed only by the mysqld-nt and mysqld-debug servers. For + MySQL 5.1.21 and later, the mysqld and mysqld-debug servers + both contain support for named-pipe connections. + +Note + + Most of the examples in this manual use mysqld as the server name. + If you choose to use a different server, such as mysqld-nt or + mysqld-debug, make the appropriate substitutions in the commands + that are shown in the examples. + +2.5.5.4. Starting the Server for the First Time + + This section gives a general overview of starting the MySQL + server. The following sections provide more specific information + for starting the MySQL server from the command line or as a + Windows service. + + The information here applies primarily if you installed MySQL + using the Noinstall version, or if you wish to configure and test + MySQL manually rather than with the GUI tools. + + The examples in these sections assume that MySQL is installed + under the default location of C:\Program Files\MySQL\MySQL Server + 5.1. Adjust the path names shown in the examples if you have MySQL + installed in a different location. + + Clients have two options. They can use TCP/IP, or they can use a + named pipe if the server supports named-pipe connections. + + MySQL for Windows also supports shared-memory connections if the + server is started with the --shared-memory option. Clients can + connect through shared memory by using the --protocol=MEMORY + option. + + For information about which server binary to run, see Section + 2.5.5.3, "Selecting a MySQL Server Type." + + Testing is best done from a command prompt in a console window (or + "DOS window"). In this way you can have the server display status + messages in the window where they are easy to see. If something is + wrong with your configuration, these messages make it easier for + you to identify and fix any problems. + + To start the server, enter this command: +C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld" --console + + For a server that includes InnoDB support, you should see the + messages similar to those following as it starts (the path names + and sizes may differ): +InnoDB: The first specified datafile c:\ibdata\ibdata1 did not exist: +InnoDB: a new database to be created! +InnoDB: Setting file c:\ibdata\ibdata1 size to 209715200 +InnoDB: Database physically writes the file full: wait... +InnoDB: Log file c:\iblogs\ib_logfile0 did not exist: new to be creat +ed +InnoDB: Setting log file c:\iblogs\ib_logfile0 size to 31457280 +InnoDB: Log file c:\iblogs\ib_logfile1 did not exist: new to be creat +ed +InnoDB: Setting log file c:\iblogs\ib_logfile1 size to 31457280 +InnoDB: Log file c:\iblogs\ib_logfile2 did not exist: new to be creat +ed +InnoDB: Setting log file c:\iblogs\ib_logfile2 size to 31457280 +InnoDB: Doublewrite buffer not found: creating new +InnoDB: Doublewrite buffer created +InnoDB: creating foreign key constraint system tables +InnoDB: foreign key constraint system tables created +011024 10:58:25 InnoDB: Started + + When the server finishes its startup sequence, you should see + something like this, which indicates that the server is ready to + service client connections: +mysqld: ready for connections +Version: '5.1.41' socket: '' port: 3306 + + The server continues to write to the console any further + diagnostic output it produces. You can open a new console window + in which to run client programs. + + If you omit the --console option, the server writes diagnostic + output to the error log in the data directory (C:\Program + Files\MySQL\MySQL Server 5.1\data by default). The error log is + the file with the .err extension. + +Note + + The accounts that are listed in the MySQL grant tables initially + have no passwords. After starting the server, you should set up + passwords for them using the instructions in Section 2.13, + "Post-Installation Setup and Testing." + +2.5.5.5. Starting MySQL from the Windows Command Line + + The MySQL server can be started manually from the command line. + This can be done on any version of Windows. + + To start the mysqld server from the command line, you should start + a console window (or "DOS window") and enter this command: +C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld" + + The path to mysqld may vary depending on the install location of + MySQL on your system. + + You can stop the MySQL server by executing this command: +C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqladmin" -u root + shutdown + +Note + + If the MySQL root user account has a password, you need to invoke + mysqladmin with the -p option and supply the password when + prompted. + + This command invokes the MySQL administrative utility mysqladmin + to connect to the server and tell it to shut down. The command + connects as the MySQL root user, which is the default + administrative account in the MySQL grant system. Note that users + in the MySQL grant system are wholly independent from any login + users under Windows. + + If mysqld doesn't start, check the error log to see whether the + server wrote any messages there to indicate the cause of the + problem. The error log is located in the C:\Program + Files\MySQL\MySQL Server 5.1\data directory. It is the file with a + suffix of .err. You can also try to start the server as mysqld + --console; in this case, you may get some useful information on + the screen that may help solve the problem. + + The last option is to start mysqld with the --standalone and + --debug options. In this case, mysqld writes a log file + C:\mysqld.trace that should contain the reason why mysqld doesn't + start. See MySQL Internals: Porting + (http://forge.mysql.com/wiki/MySQL_Internals_Porting). + + Use mysqld --verbose --help to display all the options that mysqld + supports. + +2.5.5.6. Starting MySQL as a Windows Service + + On Windows, the recommended way to run MySQL is to install it as a + Windows service, whereby MySQL starts and stops automatically when + Windows starts and stops. A MySQL server installed as a service + can also be controlled from the command line using NET commands, + or with the graphical Services utility. Generally, to install + MySQL as a Windows service you should be logged in using an + account that has administrator rights. + + The Services utility (the Windows Service Control Manager) can be + found in the Windows Control Panel (under Administrative Tools on + Windows 2000, XP, Vista and Server 2003). To avoid conflicts, it + is advisable to close the Services utility while performing server + installation or removal operations from the command line. + + Before installing MySQL as a Windows service, you should first + stop the current server if it is running by using the following + command: +C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqladmin" + -u root shutdown + +Note + + If the MySQL root user account has a password, you need to invoke + mysqladmin with the -p option and supply the password when + prompted. + + This command invokes the MySQL administrative utility mysqladmin + to connect to the server and tell it to shut down. The command + connects as the MySQL root user, which is the default + administrative account in the MySQL grant system. Note that users + in the MySQL grant system are wholly independent from any login + users under Windows. + + Install the server as a service using this command: +C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld" --install + + The service-installation command does not start the server. + Instructions for that are given later in this section. + + To make it easier to invoke MySQL programs, you can add the path + name of the MySQL bin directory to your Windows system PATH + environment variable: + + * On the Windows desktop, right-click on the My Computer icon, + and select Properties. + + * Next select the Advanced tab from the System Properties menu + that appears, and click the Environment Variables button. + + * Under System Variables, select Path, and then click the Edit + button. The Edit System Variable dialogue should appear. + + * Place your cursor at the end of the text appearing in the + space marked Variable Value. (Use the End key to ensure that + your cursor is positioned at the very end of the text in this + space.) Then enter the complete path name of your MySQL bin + directory (for example, C:\Program Files\MySQL\MySQL Server + 5.1\bin), Note that there should be a semicolon separating + this path from any values present in this field. Dismiss this + dialogue, and each dialogue in turn, by clicking OK until all + of the dialogues that were opened have been dismissed. You + should now be able to invoke any MySQL executable program by + typing its name at the DOS prompt from any directory on the + system, without having to supply the path. This includes the + servers, the mysql client, and all MySQL command-line + utilities such as mysqladmin and mysqldump. + You should not add the MySQL bin directory to your Windows + PATH if you are running multiple MySQL servers on the same + machine. + +Warning + + You must exercise great care when editing your system PATH by + hand; accidental deletion or modification of any portion of the + existing PATH value can leave you with a malfunctioning or even + unusable system. + + The following additional arguments can be used in MySQL 5.1 when + installing the service: + + * You can specify a service name immediately following the + --install option. The default service name is MySQL. + + * If a service name is given, it can be followed by a single + option. By convention, this should be + --defaults-file=file_name to specify the name of an option + file from which the server should read options when it starts. + The use of a single option other than --defaults-file is + possible but discouraged. --defaults-file is more flexible + because it enables you to specify multiple startup options for + the server by placing them in the named option file. + + * You can also specify a --local-service option following the + service name. This causes the server to run using the + LocalService Windows account that has limited system + privileges. This account is available only for Windows XP or + newer. If both --defaults-file and --local-service are given + following the service name, they can be in any order. + + For a MySQL server that is installed as a Windows service, the + following rules determine the service name and option files that + the server uses: + + * If the service-installation command specifies no service name + or the default service name (MySQL) following the --install + option, the server uses the a service name of MySQL and reads + options from the [mysqld] group in the standard option files. + + * If the service-installation command specifies a service name + other than MySQL following the --install option, the server + uses that service name. It reads options from the [mysqld] + group and the group that has the same name as the service in + the standard option files. This allows you to use the [mysqld] + group for options that should be used by all MySQL services, + and an option group with the service name for use by the + server installed with that service name. + + * If the service-installation command specifies a + --defaults-file option after the service name, the server + reads options only from the [mysqld] group of the named file + and ignores the standard option files. + + As a more complex example, consider the following command: +C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld" + --install MySQL --defaults-file=C:\my-opts.cnf + + Here, the default service name (MySQL) is given after the + --install option. If no --defaults-file option had been given, + this command would have the effect of causing the server to read + the [mysqld] group from the standard option files. However, + because the --defaults-file option is present, the server reads + options from the [mysqld] option group, and only from the named + file. + + You can also specify options as Start parameters in the Windows + Services utility before you start the MySQL service. + + Once a MySQL server has been installed as a service, Windows + starts the service automatically whenever Windows starts. The + service also can be started immediately from the Services utility, + or by using a NET START MySQL command. The NET command is not case + sensitive. + + When run as a service, mysqld has no access to a console window, + so no messages can be seen there. If mysqld does not start, check + the error log to see whether the server wrote any messages there + to indicate the cause of the problem. The error log is located in + the MySQL data directory (for example, C:\Program + Files\MySQL\MySQL Server 5.1\data). It is the file with a suffix + of .err. + + When a MySQL server has been installed as a service, and the + service is running, Windows stops the service automatically when + Windows shuts down. The server also can be stopped manually by + using the Services utility, the NET STOP MySQL command, or the + mysqladmin shutdown command. + + You also have the choice of installing the server as a manual + service if you do not wish for the service to be started + automatically during the boot process. To do this, use the + --install-manual option rather than the --install option: +C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld" --install-m +anual + + To remove a server that is installed as a service, first stop it + if it is running by executing NET STOP MySQL. Then use the + --remove option to remove it: +C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld" --remove + + If mysqld is not running as a service, you can start it from the + command line. For instructions, see Section 2.5.5.5, "Starting + MySQL from the Windows Command Line." + + Please see Section 2.5.6, "Troubleshooting a MySQL Installation + Under Windows," if you encounter difficulties during installation. + +2.5.5.7. Testing The MySQL Installation + + You can test whether the MySQL server is working by executing any + of the following commands: +C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqlshow" +C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqlshow" -u root +mysql +C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqladmin" version + status proc +C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysql" test + +Note + + By default, mysqlshow will try to connect using the ODBC user. + This user is not created by default. You should specify a valid + user, or root with the right password to check the operation of + the server. + + If mysqld is slow to respond to TCP/IP connections from client + programs, there is probably a problem with your DNS. In this case, + start mysqld with the --skip-name-resolve option and use only + localhost and IP numbers in the Host column of the MySQL grant + tables. + + You can force a MySQL client to use a named-pipe connection rather + than TCP/IP by specifying the --pipe or --protocol=PIPE option, or + by specifying . (period) as the host name. Use the --socket option + to specify the name of the pipe if you do not want to use the + default pipe name. + + Note that if you have set a password for the root account, deleted + the anonymous account, or created a new user account, then you + must use the appropriate -u and -p options with the commands shown + above in order to connect with the MySQL Server. See Section + 4.2.2, "Connecting to the MySQL Server." + + For more information about mysqlshow, see Section 4.5.6, + "mysqlshow --- Display Database, Table, and Column Information." + +2.5.6. Troubleshooting a MySQL Installation Under Windows + + When installing and running MySQL for the first time, you may + encounter certain errors that prevent the MySQL server from + starting. The purpose of this section is to help you diagnose and + correct some of these errors. + + Your first resource when troubleshooting server issues is the + error log. The MySQL server uses the error log to record + information relevant to the error that prevents the server from + starting. The error log is located in the data directory specified + in your my.ini file. The default data directory location is + C:\Program Files\MySQL\MySQL Server 5.1\data. See Section 5.2.2, + "The Error Log." + + Another source of information regarding possible errors is the + console messages displayed when the MySQL service is starting. Use + the NET START MySQL command from the command line after installing + mysqld as a service to see any error messages regarding the + starting of the MySQL server as a service. See Section 2.5.5.6, + "Starting MySQL as a Windows Service." + + The following examples show other common error messages you may + encounter when installing MySQL and starting the server for the + first time: + + * If the MySQL server cannot find the mysql privileges database + or other critical files, you may see these messages: +System error 1067 has occurred. +Fatal error: Can't open privilege tables: Table 'mysql.host' doesn't +exist + These messages often occur when the MySQL base or data + directories are installed in different locations than the + default locations (C:\Program Files\MySQL\MySQL Server 5.1 and + C:\Program Files\MySQL\MySQL Server 5.1\data, respectively). + This situation may occur when MySQL is upgraded and installed + to a new location, but the configuration file is not updated + to reflect the new location. In addition, there may be old and + new configuration files that conflict. Be sure to delete or + rename any old configuration files when upgrading MySQL. + If you have installed MySQL to a directory other than + C:\Program Files\MySQL\MySQL Server 5.1, you need to ensure + that the MySQL server is aware of this through the use of a + configuration (my.ini) file. The my.ini file needs to be + located in your Windows directory, typically C:\WINDOWS. You + can determine its exact location from the value of the WINDIR + environment variable by issuing the following command from the + command prompt: +C:\> echo %WINDIR% + An option file can be created and modified with any text + editor, such as Notepad. For example, if MySQL is installed in + E:\mysql and the data directory is D:\MySQLdata, you can + create the option file and set up a [mysqld] section to + specify values for the basedir and datadir options: +[mysqld] +# set basedir to your installation path +basedir=E:/mysql +# set datadir to the location of your data directory +datadir=D:/MySQLdata + Note that Windows path names are specified in option files + using (forward) slashes rather than backslashes. If you do use + backslashes, double them: +[mysqld] +# set basedir to your installation path +basedir=C:\\Program Files\\MySQL\\MySQL Server 5.1 +# set datadir to the location of your data directory +datadir=D:\\MySQLdata + The rules for use of backslash in option file values are given + in Section 4.2.3.3, "Using Option Files." + If you change the datadir value in your MySQL configuration + file, you must move the contents of the existing MySQL data + directory before restarting the MySQL server. + See Section 2.5.5.2, "Creating an Option File." + + * If you reinstall or upgrade MySQL without first stopping and + removing the existing MySQL service and install MySQL using + the MySQL Config Wizard, you may see this error: +Error: Cannot create Windows service for MySql. Error: 0 + This occurs when the Config Wizard tries to install the + service and finds an existing service with the same name. + One solution to this problem is to choose a service name other + than mysql when using the configuration wizard. This allows + the new service to be installed correctly, but leaves the + outdated service in place. Although this is harmless, it is + best to remove old services that are no longer in use. + To permanently remove the old mysql service, execute the + following command as a user with administrative privileges, on + the command-line: +C:\> sc delete mysql +[SC] DeleteService SUCCESS + If the sc utility is not available for your version of + Windows, download the delsrv utility from + http://www.microsoft.com/windows2000/techinfo/reskit/tools/exi + sting/delsrv-o.asp and use the delsrv mysql syntax. + +2.5.7. Upgrading MySQL on Windows + + This section lists some of the steps you should take when + upgrading MySQL on Windows. + + 1. Review Section 2.4.1, "Upgrading MySQL," for additional + information on upgrading MySQL that is not specific to + Windows. + + 2. You should always back up your current MySQL installation + before performing an upgrade. See Section 6.1, "Database + Backup Methods." + + 3. Download the latest Windows distribution of MySQL from + http://dev.mysql.com/downloads/. + + 4. Before upgrading MySQL, you must stop the server. If the + server is installed as a service, stop the service with the + following command from the command prompt: +C:\> NET STOP MySQL + If you are not running the MySQL server as a service, use the + following command to stop it: +C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqladmin" -u root + shutdown + +Note + If the MySQL root user account has a password, you need to + invoke mysqladmin with the -p option and supply the password + when prompted. + + 5. When upgrading to MySQL 5.1 from a version previous to 4.1.5, + or when upgrading from a version of MySQL installed from a Zip + archive to a version of MySQL installed with the MySQL + Installation Wizard, you must manually remove the previous + installation and MySQL service (if the server is installed as + a service). + To remove the MySQL service, use the following command: +C:\> C:\mysql\bin\mysqld --remove + If you do not remove the existing service, the MySQL + Installation Wizard may fail to properly install the new MySQL + service. + + 6. When upgrading from MySQL 5.1.23 to MySQL 5.1.24, the change + in the default location of the data directory from a directory + within the MySQL installation to the AppData folder means that + you must manually copy the data files from your old + installation to the new location. + + 7. If you are using the MySQL Installation Wizard, start the + wizard as described in Section 2.5.3.1, "Using the MySQL + Installation Wizard." + + 8. If you are installing MySQL from a Zip archive, extract the + archive. You may either overwrite your existing MySQL + installation (usually located at C:\mysql), or install it into + a different directory, such as C:\mysql5. Overwriting the + existing installation is recommended. + + 9. If you were running MySQL as a Windows service and you had to + remove the service earlier in this procedure, reinstall the + service. (See Section 2.5.5.6, "Starting MySQL as a Windows + Service.") + 10. Restart the server. For example, use NET START MySQL if you + run MySQL as a service, or invoke mysqld directly otherwise. + 11. If you encounter errors, see Section 2.5.6, "Troubleshooting a + MySQL Installation Under Windows." + +2.5.8. Windows Post-Installation Procedures + + On Windows, the data directory and the grant tables do not have to + be created. MySQL Windows distributions include the grant tables + with a set of preinitialized accounts in the mysql database under + the data directory. It is unnecessary to run the mysql_install_db + script that is used on Unix. Regarding passwords, if you installed + MySQL using the Windows Installation Wizard, you may have already + assigned passwords to the accounts. (See Section 2.5.3.1, "Using + the MySQL Installation Wizard.") Otherwise, use the + password-assignment procedure given in Section 2.13.2, "Securing + the Initial MySQL Accounts." + + Before setting up passwords, you might want to try running some + client programs to make sure that you can connect to the server + and that it is operating properly. Make sure that the server is + running (see Section 2.5.5.4, "Starting the Server for the First + Time"), and then issue the following commands to verify that you + can retrieve information from the server. The output should be + similar to what is shown here: +C:\> C:\mysql\bin\mysqlshow ++--------------------+ +| Databases | ++--------------------+ +| information_schema | +| mysql | +| test | ++--------------------+ + +Note + + The above may not work if the correct user does not exist. If you + installed using the MSI packages and used the MySQL Server + Instance Config Wizard, then the root will haqve been created + automatically with the password you supplied. In this case, you + should use the -u and -p options where you will be prompted for + the password. + +Note + + The list of installed databases may vary, but will always include + the minimum of mysql and information_schema. In most cases, the + test database will also be installed automatically. + + If you specify the name of the database, then a list of the tables + within a given database will be displayed: +C:\> C:\mysql\bin\mysqlshow mysql +Database: mysql ++---------------------------+ +| Tables | ++---------------------------+ +| columns_priv | +| db | +| event | +| func | +| general_log | +| help_category | +| help_keyword | +| help_relation | +| help_topic | +| host | +| plugin | +| proc | +| procs_priv | +| servers | +| slow_log | +| tables_priv | +| time_zone | +| time_zone_leap_second | +| time_zone_name | +| time_zone_transition | +| time_zone_transition_type | +| user | ++---------------------------+ + + +C:\> C:\mysql\bin\mysql -e "SELECT Host,Db,User FROM db" mysql ++------+-------+------+ +| host | db | user | ++------+-------+------+ +| % | test% | | ++------+-------+------+ + + You may need to specify a different directory from the one shown; + if you used the Windows Installation Wizard, then the default + directory is C:\Program Files\MySQL\MySQL Server 5.1, and the + mysql and mysqlshow client programs are in C:\Program + Files\MySQL\MySQL Server 5.1\bin. See Section 2.5.3.1, "Using the + MySQL Installation Wizard," for more information. + + If you have already secured the initial MySQL accounts, you may + need to use the -u and -p options to supply a user name and + password to the mysqlshow and mysql client programs; otherwise the + programs may fail with an error, or you may not be able to view + all databases. For example, if you have assigned the password + "secretpass" to the MySQL root account, then you can invoke + mysqlshow and mysql as shown here: +C:\> C:\mysql\bin\mysqlshow -uroot -psecretpass ++--------------------+ +| Databases | ++--------------------+ +| information_schema | +| mysql | +| test | ++--------------------+ + +C:\> C:\mysql\bin\mysqlshow -uroot -psecretpass mysql +Database: mysql ++---------------------------+ +| Tables | ++---------------------------+ +| columns_priv | +| db | +| event | +| func | +| general_log | +| help_category | +| help_keyword | +| help_relation | +| help_topic | +| host | +| plugin | +| proc | +| procs_priv | +| servers | +| slow_log | +| tables_priv | +| time_zone | +| time_zone_leap_second | +| time_zone_name | +| time_zone_transition | +| time_zone_transition_type | +| user | ++---------------------------+ + + +C:\> C:\mysql\bin\mysql -uroot -psecretpass -e "SELECT Host,Db,User F +ROM db" mysql ++------+-------+------+ +| host | db | user | ++------+-------+------+ +| % | test% | | ++------+-------+------+ + + For more information about these programs, see Section 4.5.6, + "mysqlshow --- Display Database, Table, and Column Information," + and Section 4.5.1, "mysql --- The MySQL Command-Line Tool." + + If you are running a version of Windows that supports services and + you want the MySQL server to run automatically when Windows + starts, see Section 2.5.5.6, "Starting MySQL as a Windows + Service." + +2.5.9. MySQL on Windows Compared to MySQL on Unix + + MySQL for Windows has proven itself to be very stable. The Windows + version of MySQL has the same features as the corresponding Unix + version, with the following exceptions: + + * Limited number of ports + Windows systems have about 4,000 ports available for client + connections, and after a connection on a port closes, it takes + two to four minutes before the port can be reused. In + situations where clients connect to and disconnect from the + server at a high rate, it is possible for all available ports + to be used up before closed ports become available again. If + this happens, the MySQL server appears to be unresponsive even + though it is running. Note that ports may be used by other + applications running on the machine as well, in which case the + number of ports available to MySQL is lower. + For more information about this problem, see + http://support.microsoft.com/default.aspx?scid=kb;en-us;196271 + . + + * Concurrent reads + MySQL depends on the pread() and pwrite() system calls to be + able to mix INSERT and SELECT. Currently, we use mutexes to + emulate pread() and pwrite(). We intend to replace the file + level interface with a virtual interface in the future so that + we can use the readfile()/writefile() interface to get more + speed. The current implementation limits the number of open + files that MySQL 5.1 can use to 2,048, which means that you + cannot run as many concurrent threads on Windows as on Unix. + + * Blocking read + MySQL uses a blocking read for each connection. That has the + following implications if named-pipe connections are enabled: + + + A connection is not disconnected automatically after + eight hours, as happens with the Unix version of MySQL. + + + If a connection hangs, it is not possible to break it + without killing MySQL. + + + mysqladmin kill does not work on a sleeping connection. + + + mysqladmin shutdown cannot abort as long as there are + sleeping connections. + We plan to fix this problem in the future. + + * ALTER TABLE + While you are executing an ALTER TABLE statement, the table is + locked from being used by other threads. This has to do with + the fact that on Windows, you can't delete a file that is in + use by another thread. In the future, we may find some way to + work around this problem. + + * DATA DIRECTORY and INDEX DIRECTORY + The DATA DIRECTORY and INDEX DIRECTORY options for CREATE + TABLE are ignored on Windows, because Windows doesn't support + symbolic links. These options also are ignored on systems that + have a nonfunctional realpath() call. + + * DROP DATABASE + You cannot drop a database that is in use by another thread. + + * Case-insensitive names + File names are not case sensitive on Windows, so MySQL + database and table names are also not case sensitive on + Windows. The only restriction is that database and table names + must be specified using the same case throughout a given + statement. See Section 8.2.2, "Identifier Case Sensitivity." + + * Directory and file names + On Windows, MySQL Server supports only directory and file + names that are compatible with the current ANSI code pages. + For example, the following Japanese directory name will not + work in the Western locale (code page 1252): +datadir="C:/维基百科关于ä¸æ–‡ç»´åŸºç™¾ç§‘" + The same limitation applies to directory and file names + referred to in SQL statements, such as the data file path name + in LOAD DATA INFILE. + + * The "\" path name separator character + Path name components in Windows are separated by the "\" + character, which is also the escape character in MySQL. If you + are using LOAD DATA INFILE or SELECT ... INTO OUTFILE, use + Unix-style file names with "/" characters: +mysql> LOAD DATA INFILE 'C:/tmp/skr.txt' INTO TABLE skr; +mysql> SELECT * INTO OUTFILE 'C:/tmp/skr.txt' FROM skr; + Alternatively, you must double the "\" character: +mysql> LOAD DATA INFILE 'C:\\tmp\\skr.txt' INTO TABLE skr; +mysql> SELECT * INTO OUTFILE 'C:\\tmp\\skr.txt' FROM skr; + + * Problems with pipes + Pipes do not work reliably from the Windows command-line + prompt. If the pipe includes the character ^Z / CHAR(24), + Windows thinks that it has encountered end-of-file and aborts + the program. + This is mainly a problem when you try to apply a binary log as + follows: +C:\> mysqlbinlog binary_log_file | mysql --user=root + If you have a problem applying the log and suspect that it is + because of a ^Z / CHAR(24) character, you can use the + following workaround: +C:\> mysqlbinlog binary_log_file --result-file=/tmp/bin.sql +C:\> mysql --user=root --execute "source /tmp/bin.sql" + The latter command also can be used to reliably read in any + SQL file that may contain binary data. + + * Access denied for user error + If MySQL cannot resolve your host name properly, you may get + the following error when you attempt to run a MySQL client + program to connect to a server running on the same machine: +Access denied for user 'some_user'@'unknown' +to database 'mysql' + To fix this problem, you should create a file named + \windows\hosts containing the following information: +127.0.0.1 localhost + + Here are some open issues for anyone who might want to help us + improve MySQL on Windows: + + * Add macros to use the faster thread-safe increment/decrement + methods provided by Windows. + +2.5.10. Installing MySQL from Source on Windows + + These instructions describe how to build binaries from source for + MySQL 5.1 on Windows. Instructions are provided for building + binaries from a standard source distribution or from the Bazaar + tree that contains the latest development source. -2.13.1.4. Linux Post-Installation Notes +Note + + The instructions here are strictly for users who want to test + MySQL on Microsoft Windows from the latest source distribution or + from the Bazaar tree. For production use, we do not advise using a + MySQL server built by yourself from source. Normally, it is best + to use precompiled binary distributions of MySQL that are built + specifically for optimal performance on Windows by Sun + Microsystems, Inc. Instructions for installing binary + distributions are available in Section 2.5, "Installing MySQL on + Windows." + + To build MySQL on Windows from source, you must satisfy the + following system, compiler, and resource requirements: + + * Windows 2000, Windows XP, or newer version. + Windows Vista is supported when using Visual Studio 2005 + provided you have installed the following updates: + + + Microsoft Visual Studio 2005 Professional Edition - ENU + Service Pack 1 (KB926601) + (http://support.microsoft.com/?kbid=926601) + + + Security Update for Microsoft Visual Studio 2005 + Professional Edition - ENU (KB937061) + (http://support.microsoft.com/?kbid=937061) + + + Update for Microsoft Visual Studio 2005 Professional + Edition - ENU (KB932232) + (http://support.microsoft.com/?kbid=932232) + + * CMake, which can be downloaded from http://www.cmake.org. + After installing, modify your path to include the cmake + binary. + + * Microsoft Visual C++ 2005 Express Edition, Visual Studio .Net + 2003 (7.1), or Visual Studio 2005 (8.0) compiler system. + + * If you are using Visual C++ 2005 Express Edition, you must + also install an appropriate Platform SDK. More information and + links to downloads for various Windows platforms is available + from + http://www.microsoft.com/downloads/details.aspx?familyid=0baf2 + b35-c656-4969-ace8-e4c0c0716adb. + + * If you are compiling from a Bazaar tree or making changes to + the parser, you need bison for Windows, which can be + downloaded from + http://gnuwin32.sourceforge.net/packages/bison.htm. Download + the package labeled "Complete package, excluding sources". + After installing the package, modify your path to include the + bison binary and ensure that this binary is accessible from + Visual Studio. + + * Cygwin might be necessary if you want to run the test script + or package the compiled binaries and support files into a Zip + archive. (Cygwin is needed only to test or package the + distribution, not to build it.) Cygwin is available from + http://cygwin.com. + + * 3GB to 5GB of disk space. + + The exact system requirements for Visual Studio can be found here: + http://msdn.microsoft.com/vstudio/Previous/2003/sysreqs/default.as + px and + http://msdn.microsoft.com/vstudio/products/sysreqs/default.aspx + + You also need a MySQL source distribution for Windows, which can + be obtained two ways: + + * Obtain a source distribution packaged by Sun Microsystems, + Inc. These are available from http://dev.mysql.com/downloads/. + + * Package a source distribution yourself from the latest Bazaar + developer source tree. For instructions on pulling the latest + source files, see Section 2.3.3, "Installing from the + Development Source Tree." + + If you find something not working as expected, or you have + suggestions about ways to improve the current build process on + Windows, please send a message to the win32 mailing list. See + Section 1.5.1, "MySQL Mailing Lists." + +2.5.10.1. Building MySQL from Source Using CMake and Visual Studio + + You can build MySQL on Windows by using a combination of cmake and + Microsoft Visual Studio .NET 2003 (7.1), Microsoft Visual Studio + 2005 (8.0) or Microsoft Visual C++ 2005 Express Edition. You must + have the appropriate Microsoft Platform SDK installed. + +Note + + To compile from the source code on Windows you must use the + standard source distribution (for example, mysql-5.1.41.tar.gz). + You build from the same distribution as used to build MySQL on + Unix, Linux and other platforms. Do not use the Windows Source + distributions as they do not contain the necessary configuration + script and other files. + + Follow this procedure to build MySQL: + + 1. If you are installing from a packaged source distribution, + create a work directory (for example, C:\workdir), and unpack + the source distribution there using WinZip or another Windows + tool that can read .zip files. This directory is the work + directory in the following instructions. + + 2. Using a command shell, navigate to the work directory and run + the following command: +C:\workdir>win\configure.js options + If you have associated the .js file extension with an + application such as a text editor, then you may need to use + the following command to force configure.js to be executed as + a script: +C:\workdir>cscript win\configure.js options + These options are available for configure.js: + + + WITH_INNOBASE_STORAGE_ENGINE: Enable the InnoDB storage + engine. + + + WITH_PARTITION_STORAGE_ENGINE: Enable user-defined + partitioning. + + + WITH_ARCHIVE_STORAGE_ENGINE: Enable the ARCHIVE storage + engine. + + + WITH_BLACKHOLE_STORAGE_ENGINE: Enable the BLACKHOLE + storage engine. + + + WITH_EXAMPLE_STORAGE_ENGINE: Enable the EXAMPLE storage + engine. + + + WITH_FEDERATED_STORAGE_ENGINE: Enable the FEDERATED + storage engine. + + + WITH_NDBCLUSTER_STORAGE_ENGINE (experimental): Enable the + NDBCLUSTER storage engine in the MySQL server; cause + binaries for the MySQL Cluster management and data node, + management client, and other programs to be built. + This option is supported only in MySQL Cluster NDB 7.0 + (NDBCLUSTER storage engine versions 6.4.0 and later) + using the MySQL Cluster sources. It cannot be used to + enable clustering support in other MySQL source trees or + distributions. + + + MYSQL_SERVER_SUFFIX=suffix: Server suffix, default none. + + + COMPILATION_COMMENT=comment: Server comment, default + "Source distribution". + + + MYSQL_TCP_PORT=port: Server port, default 3306. + + + DISABLE_GRANT_OPTIONS: Disables the --bootstrap, + --skip-grant-tables, and --init-file options for mysqld. + This option is available as of MySQL 5.1.15. + For example (type the command on one line): +C:\workdir>win\configure.js WITH_INNOBASE_STORAGE_ENGINE + WITH_PARTITION_STORAGE_ENGINE MYSQL_SERVER_SUFFIX=-pro + + 3. From the work directory, execute the win\build-vs8.bat or + win\build-vs71.bat file, depending on the version of Visual + Studio you have installed. The script invokes CMake, which + generates the mysql.sln solution file. + You can also use win\build-vs8_x64.bat to build the 64-bit + version of MySQL. However, you cannot build the 64-bit version + with Visual Studio Express Edition. You must use Visual Studio + 2005 (8.0) or higher. + + 4. From the work directory, open the generated mysql.sln file + with Visual Studio and select the proper configuration using + the Configuration menu. The menu provides Debug, Release, + RelwithDebInfo, MinRelInfo options. Then select Solution > + Build to build the solution. + Remember the configuration that you use in this step. It is + important later when you run the test script because that + script needs to know which configuration you used. + + 5. Test the server. The server built using the preceding + instructions expects that the MySQL base directory and data + directory are C:\mysql and C:\mysql\data by default. If you + want to test your server using the source tree root directory + and its data directory as the base directory and data + directory, you need to tell the server their path names. You + can either do this on the command line with the --basedir and + --datadir options, or by placing appropriate options in an + option file. (See Section 4.2.3.3, "Using Option Files.") If + you have an existing data directory elsewhere that you want to + use, you can specify its path name instead. + When the server is running in standalone fashion or as a + service based on your configuration, try to connect to it from + the mysql interactive command-line utility. + You can also run the standard test script, mysql-test-run.pl. + This script is written in Perl, so you'll need either Cygwin + or ActiveState Perl to run it. You may also need to install + the modules required by the script. To run the test script, + change location into the mysql-test directory under the work + directory, set the MTR_VS_CONFIG environment variable to the + configuration you selected earlier (or use the --vs-config + option), and invoke mysql-test-run.pl. For example (using + Cygwin and the bash shell): +shell> cd mysql-test +shell> export MTR_VS_CONFIG=debug +shell> ./mysql-test-run.pl --force --timer +shell> ./mysql-test-run.pl --force --timer --ps-protocol + + When you are satisfied that the programs you have built are + working correctly, stop the server. Now you can install the + distribution. One way to do this is to use the make_win_bin_dist + script in the scripts directory of the MySQL source distribution + (see Section 4.4.2, "make_win_bin_dist --- Package MySQL + Distribution as ZIP Archive"). This is a shell script, so you must + have Cygwin installed if you want to use it. It creates a Zip + archive of the built executables and support files that you can + unpack in the location at which you want to install MySQL. + + It is also possible to install MySQL by copying directories and + files directly: + + 1. Create the directories where you want to install MySQL. For + example, to install into C:\mysql, use these commands: +C:\> mkdir C:\mysql +C:\> mkdir C:\mysql\bin +C:\> mkdir C:\mysql\data +C:\> mkdir C:\mysql\share +C:\> mkdir C:\mysql\scripts + If you want to compile other clients and link them to MySQL, + you should also create several additional directories: +C:\> mkdir C:\mysql\include +C:\> mkdir C:\mysql\lib +C:\> mkdir C:\mysql\lib\debug +C:\> mkdir C:\mysql\lib\opt + If you want to benchmark MySQL, create this directory: +C:\> mkdir C:\mysql\sql-bench + Benchmarking requires Perl support. See Section 2.15, "Perl + Installation Notes." + + 2. From the work directory, copy into the C:\mysql directory the + following directories: +C:\> cd \workdir +C:\workdir> copy client_release\*.exe C:\mysql\bin +C:\workdir> copy client_debug\mysqld.exe C:\mysql\bin\mysqld-debug.ex +e +C:\workdir> xcopy scripts\*.* C:\mysql\scripts /E +C:\workdir> xcopy share\*.* C:\mysql\share /E + If you want to compile other clients and link them to MySQL, + you should also copy several libraries and header files: +C:\workdir> copy lib_debug\mysqlclient.lib C:\mysql\lib\debug +C:\workdir> copy lib_debug\libmysql.* C:\mysql\lib\debug +C:\workdir> copy lib_debug\zlib.* C:\mysql\lib\debug +C:\workdir> copy lib_release\mysqlclient.lib C:\mysql\lib\opt +C:\workdir> copy lib_release\libmysql.* C:\mysql\lib\opt +C:\workdir> copy lib_release\zlib.* C:\mysql\lib\opt +C:\workdir> copy include\*.h C:\mysql\include +C:\workdir> copy libmysql\libmysql.def C:\mysql\include + If you want to benchmark MySQL, you should also do this: +C:\workdir> xcopy sql-bench\*.* C:\mysql\bench /E + + After installation, set up and start the server in the same way as + for binary Windows distributions. See Section 2.5, "Installing + MySQL on Windows." + +2.5.11. Compiling MySQL Clients on Windows + + In your source files, you should include my_global.h before + mysql.h: +#include <my_global.h> +#include <mysql.h> + + my_global.h includes any other files needed for Windows + compatibility (such as windows.h) if you compile your program on + Windows. + + You can either link your code with the dynamic libmysql.lib + library, which is just a wrapper to load in libmysql.dll on + demand, or link with the static mysqlclient.lib library. + + The MySQL client libraries are compiled as threaded libraries, so + you should also compile your code to be multi-threaded. + +2.6. Installing MySQL on Linux + + The following sections covers the installation of Linux using + RPMs. For information on using a generic binary package using tar, + see Section 2.2, "Installing MySQL from Generic Binaries on + Unix/Linux." For information on installing from source, see + Section 2.3, "MySQL Installation Using a Source Distribution." mysql.server can be found in the support-files directory under the MySQL installation directory or in a MySQL source tree. You can install it as /etc/init.d/mysql for automatic MySQL startup and - shutdown. See Section 2.11.2.2, "Starting and Stopping MySQL + shutdown. See Section 2.13.1.2, "Starting and Stopping MySQL Automatically." - If MySQL cannot open enough files or connections, it may be that - you have not configured Linux to handle enough files. - - In Linux 2.2 and onward, you can check the number of allocated - file handles as follows: -shell> cat /proc/sys/fs/file-max -shell> cat /proc/sys/fs/dquot-max -shell> cat /proc/sys/fs/super-max - - If you have more than 16MB of memory, you should add something - like the following to your init scripts (for example, - /etc/init.d/boot.local on SuSE Linux): -echo 65536 > /proc/sys/fs/file-max -echo 8192 > /proc/sys/fs/dquot-max -echo 1024 > /proc/sys/fs/super-max - - You can also run the echo commands from the command line as root, - but these settings are lost the next time your computer restarts. - - Alternatively, you can set these parameters on startup by using - the sysctl tool, which is used by many Linux distributions - (including SuSE Linux 8.0 and later). Put the following values - into a file named /etc/sysctl.conf: -# Increase some values for MySQL -fs.file-max = 65536 -fs.dquot-max = 8192 -fs.super-max = 1024 - - You should also add the following to /etc/my.cnf: -[mysqld_safe] -open-files-limit=8192 - - This should allow the server a limit of 8,192 for the combined - number of connections and open files. - - The STACK_SIZE constant in LinuxThreads controls the spacing of - thread stacks in the address space. It needs to be large enough so - that there is plenty of room for each individual thread stack, but - small enough to keep the stack of some threads from running into - the global mysqld data. Unfortunately, as we have experimentally - discovered, the Linux implementation of mmap() successfully unmaps - a mapped region if you ask it to map out an address currently in - use, zeroing out the data on the entire page instead of returning - an error. So, the safety of mysqld or any other threaded - application depends on the "gentlemanly" behavior of the code that - creates threads. The user must take measures to make sure that the - number of running threads at any given time is sufficiently low - for thread stacks to stay away from the global heap. With mysqld, - you should enforce this behavior by setting a reasonable value for - the max_connections variable. - - If you build MySQL yourself, you can patch LinuxThreads for better - stack use. See Section 2.13.1.3, "Linux Source Distribution - Notes." If you do not want to patch LinuxThreads, you should set - max_connections to a value no higher than 500. It should be even - less if you have a large key buffer, large heap tables, or some - other things that make mysqld allocate a lot of memory, or if you - are running a 2.2 kernel with a 2GB patch. If you are using our - binary or RPM version, you can safely set max_connections at 1500, - assuming no large key buffer or heap tables with lots of data. The - more you reduce STACK_SIZE in LinuxThreads the more threads you - can safely create. Values between 128KB and 256KB are recommended. - - If you use a lot of concurrent connections, you may suffer from a - "feature" in the 2.2 kernel that attempts to prevent fork bomb - attacks by penalizing a process for forking or cloning a child. - This causes MySQL not to scale well as you increase the number of - concurrent clients. On single-CPU systems, we have seen this - manifest as very slow thread creation; it may take a long time to - connect to MySQL (as long as one minute), and it may take just as - long to shut it down. On multiple-CPU systems, we have observed a - gradual drop in query speed as the number of clients increases. In - the process of trying to find a solution, we have received a - kernel patch from one of our users who claimed it helped for his - site. This patch is available at - http://dev.mysql.com/Downloads/Patches/linux-fork.patch. We have - done rather extensive testing of this patch on both development - and production systems. It has significantly improved MySQL - performance without causing any problems and is recommended for - users who still run high-load servers on 2.2 kernels. - - This issue has been fixed in the 2.4 kernel, so if you are not - satisfied with the current performance of your system, rather than - patching your 2.2 kernel, it might be easier to upgrade to 2.4. On - SMP systems, upgrading also gives you a nice SMP boost in addition - to fixing the fairness bug. - - We have tested MySQL on the 2.4 kernel on a two-CPU machine and - found MySQL scales much better. There was virtually no slowdown on - query throughput all the way up to 1,000 clients, and the MySQL - scaling factor (computed as the ratio of maximum throughput to the - throughput for one client) was 180%. We have observed similar - results on a four-CPU system: Virtually no slowdown as the number - of clients was increased up to 1,000, and a 300% scaling factor. - Based on these results, for a high-load SMP server using a 2.2 - kernel, it is definitely recommended to upgrade to the 2.4 kernel - at this point. - - We have discovered that it is essential to run the mysqld process - with the highest possible priority on the 2.4 kernel to achieve - maximum performance. This can be done by adding a renice -20 $$ - command to mysqld_safe. In our testing on a four-CPU machine, - increasing the priority resulted in a 60% throughput increase with - 400 clients. - - We are currently also trying to collect more information on how - well MySQL performs with a 2.4 kernel on four-way and eight-way - systems. If you have access such a system and have done some - benchmarks, please send an email message to benchmarks@mysql.com - with the results. We will review them for inclusion in the manual. - - If you see a dead mysqld server process with ps, this usually - means that you have found a bug in MySQL or you have a corrupted - table. See Section B.1.4.2, "What to Do If MySQL Keeps Crashing." - - To get a core dump on Linux if mysqld dies with a SIGSEGV signal, - you can start mysqld with the --core-file option. Note that you - also probably need to raise the core file size by adding ulimit -c - 1000000 to mysqld_safe or starting mysqld_safe with - --core-file-size=1000000. See Section 4.3.2, "mysqld_safe --- - MySQL Server Startup Script." - -2.13.1.5. Linux x86 Notes - - MySQL requires libc 5.4.12 or newer. It is known to work with libc - 5.4.46. glibc 2.0.6 and later should also work. There have been - some problems with the glibc RPMs from Red Hat, so if you have - problems, check whether there are any updates. The glibc 2.0.7-19 - and 2.0.7-29 RPMs are known to work. - - If you are using Red Hat 8.0 or a new glibc 2.2.x library, you may - see mysqld die in gethostbyaddr(). This happens because the new - glibc library requires a stack size greater than 128KB for this - call. To fix the problem, start mysqld with the - --thread-stack=192K option. (Use -O thread_stack=192K before MySQL - 4.) This stack size is the default on MySQL 4.0.10 and above, so - you should not see the problem. - - If you are using gcc 3.0 and above to compile MySQL, you must - install the libstdc++v3 library before compiling MySQL; if you - don't do this, you get an error about a missing __cxa_pure_virtual - symbol during linking. - - On some older Linux distributions, configure may produce an error - like this: -Syntax error in sched.h. Change _P to __P in the -/usr/include/sched.h file. -See the Installation chapter in the Reference Manual. - - Just do what the error message says. Add an extra underscore to - the _P macro name that has only one underscore, and then try - again. - - You may get some warnings when compiling. Those shown here can be - ignored: -mysqld.cc -o objs-thread/mysqld.o -mysqld.cc: In function `void init_signals()': -mysqld.cc:315: warning: assignment of negative value `-1' to -`long unsigned int' -mysqld.cc: In function `void * signal_hand(void *)': -mysqld.cc:346: warning: assignment of negative value `-1' to -`long unsigned int' - - If mysqld always dumps core when it starts, the problem may be - that you have an old /lib/libc.a. Try renaming it, and then remove - sql/mysqld and do a new make install and try again. This problem - has been reported on some Slackware installations. - - If you get the following error when linking mysqld, it means that - your libg++.a is not installed correctly: -/usr/lib/libc.a(putc.o): In function `_IO_putc': -putc.o(.text+0x0): multiple definition of `_IO_putc' - - You can avoid using libg++.a by running configure like this: -shell> CXX=gcc ./configure - -2.13.1.6. Linux SPARC Notes - - In some implementations, readdir_r() is broken. The symptom is - that the SHOW DATABASES statement always returns an empty set. - This can be fixed by removing HAVE_READDIR_R from config.h after - configuring and before compiling. - -2.13.1.7. Linux Alpha Notes - - We have tested MySQL 5.1 on Alpha with our benchmarks and test - suite, and it appears to work well. - - We currently build the MySQL binary packages on SuSE Linux 7.0 for - AXP, kernel 2.4.4-SMP, Compaq C compiler (V6.2-505) and Compaq C++ - compiler (V6.3-006) on a Compaq DS20 machine with an Alpha EV6 - processor. +2.6.1. Installing MySQL from RPM Packages on Linux - You can find the preceding compilers at - http://www.support.compaq.com/alpha-tools/. By using these - compilers rather than gcc, we get about 9-14% better MySQL - performance. - - For MySQL on Alpha, we use the -arch generic flag to our compile - options, which ensures that the binary runs on all Alpha - processors. We also compile statically to avoid library problems. - The configure command looks like this: -CC=ccc CFLAGS="-fast -arch generic" CXX=cxx \ -CXXFLAGS="-fast -arch generic -noexceptions -nortti" \ -./configure --prefix=/usr/local/mysql --disable-shared \ - --with-extra-charsets=complex --enable-thread-safe-client \ - --with-mysqld-ldflags=-non_shared --with-client-ldflags=-non_shar -ed + The recommended way to install MySQL on RPM-based Linux + distributions is by using the RPM packages. The RPMs that we + provide to the community should work on all versions of Linux that + support RPM packages and use glibc 2.3. To obtain RPM packages, + see Section 2.1.3, "How to Get MySQL." - Some known problems when running MySQL on Linux-Alpha: + For non-RPM Linux distributions, you can install MySQL using a + .tar.gz package. See Section 2.2, "Installing MySQL from Generic + Binaries on Unix/Linux." - * Debugging threaded applications like MySQL does not work with - gdb 4.18. You should use gdb 5.1 instead. + We do provide some platform-specific RPMs; the difference between + a platform-specific RPM and a generic RPM is that a + platform-specific RPM is built on the targeted platform and is + linked dynamically whereas a generic RPM is linked statically with + LinuxThreads. - * If you try linking mysqld statically when using gcc, the - resulting image dumps core at startup time. In other words, do - not use --with-mysqld-ldflags=-all-static with gcc. +Note -2.13.1.8. Linux PowerPC Notes + RPM distributions of MySQL often are provided by other vendors. Be + aware that they may differ in features and capabilities from those + built by us, and that the instructions in this manual do not + necessarily apply to installing them. The vendor's instructions + should be consulted instead. - MySQL should work on MkLinux with the newest glibc package (tested - with glibc 2.0.7). + In most cases, you need to install only the MySQL-server and + MySQL-client packages to get a functional MySQL installation. The + other packages are not required for a standard installation. -2.13.1.9. Linux MIPS Notes + RPMs for MySQL Cluster. Beginning with MySQL 5.1.24, standard + MySQL server RPMs built by MySQL no longer provide support for the + NDBCLUSTER storage engine. MySQL Cluster users wanting to upgrade + MySQL 5.1.23 or earlier installations from RPMs built by MySQL + should upgrade to MySQL Cluster NDB 6.2 or MySQL Cluster NDB 6.3; + RPMs that should work with most Linux distributions are available + for both of these release series. - To get MySQL to work on Qube2 (Linux Mips), you need the newest - glibc libraries. glibc-2.0.7-29C2 is known to work. You must also - use gcc 2.95.2 or newer). +Important -2.13.1.10. Linux IA-64 Notes + When upgrading a MySQL Cluster RPM installation, you must upgrade + all installed RPMs, including the Server and Client RPMs. - To get MySQL to compile on Linux IA-64, we use the following - configure command for building with gcc 2.96: -CC=gcc \ -CFLAGS="-O3 -fno-omit-frame-pointer" \ -CXX=gcc \ -CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors \ - -fno-exceptions -fno-rtti" \ - ./configure --prefix=/usr/local/mysql \ - "--with-comment=Official MySQL binary" \ - --with-extra-charsets=complex + For more information about installing MySQL Cluster from RPMs, see + Section 17.2.1, "MySQL Cluster Multi-Computer Installation." - On IA-64, the MySQL client binaries use shared libraries. This - means that if you install our binary distribution at a location - other than /usr/local/mysql, you need to add the path of the - directory where you have libmysqlclient.so installed either to the - /etc/ld.so.conf file or to the value of your LD_LIBRARY_PATH - environment variable. + For upgrades, if your installation was originally produced by + installing multiple RPM packages, it is best to upgrade all the + packages, not just some. For example, if you previously installed + the server and client RPMs, do not upgrade just the server RPM. - See Section B.1.3.1, "Problems Linking to the MySQL Client - Library." + The RPM packages shown in the following list are available. The + names shown here use a suffix of .glibc23.i386.rpm, but particular + packages can have different suffixes, described later. -2.13.1.11. SELinux Notes + * MySQL-server-VERSION.glibc23.i386.rpm + The MySQL server. You need this unless you only want to + connect to a MySQL server running on another machine. - RHEL4 comes with SELinux, which supports tighter access control - for processes. If SELinux is enabled (SELINUX in - /etc/selinux/config is set to enforcing, SELINUXTYPE is set to - either targeted or strict), you might encounter problems - installing Sun Microsystems, Inc. RPM packages. + * MySQL-client-VERSION.glibc23.i386.rpm + The standard MySQL client programs. You probably always want + to install this package. - Red Hat has an update that solves this. It involves an update of - the "security policy" specification to handle the install - structure of the RPMs provided by Sun Microsystems, Inc. For - further information, see - https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167551 and - http://rhn.redhat.com/errata/RHBA-2006-0049.html. + * MySQL-devel-VERSION.glibc23.i386.rpm + The libraries and include files that are needed if you want to + compile other MySQL clients, such as the Perl modules. - The preceding discussion applies only to RHEL4. The patch is - unnecessary for RHEL5. + * MySQL-debuginfo-VERSION.glibc23.i386.rpm + This package contains debugging information. debuginfo RPMs + are never needed to use MySQL software; this is true both for + the server and for client programs. However, they contain + additional information that might be needed by a debugger to + analyze a crash. -2.13.2. Mac OS X Notes + * MySQL-shared-VERSION.glibc23.i386.rpm + This package contains the shared libraries + (libmysqlclient.so*) that certain languages and applications + need to dynamically load and use MySQL. It contains + single-threaded and thread-safe libraries. If you install this + package, do not install the MySQL-shared-compat package. - On Mac OS X, tar cannot handle long file names. If you need to - unpack a .tar.gz distribution, use gnutar instead. + * MySQL-shared-compat-VERSION.glibc23.i386.rpm + This package includes the shared libraries for MySQL 3.23, + 4.0, and so on, up to the current release. It contains + single-threaded and thread-safe libraries. Install this + package instead of MySQL-shared if you have applications + installed that are dynamically linked against older versions + of MySQL but you want to upgrade to the current version + without breaking the library dependencies. -2.13.2.1. Mac OS X 10.x (Darwin) + * MySQL-shared-compat-advanced-gpl-VERSION.glibc23.i386.rpm, + MySQL-shared-compat-advanced-VERSION.glibc23.i386.rpm + These are like the MySQL-shared-compat package, but are for + the "MySQL Enterprise Server - Advanced Edition" products. + Install these packages rather than the normal + MySQL-shared-compat package if you want to included shared + client libraries for older MySQL versions. - MySQL should work without major problems on Mac OS X 10.x - (Darwin). + * MySQL-embedded-VERSION.glibc23.i386.rpm + The embedded MySQL server library. - Known issues: + * MySQL-ndb-management-VERSION.glibc23.i386.rpm, + MySQL-ndb-storage-VERSION.glibc23.i386.rpm, + MySQL-ndb-tools-VERSION.glibc23.i386.rpm, + MySQL-ndb-extra-VERSION.glibc23.i386.rpm + Packages that contain additional files for MySQL Cluster + installations. - * If you have problems with performance under heavy load, try - using the --skip-thread-priority option to mysqld. This runs - all threads with the same priority. On Mac OS X, this gives - better performance, at least until Apple fixes its thread - scheduler. +Note + The MySQL-ndb-tools RPM requires a working installation of + perl. Prior to MySQL 5.1.18, the DBI and HTML::Template + packages were also required. See Section 2.15, "Perl + Installation Notes," and Section 17.4.21, "ndb_size.pl --- + NDBCLUSTER Size Requirement Estimator," for more information. - * The connection times (wait_timeout, interactive_timeout and - net_read_timeout) values are not honored. - This is probably a signal handling problem in the thread - library where the signal doesn't break a pending read and we - hope that a future update to the thread libraries will fix - this. + * MySQL-test-VERSION.glibc23.i386.rpm + This package includes the MySQL test suite. - Our binary for Mac OS X is compiled on Darwin 6.3 with the - following configure line: -CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc \ -CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors \ - -fno-exceptions -fno-rtti" \ - ./configure --prefix=/usr/local/mysql \ - --with-extra-charsets=complex --enable-thread-safe-client \ - --enable-local-infile --disable-shared + * MySQL-VERSION.src.rpm + This contains the source code for all of the previous + packages. It can also be used to rebuild the RPMs on other + architectures (for example, Alpha or SPARC). - See Section 2.5, "Installing MySQL on Mac OS X." + The suffix of RPM package names (following the VERSION value) has + the following syntax: +.PLATFORM.CPU.rpm -2.13.2.2. Mac OS X Server 1.2 (Rhapsody) + The PLATFORM and CPU values indicate the type of system for which + the package is built. PLATFORM indicates the platform and CPU + indicates the processor type or family. - For current versions of Mac OS X Server, no operating system - changes are necessary before compiling MySQL. Compiling for the - Server platform is the same as for the client version of Mac OS X. + All packages are dynamically linked against glibc 2.3. The + PLATFORM value indicates whether the package is platform + independent or intended for a specific platform, as shown in the + following table. + glibc23 Platform independent, should run on any Linux distribution + that supports glibc 2.3 + rhel3, rhel4 Red Hat Enterprise Linux 3 or 4 + sles9, sles10 SuSE Linux Enterprise Server 9 or 10 - For older versions (Mac OS X Server 1.2, a.k.a. Rhapsody), you - must first install a pthread package before trying to configure - MySQL. + In MySQL 5.1, only glibc23 packages are available currently. - See Section 2.5, "Installing MySQL on Mac OS X." + The CPU value indicates the processor type or family for which the + package is built. + i386 x86 processor, 386 and up + i586 x86 processor, Pentium and up + x86_64 64-bit x86 processor + ia64 Itanium (IA-64) processor -2.13.3. Solaris Notes + To see all files in an RPM package (for example, a MySQL-server + RPM), run a command like this: +shell> rpm -qpl MySQL-server-VERSION.glibc23.i386.rpm - For information about installing MySQL on Solaris using PKG - distributions, see Section 2.6, "Installing MySQL on Solaris." + To perform a standard minimal installation, install the server and + client RPMs: +shell> rpm -i MySQL-server-VERSION.glibc23.i386.rpm +shell> rpm -i MySQL-client-VERSION.glibc23.i386.rpm - On Solaris, you may run into trouble even before you get the MySQL + To install only the client programs, install just the client RPM: +shell> rpm -i MySQL-client-VERSION.glibc23.i386.rpm + + RPM provides a feature to verify the integrity and authenticity of + packages before installing them. If you would like to learn more + about this feature, see Section 2.1.4, "Verifying Package + Integrity Using MD5 Checksums or GnuPG." + + The server RPM places data under the /var/lib/mysql directory. The + RPM also creates a login account for a user named mysql (if one + does not exist) to use for running the MySQL server, and creates + the appropriate entries in /etc/init.d/ to start the server + automatically at boot time. (This means that if you have performed + a previous installation and have made changes to its startup + script, you may want to make a copy of the script so that you + don't lose it when you install a newer RPM.) See Section 2.13.1.2, + "Starting and Stopping MySQL Automatically," for more information + on how MySQL can be started automatically on system startup. + + If you want to install the MySQL RPM on older Linux distributions + that do not support initialization scripts in /etc/init.d + (directly or via a symlink), you should create a symbolic link + that points to the location where your initialization scripts + actually are installed. For example, if that location is + /etc/rc.d/init.d, use these commands before installing the RPM to + create /etc/init.d as a symbolic link that points there: +shell> cd /etc +shell> ln -s rc.d/init.d . + + However, all current major Linux distributions should support the + new directory layout that uses /etc/init.d, because it is required + for LSB (Linux Standard Base) compliance. + + If the RPM files that you install include MySQL-server, the mysqld + server should be up and running after installation. You should be + able to start using MySQL. + + If something goes wrong, you can find more information in the + binary installation section. See Section 2.2, "Installing MySQL + from Generic Binaries on Unix/Linux." + +Note + + The accounts that are listed in the MySQL grant tables initially + have no passwords. After starting the server, you should set up + passwords for them using the instructions in Section 2.13, + "Post-Installation Setup and Testing." + + During RPM installation, a user named mysql and a group named + mysql are created on the system. This is done using the useradd, + groupadd, and usermod commands. Those commands require appropriate + administrative privileges, which is ensured for locally managed + users and groups (as listed in the /etc/passwd and /etc/group + files) by the RPM installation process being run by root. + + For nonlocal user management (LDAP, NIS, and so forth), the + administrative tools may require additional authentication (such + as a password), and will fail if the installing user does not + provide this authentication. Even if they fail, the RPM + installation will not abort but succeed, and this is intentional. + If they failed, some of the intended transfer of ownership may be + missing, and it is recommended that the system administrator then + manually ensures some appropriate user andgroup exists and + manually transfers ownership following the actions in the RPM spec + file. + +2.7. Installing MySQL on Mac OS X + + MySQL for Mac OS X is available in a number of different forms: + + * Native Package Installer format, which uses the native Mac OS + X installer to walk you through the installation of MySQL. For + more information, see Section 2.7.1, "Installing MySQL Using + the Installation Package." You can use the package installer + with Mac OS X 10.3 and later, and available for both PowerPC + and Intel architectures, and both 32-bit and 64-bit + architectures. There is no Universal Binary available using + the package installation method. The user you use to perform + the installation must have administrator privileges. + + * Tar package format, which uses a file packaged using the Unix + tar and gzip commands. To use this method, you will need to + open a Terminal window. You do not need administrator + privileges using this method, as you can install the MySQL + server anywhere using this method. For more information on + using this method, you can use the generic instructions for + using a tarball, Section 2.2, "Installing MySQL from Generic + Binaries on Unix/Linux."You can use the package installer with + Mac OS X 10.3 and later, and available for both PowerPC and + Intel architectures, and both 32-bit and 64-bit architectures. + A Universal Binary, incorporating both Power PC and Intel + architectures and 32-bit and 64-bit binaries is available. + In addition to the core installation, the Package Installer + also includes Section 2.7.2, "Installing the MySQL Startup + Item" and Section 2.7.3, "Installing and Using the MySQL + Preference Pane," both of which simplify the management of + your installation. + + * Mac OS X server includes a version of MySQL as standard. If + you want to use a more recent version than that supplied with + the Mac OS X server release, you can make use of the package + or tar formats. For more information on using the MySQL + bundled with Mac OS X, see Section 2.7.4, "Using MySQL on Mac + OS X Server." + + For additional information on using MySQL on Mac OS X, see Section + 2.7.5, "MySQL Installation on Mac OS X Notes." + +2.7.1. Installing MySQL Using the Installation Package + + You can install MySQL on Mac OS X 10.3.x ("Panther") or newer + using a Mac OS X binary package in PKG format instead of the + binary tarball distribution. Please note that older versions of + Mac OS X (for example, 10.1.x or 10.2.x) are not supported by this + package. + + The package is located inside a disk image (.dmg) file that you + first need to mount by double-clicking its icon in the Finder. It + should then mount the image and display its contents. + +Note + + Before proceeding with the installation, be sure to shut down all + running MySQL server instances by either using the MySQL Manager + Application (on Mac OS X Server) or via mysqladmin shutdown on the + command line. + + When installing from the package version, you should also install + the MySQL Preference Pane, which will allow you to control the + startup and execution of your MySQL server from System + Preferences. For more information, see Section 2.7.3, "Installing + and Using the MySQL Preference Pane." + + When installing using the package installer, the files are + installed into a directory within /usr/local matching the name of + the installation version and platform. For example, the installer + file mysql-5.1.39-osx10.5-x86_64.pkg installs MySQL into + /usr/local/mysql-5.1.39-osx10.5-x86_64 . The installation layout + of the directory is as shown in the following table: + Directory Contents of Directory + bin Client programs and the mysqld server + data Log files, databases + docs Manual in Info format + include Include (header) files + lib Libraries + man Unix manual pages + mysql-test MySQL test suite + scripts Contains the mysql_install_db script + share/mysql Error message files + sql-bench Benchmarks + support-files Scripts and sample configuration files + /tmp/mysql.sock The location of the MySQL Unix socket + + During the package installer process, a symbolic link from + /usr/local/mysql to the version/platform specific directory + created during installation will be created automatically. + + 1. Download and open the MySQL package installer, which is + provided on a disk image (.dmg). Double-click to open the disk + image, which includes the main MySQL installation package, the + MySQLStartupItem.pkg installation package, and the + MySQL.prefPane. + + 2. Double-click on the MySQL installer package. It will be named + according to the version of MySQL you have downloaded. For + example, if you have downloaded MySQL 5.1.39, double-click + mysql-5.1.39-osx10.5-x86.pkg. + + 3. You will be presented with the openin installer dialog. Click + Continue to begihn installation. + MySQL Package Installer: Step 1 + + 4. A copy of the installation instructions and other important + information relevant to this installation are display. Click + Continue . + + 5. If you have downloaded the community version of MySQL, you + will be shown a copy of the relevent GNU General Public + License. Click Continue . + + 6. Select the drive you want to use to install the MySQL Startup + Item. The drive must have a valid, bootable, Mac OS X + operating system installed. Click Continue. + MySQL Package Installer: Step 4 + + 7. You will be asked to confirm the details of the installation, + including the space required for the installation. To change + the drive on which the startup item is installed you can click + either Go Back or Change Install Location.... To install the + startup item, click Install. + + 8. Once the installation has been completed successfully, you + will be given an Install Succeeded message. + + Once you have completed the basic installation, you must complete + the post-installation steps as specifed in Section 2.13, + "Post-Installation Setup and Testing." + + For convenience, you may also want to install the Section 2.7.2, + "Installing the MySQL Startup Item" and Section 2.7.3, "Installing + and Using the MySQL Preference Pane." + +2.7.2. Installing the MySQL Startup Item + + The MySQL Installation Package includes a startup item that can be + used to automatically startup and shutdown MySQL during boot. + + To install the MySQL Startup Item: + + 1. Download and open the MySQL package installer, which is + provided on a disk image (.dmg). Double-click to open the disk + image, which includes the main MySQL installation package, the + MySQLStartupItem.pkg installation package, and the + MySQL.prefPane. + + 2. Double-click on the MySQLStartItem.pkg file to start the + installation process. + + 3. You will be presented with the Install MySQL Startup Item + dialog. + MySQL Startup Item Installer: Step 1 + Click Continue to continue the installation process. + + 4. A copy of the installation instructions and other important + information relevant to this installation are display. Click + Continue . + + 5. Select the drive you want to use to install the MySQL Startup + Item. The drive must have a valid, bootable, Mac OS X + operating system installed. Click Continue. + MySQL Startup Item Installer: Step 3 + + 6. You will be asked to confirm the details of the installation. + To change the drive on which the startup item is installed you + can click either Go Back or Change Install Location.... To + install the startup item, click Install. + + 7. Once the installation has been completed successfully, you + will be given an Install Succeeded message. + MySQL Startup Item Installer: Step 5 + + The Startup Item for MySQL is installed into + /Library/StartupItems/MySQLCOM. The Startup Item installation adds + a variable MYSQLCOM=-YES- to the system configuration file + /etc/hostconfig. If you want to disable the automatic startup of + MySQL, simply change this variable to MYSQLCOM=-NO-. + + After the installation, you can start up MySQL by running the + following commands in a terminal window. You must have + administrator privileges to perform this task. + + If you have installed the Startup Item, use this command to start + the server: +shell> sudo /Library/StartupItems/MySQLCOM/MySQLCOM start + + You may be prompted for your password to complete the startup. + + If you have installed the Startup Item, use this command to stop + the server: +shell> sudo /Library/StartupItems/MySQLCOM/MySQLCOM stop + + You may be prompted for your password to complete the shutdown. + +2.7.3. Installing and Using the MySQL Preference Pane + + The MySQL Package installer disk image also includes a custom + MySQL Preference Pane that enables you to start, stop and control + automated startup during boot of your MySQL installation. + + To install the MySQL Preference Pane: + + 1. Download and open the MySQL package installer package, which + is provided on a disk image (.dmg). Double-click to open the + disk image, which includes the main MySQL installation + package, the MySQLStartupItem.pkg installation package, and + the MySQL.prefPane. + + 2. Double click on MySQL.prefPane. The MySQL System Preferences + will open. + + 3. If this is the first time you have installed the preference + pane, you will be asked to confirm installation and whether + you want to install the preference pane for all users, or only + the current user. To install the preference pane for all users + you will need administrator privileges. If necessary, you will + be prompted for the username and password for a user with + administrator privileges. + + 4. If you already have the MySQL Preference Pane installed, you + will be asked to confirm whether you want to overwrite the + existing MySQL Preference Pane. + +Note + + The MySQL Preference Pane only starts and stops MySQL installation + installed from the MySQL package installation that have been + installed in the default location. + + Once the MySQL Preference Pane has been installed, you can control + your MySQL server instance using the preference pane. To use the + preference pane, open the System Preferences... from the Apple + menu. Select the MySQL preference pane by clicking on the MySQL + logo within the Other section of the preference panes list. + MySQL Preference Pane + + The MySQL Preference Pane shows the current status of the MySQL + server, showing stopped (in red) if the server is not running and + running (in green) if the server has already been started. The + preference pane will also show the current setting for whether the + MySQL server has been set to start up automatically. + + * To start MySQL using the preference pane: + Click Start MySQL Server. You may be prompted for the username + and password of a user with administrator privileges to start + the MySQL server. + + * To stop MySQL using the preference pane: + Click Stop MySQL Server. You may be prompted for the username + and password of a user with administrator privileges to + shutdown the MySQL server. + + * To automatically start the MySQL server when the system boots: + Check the checkbox next to Automatically Start MySQL Server on + Startup. + + * To disable the automatic starting of the MySQL server when the + system boots: + Uncheck the checkbox next to Automatically Start MySQL Server + on Startup. + + You can close the System Preferences... once you have completed + your settings. + +2.7.4. Using MySQL on Mac OS X Server + + If you are running Mac OS X Server, a version of MySQL should + already be installed. The following table shows the versions of + MySQL that ship with Mac OS X Server versions. + Mac OS X Server Version MySQL Version + 10.2-10.2.2 3.23.51 + 10.2.3-10.2.6 3.23.53 + 10.3 4.0.14 + 10.3.2 4.0.16 + 10.4.0 4.1.10a + 10.5.0 5.0.45 + 10.6.0 5.0.82 + + The installation layout of MySQL on Mac OS X Server is as shown in + the table below: + Directory Contents of Directory + /usr/bin Client programs + /var/mysql Log files, databases + /usr/libexec The mysqld server + /usr/share/man Unix manual pages + /usr/share/mysql/mysql-test MySQL test suite + /usr/share/mysql Contains the mysql_install_db script + /var/mysql/mysql.sock The location of the MySQL Unix socket + +Note + + The MySQL server bundled with Mac OS X Server does not include the + MySQL client libraries and header files required if you want to + access and use MySQL from a third-party driver, such as Perl DBI + or PHP. For more information on obtaining and installing MySQL + libraries, see Mac OS X Server version 10.5: MySQL libraries + available for download (http://support.apple.com/kb/TA25017). + Alternatively, you can ignore the bundled MySQL server and install + MySQL from the package or tarball installation. + + For more information on managing the bundled MySQL instance in Mac + OS X Server 10.5, see Mac OS X Server: Web Technologies + Administration For Version 10.5 Leopard + (http://images.apple.com/server/macosx/docs/Web_Technologies_Admin + _v10.5.pdf). For more information on managing the bundled MySQL + instance in Mac OS X Server 10.6, see Mac OS X Server: Web + Technologies Administration Version 10.6 Snow Leopard + (http://manuals.info.apple.com/en_US/WebTech_v10.6.pdf). + +2.7.5. MySQL Installation on Mac OS X Notes + + You should keep the following issues and notes in mind: + + * The default location for the MySQL Unix socket is different on + Mac OS X and Mac OS X Server depending on the installation + type you chose. The default locations by installation are as + follows: + + Package Installer from MySQL /tmp/mysql.sock + Tarball from MySQL /tmp/mysql.sock + MySQL Bundled with Mac OS X Server /var/mysql/mysql.sock + To prevent issues, you should either change the configuration + of the socket used within your application (for example, + changing php.ini), or you should configure the socket location + using a MySQL configuration file and the socket option. For + more information, see Section 5.1.2, "Server Command Options." + + * You may need (or want) to create a specific mysql user to own + the MySQL directory and data. On Mac OS X 10.4 and lower you + can do this by using the Netinfo Manager application, located + within the Utilities folder within the Applications folder. On + Mac OS X 10.5 and later you can do this through the Directory + Utility. From Mac OS X 10.5 and later (including Mac OS X + Server 10.5) the mysql should already exist. For use in single + user mode, an entry for _mysql (note the underscore prefix) + should already exist within the system /etc/passwd file. + + * Due to a bug in the Mac OS X package installer, you may see + this error message in the destination disk selection dialog: +You cannot install this software on this disk. (null) + If this error occurs, simply click the Go Back button once to + return to the previous screen. Then click Continue to advance + to the destination disk selection again, and you should be + able to choose the destination disk correctly. We have + reported this bug to Apple and it is investigating this + problem. + + * Because the MySQL package installer installs the MySQL + contents into a version and platform specific directory, you + can use this to upgrade and migrate your database between + versions. You will need to either copy the data directory from + the old version to the new version, or alternatively specify + an alternative datadir value to set location of the data + directory. + + * You might want to add aliases to your shell's resource file to + make it easier to access commonly used programs such as mysql + and mysqladmin from the command line. The syntax for bash is: +alias mysql=/usr/local/mysql/bin/mysql +alias mysqladmin=/usr/local/mysql/bin/mysqladmin + For tcsh, use: +alias mysql /usr/local/mysql/bin/mysql +alias mysqladmin /usr/local/mysql/bin/mysqladmin + Even better, add /usr/local/mysql/bin to your PATH environment + variable. You can do this by modifying the appropriate startup + file for your shell. For more information, see Section 4.2.1, + "Invoking MySQL Programs." + + * After you have copied over the MySQL database files from the + previous installation and have successfully started the new + server, you should consider removing the old installation + files to save disk space. Additionally, you should also remove + older versions of the Package Receipt directories located in + /Library/Receipts/mysql-VERSION.pkg. + +2.8. Installing MySQL on Solaris + + To obtain a binary MySQL distribution for Solaris in tarball or + PKG format, http://dev.mysql.com/downloads/mysql/5.1.html. + + If you install MySQL using a binary tarball distribution on + Solaris, you may run into trouble even before you get the MySQL distribution unpacked, as the Solaris tar cannot handle long file names. This means that you may see errors when you try to unpack MySQL. @@ -7504,30 +6353,45 @@ CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors \ If this occurs, you must use GNU tar (gtar) to unpack the distribution. - Sun native threads work only on Solaris 2.5 and higher. For - Solaris 2.4 and earlier, MySQL automatically uses MIT-pthreads. - See Section 2.10.5, "MIT-pthreads Notes." + You can install MySQL on Solaris using a binary package in PKG + format instead of the binary tarball distribution. Before + installing using the binary PKG format, you should create the + mysql user and group, for example: +groupadd mysql +useradd -g mysql mysql - If you get the following error from configure, it means that you - have something wrong with your compiler installation: -checking for restartable system calls... configure: error can not -run test programs while cross compiling + Some basic PKG-handling commands follow: - In this case, you should upgrade your compiler to a newer version. - You may also be able to solve this problem by inserting the - following row into the config.cache file: -ac_cv_sys_restartable_syscalls=${ac_cv_sys_restartable_syscalls='no'} + * To add a package: +pkgadd -d package_name.pkg - If you are using Solaris on a SPARC, the recommended compiler is - gcc 2.95.2 or 3.2. You can find this at http://gcc.gnu.org/. Note - that gcc 2.8.1 does not work reliably on SPARC. + * To remove a package: +pkgrm package_name - The recommended configure line when using gcc 2.95.2 is: -CC=gcc CFLAGS="-O3" \ -CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" - \ -./configure --prefix=/usr/local/mysql --with-low-memory \ - --enable-assembler + * To get a full list of installed packages: +pkginfo + + * To get detailed information for a package: +pkginfo -l package_name + + * To list the files belonging to a package: +pkgchk -v package_name + + * To get packaging information for an arbitrary file: +pkgchk -l -p file_name + +2.8.1. Solaris Notes + + For information about installing MySQL on Solaris using PKG + distributions, see Section 2.8, "Installing MySQL on Solaris." + + On Solaris, you may run into trouble even before you get the MySQL + distribution unpacked, as the Solaris tar cannot handle long file + names. This means that you may see errors when you try to unpack + MySQL. + + If this occurs, you must use GNU tar (gtar) to unpack the + distribution. If you have an UltraSPARC system, you can get 4% better performance by adding -mcpu=v8 -Wa,-xarch=v8plusa to the CFLAGS @@ -7565,44 +6429,6 @@ CXX=CC CXXFLAGS="-noex -mt -xarch=v9" ASFLAGS="-xarch=v9" \ If you get a problem with fdatasync or sched_yield, you can fix this by adding LIBS=-lrt to the configure line - For compilers older than WorkShop 5.3, you might have to edit the - configure script. Change this line: -#if !defined(__STDC__) || __STDC__ != 1 - - To this: -#if !defined(__STDC__) - - If you turn on __STDC__ with the -Xc option, the Sun compiler - can't compile with the Solaris pthread.h header file. This is a - Sun bug (broken compiler or broken include file). - - If mysqld issues the following error message when you run it, you - have tried to compile MySQL with the Sun compiler without enabling - the -mt multi-thread option: -libc internal error: _rmutex_unlock: rmutex not held - - Add -mt to CFLAGS and CXXFLAGS and recompile. - - If you are using the SFW version of gcc (which comes with Solaris - 8), you must add /opt/sfw/lib to the environment variable - LD_LIBRARY_PATH before running configure. - - If you are using the gcc available from sunfreeware.com, you may - have many problems. To avoid this, you should recompile gcc and - GNU binutils on the machine where you are running them. - - If you get the following error when compiling MySQL with gcc, it - means that your gcc is not configured for your version of Solaris: -shell> gcc -O3 -g -O2 -DDBUG_OFF -o thr_alarm ... -./thr_alarm.c: In function `signal_hand': -./thr_alarm.c:556: too many arguments to function `sigwait' - - The proper thing to do in this case is to get the newest version - of gcc and compile it with your current gcc compiler. At least for - Solaris 2.5, almost all binary versions of gcc have old, unusable - include files that break all programs that use threads, and - possibly other programs as well. - Solaris does not provide static versions of all system libraries (libpthreads and libdl), so you cannot compile MySQL with --static. If you try to do so, you get one of the following @@ -7651,102 +6477,276 @@ Error in accept: Protocol error You might try starting the server with the --back_log=50 option as a workaround for this. (Use -O back_log=50 before MySQL 4.) - Solaris doesn't support core files for setuid() applications, so - you can't get a core file from mysqld if you are using the --user - option. + To configure the generation of core files on Solaris you should + use the coreadm command. Because of the security implications of + generating a core on a setuid() application, by default, Solaris + does not support core files on setuid() programs. However, you can + modify this behavior using coreadm. If you enable setuid() core + files for the current user, they will be generated using the mode + 600 and owned by the superuser. -2.13.3.1. Solaris 2.7/2.8 Notes +2.9. Installing MySQL on i5/OS - Normally, you can use a Solaris 2.6 binary on Solaris 2.7 and 2.8. - Most of the Solaris 2.6 issues also apply for Solaris 2.7 and 2.8. + The i5/OS POWER MySQL package was created in cooperation with IBM. + MySQL works within the Portable Application Solution Environment + (PASE) on the System i series of hardware and will also provide + database services for the Zend Core for i5/OS. - MySQL should be able to detect new versions of Solaris - automatically and enable workarounds for the following problems. + MySQL for i5/OS is provided both as a tar file and as a save file + (.savf) package that can be downloaded and installed directly + without any additional installation steps required. To install + MySQL using the tar file, see Section 2.2, "Installing MySQL from + Generic Binaries on Unix/Linux." - Solaris 2.7 / 2.8 has some bugs in the include files. You may see - the following error when you use gcc: -/usr/include/widec.h:42: warning: `getwc' redefined -/usr/include/wchar.h:326: warning: this is the location of the previo -us -definition + MySQL is only supported on i5/OS V5R4 or later releases. The i5/OS + PASE must be installed for MySQL to operate. You must be able to + login as a user in *SECOFR class. - If this occurs, you can fix the problem by copying - /usr/include/widec.h to .../lib/gcc-lib/os/gcc-version/include and - changing line 41 from this: -#if !defined(lint) && !defined(__lint) + You should the installation notes and tips for i5/OS before + starting installation. See i5/OS Installation Notes. - To this: -#if !defined(lint) && !defined(__lint) && !defined(getwc) + Before Installation: - Alternatively, you can edit /usr/include/widec.h directly. Either - way, after you make the fix, you should remove config.cache and - run configure again. +Note - If you get the following errors when you run make, it is because - configure didn't detect the curses.h file (probably because of the - error in /usr/include/widec.h): -In file included from mysql.cc:50: -/usr/include/term.h:1060: syntax error before `,' -/usr/include/term.h:1081: syntax error before `;' + The installation package will use an existing configuration if you + have previously installed MySQL (which is identified by looking + for the file /etc/my.cnf). The values for the data directory + (DATADIR) and owner of the MySQL files (USRPRF) specified during + the installation will be ignored, and the values determined from + the /etc/my.cnf will be used instead. - The solution to this problem is to do one of the following: + If you want to change these parameters during a new install, you + should temporarily rename /etc/my.cnf, install MySQL using the new + parameters you want to use, and then merge your previous + /etc/my.cnf configuration settings with the new /etc/my.cnf file + that is created during installation. - 1. Configure with CFLAGS=-DHAVE_CURSES_H CXXFLAGS=-DHAVE_CURSES_H - ./configure. + * You must have a user profile with PASE with suitable + privileges. The user should be within the *SECOFR class, such + as the QSECOFR user ID. You can use the WRKUSRPRF command to + check your user profile. - 2. Edit /usr/include/widec.h as indicated in the preceding - discussion and re-run configure. + * For network connections to MySQL, you must have TCP/IP + enabled. You should also check the following: - 3. Remove the #define HAVE_TERM line from the config.h file and - run make again. + + Ensure that a name has defined for the system. Run the + Configure TCP/IP (CFGTCP) command and select option 12 + (Change TCP/IP domain information) to display this + setting. Make sure that a value is listed in the Host + name field. - If your linker cannot find -lz when linking client programs, the - problem is probably that your libz.so file is installed in - /usr/local/lib. You can fix this problem by one of the following - methods: + + Make sure that the system has a loopback entry which + represents the localhost or 127.0.0.1. - * Add /usr/local/lib to LD_LIBRARY_PATH. + + Ensure that the IP address of the IBM i machine is mapped + correctly to the host name. - * Add a link to libz.so from /lib. + To install MySQL on i5/OS, follow these steps: - * If you are using Solaris 8, you can install the optional zlib - from your Solaris 8 CD distribution. + 1. On the System i machine, create a save file that will be used + to receive the downloaded installation save file. The file + should be located within the General Purpose Library (QGPL): +CRTSAVF FILE(QGPL/MYSQLINST) TESXT('MySQL Save file') - * Run configure with the --with-named-z-libs=no option when - building MySQL. + 2. Download the MySQL installation save file in 32-bit + (mysql-5.1.39-i5os-power-32bit.savf) or 64-bit + (mysql-5.1.39-i5os-power-64bit.savf) from MySQL Downloads + (http://dev.mysql.com/downloads). -2.13.3.2. Solaris x86 Notes + 3. You need to FTP the downloaded .savf file directly into the + QGPL/MYSQLINST file on the System i server. You can do this + through FTP using the following steps after logging in to the + System i machine: +ftp> bin +ftp> cd qgpl +ftp> put mysql-5.1.39-i5os-power.savf mysqlinst + + 4. Log into the System i server using a user in the *SECOFR + class, such as the QSECOFR user ID. - On Solaris 8 on x86, mysqld dumps core if you remove the debug - symbols using strip. + 5. You need to restore the installation library stored in the + .savf save file: +RSTLIB MYSQLINST DEV(*SAVF) SAVF(QGPL/MYSQLINST) MBROPT(*ALL) ALWOBJD +IF(*ALL) - If you are using gcc on Solaris x86 and you experience problems - with core dumps under load, you should use the following configure - command: -CC=gcc CFLAGS="-O3 -fomit-frame-pointer -DHAVE_CURSES_H" \ -CXX=gcc \ -CXXFLAGS="-O3 -fomit-frame-pointer -felide-constructors \ - -fno-exceptions -fno-rtti -DHAVE_CURSES_H" \ -./configure --prefix=/usr/local/mysql +Note + You can ignore the security changes-type message at the bottom + of the installation panel. - This avoids problems with the libstdc++ library and with C++ - exceptions. + 6. Once you have finished restoring the MYSQLINST library, check + that all the necessary objects for installation are on the + system by using the Display Library (DSPLIB) command: +DSPLIB LIB(MYSQLINST) - If this doesn't help, you should compile a debug version and run - it with a trace file or under gdb. See MySQL Internals: Porting - (http://forge.mysql.com/wiki/MySQL_Internals_Porting). + 7. You need to execute the installation command, + MYSQLINST/INSMYSQL. You can specify three parameter settings + during installation: -2.13.4. BSD Notes + + DIR('/QOpenSys/usr/local/mysql') sets the installation + location for the MySQL files. The directory will be + created if it does not already exist. - This section provides information about using MySQL on variants of - BSD Unix. + + DATADIR('/QOpenSys/usr/local/mysql/data') sets the + location of the directory that will be used to store the + database files and binary logs. The default setting is + /QOpenSys/usr/local/mysql/data. Note that if the + installer detects an existing installation (due to the + existence of /etc/my.cnf), then the existing setting will + be used instead of the default. + + + USRPRF(MYSQL) sets the user profile that will own the + files that are installed. The profile will be created if + it does not already exist. + +Note + You should choose an appropriate user for using the MySQL + server installation. The user will be used whenever you + need to do any administration on the MySQL server. + Once you have set the appropriate parameters, you can begin + the installation. + The installation copies all the necessary files into a + directory matching the DIR configuration value; sets the + ownership on those files, sets up the MySQL environment and + creates the MySQL configuration file (in /etc/my.cnf) + completing all the steps in a typical binary installation + process automatically. If this is a new installation of MySQL, + or if the installer detects that this is a new version + (because the /etc/my.cnf file does not exist), then the + initial core MySQL databases will also be created during + installation. + Once the installation has been completed, you will get a + notice advising you to set the password for the root user. For + more information, Section 2.13, "Post-Installation Setup and + Testing." + + 8. Once the installation has completed, you can delete the + installation file: +DLTLIB LIB(MYSQLINST) + + Upgrading an existing MySQL instance + + You need to execute the upgrade command, MYSQLINST/UPGMYSQL. You + must specify 6 parameters to perform an upgrade: + + * DIR('/QOpenSys/usr/local/') --- sets the installation location + for the MySQL files. The directory will be created if it does + not already exist. This is the directory that the MySQL server + will be installed into, inside a directory with a name + matching the version and release. For example if installing + MySQL 5.1.39 with the DIR set to /QOpenSys/usr/local/ would + result in /QOpenSys/usr/local/mysql-5.1.39-i5os-power64 and a + symbolic link to this directory will be created in + /QOpenSys/usr/local/mysql. + + * DATADIR('/QOpenSys/mysql/data') --- sets the location of the + directory that will be upgraded. + + * USRPRF('MYSQL') --- sets the user profile that will own the + files that are installed. The profile will be created if it + does not already exist; if it is created as part of the + upgrade process, it will be disabled initially. You may wish + to enable this user profile so that it can be used to start + the MySQL server later. It is best practice to use the one + previously created during the first installation. + + * MYSQLUSR('root user') --- any user account in the current + MySQL server with SUPER privileges. + + * PASSWORD('root user password') --- the password for the above + account. This is necessary as the upgrade starts the MySQL + server to upgrade the tables and the password is need to be + able to shutdown the MySQL server. + + * CURINST('path to previous install') --- the full path to the + installation that is being upgraded. For example an + installation in /QOpenSys/usr/local/ will be + /QOpenSys/usr/local/msyql-5.1.30-i5os-power64. Failure to + specify this option may result in corruption of your existing + data files. + + For example: +MYSQLINST/UPGMYSQL DIR('/QOpenSys/usr/local/') DATADIR('/QOpenSys/mys +ql/data') » + USERPRF(MYSQL) MYSQLUSR('root') PASSWORD('root') CURINST('/QOpen +Sys/usr/local/mysql-5.1.30-i5os-power64') + + You should receive a Program Message indicating UPGRADE + SUCCESSFUL! upon completion or an error message if there is a + problem.You can view the upgrade programs progression and the + error in the text file upgrade.log in the installation directory. + + To start MySQL: + + 1. Log into the System i server using the user profile create or + specified during installation. By default, this is MYSQL. + +Note + You should start mysqld_safe using a user that in the PASE + environment has the id=0 (the equivalent of the standard Unix + root user). If you do not use a user with this ID then the + system will be unable to change the user when executing mysqld + as set using --user option. If this happens, mysqld may be + unable to read the files located within the MySQL data + directory and the execution will fail. + + 2. Enter the PASE environment using call qp2term. + + 3. Start the MySQL server by changing to the installation + directory and running mysqld_safe, specifying the user name + used to install the server. The installer conveniently + installs a symbolic link to the installation directory + (mysql-5.0.42-i5os-power-32bit) as /opt/mysql/mysql: +> cd /opt/mysql/mysql +> bin/mysqld_safe --user=mysql & + You should see a message similar to the following: +Starting mysqld daemon with databases » + from /opt/mysql/mysql-enterprise-5.0.42-i5os-power-32bit/data + + If you are having problems starting MySQL server, see Section + 2.13.1.3, "Starting and Troubleshooting the MySQL Server." + + To stop MySQL: + + 1. Log into the System i server using the user profile create or + specified during installation. By default, this is MYSQL. + + 2. Enter the PASE environment using call qp2term. + + 3. Stop the MySQL server by changing into the installation + directory and running mysqladmin, specifying the user name + used to install the server: +> cd /opt/mysql/mysql +> bin/mysqladmin -u root shutdown + If the session that you started and stopped MySQL are the + same, you may get the log output from mysqld: + STOPPING server from pid file » + /opt/mysql/mysql-enterprise-5.0.42-i5os-power-32bit/data/I5DBX.R +CHLAND.IBM.COM.pid + 070718 10:34:20 mysqld ended + If the sessions used to start and stop MySQL are different, + you will not receive any confirmation of the shutdown. + + Note and tips + + * A problem has been identified with the installation process on + DBCS systems. If you are having problems install MySQL on a + DBCS system, you need to change your job's coded character set + identifier (CSSID) to 37 (EBCDIC) before executing the install + command, INSMYSQL. To do this, determine your existing CSSID + (using DSPJOB and selecting option 2), execute CHGJOB + CSSID(37), run INSMYSQL to install MySQL and then execute + CHGJOB again with your original CSSID. -2.13.4.1. FreeBSD Notes + * If you want to use the Perl scripts that are included with + MySQL, you need to download the iSeries Tools for Developers + (5799-PTL). See + http://www-03.ibm.com/servers/enable/site/porting/tools/. - FreeBSD 4.x or newer is recommended for running MySQL, because the - thread package is much more integrated. To get a secure and stable - system, you should use only FreeBSD kernels that are marked - -RELEASE. +2.10. Installing MySQL on FreeBSD + + This section provides information about using MySQL on variants of + FreeBSD Unix. The easiest (and preferred) way to install MySQL is to use the mysql-server and mysql-client ports available at @@ -7766,37 +6766,6 @@ CXXFLAGS="-O3 -fomit-frame-pointer -felide-constructors \ * The ability to use pkg_delete to remove MySQL if you no longer want it on your machine. - It is recommended you use MIT-pthreads on FreeBSD 2.x, and native - threads on FreeBSD 3 and up. It is possible to run with native - threads on some late 2.2.x versions, but you may encounter - problems shutting down mysqld. - - Unfortunately, certain function calls on FreeBSD are not yet fully - thread-safe. Most notably, this includes the gethostbyname() - function, which is used by MySQL to convert host names into IP - addresses. Under certain circumstances, the mysqld process - suddenly causes 100% CPU load and is unresponsive. If you - encounter this problem, try to start MySQL using the - --skip-name-resolve option. - - Alternatively, you can link MySQL on FreeBSD 4.x against the - LinuxThreads library, which avoids a few of the problems that the - native FreeBSD thread implementation has. For a very good - comparison of LinuxThreads versus native threads, see Jeremy - Zawodny's article FreeBSD or Linux for your MySQL Server? at - http://jeremy.zawodny.com/blog/archives/000697.html. - - Known problem when using LinuxThreads on FreeBSD is: - - * The connection times (wait_timeout, interactive_timeout and - net_read_timeout) values are not honored. The symptom is that - persistent connections can hang for a very long time without - getting closed down and that a 'kill' for a thread will not - take affect until the thread does it a new command - This is probably a signal handling problem in the thread - library where the signal doesn't break a pending read. This is - supposed to be fixed in FreeBSD 5.0 - The MySQL build process requires GNU make (gmake) to work. If GNU make is not available, you must install it first before compiling MySQL. @@ -7813,23 +6782,8 @@ cd /usr/local/mysql bin/mysql_install_db --user=mysql bin/mysqld_safe & - If you notice that configure uses MIT-pthreads, you should read - the MIT-pthreads notes. See Section 2.10.5, "MIT-pthreads Notes." - - If you get an error from make install that it can't find - /usr/include/pthreads, configure didn't detect that you need - MIT-pthreads. To fix this problem, remove config.cache, and then - re-run configure with the --with-mit-threads option. - - Be sure that your name resolver setup is correct. Otherwise, you - may experience resolver delays or failures when connecting to - mysqld. Also make sure that the localhost entry in the /etc/hosts - file is correct. The file should start with a line similar to - this: -127.0.0.1 localhost localhost.your.domain - FreeBSD is known to have a very low default file handle limit. See - Section B.1.2.18, "'File' Not Found and Similar Errors." Start the + Section B.5.2.18, "'File' Not Found and Similar Errors." Start the server by using the --open-files-limit option for mysqld_safe, or raise the limits for the mysqld user in /etc/login.conf and rebuild it with cap_mkdb /etc/login.conf. Also be sure that you @@ -7837,15 +6791,11 @@ bin/mysqld_safe & you are not using the default (use chpass mysqld-user-name). See Section 4.3.2, "mysqld_safe --- MySQL Server Startup Script." - FreeBSD limits the size of a process to 512MB, even if you have - much more RAM available on the system. So you may get an error - such as this: -Out of memory (Needed 16391 bytes) - In current versions of FreeBSD (at least 4.x and greater), you may - increase this limit by adding the following entries to the - /boot/loader.conf file and rebooting the machine (these are not - settings that can be changed at run time with the sysctl command): + increase the limit on the amount of memory available for a process + by adding the following entries to the /boot/loader.conf file and + rebooting the machine (these are not settings that can be changed + at run time with the sysctl command): kern.maxdsiz="1073741824" # 1GB kern.dfldsiz="1073741824" # 1GB kern.maxssiz="134217728" # 128MB @@ -7858,135 +6808,7 @@ kern.maxssiz="134217728" # 128MB If you get problems with the current date in MySQL, setting the TZ variable should help. See Section 2.14, "Environment Variables." -2.13.4.2. NetBSD Notes - - To compile on NetBSD, you need GNU make. Otherwise, the build - process fails when make tries to run lint on C++ files. - -2.13.4.3. OpenBSD 2.5 Notes - - On OpenBSD 2.5, you can compile MySQL with native threads with the - following options: -CFLAGS=-pthread CXXFLAGS=-pthread ./configure --with-mit-threads=no - -2.13.4.4. BSD/OS Version 2.x Notes - - If you get the following error when compiling MySQL, your ulimit - value for virtual memory is too low: -item_func.h: In method -`Item_func_ge::Item_func_ge(const Item_func_ge &)': -item_func.h:28: virtual memory exhausted -make[2]: *** [item_func.o] Error 1 - - Try using ulimit -v 80000 and run make again. If this doesn't work - and you are using bash, try switching to csh or sh; some BSDI - users have reported problems with bash and ulimit. - - If you are using gcc, you may also use have to use the - --with-low-memory flag for configure to be able to compile - sql_yacc.cc. - - If you get problems with the current date in MySQL, setting the TZ - variable should help. See Section 2.14, "Environment Variables." - -2.13.4.5. BSD/OS Version 3.x Notes - - Upgrade to BSD/OS 3.1. If that is not possible, install BSDIpatch - M300-038. - - Use the following command when configuring MySQL: -env CXX=shlicc++ CC=shlicc2 \ -./configure \ - --prefix=/usr/local/mysql \ - --localstatedir=/var/mysql \ - --without-perl \ - --with-unix-socket-path=/var/mysql/mysql.sock - - The following is also known to work: -env CC=gcc CXX=gcc CXXFLAGS=-O3 \ -./configure \ - --prefix=/usr/local/mysql \ - --with-unix-socket-path=/var/mysql/mysql.sock - - You can change the directory locations if you wish, or just use - the defaults by not specifying any locations. - - If you have problems with performance under heavy load, try using - the --skip-thread-priority option to mysqld. This runs all threads - with the same priority. On BSDI 3.1, this gives better - performance, at least until BSDI fixes its thread scheduler. - - If you get the error virtual memory exhausted while compiling, you - should try using ulimit -v 80000 and running make again. If this - doesn't work and you are using bash, try switching to csh or sh; - some BSDI users have reported problems with bash and ulimit. - -2.13.4.6. BSD/OS Version 4.x Notes - - BSDI 4.x has some thread-related bugs. If you want to use MySQL on - this, you should install all thread-related patches. At least - M400-023 should be installed. - - On some BSDI 4.x systems, you may get problems with shared - libraries. The symptom is that you can't execute any client - programs, for example, mysqladmin. In this case, you need to - reconfigure not to use shared libraries with the --disable-shared - option to configure. - - Some customers have had problems on BSDI 4.0.1 that the mysqld - binary after a while can't open tables. This occurs because some - library/system-related bug causes mysqld to change current - directory without having asked for that to happen. - - The fix is to either upgrade MySQL to at least version 3.23.34 or, - after running configure, remove the line #define HAVE_REALPATH - from config.h before running make. - - Note that this means that you can't symbolically link a database - directories to another database directory or symbolic link a table - to another database on BSDI. (Making a symbolic link to another - disk is okay). - -2.13.5. Other Unix Notes - -2.13.5.1. HP-UX Version 10.20 Notes - - If you install MySQL using a binary tarball distribution on HP-UX, - you may run into trouble even before you get the MySQL - distribution unpacked, as the HP-UX tar cannot handle long file - names. This means that you may see errors when you try to unpack - MySQL. - - If this occurs, you must use GNU tar (gtar) to unpack the - distribution. - - There are a couple of small problems when compiling MySQL on - HP-UX. Use gcc instead of the HP-UX native compiler, because gcc - produces better code. - - Use gcc 2.95 on HP-UX. Don't use high optimization flags (such as - -O6) because they may not be safe on HP-UX. - - The following configure line should work with gcc 2.95: -CFLAGS="-I/opt/dce/include -fpic" \ -CXXFLAGS="-I/opt/dce/include -felide-constructors -fno-exceptions \ --fno-rtti" \ -CXX=gcc \ -./configure --with-pthread \ - --with-named-thread-libs='-ldce' \ - --prefix=/usr/local/mysql --disable-shared - - The following configure line should work with gcc 3.1: -CFLAGS="-DHPUX -I/opt/dce/include -O3 -fPIC" CXX=gcc \ -CXXFLAGS="-DHPUX -I/opt/dce/include -felide-constructors \ - -fno-exceptions -fno-rtti -O3 -fPIC" \ -./configure --prefix=/usr/local/mysql \ - --with-extra-charsets=complex --enable-thread-safe-client \ - --enable-local-infile --with-pthread \ - --with-named-thread-libs=-ldce --with-lib-ccflags=-fPIC - --disable-shared - -2.13.5.2. HP-UX Version 11.x Notes +2.11. Installing MySQL on HP-UX If you install MySQL using a binary tarball distribution on HP-UX, you may run into trouble even before you get the MySQL @@ -8065,7 +6887,7 @@ Try gcc. See the Installation chapter in the Reference Manual. 11. If you encounter problems, you should be sure to check your HP-UX patch level. -2.13.5.3. IBM-AIX notes +2.12. Installing MySQL on AIX Automatic detection of xlC is missing from Autoconf, so a number of variables need to be set before running configure. The @@ -8127,6 +6949,9 @@ CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti" \ This gives you a machine type and a machine model you can use to determine what type of CPU you have. + If you have problems with threads on AIX 5.3, you should upgrade + AIX 5.3 to technology level 7 (5300-07). + If you have problems with signals (MySQL dies unexpectedly under high load), you may have found an OS bug with threads and signals. In this case, you can tell MySQL not to use signals by configuring @@ -8211,752 +7036,904 @@ fined extern int endwin (void); extern int getcurx (WINDOW *); -2.13.5.4. SunOS 4 Notes - - On SunOS 4, MIT-pthreads is needed to compile MySQL. This in turn - means you need GNU make. - - Some SunOS 4 systems have problems with dynamic libraries and - libtool. You can use the following configure line to avoid this - problem: -./configure --disable-shared --with-mysqld-ldflags=-all-static - - When compiling readline, you may get warnings about duplicate - defines. These can be ignored. - - When compiling mysqld, there are some implicit declaration of - function warnings. These can be ignored. - -2.13.5.5. Alpha-DEC-UNIX Notes (Tru64) - - If you are using egcs 1.1.2 on Digital Unix, you should upgrade to - gcc 2.95.2, because egcs on DEC has some serious bugs! - - When compiling threaded programs under Digital Unix, the - documentation recommends using the -pthread option for cc and cxx - and the -lmach -lexc libraries (in addition to -lpthread). You - should run configure something like this: -CC="cc -pthread" CXX="cxx -pthread -O" \ -./configure --with-named-thread-libs="-lpthread -lmach -lexc -lc" - - When compiling mysqld, you may see a couple of warnings like this: -mysqld.cc: In function void handle_connections()': -mysqld.cc:626: passing long unsigned int *' as argument 3 of -accept(int,sockadddr *, int *)' - - You can safely ignore these warnings. They occur because configure - can detect only errors, not warnings. - - If you start the server directly from the command line, you may - have problems with it dying when you log out. (When you log out, - your outstanding processes receive a SIGHUP signal.) If so, try - starting the server like this: -nohup mysqld [options] & - - nohup causes the command following it to ignore any SIGHUP signal - sent from the terminal. Alternatively, start the server by running - mysqld_safe, which invokes mysqld using nohup for you. See Section - 4.3.2, "mysqld_safe --- MySQL Server Startup Script." - - If you get a problem when compiling mysys/get_opt.c, just remove - the #define _NO_PROTO line from the start of that file. - - If you are using Compaq's CC compiler, the following configure - line should work: -CC="cc -pthread" -CFLAGS="-O4 -ansi_alias -ansi_args -fast -inline speed \ - -speculate all -arch host" -CXX="cxx -pthread" -CXXFLAGS="-O4 -ansi_alias -ansi_args -fast -inline speed \ - -speculate all -arch host -noexceptions -nortti" -export CC CFLAGS CXX CXXFLAGS -./configure \ - --prefix=/usr/local/mysql \ - --with-low-memory \ - --enable-large-files \ - --enable-shared=yes \ - --with-named-thread-libs="-lpthread -lmach -lexc -lc" -gnumake - - If you get a problem with libtool when compiling with shared - libraries as just shown, when linking mysql, you should be able to - get around this by issuing these commands: -cd mysql -/bin/sh ../libtool --mode=link cxx -pthread -O3 -DDBUG_OFF \ - -O4 -ansi_alias -ansi_args -fast -inline speed \ - -speculate all \ -arch host -DUNDEF_HAVE_GETHOSTBYNAME_R \ - -o mysql mysql.o readline.o sql_string.o completion_hash.o \ - ../readline/libreadline.a -lcurses \ - ../libmysql/.libs/libmysqlclient.so -lm -cd .. -gnumake -gnumake install -scripts/mysql_install_db - -2.13.5.6. Alpha-DEC-OSF/1 Notes - - If you have problems compiling and have DEC CC and gcc installed, - try running configure like this: -CC=cc CFLAGS=-O CXX=gcc CXXFLAGS=-O3 \ -./configure --prefix=/usr/local/mysql - - If you get problems with the c_asm.h file, you can create and use - a 'dummy' c_asm.h file with: -touch include/c_asm.h -CC=gcc CFLAGS=-I./include \ -CXX=gcc CXXFLAGS=-O3 \ -./configure --prefix=/usr/local/mysql - - Note that the following problems with the ld program can be fixed - by downloading the latest DEC (Compaq) patch kit from: - http://ftp.support.compaq.com/public/unix/. - - On OSF/1 V4.0D and compiler "DEC C V5.6-071 on Digital Unix V4.0 - (Rev. 878)," the compiler had some strange behavior (undefined asm - symbols). /bin/ld also appears to be broken (problems with _exit - undefined errors occurring while linking mysqld). On this system, - we have managed to compile MySQL with the following configure - line, after replacing /bin/ld with the version from OSF 4.0C: -CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql - - With the Digital compiler "C++ V6.1-029," the following should - work: -CC=cc -pthread -CFLAGS=-O4 -ansi_alias -ansi_args -fast -inline speed \ - -speculate all -arch host -CXX=cxx -pthread -CXXFLAGS=-O4 -ansi_alias -ansi_args -fast -inline speed \ - -speculate all -arch host -noexceptions -nortti -export CC CFLAGS CXX CXXFLAGS -./configure --prefix=/usr/mysql/mysql \ - --with-mysqld-ldflags=-all-static --disable-shared \ - --with-named-thread-libs="-lmach -lexc -lc" - - In some versions of OSF/1, the alloca() function is broken. Fix - this by removing the line in config.h that defines 'HAVE_ALLOCA'. - - The alloca() function also may have an incorrect prototype in - /usr/include/alloca.h. This warning resulting from this can be - ignored. - - configure uses the following thread libraries automatically: - --with-named-thread-libs="-lpthread -lmach -lexc -lc". - - When using gcc, you can also try running configure like this: -CFLAGS=-D_PTHREAD_USE_D4 CXX=gcc CXXFLAGS=-O3 ./configure ... +2.13. Post-Installation Setup and Testing - If you have problems with signals (MySQL dies unexpectedly under - high load), you may have found an OS bug with threads and signals. - In this case, you can tell MySQL not to use signals by configuring - with: -CFLAGS=-DDONT_USE_THR_ALARM \ -CXXFLAGS=-DDONT_USE_THR_ALARM \ -./configure ... + After installing MySQL, there are some issues that you should + address. For example, on Unix, you should initialize the data + directory and create the MySQL grant tables. On all platforms, an + important security concern is that the initial accounts in the + grant tables have no passwords. You should assign passwords to + prevent unauthorized access to the MySQL server. Optionally, you + can create time zone tables to enable recognition of named time + zones. - This does not affect the performance of MySQL, but has the side - effect that you can't kill clients that are "sleeping" on a - connection with mysqladmin kill or mysqladmin shutdown. Instead, - the client dies when it issues its next command. + The following sections include post-installation procedures that + are specific to Windows systems and to Unix systems. Another + section, Section 2.13.1.3, "Starting and Troubleshooting the MySQL + Server," applies to all platforms; it describes what to do if you + have trouble getting the server to start. Section 2.13.2, + "Securing the Initial MySQL Accounts," also applies to all + platforms. You should follow its instructions to make sure that + you have properly protected your MySQL accounts by assigning + passwords to them. - With gcc 2.95.2, you may encounter the following compile error: -sql_acl.cc:1456: Internal compiler error in `scan_region', -at except.c:2566 -Please submit a full bug report. - - To fix this, you should change to the sql directory and do a - cut-and-paste of the last gcc line, but change -O3 to -O0 (or add - -O0 immediately after gcc if you don't have any -O option on your - compile line). After this is done, you can just change back to the - top-level directory and run make again. - -2.13.5.7. SGI Irix Notes - - As of MySQL 5.0, we don't provide binaries for Irix any more. - - If you are using Irix 6.5.3 or newer, mysqld is able to create - threads only if you run it as a user that has CAP_SCHED_MGT - privileges (such as root) or give the mysqld server this privilege - with the following shell command: -chcap "CAP_SCHED_MGT+epi" /opt/mysql/libexec/mysqld - - You may have to undefine some symbols in config.h after running - configure and before compiling. - - In some Irix implementations, the alloca() function is broken. If - the mysqld server dies on some SELECT statements, remove the lines - from config.h that define HAVE_ALLOC and HAVE_ALLOCA_H. If - mysqladmin create doesn't work, remove the line from config.h that - defines HAVE_READDIR_R. You may have to remove the HAVE_TERM_H - line as well. - - SGI recommends that you install all the patches on this page as a - set: - http://support.sgi.com/surfzone/patches/patchset/6.2_indigo.rps.ht - ml - - At the very minimum, you should install the latest kernel rollup, - the latest rld rollup, and the latest libc rollup. - - You definitely need all the POSIX patches on this page, for - pthreads support: - - http://support.sgi.com/surfzone/patches/patchset/6.2_posix.rps.htm - l - - If you get the something like the following error when compiling - mysql.cc: -"/usr/include/curses.h", line 82: error(1084): -invalid combination of type - - Type the following in the top-level directory of your MySQL source - tree: -extra/replace bool curses_bool < /usr/include/curses.h > include/curs -es.h -make - - There have also been reports of scheduling problems. If only one - thread is running, performance is slow. Avoid this by starting - another client. This may lead to a two-to-tenfold increase in - execution speed thereafter for the other thread. This is a poorly - understood problem with Irix threads; you may have to improvise to - find solutions until this can be fixed. - - If you are compiling with gcc, you can use the following configure - command: -CC=gcc CXX=gcc CXXFLAGS=-O3 \ -./configure --prefix=/usr/local/mysql --enable-thread-safe-client \ - --with-named-thread-libs=-lpthread - - On Irix 6.5.11 with native Irix C and C++ compilers ver. 7.3.1.2, - the following is reported to work -CC=cc CXX=CC CFLAGS='-O3 -n32 -TARG:platform=IP22 -I/usr/local/includ -e \ --L/usr/local/lib' CXXFLAGS='-O3 -n32 -TARG:platform=IP22 \ --I/usr/local/include -L/usr/local/lib' \ -./configure --prefix=/usr/local/mysql --with-innodb \ - --with-libwrap=/usr/local \ - --with-named-curses-libs=/usr/local/lib/libncurses.a - -2.13.5.8. SCO UNIX and OpenServer 5.0.x Notes - - The current port is tested only on sco3.2v5.0.5, sco3.2v5.0.6, and - sco3.2v5.0.7 systems. There has also been progress on a port to - sco3.2v4.2. Open Server 5.0.8 (Legend) has native threads and - allows files greater than 2GB. The current maximum file size is - 2GB. - - We have been able to compile MySQL with the following configure - command on OpenServer with gcc 2.95.3. -CC=gcc CFLAGS="-D_FILE_OFFSET_BITS=64 -O3" \ -CXX=gcc CXXFLAGS="-D_FILE_OFFSET_BITS=64 -O3" \ -./configure --prefix=/usr/local/mysql \ - --enable-thread-safe-client --with-innodb \ - --with-openssl --with-vio --with-extra-charsets=complex - - gcc is available at - ftp://ftp.sco.com/pub/openserver5/opensrc/gnutools-5.0.7Kj. - - This development system requires the OpenServer Execution - Environment Supplement oss646B on OpenServer 5.0.6 and oss656B and - The OpenSource libraries found in gwxlibs. All OpenSource tools - are in the opensrc directory. They are available at - ftp://ftp.sco.com/pub/openserver5/opensrc/. - - Use the latest production release of MySQL. - - SCO provides operating system patches at - ftp://ftp.sco.com/pub/openserver5 for OpenServer 5.0.[0-6] and - ftp://ftp.sco.com/pub/openserverv5/507 for OpenServer 5.0.7. - - SCO provides information about security fixes at - ftp://ftp.sco.com/pub/security/OpenServer for OpenServer 5.0.x. - - The maximum file size on an OpenServer 5.0.x system is 2GB. - - The total memory which can be allocated for streams buffers, - clists, and lock records cannot exceed 60MB on OpenServer 5.0.x. - - Streams buffers are allocated in units of 4096 byte pages, clists - are 70 bytes each, and lock records are 64 bytes each, so: -(NSTRPAGES x 4096) + (NCLIST x 70) + (MAX_FLCKREC x 64) <= 62914560 - - Follow this procedure to configure the Database Services option. - If you are unsure whether an application requires this, see the - documentation provided with the application. - - 1. Log in as root. - - 2. Enable the SUDS driver by editing the /etc/conf/sdevice.d/suds - file. Change the N in the second field to a Y. - - 3. Use mkdev aio or the Hardware/Kernel Manager to enable support - for asynchronous I/O and relink the kernel. To allow users to - lock down memory for use with this type of I/O, update the - aiomemlock(F) file. This file should be updated to include the - names of users that can use AIO and the maximum amounts of - memory they can lock down. - - 4. Many applications use setuid binaries so that you need to - specify only a single user. See the documentation provided - with the application to determine whether this is the case for - your application. - - After you complete this process, reboot the system to create a new - kernel incorporating these changes. - - By default, the entries in /etc/conf/cf.d/mtune are set as - follows: -Value Default Min Max ------ ------- --- --- -NBUF 0 24 450000 -NHBUF 0 32 524288 -NMPBUF 0 12 512 -MAX_INODE 0 100 64000 -MAX_FILE 0 100 64000 -CTBUFSIZE 128 0 256 -MAX_PROC 0 50 16000 -MAX_REGION 0 500 160000 -NCLIST 170 120 16640 -MAXUP 100 15 16000 -NOFILES 110 60 11000 -NHINODE 128 64 8192 -NAUTOUP 10 0 60 -NGROUPS 8 0 128 -BDFLUSHR 30 1 300 -MAX_FLCKREC 0 50 16000 -PUTBUFSZ 8000 2000 20000 -MAXSLICE 100 25 100 -ULIMIT 4194303 2048 4194303 -* Streams Parameters -NSTREAM 64 1 32768 -NSTRPUSH 9 9 9 -NMUXLINK 192 1 4096 -STRMSGSZ 16384 4096 524288 -STRCTLSZ 1024 1024 1024 -STRMAXBLK 524288 4096 524288 -NSTRPAGES 500 0 8000 -STRSPLITFRAC 80 50 100 -NLOG 3 3 3 -NUMSP 64 1 256 -NUMTIM 16 1 8192 -NUMTRW 16 1 8192 -* Semaphore Parameters -SEMMAP 10 10 8192 -SEMMNI 10 10 8192 -SEMMNS 60 60 8192 -SEMMNU 30 10 8192 -SEMMSL 25 25 150 -SEMOPM 10 10 1024 -SEMUME 10 10 25 -SEMVMX 32767 32767 32767 -SEMAEM 16384 16384 16384 -* Shared Memory Parameters -SHMMAX 524288 131072 2147483647 -SHMMIN 1 1 1 -SHMMNI 100 100 2000 -FILE 0 100 64000 -NMOUNT 0 4 256 -NPROC 0 50 16000 -NREGION 0 500 160000 - - Set these values as follows: - - * NOFILES should be 4096 or 2048. - - * MAXUP should be 2048. - - To make changes to the kernel, use the idtune name parameter - command. idtune modifies the /etc/conf/cf.d/stune file for you. - For example, to change SEMMS to 200, execute this command as root: -# /etc/conf/bin/idtune SEMMNS 200 - - Then rebuild and reboot the kernel by issuing this command: -# /etc/conf/bin/idbuild -B && init 6 - - To tune the system, the proper parameter values to use depend on - the number of users accessing the application or database and size - the of the database (that is, the used buffer pool). The following - kernel parameters can be set with idtune: - - * SHMMAX (recommended setting: 128MB) and SHMSEG (recommended - setting: 15). These parameters have an influence on the MySQL - database engine to create user buffer pools. - - * NOFILES and MAXUP should be set to at least 2048. - - * MAXPROC should be set to at least 3000/4000 (depends on number - of users) or more. - - * The following formulas are recommended to calculate values for - SEMMSL, SEMMNS, and SEMMNU: -SEMMSL = 13 - 13 is what has been found to be the best for both Progress and - MySQL. -SEMMNS = SEMMSL x number of db servers to be run on the system - Set SEMMNS to the value of SEMMSL multiplied by the number of - database servers (maximum) that you are running on the system - at one time. -SEMMNU = SEMMNS - Set the value of SEMMNU to equal the value of SEMMNS. You - could probably set this to 75% of SEMMNS, but this is a - conservative estimate. - - You need to at least install the SCO OpenServer Linker and - Application Development Libraries or the OpenServer Development - System to use gcc. You cannot use the GCC Dev system without - installing one of these. - - You should get the FSU Pthreads package and install it first. This - can be found at - http://moss.csc.ncsu.edu/~mueller/ftp/pub/PART/pthreads.tar.gz. - You can also get a precompiled package from - ftp://ftp.zenez.com/pub/zenez/prgms/FSU-threads-3.14.tar.gz. - - FSU Pthreads can be compiled with SCO Unix 4.2 with tcpip, or - using OpenServer 3.0 or Open Desktop 3.0 (OS 3.0 ODT 3.0) with the - SCO Development System installed using a good port of GCC 2.5.x. - For ODT or OS 3.0, you need a good port of GCC 2.5.x. There are a - lot of problems without a good port. The port for this product - requires the SCO Unix Development system. Without it, you are - missing the libraries and the linker that is needed. You also need - SCO-3.2v4.2-includes.tar.gz. This file contains the changes to the - SCO Development include files that are needed to get MySQL to - build. You need to replace the existing system include files with - these modified header files. They can be obtained from - ftp://ftp.zenez.com/pub/zenez/prgms/SCO-3.2v4.2-includes.tar.gz. - - To build FSU Pthreads on your system, all you should need to do is - run GNU make. The Makefile in FSU-threads-3.14.tar.gz is set up to - make FSU-threads. - - You can run ./configure in the threads/src directory and select - the SCO OpenServer option. This command copies Makefile.SCO5 to - Makefile. Then run make. - - To install in the default /usr/include directory, log in as root, - and then cd to the thread/src directory and run make install. - - Remember that you must use GNU make to build MySQL. + When you are ready to create additional user accounts, you can + find information on the MySQL access control system and account + management in Section 5.4, "The MySQL Access Privilege System," + and Section 5.5, "MySQL User Account Management." -Note +2.13.1. Unix Post-Installation Procedures - If you don't start mysqld_safe as root, you should get only the - default 110 open files per process. mysqld writes a note about - this in the log file. + After installing MySQL on Unix, you need to initialize the grant + tables, start the server, and make sure that the server works + satisfactorily. You may also wish to arrange for the server to be + started and stopped automatically when your system starts and + stops. You should also assign passwords to the accounts in the + grant tables. - With SCO 3.2V4.2, you should use FSU Pthreads version 3.14 or - newer. The following configure command should work: -CFLAGS="-D_XOPEN_XPG4" CXX=gcc CXXFLAGS="-D_XOPEN_XPG4" \ -./configure \ - --prefix=/usr/local/mysql \ - --with-named-thread-libs="-lgthreads -lsocket -lgen -lgthreads" \ - --with-named-curses-libs="-lcurses" + On Unix, the grant tables are set up by the mysql_install_db + program. For some installation methods, this program is run for + you automatically: - You may have problems with some include files. In this case, you - can find new SCO-specific include files at - ftp://ftp.zenez.com/pub/zenez/prgms/SCO-3.2v4.2-includes.tar.gz. + * If you install MySQL on Linux using RPM distributions, the + server RPM runs mysql_install_db. - You should unpack this file in the include directory of your MySQL - source tree. + * If you install MySQL on Mac OS X using a PKG distribution, the + installer runs mysql_install_db. - SCO development notes: + Otherwise, you'll need to run mysql_install_db yourself. - * MySQL should automatically detect FSU Pthreads and link mysqld - with -lgthreads -lsocket -lgthreads. + The following procedure describes how to initialize the grant + tables (if that has not previously been done) and then start the + server. It also suggests some commands that you can use to test + whether the server is accessible and working properly. For + information about starting and stopping the server automatically, + see Section 2.13.1.2, "Starting and Stopping MySQL Automatically." - * The SCO development libraries are re-entrant in FSU Pthreads. - SCO claims that its library functions are re-entrant, so they - must be re-entrant with FSU Pthreads. FSU Pthreads on - OpenServer tries to use the SCO scheme to make re-entrant - libraries. + After you complete the procedure and have the server running, you + should assign passwords to the accounts created by + mysql_install_db. Instructions for doing so are given in Section + 2.13.2, "Securing the Initial MySQL Accounts." - * FSU Pthreads (at least the version at ftp://ftp.zenez.com) - comes linked with GNU malloc. If you encounter problems with - memory usage, make sure that gmalloc.o is included in - libgthreads.a and libgthreads.so. + In the examples shown here, the server runs under the user ID of + the 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. - * In FSU Pthreads, the following system calls are - pthreads-aware: read(), write(), getmsg(), connect(), - accept(), select(), and wait(). + 1. Change location into the top-level directory of your MySQL + installation, represented here by BASEDIR: +shell> cd BASEDIR + BASEDIR is likely to be something like /usr/local/mysql or + /usr/local. The following steps assume that you are located in + this directory. - * The CSSA-2001-SCO.35.2 (the patch is listed in custom as - erg711905-dscr_remap security patch (version 2.0.0)) breaks - FSU threads and makes mysqld unstable. You have to remove this - one if you want to run mysqld on an OpenServer 5.0.6 machine. + 2. If necessary, run the mysql_install_db program to set up the + initial MySQL grant tables containing the privileges that + determine how users are allowed to connect to the server. + You'll need to do this if you used a distribution type for + which the installation procedure doesn't run the program for + you. + Typically, mysql_install_db needs to be run only the first + time you install MySQL, so you can skip this step if you are + upgrading an existing installation, However, mysql_install_db + does not overwrite any existing privilege tables, so it should + be safe to run in any circumstances. + To initialize the grant tables, use one of the following + commands, depending on whether mysql_install_db is located in + the bin or scripts directory: +shell> bin/mysql_install_db --user=mysql +shell> scripts/mysql_install_db --user=mysql + It might be necessary to specify other options such as + --basedir or --datadir if mysql_install_db does not use the + correct locations for the installation directory or data + directory. For example: +shell> bin/mysql_install_db --user=mysql \ + --basedir=/opt/mysql/mysql \ + --datadir=/opt/mysql/mysql/data + The mysql_install_db script creates the server's data + directory. Under the data directory, it creates directories + for the mysql database that holds all database privileges and + the test database that you can use to test MySQL. The script + also creates privilege table entries for root and + anonymous-user accounts. The accounts have no passwords + initially. A description of their initial privileges is given + in Section 2.13.2, "Securing the Initial MySQL Accounts." + Briefly, these privileges allow the MySQL root user to do + anything, and allow anybody to create or use databases with a + name of test or starting with test_. + It is important to make sure that the database directories and + files are owned by the mysql login account so that the server + has read and write access to them when you run it later. To + ensure this, the --user option should be used as shown if you + run mysql_install_db as root. Otherwise, you should execute + the script while logged in as mysql, in which case you can + omit the --user option from the command. + mysql_install_db creates several tables in the mysql database, + including user, db, host, tables_priv, columns_priv, func, and + others. See Section 5.4, "The MySQL Access Privilege System," + for a complete listing and description of these tables. + If you don't want to have the test database, you can remove it + with mysqladmin -u root drop test after starting the server. + If you have trouble with mysql_install_db at this point, see + Section 2.13.1.1, "Problems Running mysql_install_db." - * If you use SCO OpenServer 5, you may need to recompile FSU - pthreads with -DDRAFT7 in CFLAGS. Otherwise, InnoDB may hang - at a mysqld startup. + 3. Start the MySQL server: +shell> bin/mysqld_safe --user=mysql & + It is important that the MySQL server be run using an + unprivileged (non-root) login account. To ensure this, the + --user option should be used as shown if you run mysqld_safe + as system root. Otherwise, you should execute the script while + logged in to the system as mysql, in which case you can omit + the --user option from the command. + Further instructions for running MySQL as an unprivileged user + are given in Section 5.3.5, "How to Run MySQL as a Normal + User." + If you neglected to create the grant tables before proceeding + to this step, the following message appears in the error log + file when you start the server: +mysqld: Can't find file: 'host.frm' + If you have other problems starting the server, see Section + 2.13.1.3, "Starting and Troubleshooting the MySQL Server." - * SCO provides operating system patches at - ftp://ftp.sco.com/pub/openserver5 for OpenServer 5.0.x. + 4. Use mysqladmin to verify that the server is running. The + following commands provide simple tests to check whether the + server is up and responding to connections: +shell> bin/mysqladmin version +shell> bin/mysqladmin variables + The output from mysqladmin version varies slightly depending + on your platform and version of MySQL, but should be similar + to that shown here: +shell> bin/mysqladmin version +mysqladmin Ver 14.12 Distrib 5.1.41, for pc-linux-gnu on i686 +... - * SCO provides security fixes and libsocket.so.2 at - ftp://ftp.sco.com/pub/security/OpenServer and - ftp://ftp.sco.com/pub/security/sse for OpenServer 5.0.x. +Server version 5.1.41 +Protocol version 10 +Connection Localhost via UNIX socket +UNIX socket /var/lib/mysql/mysql.sock +Uptime: 14 days 5 hours 5 min 21 sec - * Pre-OSR506 security fixes. Also, the telnetd fix at - ftp://stage.caldera.com/pub/security/openserver/ or - ftp://stage.caldera.com/pub/security/openserver/CSSA-2001-SCO. - 10/ as both libsocket.so.2 and libresolv.so.1 with - instructions for installing on pre-OSR506 systems. - It is probably a good idea to install these patches before - trying to compile/use MySQL. +Threads: 1 Questions: 366 Slow queries: 0 +Opens: 0 Flush tables: 1 Open tables: 19 +Queries per second avg: 0.000 + To see what else you can do with mysqladmin, invoke it with + the --help option. - Beginning with Legend/OpenServer 6.0.0, there are native threads - and no 2GB file size limit. + 5. Verify that you can shut down the server: +shell> bin/mysqladmin -u root shutdown -2.13.5.9. SCO OpenServer 6.0.x Notes + 6. Verify that you can start the server again. Do this by using + mysqld_safe or by invoking mysqld directly. For example: +shell> bin/mysqld_safe --user=mysql --log & + If mysqld_safe fails, see Section 2.13.1.3, "Starting and + Troubleshooting the MySQL Server." - OpenServer 6 includes these key improvements: + 7. Run some simple tests to verify that you can retrieve + information from the server. The output should be similar to + what is shown here: +shell> bin/mysqlshow ++-----------+ +| Databases | ++-----------+ +| mysql | +| test | ++-----------+ - * Larger file support up to 1 TB +shell> bin/mysqlshow mysql +Database: mysql ++---------------------------+ +| Tables | ++---------------------------+ +| columns_priv | +| db | +| func | +| help_category | +| help_keyword | +| help_relation | +| help_topic | +| host | +| proc | +| procs_priv | +| tables_priv | +| time_zone | +| time_zone_leap_second | +| time_zone_name | +| time_zone_transition | +| time_zone_transition_type | +| user | ++---------------------------+ - * Multiprocessor support increased from 4 to 32 processors +shell> bin/mysql -e "SELECT Host,Db,User FROM db" mysql ++------+--------+------+ +| host | db | user | ++------+--------+------+ +| % | test | | +| % | test_% | | ++------+--------+------+ - * Increased memory support up to 64GB + 8. There is a benchmark suite in the sql-bench directory (under + the MySQL installation directory) that you can use to compare + how MySQL performs on different platforms. The benchmark suite + is written in Perl. It requires the Perl DBI module that + provides a database-independent interface to the various + databases, and some other additional Perl modules: +DBI +DBD::mysql +Data::Dumper +Data::ShowTable + These modules can be obtained from CPAN + (http://www.cpan.org/). See also Section 2.15.1, "Installing + Perl on Unix." + The sql-bench/Results directory contains the results from many + runs against different databases and platforms. To run all + tests, execute these commands: +shell> cd sql-bench +shell> perl run-all-tests + If you don't have the sql-bench directory, you probably + installed MySQL using RPM files other than the source RPM. + (The source RPM includes the sql-bench benchmark directory.) + In this case, you must first install the benchmark suite + before you can use it. There are separate benchmark RPM files + named mysql-bench-VERSION.i386.rpm that contain benchmark code + and data. + If you have a source distribution, there are also tests in its + tests subdirectory that you can run. For example, to run + auto_increment.tst, execute this command from the top-level + directory of your source distribution: +shell> mysql -vvf test < ./tests/auto_increment.tst + The expected result of the test can be found in the + ./tests/auto_increment.res file. - * Extending the power of UnixWare into OpenServer 6 + 9. At this point, you should have the server running. However, + none of the initial MySQL accounts have a password, so you + should assign passwords using the instructions found in + Section 2.13.2, "Securing the Initial MySQL Accounts." - * Dramatic performance improvement + The MySQL 5.1 installation procedure creates time zone tables in + the mysql database. However, you must populate the tables manually + using the instructions in Section 9.7, "MySQL Server Time Zone + Support." - OpenServer 6.0.0 commands are organized as follows: +2.13.1.1. Problems Running mysql_install_db - * /bin is for commands that behave exactly the same as on - OpenServer 5.0.x. + The purpose of the mysql_install_db script is to generate new + MySQL privilege tables. It does not overwrite existing MySQL + privilege tables, and it does not affect any other data. - * /u95/bin is for commands that have better standards - conformance, for example Large File System (LFS) support. + If you want to re-create your privilege tables, first stop the + mysqld server if it is running. Then rename the mysql directory + under the data directory to save it, and then run + mysql_install_db. Suppose that your current directory is the MySQL + installation directory and that mysql_install_db is located in the + bin directory and the data directory is named data. To rename the + mysql database and re-run mysql_install_db, use these commands. +shell> mv data/mysql data/mysql.old +shell> bin/mysql_install_db --user=mysql - * /udk/bin is for commands that behave the same as on UnixWare - 7.1.4. The default is for the LFS support. + When you run mysql_install_db, you might encounter the following + problems: - The following is a guide to setting PATH on OpenServer 6. If the - user wants the traditional OpenServer 5.0.x then PATH should be - /bin first. If the user wants LFS support, the path should be - /u95/bin:/bin. If the user wants UnixWare 7 support first, the - path would be /udk/bin:/u95/bin:/bin:. + * mysql_install_db fails to install the grant tables + You may find that mysql_install_db fails to install the grant + tables and terminates after displaying the following messages: +Starting mysqld daemon with databases from XXXXXX +mysqld ended + In this case, you should examine the error log file very + carefully. The log should be located in the directory XXXXXX + named by the error message and should indicate why mysqld + didn't start. If you do not understand what happened, include + the log when you post a bug report. See Section 1.6, "How to + Report Bugs or Problems." - Use the latest production release of MySQL. Should you choose to - use an older release of MySQL on OpenServer 6.0.x, you must use a - version of MySQL at least as recent as 3.22.13 to get fixes for - some portability and OS problems. + * There is a mysqld process running + This indicates that the server is running, in which case the + grant tables have probably been created already. If so, there + is no need to run mysql_install_db at all because it needs to + be run only once (when you install MySQL the first time). - MySQL distribution files with names of the following form are tar - archives of media are tar archives of media images suitable for - installation with the SCO Software Manager (/etc/custom) on SCO - OpenServer 6: -mysql-PRODUCT-5.1.39-sco-osr6-i686.VOLS.tar + * Installing a second mysqld server does not work when one + server is running + This can happen when you have an existing MySQL installation, + but want to put a new installation in a different location. + For example, you might have a production installation, but you + want to create a second installation for testing purposes. + Generally the problem that occurs when you try to run a second + server is that it tries to use a network interface that is in + use by the first server. In this case, you should see one of + the following error messages: +Can't start server: Bind on TCP/IP port: +Address already in use +Can't start server: Bind on unix socket... + For instructions on setting up multiple servers, see Section + 5.6, "Running Multiple MySQL Servers on the Same Machine." + + * You do not have write access to the /tmp directory + If you do not have write access to create temporary files or a + Unix socket file in the default location (the /tmp directory), + an error occurs when you run mysql_install_db or the mysqld + server. + You can specify different locations for the temporary + directory and Unix socket file by executing these commands + prior to starting mysql_install_db or mysqld, where + some_tmp_dir is the full path name to some directory for which + you have write permission: +shell> TMPDIR=/some_tmp_dir/ +shell> MYSQL_UNIX_PORT=/some_tmp_dir/mysql.sock +shell> export TMPDIR MYSQL_UNIX_PORT + Then you should be able to run mysql_install_db and start the + server with these commands: +shell> bin/mysql_install_db --user=mysql +shell> bin/mysqld_safe --user=mysql & + If mysql_install_db is located in the scripts directory, + modify the first command to scripts/mysql_install_db. + See Section B.5.4.5, "How to Protect or Change the MySQL Unix + Socket File," and Section 2.14, "Environment Variables." - A distribution where PRODUCT is pro-cert is the Commercially - licensed MySQL Pro Certified server. A distribution where PRODUCT - is pro-gpl-cert is the MySQL Pro Certified server licensed under - the terms of the General Public License (GPL). + There are some alternatives to running the mysql_install_db script + provided in the MySQL distribution: - Select whichever distribution you wish to install and, after - download, extract the tar archive into an empty directory. For - example: -shell> mkdir /tmp/mysql-pro -shell> cd /tmp/mysql-pro -shell> tar xf /tmp/mysql-pro-cert-5.1.39-sco-osr6-i686.VOLS.tar + * If you want the initial privileges to be different from the + standard defaults, you can modify mysql_install_db before you + run it. However, it is preferable to use GRANT and REVOKE to + change the privileges after the grant tables have been set up. + In other words, you can run mysql_install_db, and then use + mysql -u root mysql to connect to the server as the MySQL root + user so that you can issue the necessary GRANT and REVOKE + statements. + If you want to install MySQL on several machines with the same + privileges, you can put the GRANT and REVOKE statements in a + file and execute the file as a script using mysql after + running mysql_install_db. For example: +shell> bin/mysql_install_db --user=mysql +shell> bin/mysql -u root < your_script_file + By doing this, you can avoid having to issue the statements + manually on each machine. - Prior to installation, back up your data in accordance with the - procedures outlined in Section 2.12.1, "Upgrading MySQL." + * It is possible to re-create the grant tables completely after + they have previously been created. You might want to do this + if you're just learning how to use GRANT and REVOKE and have + made so many modifications after running mysql_install_db that + you want to wipe out the tables and start over. + To re-create the grant tables, remove all the .frm, .MYI, and + .MYD files in the mysql database directory. Then run the + mysql_install_db script again. - Remove any previously installed pkgadd version of MySQL: -shell> pkginfo mysql 2>&1 > /dev/null && pkgrm mysql + * You can start mysqld manually using the --skip-grant-tables + option and add the privilege information yourself using mysql: +shell> bin/mysqld_safe --user=mysql --skip-grant-tables & +shell> bin/mysql mysql + From mysql, manually execute the SQL commands contained in + mysql_install_db. Make sure that you run mysqladmin + flush-privileges or mysqladmin reload afterward to tell the + server to reload the grant tables. + Note that by not using mysql_install_db, you not only have to + populate the grant tables manually, you also have to create + them first. - Install MySQL Pro from media images using the SCO Software - Manager: -shell> /etc/custom -p SCO:MySQL -i -z /tmp/mysql-pro +2.13.1.2. Starting and Stopping MySQL Automatically - Alternatively, the SCO Software Manager can be displayed - graphically by clicking on the Software Manager icon on the - desktop, selecting Software -> Install New, selecting the host, - selecting Media Images for the Media Device, and entering - /tmp/mysql-pro as the Image Directory. + Generally, you start the mysqld server in one of these ways: - After installation, run mkdev mysql as the root user to configure - your newly installed MySQL Pro Certified server. + * Invoke mysqld directly. This works on any platform. -Note + * Run the MySQL server as a Windows service. The service can be + set to start the server automatically when Windows starts, or + as a manual service that you start on request. For + instructions, see Section 2.5.5.6, "Starting MySQL as a + Windows Service." - The installation procedure for VOLS packages does not create the - mysql user and group that the package uses by default. You should - either create the mysql user and group, or else select a different - user and group using an option in mkdev mysql. + * Invoke mysqld_safe, which tries to determine the proper + options for mysqld and then runs it with those options. This + script is used on Unix and Unix-like systems. See Section + 4.3.2, "mysqld_safe --- MySQL Server Startup Script." - If you wish to configure your MySQL Pro server to interface with - the Apache Web server via PHP, download and install the PHP update - from SCO at - ftp://ftp.sco.com/pub/updates/OpenServer/SCOSA-2006.17/. + * Invoke mysql.server. This script is used primarily at system + startup and shutdown on systems that use System V-style run + directories, where it usually is installed under the name + mysql. The mysql.server script starts the server by invoking + mysqld_safe. See Section 4.3.3, "mysql.server --- MySQL Server + Startup Script." - We have been able to compile MySQL with the following configure - command on OpenServer 6.0.x: -CC=cc CFLAGS="-D_FILE_OFFSET_BITS=64 -O3" \ -CXX=CC CXXFLAGS="-D_FILE_OFFSET_BITS=64 -O3" \ -./configure --prefix=/usr/local/mysql \ - --enable-thread-safe-client \ - --with-extra-charsets=complex \ - --build=i686-unknown-sysv5SCO_SV6.0.0 + * On Mac OS X, install a separate MySQL Startup Item package to + enable the automatic startup of MySQL on system startup. The + Startup Item starts the server by invoking mysql.server. See + Section 2.7, "Installing MySQL on Mac OS X," for details. - If you use gcc, you must use gcc 2.95.3 or newer. -CC=gcc CXX=g++ ... ./configure ... + The mysqld_safe and mysql.server scripts and the Mac OS X Startup + Item can be used to start the server manually, or automatically at + system startup time. mysql.server and the Startup Item also can be + used to stop the server. - SCO provides OpenServer 6 operating system patches at - ftp://ftp.sco.com/pub/openserver6. + To start or stop the server manually using the mysql.server + script, invoke it with start or stop arguments: +shell> mysql.server start +shell> mysql.server stop - SCO provides information about security fixes at - ftp://ftp.sco.com/pub/security/OpenServer. + Before mysql.server starts the server, it changes location to the + MySQL installation directory, and then invokes mysqld_safe. If you + want the server to run as some specific user, add an appropriate + user option to the [mysqld] group of the /etc/my.cnf option file, + as shown later in this section. (It is possible that you will need + to 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, so you should 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 need to + add start and stop commands to the appropriate places in your + /etc/rc* files. - By default, the maximum file size on a OpenServer 6.0.0 system is - 1TB. Some operating system utilities have a limitation of 2GB. The - maximum possible file size on UnixWare 7 is 1TB with VXFS or HTFS. + If you use the Linux server RPM package + (MySQL-server-VERSION.rpm), the mysql.server script is installed + in the /etc/init.d directory with the name mysql. You need not + install it manually. See Section 2.6.1, "Installing MySQL from RPM + Packages on Linux," for more information on the Linux RPM + packages. - OpenServer 6 can be configured for large file support (file sizes - greater than 2GB) by tuning the UNIX kernel. + Some vendors provide RPM packages that install a startup script + under a different name such as mysqld. - By default, the entries in /etc/conf/cf.d/mtune are set as - follows: -Value Default Min Max ------ ------- --- --- -SVMMLIM 0x9000000 0x1000000 0x7FFFFFFF -HVMMLIM 0x9000000 0x1000000 0x7FFFFFFF - - To make changes to the kernel, use the idtune name parameter - command. idtune modifies the /etc/conf/cf.d/stune file for you. To - set the kernel values, execute the following commands as root: -# /etc/conf/bin/idtune SDATLIM 0x7FFFFFFF -# /etc/conf/bin/idtune HDATLIM 0x7FFFFFFF -# /etc/conf/bin/idtune SVMMLIM 0x7FFFFFFF -# /etc/conf/bin/idtune HVMMLIM 0x7FFFFFFF -# /etc/conf/bin/idtune SFNOLIM 2048 -# /etc/conf/bin/idtune HFNOLIM 2048 - - Then rebuild and reboot the kernel by issuing this command: -# /etc/conf/bin/idbuild -B && init 6 - - To tune the system, the proper parameter values to use depend on - the number of users accessing the application or database and size - the of the database (that is, the used buffer pool). The following - kernel parameters can be set with idtune: - - * SHMMAX (recommended setting: 128MB) and SHMSEG (recommended - setting: 15). These parameters have an influence on the MySQL - database engine to create user buffer pools. - - * SFNOLIM and HFNOLIM should be at maximum 2048. - - * NPROC should be set to at least 3000/4000 (depends on number - of users). - - * The following formulas are recommended to calculate values for - SEMMSL, SEMMNS, and SEMMNU: -SEMMSL = 13 - 13 is what has been found to be the best for both Progress and - MySQL. -SEMMNS = SEMMSL x number of db servers to be run on the system - Set SEMMNS to the value of SEMMSL multiplied by the number of - database servers (maximum) that you are running on the system - at one time. -SEMMNU = SEMMNS - Set the value of SEMMNU to equal the value of SEMMNS. You - could probably set this to 75% of SEMMNS, but this is a - conservative estimate. - -2.13.5.10. SCO UnixWare 7.1.x and OpenUNIX 8.0.0 Notes - - Use the latest production release of MySQL. Should you choose to - use an older release of MySQL on UnixWare 7.1.x, you must use a - version of MySQL at least as recent as 3.22.13 to get fixes for - some portability and OS problems. - - We have been able to compile MySQL with the following configure - command on UnixWare 7.1.x: -CC="cc" CFLAGS="-I/usr/local/include" \ -CXX="CC" CXXFLAGS="-I/usr/local/include" \ -./configure --prefix=/usr/local/mysql \ - --enable-thread-safe-client \ - --with-innodb --with-openssl --with-extra-charsets=complex - - If you want to use gcc, you must use gcc 2.95.3 or newer. -CC=gcc CXX=g++ ... ./configure ... - - SCO provides operating system patches at - ftp://ftp.sco.com/pub/unixware7 for UnixWare 7.1.1, - ftp://ftp.sco.com/pub/unixware7/713/ for UnixWare 7.1.3, - ftp://ftp.sco.com/pub/unixware7/714/ for UnixWare 7.1.4, and - ftp://ftp.sco.com/pub/openunix8 for OpenUNIX 8.0.0. - - SCO provides information about security fixes at - ftp://ftp.sco.com/pub/security/OpenUNIX for OpenUNIX and - ftp://ftp.sco.com/pub/security/UnixWare for UnixWare. - - The UnixWare 7 file size limit is 1 TB with VXFS. Some OS - utilities have a limitation of 2GB. - - On UnixWare 7.1.4 you do not need to do anything to get large file - support, but to enable large file support on prior versions of - UnixWare 7.1.x, run fsadm. -# fsadm -Fvxfs -o largefiles / -# fsadm / * Note -# ulimit unlimited -# /etc/conf/bin/idtune SFSZLIM 0x7FFFFFFF ** Note -# /etc/conf/bin/idtune HFSZLIM 0x7FFFFFFF ** Note -# /etc/conf/bin/idbuild -B - -* This should report "largefiles". -** 0x7FFFFFFF represents infinity for these values. - - Reboot the system using shutdown. - - By default, the entries in /etc/conf/cf.d/mtune are set as + If you install MySQL from a source distribution or using a binary + distribution format that does not install mysql.server + automatically, you can install it manually. The script can be + found in the support-files directory under the MySQL installation + directory or in a MySQL source tree. + + To install mysql.server manually, copy it to the /etc/init.d + directory with the name mysql, and then make it executable. Do + this by changing location into the appropriate directory where + mysql.server is located and executing these commands: +shell> cp mysql.server /etc/init.d/mysql +shell> chmod +x /etc/init.d/mysql + + Older Red Hat systems use the /etc/rc.d/init.d directory rather + than /etc/init.d. Adjust the preceding commands accordingly. + Alternatively, first create /etc/init.d as a symbolic link that + points to /etc/rc.d/init.d: +shell> cd /etc +shell> ln -s rc.d/init.d . + + 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: +shell> chkconfig --add mysql + + On some Linux systems, the following command also seems to be + necessary to fully enable the mysql script: +shell> chkconfig --level 345 mysql on + + On FreeBSD, startup scripts generally should go in + /usr/local/etc/rc.d/. The rc(8) manual page states that scripts in + this directory are executed only if their basename matches the + *.sh shell file name pattern. Any other files or directories + present within the directory are silently ignored. In other words, + on FreeBSD, you should install the mysql.server script as + /usr/local/etc/rc.d/mysql.server.sh to enable automatic startup. + + 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, you could append a command like the one following to the + appropriate startup file: +/bin/sh -c 'cd /usr/local/mysql; ./bin/mysqld_safe --user=mysql &' + + For other systems, consult your operating system documentation to + see how to install startup scripts. + + You can add options for mysql.server in a global /etc/my.cnf file. + A typical /etc/my.cnf file might look like this: +[mysqld] +datadir=/usr/local/mysql/var +socket=/var/tmp/mysql.sock +port=3306 +user=mysql + +[mysql.server] +basedir=/usr/local/mysql + + The mysql.server script supports the following options: basedir, + datadir, and pid-file. 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. + + The following table shows which option groups the server and each + startup script read from option files. + Script Option Groups + mysqld [mysqld], [server], [mysqld-major_version] + mysqld_safe [mysqld], [server], [mysqld_safe] + mysql.server [mysqld], [mysql.server], [server] + + [mysqld-major_version] means that groups with names like + [mysqld-5.0] and [mysqld-5.1] are read by servers having versions + 5.0.x, 5.1.x, and so forth. This feature can be used to specify + options that can be read only by servers within a given release + series. + + For backward compatibility, mysql.server also reads the + [mysql_server] group and mysqld_safe also reads the [safe_mysqld] + group. However, you should update your option files to use the + [mysql.server] and [mysqld_safe] groups instead when using MySQL + 5.1. + + See Section 4.2.3.3, "Using Option Files." + +2.13.1.3. Starting and Troubleshooting the MySQL Server + + This section provides troubleshooting suggestions for problems + starting the server on Unix. If you are using Windows, see Section + 2.5.6, "Troubleshooting a MySQL Installation Under Windows." + + If you have problems starting the server, here are some things to + try: + + * Check the error log to see why the server does not start. + + * Specify any special options needed by the storage engines you + are using. + + * Make sure that the server knows where to find the data + directory. + + * Make sure that the server can access the data directory. The + ownership and permissions of the data directory and its + contents must be set such that the server can read and modify + them. + + * Verify that the network interfaces the server wants to use are + available. + + Some storage engines have options that control their behavior. You + can create a my.cnf file and specify startup options for the + engines that you plan to use. If you are going to use storage + engines that support transactional tables (InnoDB, NDB), be sure + that you have them configured the way you want before starting the + server: + + * If you are using InnoDB tables, see Section 13.6.2, "InnoDB + Configuration." + + * If you are using MySQL Cluster, see Section 17.3, "MySQL + Cluster Configuration." + + MySQL Enterprise For expert advice on start-up options appropriate + to your circumstances, subscribe to The MySQL Enterprise Monitor. + For more information, see + http://www.mysql.com/products/enterprise/advisors.html. + + Storage engines will use default option values if you specify + none, but it is recommended that you review the available options + and specify explicit values for those for which the defaults are + not appropriate for your installation. + + When the mysqld server starts, it changes location to the data + directory. This is where it expects to find databases and where it + expects to write log files. The server also writes the pid + (process ID) file in the data directory. + + The data directory location is hardwired in when the server is + compiled. This is where the server looks for the data directory by + default. If the data directory is located somewhere else on your + system, the server will not work properly. You can determine what + the default path settings are by invoking mysqld with the + --verbose and --help options. + + If the default locations don't match the MySQL installation layout + on your system, you can override them by specifying options to + mysqld or mysqld_safe on the command line or in an option file. + + To specify the location of the data directory explicitly, use the + --datadir option. However, normally you can tell mysqld the + location of the base directory under which MySQL is installed and + it looks for the data directory there. You can do this with the + --basedir option. + + To check the effect of specifying path options, invoke mysqld with + those options followed by the --verbose and --help options. For + example, if you change location into the directory where mysqld is + installed and then run the following command, it shows the effect + of starting the server with a base directory of /usr/local: +shell> ./mysqld --basedir=/usr/local --verbose --help + + You can specify other options such as --datadir as well, but + --verbose and --help must be the last options. + + Once you determine the path settings you want, start the server + without --verbose and --help. + + If mysqld is currently running, you can find out what path + settings it is using by executing this command: +shell> mysqladmin variables + + Or: +shell> mysqladmin -h host_name variables + + host_name is the name of the MySQL server host. + + If you get Errcode 13 (which means Permission denied) when + starting mysqld, this means that the privileges of the data + directory or its contents do not allow the server access. In this + case, you change the permissions for the involved files and + directories so that the server has the right to use them. You can + also start the server as root, but this raises security issues and + should be avoided. + + On Unix, change location into the data directory and check the + ownership of the data directory and its contents to make sure the + server has access. For example, if the data directory is + /usr/local/mysql/var, use this command: +shell> ls -la /usr/local/mysql/var + + If the data directory or its files or subdirectories are not owned + by the login account that you use for running the server, change + their ownership to that account. If the account is named mysql, + use these commands: +shell> chown -R mysql /usr/local/mysql/var +shell> chgrp -R mysql /usr/local/mysql/var + + If it possible that even with correct ownership, MySQL may fail to + start up if there is other security software running on your + system that manages application access to various parts of the + file system. In this case, you may need to reconfigure that + software to enable mysqld to access the directories it uses during + normal operation. + + If the server fails to start up correctly, check the error log. + Log files are located in the data directory (typically C:\Program + Files\MySQL\MySQL Server 5.1\data on Windows, + /usr/local/mysql/data for a Unix binary distribution, and + /usr/local/var for a Unix source distribution). Look in the data + directory for files with names of the form host_name.err and + host_name.log, where host_name is the name of your server host. + Then examine the last few lines of these files. On Unix, you can + use tail to display them: +shell> tail host_name.err +shell> tail host_name.log + + The error log should contain information that indicates why the + server couldn't start. + + If either of the following errors occur, it means that some other + program (perhaps another mysqld server) is using the TCP/IP port + or Unix socket file that mysqld is trying to use: +Can't start server: Bind on TCP/IP port: Address already in use +Can't start server: Bind on unix socket... + + Use ps to determine whether you have another mysqld server + running. If so, shut down the server before starting mysqld again. + (If another server is running, and you really want to run multiple + servers, you can find information about how to do so in Section + 5.6, "Running Multiple MySQL Servers on the Same Machine.") + + If no other server is running, try to execute the command telnet + your_host_name tcp_ip_port_number. (The default MySQL port number + is 3306.) Then press Enter a couple of times. If you don't get an + error message like telnet: Unable to connect to remote host: + Connection refused, some other program is using the TCP/IP port + that mysqld is trying to use. You'll need to track down what + program this is and disable it, or else tell mysqld to listen to a + different port with the --port option. In this case, you'll also + need to specify the port number for client programs when + connecting to the server via TCP/IP. + + Another reason the port might be inaccessible is that you have a + firewall running that blocks connections to it. If so, modify the + firewall settings to allow access to the port. + + If the server starts but you can't connect to it, you should make + sure that you have an entry in /etc/hosts that looks like this: +127.0.0.1 localhost + + This problem occurs only on systems that do not have a working + thread library and for which MySQL must be configured to use + MIT-pthreads. + + If you cannot get mysqld to start, you can try to make a trace + file to find the problem by using the --debug option. See MySQL + Internals: Porting + (http://forge.mysql.com/wiki/MySQL_Internals_Porting). + +2.13.2. Securing the Initial MySQL Accounts + + Part of the MySQL installation process is to set up the mysql + database that contains the grant tables: + + * Windows distributions contain preinitialized grant tables that + are installed automatically. + + * On Unix, the grant tables are populated by the + mysql_install_db program. Some installation methods run this + program for you. Others require that you execute it manually. + For details, see Section 2.13.1, "Unix Post-Installation + Procedures." + + The grant tables define the initial MySQL user accounts and their + access privileges. These accounts are set up as follows: + + * Accounts with the user name root are created. These are + superuser accounts that can do anything. The initial root + account passwords are empty, so anyone can connect to the + MySQL server as root --- without a password --- and be granted + all privileges. + + + On Windows, one root account is created; this account + allows connecting from the local host only. The Windows + installer will optionally create an account allowing for + connections from any host only if the user selects the + Enable root access from remote machines option during + installation. + + + On Unix, both root accounts are for connections from the + local host. Connections must be made from the local host + by specifying a host name of localhost for one of the + accounts, or the actual host name or IP number for the + other. + + * Two anonymous-user accounts are created, each with an empty + user name. The anonymous accounts have no password, so anyone + can use them to connect to the MySQL server. + + + On Windows, one anonymous account is for connections from + the local host. It has no global privileges. (Before + MySQL 5.1.16, it has all global privileges, just like the + root accounts.) The other is for connections from any + host and has all privileges for the test database and for + other databases with names that start with test. + + + On Unix, both anonymous accounts are for connections from + the local host. Connections must be made from the local + host by specifying a host name of localhost for one of + the accounts, or the actual host name or IP number for + the other. These accounts have all privileges for the + test database and for other databases with names that + start with test_. + + As noted, none of the initial accounts have passwords. This means + that your MySQL installation is unprotected until you do something + about it: + + * If you want to prevent clients from connecting as anonymous + users without a password, you should either assign a password + to each anonymous account or else remove the accounts. + + * You should assign a password to each MySQL root account. + + The following instructions describe how to set up passwords for + the initial MySQL accounts, first for the anonymous accounts and + then for the root accounts. Replace "newpwd" in the examples with + the actual password that you want to use. The instructions also + cover how to remove the anonymous accounts, should you prefer not + to allow anonymous access at all. + + You might want to defer setting the passwords until later, so that + you don't need to specify them while you perform additional setup + or testing. However, be sure to set them before using your + installation for production purposes. + + Anonymous Account Password Assignment + + To assign passwords to the anonymous accounts, connect to the + server as root and then use either SET PASSWORD or UPDATE. In + either case, be sure to encrypt the password using the PASSWORD() + function. + + To use SET PASSWORD on Windows, do this: +shell> mysql -u root +mysql> SET PASSWORD FOR ''@'localhost' = PASSWORD('newpwd'); +mysql> SET PASSWORD FOR ''@'%' = PASSWORD('newpwd'); + + To use SET PASSWORD on Unix, do this: +shell> mysql -u root +mysql> SET PASSWORD FOR ''@'localhost' = PASSWORD('newpwd'); +mysql> SET PASSWORD FOR ''@'host_name' = PASSWORD('newpwd'); + + In the second SET PASSWORD statement, replace host_name with the + name of the server host. This is the name that is specified in the + Host column of the non-localhost record for root in the user + table. If you don't know what host name this is, issue the + following statement before using SET PASSWORD: +mysql> SELECT Host, User FROM mysql.user; + + Look for the record that has root in the User column and something + other than localhost in the Host column. Then use that Host value + in the second SET PASSWORD statement. + + Anonymous Account Removal + + If you prefer to remove the anonymous accounts instead, do so as follows: -Value Default Min Max ------ ------- --- --- -SVMMLIM 0x9000000 0x1000000 0x7FFFFFFF -HVMMLIM 0x9000000 0x1000000 0x7FFFFFFF - - To make changes to the kernel, use the idtune name parameter - command. idtune modifies the /etc/conf/cf.d/stune file for you. To - set the kernel values, execute the following commands as root: -# /etc/conf/bin/idtune SDATLIM 0x7FFFFFFF -# /etc/conf/bin/idtune HDATLIM 0x7FFFFFFF -# /etc/conf/bin/idtune SVMMLIM 0x7FFFFFFF -# /etc/conf/bin/idtune HVMMLIM 0x7FFFFFFF -# /etc/conf/bin/idtune SFNOLIM 2048 -# /etc/conf/bin/idtune HFNOLIM 2048 - - Then rebuild and reboot the kernel by issuing this command: -# /etc/conf/bin/idbuild -B && init 6 - - To tune the system, the proper parameter values to use depend on - the number of users accessing the application or database and size - the of the database (that is, the used buffer pool). The following - kernel parameters can be set with idtune: - - * SHMMAX (recommended setting: 128MB) and SHMSEG (recommended - setting: 15). These parameters have an influence on the MySQL - database engine to create user buffer pools. - - * SFNOLIM and HFNOLIM should be at maximum 2048. - - * NPROC should be set to at least 3000/4000 (depends on number - of users). - - * The following formulas are recommended to calculate values for - SEMMSL, SEMMNS, and SEMMNU: -SEMMSL = 13 - 13 is what has been found to be the best for both Progress and - MySQL. -SEMMNS = SEMMSL x number of db servers to be run on the system - Set SEMMNS to the value of SEMMSL multiplied by the number of - database servers (maximum) that you are running on the system - at one time. -SEMMNU = SEMMNS - Set the value of SEMMNU to equal the value of SEMMNS. You - could probably set this to 75% of SEMMNS, but this is a - conservative estimate. +shell> mysql -u root +mysql> DROP USER ''; + + The DROP statement applies both to Windows and to Unix. On + Windows, if you want to remove only the anonymous account that has + the same privileges as root, do this instead: +shell> mysql -u root +mysql> DROP USER ''@'localhost'; + + That account allows anonymous access but has full privileges, so + removing it improves security. + + root Account Password Assignment + + You can assign passwords to the root accounts in several ways. The + following discussion demonstrates three methods: + + * Use the SET PASSWORD statement + + * Use the mysqladmin command-line client program + + * Use the UPDATE statement + + To assign passwords using SET PASSWORD, connect to the server as + root and issue SET PASSWORD statements. Be sure to encrypt the + password using the PASSWORD() function. + + For Windows, do this: +shell> mysql -u root +mysql> SET PASSWORD FOR 'root'@'localhost' = PASSWORD('newpwd'); +mysql> SET PASSWORD FOR 'root'@'%' = PASSWORD('newpwd'); + + For Unix, do this: +shell> mysql -u root +mysql> SET PASSWORD FOR 'root'@'localhost' = PASSWORD('newpwd'); +mysql> SET PASSWORD FOR 'root'@'host_name' = PASSWORD('newpwd'); + + In the second SET PASSWORD statement, replace host_name with the + name of the server host. This is the same host name that you used + when you assigned the anonymous account passwords. + + If the user table contains an account with User and Host values of + 'root' and '127.0.0.1', use an additional SET PASSWORD statement + to set that account's password: +mysql> SET PASSWORD FOR 'root'@'127.0.0.1' = PASSWORD('newpwd'); + + To assign passwords to the root accounts using mysqladmin, execute + the following commands: +shell> mysqladmin -u root password "newpwd" +shell> mysqladmin -u root -h host_name password "newpwd" + + These commands apply both to Windows and to Unix. In the second + command, replace host_name with the name of the server host. The + double quotes around the password are not always necessary, but + you should use them if the password contains spaces or other + characters that are special to your command interpreter. + + The mysqladmin method of setting the root account passwords does + not set the password for the 'root'@'127.0.0.1' account. To do so, + use SET PASSWORD as shown earlier. + + You can also use UPDATE to modify the user table directly. The + following UPDATE statement assigns a password to all root + accounts: +shell> mysql -u root +mysql> UPDATE mysql.user SET Password = PASSWORD('newpwd') + -> WHERE User = 'root'; +mysql> FLUSH PRIVILEGES; + + The UPDATE statement applies both to Windows and to Unix. + + After the passwords have been set, you must supply the appropriate + password whenever you connect to the server. For example, if you + want to use mysqladmin to shut down the server, you can do so + using this command: +shell> mysqladmin -u root -p shutdown +Enter password: (enter root password here) + +Note + + If you forget your root password after setting it up, Section + B.5.4.1, "How to Reset the Root Password," covers the procedure + for resetting it. + + To set up additional accounts, you can use the GRANT statement. + For instructions, see Section 5.5.2, "Adding User Accounts." 2.14. Environment Variables @@ -9003,7 +7980,7 @@ SEMMNU = SEMMNS PATH Used by the shell to find MySQL programs. TMPDIR The directory where temporary files are created. TZ This should be set to your local time zone. See Section - B.1.4.6, "Time Zone Problems." + B.5.4.6, "Time Zone Problems." UMASK The user-file creation mode when creating files. See note following table. UMASK_DIR The user-directory creation mode when creating @@ -9047,9 +8024,9 @@ SEMMNU = SEMMNS sections describe how to do this. Perl support for MySQL must be installed if you want to run the - MySQL benchmark scripts; see Section 7.1.4, "The MySQL Benchmark + MySQL benchmark scripts; see Section 7.1.3, "The MySQL Benchmark Suite." It is also required for the MySQL Cluster ndb_size.pl - utility; see Section 17.6.21, "ndb_size.pl --- NDBCLUSTER Size + utility; see Section 17.4.21, "ndb_size.pl --- NDBCLUSTER Size Requirement Estimator." 2.15.1. Installing Perl on Unix |