搜索
首页数据库mysql教程Ubuntu下安装MySQL5.6.23_MySQL

Ubuntu下安装MySQL 5.6.23
1.下载对应Linux-generic的源码包,解压,将解压后的文件夹重命名为mysql,移动到/usr/local目录下; tar –xzf mysql-5.6.23-linux-glibc2.5-x86_64.tar.gz mv mysql-5.6.23-linux-glibc2.5-x86_64 mysql sudo mv mysql /usr/local
2.创建用户mysql和组mysql vonzhou@de16-C6100: sudo groupadd mysql
vonzhou@de16-C6100: sudo useradd -r -g mysql mysql
3、进入mysql目录 vonzhou@de16-C6100: sudo cd /usr/local/mysql
4、将mysql文件夹own及grp变更为mysql vonzhou@de16-C6100:/usr/local/mysql$ sudo chown -R mysql . vonzhou@de16-C6100:/usr/local/mysql$ sudo chgrp -R mysql .

5、执行mysql安装脚本,设置用户
vonzhou@de16-C6100:/usr/local/mysql$ sudo ./scripts/mysql_install_db --user=mysql
Installing MySQL system tables..../bin/mysqld: error while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory vonzhou@de16-C6100:/usr/local/mysql$ sudo apt-get install libaio-dev
(..........)
vonzhou@de16-C6100:/usr/local/mysql$ sudo ./scripts/mysql_install_db --user=mysql
Installing MySQL system tables...2015-03-18 21:22:46 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-03-18 21:22:46 5284 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-03-18 21:22:46 5284 [Note] InnoDB: The InnoDB memory heap is disabled
2015-03-18 21:22:46 5284 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-03-18 21:22:46 5284 [Note] InnoDB: Memory barrier is not used
2015-03-18 21:22:46 5284 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-03-18 21:22:46 5284 [Note] InnoDB: Using Linux native AIO
2015-03-18 21:22:46 5284 [Note] InnoDB: Using CPU crc32 instructions
2015-03-18 21:22:46 5284 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-03-18 21:22:46 5284 [Note] InnoDB: Completed initialization of buffer pool
2015-03-18 21:22:46 5284 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2015-03-18 21:22:46 5284 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2015-03-18 21:22:46 5284 [Note] InnoDB: Database physically writes the file full: wait...
2015-03-18 21:22:46 5284 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2015-03-18 21:22:46 5284 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2015-03-18 21:22:47 5284 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2015-03-18 21:22:47 5284 [Warning] InnoDB: New log files created, LSN=45781
2015-03-18 21:22:47 5284 [Note] InnoDB: Doublewrite buffer not found: creating new
2015-03-18 21:22:47 5284 [Note] InnoDB: Doublewrite buffer created
2015-03-18 21:22:47 5284 [Note] InnoDB: 128 rollback segment(s) are active.
2015-03-18 21:22:47 5284 [Warning] InnoDB: Creating foreign key constraint system tables.
2015-03-18 21:22:47 5284 [Note] InnoDB: Foreign key constraint system tables created
2015-03-18 21:22:47 5284 [Note] InnoDB: Creating tablespace and datafile system tables.
2015-03-18 21:22:47 5284 [Note] InnoDB: Tablespace and datafile system tables created.
2015-03-18 21:22:47 5284 [Note] InnoDB: Waiting for purge to start
2015-03-18 21:22:48 5284 [Note] InnoDB: 5.6.23 started; log sequence number 0
2015-03-18 21:22:52 5284 [Note] Binlog end
2015-03-18 21:22:52 5284 [Note] InnoDB: FTS optimize thread exiting.
2015-03-18 21:22:52 5284 [Note] InnoDB: Starting shutdown...
2015-03-18 21:22:53 5284 [Note] InnoDB: Shutdown completed; log sequence number 1625977
OK

Filling help tables...2015-03-18 21:22:53 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-03-18 21:22:53 5307 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-03-18 21:22:53 5307 [Note] InnoDB: The InnoDB memory heap is disabled
2015-03-18 21:22:53 5307 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-03-18 21:22:53 5307 [Note] InnoDB: Memory barrier is not used
2015-03-18 21:22:53 5307 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-03-18 21:22:53 5307 [Note] InnoDB: Using Linux native AIO
2015-03-18 21:22:53 5307 [Note] InnoDB: Using CPU crc32 instructions
2015-03-18 21:22:53 5307 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-03-18 21:22:53 5307 [Note] InnoDB: Completed initialization of buffer pool
2015-03-18 21:22:53 5307 [Note] InnoDB: Highest supported file format is Barracuda.
2015-03-18 21:22:53 5307 [Note] InnoDB: 128 rollback segment(s) are active.
2015-03-18 21:22:53 5307 [Note] InnoDB: Waiting for purge to start
2015-03-18 21:22:53 5307 [Note] InnoDB: 5.6.23 started; log sequence number 1625977
2015-03-18 21:22:53 5307 [Note] Binlog end
2015-03-18 21:22:53 5307 [Note] InnoDB: FTS optimize thread exiting.
2015-03-18 21:22:53 5307 [Note] InnoDB: Starting shutdown...
2015-03-18 21:22:55 5307 [Note] InnoDB: Shutdown completed; log sequence number 1625987
OK

