518
518
Windows examples will assume the name md5.exe.
520
520
Linux and Microsoft Windows examples:
521
shell> md5sum mysql-standard-5.5.35-linux-i686.tar.gz
522
aaab65abbec64d5e907dcd41b8699945 mysql-standard-5.5.35-linux-i686.ta
521
shell> md5sum mysql-standard-5.5.36-linux-i686.tar.gz
522
aaab65abbec64d5e907dcd41b8699945 mysql-standard-5.5.36-linux-i686.ta
524
shell> md5.exe mysql-installer-community-5.5.35.msi
525
aaab65abbec64d5e907dcd41b8699945 mysql-installer-community-5.5.35.ms
524
shell> md5.exe mysql-installer-community-5.5.36.msi
525
aaab65abbec64d5e907dcd41b8699945 mysql-installer-community-5.5.36.ms
528
528
You should verify that the resulting checksum (the string of
633
633
Table 2.1. MySQL Package and Signature Files for Source files
634
634
File Type File Name
635
Distribution file mysql-standard-5.5.35-linux-i686.tar.gz
636
Signature file mysql-standard-5.5.35-linux-i686.tar.gz.asc
635
Distribution file mysql-standard-5.5.36-linux-i686.tar.gz
636
Signature file mysql-standard-5.5.36-linux-i686.tar.gz.asc
638
638
Make sure that both files are stored in the same directory and
639
639
then run the following command to verify the signature for the
643
643
If the downloaded package is valid, you will see a "Good
644
644
signature" similar to:
645
shell> gpg --verify mysql-standard-5.5.35-linux-i686.tar.gz.asc
645
shell> gpg --verify mysql-standard-5.5.36-linux-i686.tar.gz.asc
646
646
gpg: Signature made Tue 01 Feb 2011 02:38:30 AM CST using DSA key ID
648
648
gpg: Good signature from "MySQL Release Engineering <mysql-build@oss.
651
651
The Good signature message indicates that the file signature is
652
652
valid, when compared to the signature listed on our site. But you
653
653
might also see warnings, like so:
654
shell> gpg --verify mysql-standard-5.5.35-linux-i686.tar.gz.asc
654
shell> gpg --verify mysql-standard-5.5.36-linux-i686.tar.gz.asc
655
655
gpg: Signature made Wed 23 Jan 2013 02:25:45 AM PST using DSA key ID
657
657
gpg: checking the trustdb
733
733
Table 2.2. MySQL Package and Signature Files for MySQL Installer
734
734
for Microsoft Windows
735
735
File Type File Name
736
Distribution file mysql-installer-community-5.5.35.msi
737
Signature file mysql-installer-community-5.5.35.msi.asc
736
Distribution file mysql-installer-community-5.5.36.msi
737
Signature file mysql-installer-community-5.5.36.msi.asc
739
739
Make sure that both files are stored in the same directory and
740
740
then run the following command to verify the signature for the
770
770
shell> rpm --checksig package_name.rpm
773
shell> rpm --checksig MySQL-server-5.5.35-0.glibc23.i386.rpm
774
MySQL-server-5.5.35-0.glibc23.i386.rpm: md5 gpg OK
773
shell> rpm --checksig MySQL-server-5.5.36-0.glibc23.i386.rpm
774
MySQL-server-5.5.36-0.glibc23.i386.rpm: md5 gpg OK
851
851
MySQL compressed tar file binary distributions have names of the
852
852
form mysql-VERSION-OS.tar.gz, where VERSION is a number (for
853
example, 5.5.35), and OS indicates the type of operating system
853
example, 5.5.36), and OS indicates the type of operating system
854
854
for which the distribution is intended (for example, pc-linux-i686
1179
1179
within the "Complete Package."
1181
1181
* MySQL Installer: This package has a file name similar to
1182
mysql-installer-community-5.5.35.0.msi or
1183
mysql-installer-commercial-5.5.35.0.msi, and utilizes MSI's to
1182
mysql-installer-community-5.5.36.0.msi or
1183
mysql-installer-commercial-5.5.36.0.msi, and utilizes MSI's to
1184
1184
automatically install MySQL server and other products. It will
1185
1185
download and apply updates to itself, and for each of the
1186
1186
installed products. It also configures the additional
1201
1201
Using MySQL Installer."
1203
1203
* The Complete Package: This package has a file name similar to
1204
mysql-5.5.35-win32.msi and contains all files needed for a
1204
mysql-5.5.36-win32.msi and contains all files needed for a
1205
1205
complete Windows installation, including the Configuration
1206
1206
Wizard. This package includes optional components such as the
1207
1207
embedded server and benchmark suite.
1209
1209
* The Noinstall Archive: This package has a file name similar to
1210
mysql-5.5.35-win32.zip and contains all the files found in the
1210
mysql-5.5.36-win32.zip and contains all the files found in the
1211
1211
Complete install package, with the exception of the
1212
1212
Configuration Wizard. This package does not include an
1213
1213
automated installer, and must be manually installed and
2255
2255
directory. In a default installation it contains C:\Program
2256
2256
Files\MySQL\MySQL Server 5.5\. The Version string contains the
2257
2257
release number. For example, for an installation of MySQL Server
2258
5.5.35, the key contains a value of 5.5.35.
2258
5.5.36, the key contains a value of 5.5.36.
2260
2260
These registry keys are used to help external tools identify the
2261
2261
installed location of the MySQL server, preventing a complete scan
2345
2345
the command line (or within a script), you need to use the
2346
2346
msiexec.exe tool. For example, to perform a quiet installation
2347
2347
(which shows no dialog boxes or progress):
2348
shell> msiexec /i mysql-5.5.35.msi /quiet
2348
shell> msiexec /i mysql-5.5.36.msi /quiet
2350
2350
The /i indicates that you want to perform an installation. The
2351
2351
/quiet option indicates that you want no interactive elements.
2353
2353
To provide a dialog box showing the progress during installation,
2354
2354
and the dialog boxes providing information on the installation and
2355
2355
registration of MySQL, use /passive mode instead of /quiet:
2356
shell> msiexec /i mysql-5.5.35.msi /passive
2356
shell> msiexec /i mysql-5.5.36.msi /passive
2358
2358
Regardless of the mode of the installation, installing the package
2359
2359
in this manner performs a 'Typical' installation, and installs the
2362
2362
You can also use this method to uninstall MySQL by using the
2363
2363
/uninstall or /x options:
2364
shell> msiexec /x mysql-5.5.35.msi /uninstall
2364
shell> msiexec /x mysql-5.5.36.msi /uninstall
2366
2366
To install MySQL and configure a MySQL instance from the command
2367
2367
line, see Section 2.3.6.13, "MySQL Server Instance Config Wizard:
2946
2946
service name MySQL55 and setting the root password to 1234.
2947
2947
shell> MySQLInstanceConfig.exe -i -q "-lC:\mysql_install_log.txt" »
2948
2948
"-nMySQL Server 5.5" "-pC:\Program Files\MySQL\MySQL Server 5.5" -
2950
2950
"-tmy-template.ini" "-cC:\mytest.ini" ServerType=DEVELOPMENT Datab
2951
2951
aseType=MIXED »
2952
2952
ConnectionUsage=DSS Port=3311 ServiceName=MySQL55 RootPassword=123
3224
3224
something like this, which indicates that the server is ready to
3225
3225
service client connections:
3226
3226
mysqld: ready for connections
3227
Version: '5.5.35' socket: '' port: 3306
3227
Version: '5.5.36' socket: '' port: 3306
3229
3229
The server continues to write to the console any further
3230
3230
diagnostic output it produces. You can open a new console window
4266
4266
As an alternative, you can use the native package manager within
4267
4267
your Linux distribution to automatically download and install
4268
MySQL for you. Native package installations can take of the
4268
MySQL for you. Native package installations can take care of the
4269
4269
download and dependencies required to run MySQL, but the MySQL
4270
4270
version will often be some versions behind the currently available
4271
4271
release. You will also normally be unable to install development
4866
4866
To use ULN, you need to obtain a ULN login and register the
4867
4867
machine used for installation with ULN. This is described in
4868
detail in the ULN FAQ (https://linux.oracle.com/uln_faq.html).
4869
This page also describes how to install and update packages.
4868
detail in the ULN FAQ (https://linux.oracle.com/uln_faq.html). The
4869
page also describes how to install and update packages.The MySQL
4870
packages are in the "MySQL for Oracle Linux 6" channel for your
4871
system architecture on ULN.
4872
4874
At the time of writing this (September 2012), ULN provides MySQL
4965
4967
To use this package, download the corresponding
4966
4968
mysql-VERSION-solaris10-PLATFORM.pkg.gz file, then uncompress it.
4968
shell> gunzip mysql-5.5.35-solaris10-x86_64.pkg.gz
4970
shell> gunzip mysql-5.5.36-solaris10-x86_64.pkg.gz
4970
4972
To install a new package, use pkgadd and follow the onscreen
4971
4973
prompts. You must have root privileges to perform this operation:
4972
shell> pkgadd -d mysql-5.5.35-solaris10-x86_64.pkg
4974
shell> pkgadd -d mysql-5.5.36-solaris10-x86_64.pkg
4974
4976
The following packages are available:
4975
4977
1 mysql MySQL Community Server (GPL)
4978
4980
Select package(s) you wish to process (or 'all' to process
4979
4981
all packages). (default: all) [?,??,q]:
5262
5264
Standard distributions are available as compressed tar files,
5263
5265
Zip archives, or RPM packages. Distribution files have names
5264
5266
of the form mysql-VERSION.tar.gz, mysql-VERSION.zip, or
5265
mysql-VERSION.rpm, where VERSION is a number like 5.5.35. File
5267
mysql-VERSION.rpm, where VERSION is a number like 5.5.36. File
5266
5268
names for source distributions can be distinguished from those
5267
5269
for precompiled binary distributions in that source
5268
5270
distribution names are generic and include no platform name,
5807
5809
ODBC_INCLUDES ODBC includes directory
5808
5810
ODBC_LIB_DIR ODBC library directory
5809
5811
SYSCONFDIR Option file directory 5.5.7
5812
WITH_ASAN Enable address sanitizer OFF 5.5.35
5810
5813
WITH_BUNDLED_LIBEVENT Use bundled libevent when building
5811
5814
ndbmemcache ON 5.5.16-ndb-7.2.2
5812
5815
WITH_BUNDLED_MEMCACHED Use bundled memcached when building
6144
6147
This value can be set at server startup with the --socket
6151
Whether to enable address sanitization, for compilers that
6152
support it. The default is off. This option was added in MySQL
6147
6155
* -DWITH_DEBUG=bool
6148
6156
Whether to include debugging support.
6149
6157
Configuring MySQL with debugging support enables you to use
6415
6423
2.11. Postinstallation Setup and Testing
6417
This section discusses post-installation items for Unix systems.
6418
If you are using Windows, see Section 2.3.10, "Windows
6425
This section discusses post-installation items for Unix-like
6426
systems. If you are using Windows, see Section 2.3.10, "Windows
6419
6427
Postinstallation Procedures."
6421
6429
After installing MySQL, there are some items that you should
6422
6430
address. For example:
6424
6432
* You should initialize the data directory and create the MySQL
6425
grant tables, as describe in Section 2.11.1, "Unix
6426
Postinstallation Procedures."
6433
grant tables, as describe in Section 2.11.1, "Postinstallation
6434
Procedures for Unix-like Systems."
6428
6436
* An important security concern is that the initial accounts in
6429
6437
the grant tables have no passwords. You should assign
6443
6451
account management in Section 6.2, "The MySQL Access Privilege
6444
6452
System," and Section 6.3, "MySQL User Account Management."
6446
2.11.1. Unix Postinstallation Procedures
6454
2.11.1. Postinstallation Procedures for Unix-like Systems
6448
After installing MySQL on Unix, you must initialize the grant
6449
tables, start the server, and make sure that the server works
6450
satisfactorily. You may also wish to arrange for the server to be
6451
started and stopped automatically when your system starts and
6452
stops. You should also assign passwords to the accounts in the
6456
After installing MySQL on a Unix-like system, you must initialize
6457
the grant tables, start the server, and make sure that the server
6458
works satisfactorily. You may also wish to arrange for the server
6459
to be started and stopped automatically when your system starts
6460
and stops. You should also assign passwords to the accounts in the
6455
On Unix, the grant tables are set up by the mysql_install_db
6456
program. For some installation methods, this program is run for
6457
you automatically if an existing database cannot be found.
6463
On a Unix-like system, the grant tables are set up by the
6464
mysql_install_db program. For some installation methods, this
6465
program is run for you automatically if an existing database
6459
6468
* If you install MySQL on Linux using RPM distributions, the
6460
6469
server RPM runs mysql_install_db.
6639
6648
on your platform and version of MySQL, but should be similar
6640
6649
to that shown here:
6641
6650
shell> bin/mysqladmin version
6642
mysqladmin Ver 14.12 Distrib 5.5.35, for pc-linux-gnu on i686
6651
mysqladmin Ver 14.12 Distrib 5.5.36, for pc-linux-gnu on i686
6645
Server version 5.5.35
6654
Server version 5.5.36
6646
6655
Protocol version 10
6647
6656
Connection Localhost via UNIX socket
6648
6657
UNIX socket /var/lib/mysql/mysql.sock
7056
7065
2.11.1.3. Starting and Troubleshooting the MySQL Server
7058
7067
This section provides troubleshooting suggestions for problems
7059
starting the server on Unix. If you are using Windows, see Section
7060
2.3.8, "Troubleshooting a Microsoft Windows MySQL Server
7068
starting the server on a Unix-like system. If you are using
7069
Windows, see Section 2.3.8, "Troubleshooting a Microsoft Windows
7070
MySQL Server Installation."
7063
7072
If you have problems starting the server, here are some things to
7086
7095
that you have them configured the way you want before starting the
7089
If you are using InnoDB tables, see Section 14.3.2, "Configuring
7098
If you are using InnoDB tables, see Section 14.3.7, "InnoDB
7092
7101
Storage engines will use default option values if you specify
7093
7102
none, but it is recommended that you review the available options
7146
7155
also start the server as root, but this raises security issues and
7147
7156
should be avoided.
7149
On Unix, change location into the data directory and check the
7150
ownership of the data directory and its contents to make sure the
7151
server has access. For example, if the data directory is
7158
Change location into the data directory and check the ownership of
7159
the data directory and its contents to make sure the server has
7160
access. For example, if the data directory is
7152
7161
/usr/local/mysql/var, use this command:
7153
7162
shell> ls -la /usr/local/mysql/var
7169
7178
If the server fails to start up correctly, check the error log.
7170
7179
Log files are located in the data directory (typically C:\Program
7171
7180
Files\MySQL\MySQL Server 5.5\data on Windows,
7172
/usr/local/mysql/data for a Unix binary distribution, and
7173
/usr/local/var for a Unix source distribution). Look in the data
7174
directory for files with names of the form host_name.err and
7181
/usr/local/mysql/data for a Unix/Linux binary distribution, and
7182
/usr/local/var for a Unix/Linux source distribution). Look in the
7183
data directory for files with names of the form host_name.err and
7175
7184
host_name.log, where host_name is the name of your server host.
7176
Then examine the last few lines of these files. On Unix, you can
7177
use tail to display them:
7185
Then examine the last few lines of these files. You can use tail
7178
7187
shell> tail host_name.err
7179
7188
shell> tail host_name.log
7226
7235
* On Unix, the mysql_install_db program populates the grant
7227
7236
tables. Some installation methods run this program for you.
7228
7237
Others require that you execute it manually. For details, see
7229
Section 2.11.1, "Unix Postinstallation Procedures."
7238
Section 2.11.1, "Postinstallation Procedures for Unix-like
7231
7241
The mysql.user grant table defines the initial MySQL user accounts
7232
7242
and their access privileges:
7516
7526
* Read the Release Notes
7517
7527
(http://dev.mysql.com/doc/relnotes/mysql/5.5/en/) as well,
7518
7528
which provide information about features that are new in MySQL
7519
5.5 or differ from from those found in earlier MySQL releases.
7529
5.5 or differ from those found in earlier MySQL releases.
7521
7531
* After upgrading to a new version of MySQL, run mysql_upgrade
7522
7532
(see Section 4.4.7, "mysql_upgrade --- Check and Upgrade MySQL
7750
7760
* Known issue: As of MySQL 5.5.32, for new installations, the
7751
url columns in the mysql datatbase help tables are now created
7761
url columns in the mysql database help tables are now created
7752
7762
as type TEXT to accommodate longer URLs. For upgrades,
7753
7763
mysql_upgrade does not update the columns. Modify them
7754
7764
manually using these statements:
8571
8581
In MySQL 5.6.3, the length limit for index prefix keys is
8572
8582
increased from 767 bytes to 3072 bytes, for InnoDB tables using
8573
ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED. See Section 14.3.15,
8583
ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED. See Section 14.3.9.7,
8574
8584
"Limits on InnoDB Tables" for details. This change is also
8575
8585
backported to MySQL 5.5.14. If you downgrade from one of these
8576
8586
releases or higher, to an earlier release with a lower length
8778
8788
You can copy the .frm, .MYI, and .MYD files for MyISAM tables
8779
8789
between different architectures that support the same
8780
8790
floating-point format. (MySQL takes care of any byte-swapping
8781
issues.) See Section 14.5, "The MyISAM Storage Engine."
8791
issues.) See Section 14.4, "The MyISAM Storage Engine."
8783
8793
In cases where you need to transfer databases between different
8784
8794
architectures, you can use mysqldump to create a file containing
added
removed
INSTALL-SOURCE
