507
507
shell> md5sum package_name
510
shell> md5sum mysql-standard-5.5.18-linux-i686.tar.gz
511
aaab65abbec64d5e907dcd41b8699945 mysql-standard-5.5.18-linux-i686.ta
510
shell> md5sum mysql-standard-5.5.20-linux-i686.tar.gz
511
aaab65abbec64d5e907dcd41b8699945 mysql-standard-5.5.20-linux-i686.ta
514
514
You should verify that the resulting checksum (the string of
636
636
Table 2.1. MySQL Package and Signature Files
637
637
File Type File Name
638
Distribution file mysql-standard-5.5.18-linux-i686.tar.gz
639
Signature file mysql-standard-5.5.18-linux-i686.tar.gz.asc
638
Distribution file mysql-standard-5.5.20-linux-i686.tar.gz
639
Signature file mysql-standard-5.5.20-linux-i686.tar.gz.asc
641
641
Make sure that both files are stored in the same directory and
642
642
then run the following command to verify the signature for the
644
644
shell> gpg --verify package_name.asc
647
shell> gpg --verify mysql-standard-5.5.18-linux-i686.tar.gz.asc
647
shell> gpg --verify mysql-standard-5.5.20-linux-i686.tar.gz.asc
648
648
gpg: Signature made Tue 01 Feb 2011 02:38:30 AM CST using DSA key ID
650
650
gpg: Good signature from "MySQL Release Engineering <mysql-build@oss.
664
664
shell> rpm --checksig package_name.rpm
667
shell> rpm --checksig MySQL-server-5.5.18-0.glibc23.i386.rpm
668
MySQL-server-5.5.18-0.glibc23.i386.rpm: md5 gpg OK
667
shell> rpm --checksig MySQL-server-5.5.20-0.glibc23.i386.rpm
668
MySQL-server-5.5.20-0.glibc23.i386.rpm: md5 gpg OK
741
741
MySQL compressed tar file binary distributions have names of the
742
742
form mysql-VERSION-OS.tar.gz, where VERSION is a number (for
743
example, 5.5.18), and OS indicates the type of operating system
743
example, 5.5.20), and OS indicates the type of operating system
744
744
for which the distribution is intended (for example, pc-linux-i686
1051
1051
within the "Complete Package."
1053
1053
* MySQL Installer: This package has a file name similar to
1054
mysql-installer-5.5.18.0.msi and utilizes MSI's to
1054
mysql-installer-5.5.20.0.msi and utilizes MSI's to
1055
1055
automatically install MySQL server and other products. It will
1056
1056
download and apply updates to itself, and for each of the
1057
1057
installed products. It also configures the additional
1062
1062
Server with its components.
1064
1064
* The Complete Package: This package has a file name similar to
1065
mysql-5.5.18-win32.msi and contains all files needed for a
1065
mysql-5.5.20-win32.msi and contains all files needed for a
1066
1066
complete Windows installation, including the Configuration
1067
1067
Wizard. This package includes optional components such as the
1068
1068
embedded server and benchmark suite.
1070
1070
* The Noinstall Archive: This package has a file name similar to
1071
mysql-5.5.18-win32.zip and contains all the files found in the
1071
mysql-5.5.20-win32.zip and contains all the files found in the
1072
1072
Complete install package, with the exception of the
1073
1073
Configuration Wizard. This package does not include an
1074
1074
automated installer, and must be manually installed and
1477
1477
directory. In a default installation it contains C:\Program
1478
1478
Files\MySQL\MySQL Server 5.5\. The Version string contains the
1479
1479
release number. For example, for an installation of MySQL Server
1480
5.5.18, the key contains a value of 5.5.18.
1480
5.5.20, the key contains a value of 5.5.20.
1482
1482
These registry keys are used to help external tools identify the
1483
1483
installed location of the MySQL server, preventing a complete scan
1567
1567
the command line (or within a script), you need to use the
1568
1568
msiexec.exe tool. For example, to perform a quiet installation
1569
1569
(which shows no dialog boxes or progress):
1570
shell> msiexec /i /quiet mysql-5.5.18.msi
1570
shell> msiexec /i /quiet mysql-5.5.20.msi
1572
1572
The /i indicates that you want to perform an installation. The
1573
1573
/quiet option indicates that you want no interactive elements.
1575
1575
To provide a dialog box showing the progress during installation,
1576
1576
and the dialog boxes providing information on the installation and
1577
1577
registration of MySQL, use /passive mode instead of /quiet:
1578
shell> msiexec /i /passive mysql-5.5.18.msi
1578
shell> msiexec /i /passive mysql-5.5.20.msi
1580
1580
Regardless of the mode of the installation, installing the package
1581
1581
in this manner performs a 'Typical' installation, and installs the
1584
1584
You can also use this method to uninstall MySQL by using the
1585
1585
/uninstall or /x options:
1586
shell> msiexec /x /quiet mysql-5.5.18.msi
1586
shell> msiexec /x /quiet mysql-5.5.20.msi
1588
1588
To install MySQL and configure a MySQL instance from the command
1589
1589
line, see Section 2.3.5.13, "MySQL Server Instance Config Wizard:
2168
2168
service name MySQL55 and setting the root password to 1234.
2169
2169
shell> MySQLInstanceConfig.exe -i -q "-lC:\mysql_install_log.txt" »
2170
2170
"-nMySQL Server 5.5" "-pC:\Program Files\MySQL\MySQL Server 5.5" -
2172
2172
"-tmy-template.ini" "-cC:\mytest.ini" ServerType=DEVELOPMENT Datab
2173
2173
aseType=MIXED »
2174
2174
ConnectionUsage=DSS Port=3311 ServiceName=MySQL55 RootPassword=123
2437
2437
something like this, which indicates that the server is ready to
2438
2438
service client connections:
2439
2439
mysqld: ready for connections
2440
Version: '5.5.18' socket: '' port: 3306
2440
Version: '5.5.20' socket: '' port: 3306
2442
2442
The server continues to write to the console any further
2443
2443
diagnostic output it produces. You can open a new console window
2914
2914
11. As Administrator, run mysql_upgrade to check your tables,
2915
2915
attempt to repair them if necessary, and update your grant
2916
2916
tables if they have changed so that you can take advantage of
2917
any new capabilities. See Section 4.4.8, "mysql_upgrade ---
2917
any new capabilities. See Section 4.4.7, "mysql_upgrade ---
2918
2918
Check Tables for MySQL Upgrade."
2919
2919
12. If you encounter errors, see Section 2.3.7, "Troubleshooting a
2920
2920
MySQL Installation Under Windows."
3483
3483
/usr/share/sql-bench Benchmarks
3486
RPM distributions of MySQL often are provided by other vendors. Be
3487
aware that they may differ in features and capabilities from those
3488
built by us, and that the instructions in this manual do not
3489
necessarily apply to installing them. The vendor's instructions
3490
should be consulted instead.
3486
RPM distributions of MySQL are also provided by other vendors. Be
3487
aware that they may differ from those built by us in features,
3488
capabilities, and conventions (including communication setup), and
3489
that the instructions in this manual do not necessarily apply to
3490
installing them. The vendor's instructions should be consulted
3492
3493
In most cases, you need to install only the MySQL-server and
3493
3494
MySQL-client packages to get a functional MySQL installation. The
3513
3514
If you get a dependency failure when trying to install MySQL
3514
3515
packages (for example, error: removing these packages would break
3515
3516
dependencies: libmysqlclient.so.10 is needed by ...), you should
3516
also install the MySQL-shared-compat package, which includes both
3517
the shared libraries for backward compatibility
3518
(libmysqlclient.so.12 for MySQL 4.0 and libmysqlclient.so.10 for
3517
also install the MySQL-shared-compat package, which includes the
3518
shared libraries for older releases for backward compatibility.
3521
3520
The RPM packages shown in the following list are available. The
3522
3521
names shown here use a suffix of .glibc23.i386.rpm, but particular
3534
3533
The libraries and include files that are needed if you want to
3535
3534
compile other MySQL clients, such as the Perl modules.
3537
* MySQL-debuginfo-VERSION.glibc23.i386.rpm
3538
This package contains debugging information. debuginfo RPMs
3539
are never needed to use MySQL software; this is true both for
3540
the server and for client programs. However, they contain
3541
additional information that might be needed by a debugger to
3544
3536
* MySQL-shared-VERSION.glibc23.i386.rpm
3545
3537
This package contains the shared libraries
3546
3538
(libmysqlclient.so*) that certain languages and applications
3550
3542
MySQL-shared-compat package.
3552
3544
* MySQL-shared-compat-VERSION.glibc23.i386.rpm
3553
This package includes the shared libraries for MySQL 3.23,
3554
4.0, and so on. It contains single-threaded and thread-safe
3555
libraries. Install this package if you have applications
3556
installed that are dynamically linked against older versions
3557
of MySQL but you want to upgrade to the current version
3558
without breaking the library dependencies. Before MySQL 5.5.6,
3559
MySQL-shared-compat also includes the libraries for the
3560
current release, so if you install it, you should not also
3561
install MySQL-shared. As of 5.5.6, MySQL-shared-compat does
3562
not include the current library version, so there is no
3545
This package includes the shared libraries for older releases.
3546
It contains single-threaded and thread-safe libraries. Install
3547
this package if you have applications installed that are
3548
dynamically linked against older versions of MySQL but you
3549
want to upgrade to the current version without breaking the
3550
library dependencies. Before MySQL 5.5.6, MySQL-shared-compat
3551
also includes the libraries for the current release, so if you
3552
install it, you should not also install MySQL-shared. As of
3553
5.5.6, MySQL-shared-compat does not include the current
3554
library version, so there is no conflict.
3565
3556
* MySQL-embedded-VERSION.glibc23.i386.rpm
3566
3557
The embedded MySQL server library.
3591
3582
glibc23 Platform independent, should run on any Linux distribution
3592
3583
that supports glibc 2.3
3593
3584
rhel4, rhel5 Red Hat Enterprise Linux 4 or 5
3585
el6 Enterprise Linux 6
3594
3586
sles10, sles11 SuSE Linux Enterprise Server 10 or 11
3596
3588
In MySQL 5.5, only glibc23 packages are available currently.
3599
3591
package is built.
3601
3593
Table 2.13. MySQL Installation Packages for Linux CPU Identifier
3602
CPU Value Intended Processor Type or Family
3603
i386 x86 processor, 386 and up
3604
i586 x86 processor, Pentium and up
3605
x86_64 64-bit x86 processor
3606
ia64 Itanium (IA-64) processor
3594
CPU Value Intended Processor Type or Family
3595
i386, i586, i686 Pentium processor or better, 32 bit
3596
x86_64 64-bit x86 processor
3597
ia64 Itanium (IA-64) processor
3608
3599
To see all files in an RPM package (for example, a MySQL-server
3609
3600
RPM), run a command like this:
3633
3624
"Starting and Stopping MySQL Automatically," for more information
3634
3625
on how MySQL can be started automatically on system startup.
3636
If you want to install the MySQL RPM on older Linux distributions
3637
that do not support initialization scripts in /etc/init.d
3638
(directly or through a symlink), you should create a symbolic link
3639
that points to the location where your initialization scripts
3640
actually are installed. For example, if that location is
3641
/etc/rc.d/init.d, use these commands before installing the RPM to
3642
create /etc/init.d as a symbolic link that points there:
3644
shell> ln -s rc.d/init.d .
3646
However, all current major Linux distributions should support the
3647
new directory layout that uses /etc/init.d, because it is required
3648
for LSB (Linux Standard Base) compliance.
3650
3627
In MySQL 5.5.5 and later, during a new installation, the server
3651
3628
boot scripts are installed, but the MySQL server is not started at
3652
3629
the end of the installation, since the status of the server during
4039
4016
To use this package, download the corresponding
4040
4017
mysql-VERSION-solaris10-PLATFORM.pkg.gz file, then decompress it.
4042
shell> gunzip mysql-5.5.18-solaris10-x86_64.pkg.gz
4019
shell> gunzip mysql-5.5.20-solaris10-x86_64.pkg.gz
4044
4021
To install a new package, use pkgadd and follow the onscreen
4045
4022
prompts. You must have root privileges to perform this operation:
4046
shell> pkgadd -d mysql-5.5.18-solaris10-x86_64.pkg
4023
shell> pkgadd -d mysql-5.5.20-solaris10-x86_64.pkg
4048
4025
The following packages are available:
4049
4026
1 mysql MySQL Community Server (GPL)
4052
4029
Select package(s) you wish to process (or 'all' to process
4053
4030
all packages). (default: all) [?,??,q]:
4335
4312
Standard distributions are available as compressed tar files,
4336
4313
Zip archives, or RPM packages. Distribution files have names
4337
4314
of the form mysql-VERSION.tar.gz, mysql-VERSION.zip, or
4338
mysql-VERSION.rpm, where VERSION is a number like 5.5.18. File
4315
mysql-VERSION.rpm, where VERSION is a number like 5.5.20. File
4339
4316
names for source distributions can be distinguished from those
4340
4317
for precompiled binary distributions in that source
4341
4318
distribution names are generic and include no platform name,
4872
4849
development environment OFF 5.5.7
4873
4850
MYSQL_TCP_PORT TCP/IP port number 3306 5.5.7
4874
4851
MYSQL_UNIX_ADDR Unix socket file /tmp/mysql.sock 5.5.7
4852
ODBC_INCLUDES ODBC includes directory
4853
ODBC_LIB_DIR ODBC library directory
4875
4854
SYSCONFDIR Option file directory 5.5.7
4876
4855
WITH_COMMENT Comment about compilation environment 5.5.7
4877
4856
WITH_DEBUG Whether to include debugging support OFF 5.5.7
4885
4864
WITH_READLINE Use bundled readline OFF 5.5.7
4886
4865
WITH_SSL Type of SSL support no 5.5.7
4866
WITH_UNIXODBC Enable unixODBC support OFF
4887
4867
WITH_ZLIB Type of zlib support system 5.5.7
4888
4868
WITHOUT_xxx_STORAGE_ENGINE Exclude storage engine xxx from build
5021
5001
This value can be set at server startup with the --datadir
5004
* -DODBC_INCLUDES=dir_name
5005
The location of the ODBC includes directory, and may be used
5006
while configuring Connector/ODBC.
5008
* -DODBC_LIB_DIR=dir_name
5009
The location of the ODBC library directory, and may be used
5010
while configuring Connector/ODBC.
5024
5012
* -DSYSCONFDIR=dir_name
5025
5013
The default my.cnf option file directory.
5026
5014
This location cannot be set at server startup, but you can
5258
5249
shell> devenv MySQL.sln /clean
5259
5250
shell> del CMakeCache.txt
5252
If you build out of the source tree, remove and recreate your
5253
build directory before re-running CMake. For instructions on out
5254
of source building, see Section 2.9.2, "Installing MySQL from a
5255
Standard Source Distribution."
5261
5257
On some systems, warnings may occur due to differences in system
5262
5258
include files. The following list describes other problems that
5263
5259
have been found to occur most often when compiling MySQL:
5272
5268
shell> CXXFLAGS=-O3
5273
5269
shell> export CC CFLAGS CXX CXXFLAGS
5270
To see what flags you might need to specify, invoke
5271
mysql_config with the --cflags option.
5275
5273
* If compilation fails, check whether the MYSQL_MAINTAINER_MODE
5276
5274
option is enabled. This mode causes compiler warnings to
5551
5549
on your platform and version of MySQL, but should be similar
5552
5550
to that shown here:
5553
5551
shell> bin/mysqladmin version
5554
mysqladmin Ver 14.12 Distrib 5.5.18, for pc-linux-gnu on i686
5552
mysqladmin Ver 14.12 Distrib 5.5.20, for pc-linux-gnu on i686
5557
Server version 5.5.18
5555
Server version 5.5.20
5558
5556
Protocol version 10
5559
5557
Connection Localhost via UNIX socket
5560
5558
UNIX socket /var/lib/mysql/mysql.sock
6436
6434
or differ from those found in earlier MySQL releases.
6438
6436
* After upgrading to a new version of MySQL, run mysql_upgrade
6439
(see Section 4.4.8, "mysql_upgrade --- Check Tables for MySQL
6437
(see Section 4.4.7, "mysql_upgrade --- Check Tables for MySQL
6440
6438
Upgrade"). This program checks your tables, and attempts to
6441
6439
repair them if necessary. It also updates your grant tables to
6442
6440
make sure that they have the current structure so that you can
6566
6564
done before upgrading. Use of this statement with a version of
6567
6565
MySQL different from the one used to create the table (that
6568
6566
is, using it after upgrading) may damage the table. See
6569
Section 12.4.2.5, "REPAIR TABLE Syntax."
6567
Section 12.7.2.5, "REPAIR TABLE Syntax."
6571
6569
* Before upgrading to a new version of MySQL, Section 2.11.3,
6572
6570
"Checking Whether Tables or Indexes Must Be Rebuilt," to see
6579
6577
Tables or Indexes."
6581
6579
* After upgrading to a new version of MySQL, run mysql_upgrade
6582
(see Section 4.4.8, "mysql_upgrade --- Check Tables for MySQL
6580
(see Section 4.4.7, "mysql_upgrade --- Check Tables for MySQL
6583
6581
Upgrade"). This program checks your tables, and attempts to
6584
6582
repair them if necessary. It also updates your grant tables to
6585
6583
make sure that they have the current structure so that you can
6798
6796
throw an "out of range" error (ER_DATA_OUT_OF_RANGE) rather
6799
6797
than returning an incorrect value or NULL, when the result is
6800
6798
out of the supported range for the corresponding data type.
6801
See Section 10.6, "Out-of-Range and Overflow Handling."
6799
See Section 10.2.6, "Out-of-Range and Overflow Handling."
6803
6801
* Incompatible change: In very old versions of MySQL (prior to
6804
6802
4.1), the TIMESTAMP data type supported a display width, which
7034
7032
done before upgrading. Use of this statement with a version of
7035
7033
MySQL different from the one used to create the table (that
7036
7034
is, using it after upgrading) may damage the table. See
7037
Section 12.4.2.5, "REPAIR TABLE Syntax."
7035
Section 12.7.2.5, "REPAIR TABLE Syntax."
7039
7037
* Before upgrading to a new version of MySQL, Section 2.11.3,
7040
7038
"Checking Whether Tables or Indexes Must Be Rebuilt," to see
7047
7045
Tables or Indexes."
7049
7047
* After upgrading to a new version of MySQL, run mysql_upgrade
7050
(see Section 4.4.8, "mysql_upgrade --- Check Tables for MySQL
7048
(see Section 4.4.7, "mysql_upgrade --- Check Tables for MySQL
7051
7049
Upgrade"). This program checks your tables, and attempts to
7052
7050
repair them if necessary. It also updates your grant tables to
7053
7051
make sure that they have the current structure so that you can
7355
7353
MySQL 5.1 after upgrading. The same problem occurs for binary
7356
7354
downgrades from MySQL 5.1 to 5.0.
7356
The upgrade problem is fixed in MySQL 5.6.4: The server can open
7357
ARCHIVE tables created in MySQL 5.0. However, it remains the
7358
recommended upgrade procedure to dump 5.0 ARCHIVE tables before
7359
upgrading and reload them after upgrading.
7358
7361
Index Incompatibilities
7360
7363
In MySQL 5.5.14, the length limit for index prefix keys is
7418
7421
TABLE. However, the use of CHECK TABLE applies only after
7419
7422
upgrades, not downgrades. Also, CHECK TABLE is not applicable to
7420
7423
all storage engines. For details about which storage engines CHECK
7421
TABLE supports, see Section 12.4.2.2, "CHECK TABLE Syntax."
7424
TABLE supports, see Section 12.7.2.2, "CHECK TABLE Syntax."
7423
7426
Changes that cause index rebuilding to be necessary:
7507
7510
the file, as described earlier.
7509
7512
For specifics about which storage engines REPAIR TABLE supports,
7510
see Section 12.4.2.5, "REPAIR TABLE Syntax."
7513
see Section 12.7.2.5, "REPAIR TABLE Syntax."
7512
7515
mysqlcheck --repair provides command-line access to the REPAIR
7513
7516
TABLE statement. This can be a more convenient means of repairing
7775
7778
This procedure should work with ActiveState Perl 5.6 or newer.
7777
7780
If you cannot get the procedure to work, you should install the
7778
MyODBC driver instead and connect to the MySQL server through
7781
ODBC driver instead and connect to the MySQL server through ODBC:
7781
7783
$dbh= DBI->connect("DBI:ODBC:$dsn",$user,$password) ||
7782
7784
die "Got error $DBI::errstr when connecting to $dsn\n";
7842
7844
After this, you must run make realclean and then proceed with the
7843
7845
installation from the beginning.
7845
Copyright (c) 1997, 2011, Oracle and/or its affiliates. All rights
7846
reserved. [1]Legal Notices
7851
1. file://localhost/data0/users/mysqldoc/docs-build/mysqldoc/refman-5.5/installing-nolink.html#legalnotice
added
removed
INSTALL-SOURCE