To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:

./bin/mysqladmin -u root password 'new-password'
./bin/mysqladmin -u root -h de16-C6100 password 'new-password'

Alternatively you can run:

./bin/mysql_secure_installation

which will also give you the option of removing the test
databases and anonymous user created by default. This is
strongly recommended for production servers.

See the manual for more instructions.

You can start the MySQL daemon with:

cd . ; ./bin/mysqld_safe &

You can test the MySQL daemon with mysql-test-run.pl

cd mysql-test ; perl mysql-test-run.pl

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

WARNING: Found existing config file ./my.cnf on the system.
Because this file might be in use, it was not replaced,
but was used in bootstrap (unless you used --defaults-file)
and when you later start the server.
The new default config file was created as ./my-new.cnf,
please compare it with your file and take the changes you need. 6.上述步骤安装完成后,把该目录的所有权变更回来,除了data目录可以供我们普通用户操作; vonzhou@de16-C6100:/usr/local/mysql$ sudo chown -R root .
vonzhou@de16-C6100:/usr/local/mysql$ sudo chown -R mysql data
7. 可以改变默认配置文件的位置; vonzhou@de16-C6100:/usr/local/mysql$ sudo cp support-files/my-default.cnf /etc/my.cnf
8.后台启动mysql server;
vonzhou@de16-C6100:/usr/local/mysql$ sudo bin/mysqld_safe --user=mysql &
[1] 5375
vonzhou@de16-C6100:/usr/local/mysql$ 150318 21:29:24 mysqld_safe Logging to '/usr/local/mysql/data/de16-C6100.err'.
150318 21:29:24 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data

9. 设置MySQL root权限的密码;
vonzhou@de16-C6100:/usr/local/mysql$ sudo bin/mysqladmin -u root password '你的密码'
Warning: Using a password on the command line interface can be insecure.
10. 把执行脚本移到init.d目录下;
vonzhou@de16-C6100:/usr/local/mysql$ sudo cp support-files/mysql.server /etc/init.d/mysql.server
11.此时可以查看运行状态,可以用service命令的status/start/stop/restart控制;
vonzhou@de16-C6100:/usr/local/mysql$ sudo service mysql.server status
* MySQL running (5477)
12.设置开机启动(就是插入到那些开机会自动运行的脚本中),取消自启动的话defaults -> remove ;
vonzhou@de16-C6100:/usr/local/mysql$ sudo update-rc.d mysql.server defaults
Adding system startup for /etc/init.d/mysql.server ...
/etc/rc0.d/K20mysql.server -> ../init.d/mysql.server
/etc/rc1.d/K20mysql.server -> ../init.d/mysql.server
/etc/rc6.d/K20mysql.server -> ../init.d/mysql.server
/etc/rc2.d/S20mysql.server -> ../init.d/mysql.server
/etc/rc3.d/S20mysql.server -> ../init.d/mysql.server
/etc/rc4.d/S20mysql.server -> ../init.d/mysql.server
/etc/rc5.d/S20mysql.server -> ../init.d/mysql.server
13.搞个符号连接,方便命令的输入;
vonzhou@de16-C6100:/usr/local/mysql$ sudo ln -s /usr/local/mysql/bin/mysql /usr/local/bin/mysql
14. 此时,就按照好了,可以简单测试下。 vonzhou@de16-C6100:/usr/local/mysql$ mysql
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 2
Server version: 5.6.23 MySQL Community Server (GPL)

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> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| test |
+--------------------+
2 rows in set (0.00 sec)

mysql> exit
Bye

声明
本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容,请联系admin@php.cn
MySQL的位置:数据库和编程MySQL的位置:数据库和编程Apr 13, 2025 am 12:18 AM

MySQL在数据库和编程中的地位非常重要,它是一个开源的关系型数据库管理系统,广泛应用于各种应用场景。1)MySQL提供高效的数据存储、组织和检索功能,支持Web、移动和企业级系统。2)它使用客户端-服务器架构,支持多种存储引擎和索引优化。3)基本用法包括创建表和插入数据,高级用法涉及多表JOIN和复杂查询。4)常见问题如SQL语法错误和性能问题可以通过EXPLAIN命令和慢查询日志调试。5)性能优化方法包括合理使用索引、优化查询和使用缓存,最佳实践包括使用事务和PreparedStatemen

MySQL:从小型企业到大型企业MySQL:从小型企业到大型企业Apr 13, 2025 am 12:17 AM

MySQL适合小型和大型企业。1)小型企业可使用MySQL进行基本数据管理,如存储客户信息。2)大型企业可利用MySQL处理海量数据和复杂业务逻辑,优化查询性能和事务处理。

