189 8069 5689
这篇文章主要为大家展示了“Linux如何安装MySQL数据库”，内容简而易懂，条理清晰，希望能够帮助大家解决疑惑，下面让小编带领大家一起研究并学习一下“Linux如何安装mysql数据库”这篇文章吧。
网站制作、建网站找专业的建站公司成都创新互联:定制网站、模板网站、仿站、小程序制作、软件开发、app软件定制开发等。做网站价格咨询成都创新互联:服务完善、10余年建站、值得信赖!网站制作电话：13518219792
[root@szq enterprise]# rpm -ivh MySQL-client-advanced-5.6.24-1.el6.x86_64.rpm
Preparing... ########################################### [100%]
package MySQL-client-advanced-5.6.24-1.el6.x86_64 is already installed
[root@szq enterprise]# rpm -ivh MySQL-shared-advanced-5.6.24-1.el6.x86_64.rpm
Preparing... ########################################### [100%]
1:MySQL-shared-advanced ########################################### [100%]
[root@szq enterprise]# rpm -ivh MySQL-devel-advanced-5.6.24-1.el6.x86_64.rpm
Preparing... ########################################### [100%]
1:MySQL-devel-advanced ########################################### [100%]
[root@szq enterprise]# rpm -ivh MySQL-server-advanced-5.6.24-1.el6.x86_64.rpm
Preparing... ########################################### [100%]
file /usr/share/mysql/czech/errmsg.sys from install of MySQL-server-advanced-5.6.24-1.el6.x86_64 conflicts with file from package mysql-libs-5.1.52-1.el6_0.1.x86_64
file /usr/share/mysql/danish/errmsg.sys from install of MySQL-server-advanced-5.6.24-1.el6.x86_64 conflicts with file from package mysql-libs-5.1.52-1.el6_0.1.x86_64
file /usr/share/mysql/dutch/errmsg.sys from install of MySQL-server-advanced-5.6.24-1.el6.x86_64 conflicts with file from package mysql-libs-5.1.52-1.el6_0.1.x86_64
file /usr/share/mysql/english/errmsg.sys from install of MySQL-server-advanced-5.6.24-1.el6.x86_64 conflicts with file from package mysql-libs-5.1.52-1.el6_0.1.x86_64
file /usr/share/mysql/estonian/errmsg.sys from install of MySQL-server-advanced-5.6.24-1.el6.x86_64 conflicts with file from package mysql-libs-5.1.52-1.el6_0.1.x86_64
file /usr/share/mysql/french/errmsg.sys from install of MySQL-server-advanced-5.6.24-1.el6.x86_64 conflicts with file from package mysql-libs-5.1.52-1.el6_0.1.x86_64
file /usr/share/mysql/german/errmsg.sys from install of MySQL-server-advanced-5.6.24-1.el6.x86_64 conflicts with file from package mysql-libs-5.1.52-1.el6_0.1.x86_64
这里报错，一大堆，其实就是因为本系统之前已经有了mysql-libs 这个包，可以查看验证：
[root@szq enterprise]# rpm -qa|grep mysql-libs
mysql-libs-5.1.52-1.el6_0.1.x86_64
先将这个已经存在的安装包卸载，再安装新包：
[root@szq enterprise]# rpm -e mysql-libs-5.1.52-1.el6_0.1.x86_64
error: Failed dependencies:
libmysqlclient.so.16()(64bit) is needed by (installed) postfix-2:2.6.6-2.2.el6_1.x86_64
libmysqlclient.so.16(libmysqlclient_16)(64bit) is needed by (installed) postfix-2:2.6.6-2.2.el6_1.x86_64
mysql-libs is needed by (installed) postfix-2:2.6.6-2.2.el6_1.x86_64
[root@szq enterprise]#
这里由于依赖关系，报错，我们选择忽略依赖关系的 “--nodeps"选项，就会卸载成功！
[root@szq enterprise]# rpm -e --nodeps mysql-libs-5.1.52-1.el6_0.1.x86_64
[root@szq enterprise]#
[root@szq enterprise]# rpm -ivh MySQL-server-advanced-5.6.24-1.el6.x86_64.rpm
Preparing... ########################################### [100%]
1:MySQL-server-advanced ########################################### [100%]
2016-03-28 14:58:36 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-03-28 14:58:36 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-enterprise-commercial-advanced) starting as process 27331 ...
2016-03-28 14:58:36 27331 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-03-28 14:58:36 27331 [Note] InnoDB: The InnoDB memory heap is disabled
2016-03-28 14:58:36 27331 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-03-28 14:58:36 27331 [Note] InnoDB: Memory barrier is not used
2016-03-28 14:58:36 27331 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-03-28 14:58:36 27331 [Note] InnoDB: Using Linux native AIO
2016-03-28 14:58:36 27331 [Note] InnoDB: Not using CPU crc32 instructions
2016-03-28 14:58:36 27331 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-03-28 14:58:36 27331 [Note] InnoDB: Completed initialization of buffer pool
2016-03-28 14:58:36 27331 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2016-03-28 14:58:36 27331 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2016-03-28 14:58:36 27331 [Note] InnoDB: Database physically writes the file full: wait...
2016-03-28 14:58:36 27331 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2016-03-28 14:58:41 27331 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2016-03-28 14:58:56 27331 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2016-03-28 14:58:56 27331 [Warning] InnoDB: New log files created, LSN=45781
2016-03-28 14:58:56 27331 [Note] InnoDB: Doublewrite buffer not found: creating new
2016-03-28 14:58:57 27331 [Note] InnoDB: Doublewrite buffer created
2016-03-28 14:58:57 27331 [Note] InnoDB: 128 rollback segment(s) are active.
2016-03-28 14:58:57 27331 [Warning] InnoDB: Creating foreign key constraint system tables.
2016-03-28 14:58:57 27331 [Note] InnoDB: Foreign key constraint system tables created
2016-03-28 14:58:57 27331 [Note] InnoDB: Creating tablespace and datafile system tables.
2016-03-28 14:58:57 27331 [Note] InnoDB: Tablespace and datafile system tables created.
2016-03-28 14:58:57 27331 [Note] InnoDB: Waiting for purge to start
2016-03-28 14:58:57 27331 [Note] InnoDB: 5.6.24 started; log sequence number 0
2016-03-28 14:58:57 27331 [Note] RSA private key file not found: /var/lib/mysql//private_key.pem. Some authentication plugins will not work.
2016-03-28 14:58:57 27331 [Note] RSA public key file not found: /var/lib/mysql//public_key.pem. Some authentication plugins will not work.
A random root password has been set. You will find it in '/root/.mysql_secret'.
2016-03-28 14:58:58 27331 [Note] Binlog end
2016-03-28 14:58:58 27331 [Note] InnoDB: FTS optimize thread exiting.
2016-03-28 14:58:58 27331 [Note] InnoDB: Starting shutdown...
2016-03-28 14:59:01 27331 [Note] InnoDB: Shutdown completed; log sequence number 1625977
2016-03-28 14:59:01 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-03-28 14:59:01 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-enterprise-commercial-advanced) starting as process 27353 ...
2016-03-28 14:59:01 27353 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-03-28 14:59:01 27353 [Note] InnoDB: The InnoDB memory heap is disabled
2016-03-28 14:59:01 27353 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-03-28 14:59:01 27353 [Note] InnoDB: Memory barrier is not used
2016-03-28 14:59:01 27353 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-03-28 14:59:01 27353 [Note] InnoDB: Using Linux native AIO
2016-03-28 14:59:01 27353 [Note] InnoDB: Not using CPU crc32 instructions
2016-03-28 14:59:01 27353 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-03-28 14:59:01 27353 [Note] InnoDB: Completed initialization of buffer pool
2016-03-28 14:59:01 27353 [Note] InnoDB: Highest supported file format is Barracuda.
2016-03-28 14:59:01 27353 [Note] InnoDB: 128 rollback segment(s) are active.
2016-03-28 14:59:01 27353 [Note] InnoDB: Waiting for purge to start
2016-03-28 14:59:01 27353 [Note] InnoDB: 5.6.24 started; log sequence number 1625977
2016-03-28 14:59:01 27353 [Note] RSA private key file not found: /var/lib/mysql//private_key.pem. Some authentication plugins will not work.
2016-03-28 14:59:01 27353 [Note] RSA public key file not found: /var/lib/mysql//public_key.pem. Some authentication plugins will not work.
2016-03-28 14:59:01 27353 [Note] Binlog end
2016-03-28 14:59:01 27353 [Note] InnoDB: FTS optimize thread exiting.
2016-03-28 14:59:01 27353 [Note] InnoDB: Starting shutdown...
2016-03-28 14:59:03 27353 [Note] InnoDB: Shutdown completed; log sequence number 162598
A RANDOM PASSWORD HAS BEEN SET FOR THE MySQL root USER !
You will find that password in '/root/.mysql_secret'.
You must change that password on your first connect,
no other statement but 'SET PASSWORD' will be accepted.
See the manual for the semantics of the 'password expired' flag.
Also, the account for the anonymous user has been removed.
In addition, you can run:
/usr/bin/mysql_secure_installation
which will also give you the option of removing the test database.
This is strongly recommended for production servers.
See the manual for more instructions.
Please report any problems at http://bugs.mysql.com/
The latest information about MySQL is available on the web at
http://www.mysql.com
Support MySQL by buying support/licenses at http://shop.mysql.com
New default config file was created as /usr/my.cnf and
will be used by default by the server when you start it.
You may edit this file to change server settings
[root@szq enterprise]# cat /root/.mysql_secret
# The random password set for the root user at Mon Mar 28 14:58:58 2016 (local time): RK_wpPXYQ7MTjbZy
[root@szq enterprise]# /usr/bin/mysql_secure_installation
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!
In order to log into MySQL to secure it, we'll need the current
password for the root user. If you've just installed MySQL, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.
Enter current password for root (enter for none):
OK, successfully used password, moving on...
Setting the root password ensures that nobody can log into the MySQL
root user without the proper authorisation.
You already have a root password set, so you can safely answer 'n'.
Change the root password? [Y/n] y
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
... Success!
By default, a MySQL installation has an anonymous user, allowing anyone
to log into MySQL without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.
Remove anonymous users? [Y/n] y
... Success!
Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.
Disallow root login remotely? [Y/n] n
... skipping.
By default, MySQL comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.
Remove test database and access to it? [Y/n] y
- Dropping test database...
... Success!
- Removing privileges on test database...
... Success!
Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.
Reload privilege tables now? [Y/n] y
... Success!
All done! If you've completed all of the above steps, your MySQL
installation should now be secure.
Thanks for using MySQL!
Cleaning up...
[root@szq enterprise]# mysql -pmysql123 (小写的p后面直接跟密码，不能有空格，若有空格，则被认为是db name。其他参数无此要求，可有空格也可无空格。)
Warning: Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 16
Server version: 5.6.24-enterprise-commercial-advanced MySQL Enterprise Server - Advanced Edition (Commercial)
Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql>
以上是“Linux如何安装mysql数据库”这篇文章的所有内容，感谢各位的阅读！相信大家都有了一定的了解，希望分享的内容对大家有所帮助，如果还想学习更多知识，欢迎关注创新互联行业资讯频道！