幻影是什么读取的,InnoDB如何阻止它们(下一个键锁定)?幻影是什么读取的,InnoDB如何阻止它们(下一个键锁定)?Apr 13, 2025 am 12:16 AM

InnoDB通过Next-KeyLocking机制有效防止幻读。1)Next-KeyLocking结合行锁和间隙锁,锁定记录及其间隙,防止新记录插入。2)在实际应用中,通过优化查询和调整隔离级别,可以减少锁竞争,提高并发性能。

mysql:不是编程语言,而是...mysql:不是编程语言,而是...Apr 13, 2025 am 12:03 AM

MySQL不是一门编程语言,但其查询语言SQL具备编程语言的特性:1.SQL支持条件判断、循环和变量操作;2.通过存储过程、触发器和函数,用户可以在数据库中执行复杂逻辑操作。

MySQL:世界上最受欢迎的数据库的简介MySQL:世界上最受欢迎的数据库的简介Apr 12, 2025 am 12:18 AM

MySQL是一种开源的关系型数据库管理系统,主要用于快速、可靠地存储和检索数据。其工作原理包括客户端请求、查询解析、执行查询和返回结果。使用示例包括创建表、插入和查询数据,以及高级功能如JOIN操作。常见错误涉及SQL语法、数据类型和权限问题,优化建议包括使用索引、优化查询和分表分区。

MySQL的重要性:数据存储和管理MySQL的重要性:数据存储和管理Apr 12, 2025 am 12:18 AM

MySQL是一个开源的关系型数据库管理系统,适用于数据存储、管理、查询和安全。1.它支持多种操作系统,广泛应用于Web应用等领域。2.通过客户端-服务器架构和不同存储引擎,MySQL高效处理数据。3.基本用法包括创建数据库和表,插入、查询和更新数据。4.高级用法涉及复杂查询和存储过程。5.常见错误可通过EXPLAIN语句调试。6.性能优化包括合理使用索引和优化查询语句。

为什么要使用mysql?利益和优势为什么要使用mysql?利益和优势Apr 12, 2025 am 12:17 AM

选择MySQL的原因是其性能、可靠性、易用性和社区支持。1.MySQL提供高效的数据存储和检索功能,支持多种数据类型和高级查询操作。2.采用客户端-服务器架构和多种存储引擎,支持事务和查询优化。3.易于使用,支持多种操作系统和编程语言。4.拥有强大的社区支持,提供丰富的资源和解决方案。

描述InnoDB锁定机制(共享锁,独家锁,意向锁,记录锁,间隙锁,下一键锁)。描述InnoDB锁定机制(共享锁,独家锁,意向锁,记录锁,间隙锁,下一键锁)。Apr 12, 2025 am 12:16 AM

InnoDB的锁机制包括共享锁、排他锁、意向锁、记录锁、间隙锁和下一个键锁。1.共享锁允许事务读取数据而不阻止其他事务读取。2.排他锁阻止其他事务读取和修改数据。3.意向锁优化锁效率。4.记录锁锁定索引记录。5.间隙锁锁定索引记录间隙。6.下一个键锁是记录锁和间隙锁的组合,确保数据一致性。

See all articles

热AI工具

Undresser.AI Undress

Undresser.AI Undress

人工智能驱动的应用程序,用于创建逼真的裸体照片

AI Clothes Remover

AI Clothes Remover

用于从照片中去除衣服的在线人工智能工具。

Undress AI Tool

Undress AI Tool

免费脱衣服图片

Clothoff.io

Clothoff.io

AI脱衣机

AI Hentai Generator

AI Hentai Generator

免费生成ai无尽的。

热门文章

R.E.P.O.能量晶体解释及其做什么(黄色晶体)
3 周前By尊渡假赌尊渡假赌尊渡假赌
R.E.P.O.最佳图形设置
3 周前By尊渡假赌尊渡假赌尊渡假赌
R.E.P.O.如果您听不到任何人,如何修复音频
3 周前By尊渡假赌尊渡假赌尊渡假赌
WWE 2K25:如何解锁Myrise中的所有内容
4 周前By尊渡假赌尊渡假赌尊渡假赌

热工具

MinGW - 适用于 Windows 的极简 GNU

MinGW - 适用于 Windows 的极简 GNU

这个项目正在迁移到osdn.net/projects/mingw的过程中,你可以继续在那里关注我们。MinGW:GNU编译器集合(GCC)的本地Windows移植版本,可自由分发的导入库和用于构建本地Windows应用程序的头文件;包括对MSVC运行时的扩展,以支持C99功能。MinGW的所有软件都可以在64位Windows平台上运行。

螳螂BT

螳螂BT

Mantis是一个易于部署的基于Web的缺陷跟踪工具,用于帮助产品缺陷跟踪。它需要PHP、MySQL和一个Web服务器。请查看我们的演示和托管服务。

SublimeText3 Mac版

SublimeText3 Mac版

神级代码编辑软件(SublimeText3)

记事本++7.3.1

记事本++7.3.1

好用且免费的代码编辑器

SublimeText3汉化版

SublimeText3汉化版

中文版,非常好用