centos mysql 修改数据库目录

MySQL默认的数据文件存储目录

/var/lib/mysql，现在要把目录修改为/home/data/mysql

cd

/home

mkdir

data

//在home目录下建data目录

mysqladmin

-u

root

-p

shutdown

//停止MySQL服务进程：

mv

/var/lib/mysql　/home/data/

//移动目录

cp

/etc/mycnf　/etc/mycnf

//在/etc/目录下找mycnf配置文件

[如果找不到，可到/usr/share/mysql/下找到cnf文件，拷一个到/etc/并改名为mycnf，

cp

/usr/share/mysql/my-mediumcnf　/etc/mycnf

]

编辑MySQL的配置文件/etc/mycnf,为MySQL能够正常工作，指明mysqlsock文件的产生位置,

修改

socket=/var/lib/mysql/mysqlsock

成为：

socket=/home/mysql/mysqlsock

*** 作过程

vi　

mycnf

#

The

MySQL

server

[mysqld]

port　=

3306

#socket

=

/var/lib/mysql/mysqlsock

//原内容，为了稳妥用“#”注释此行,加上下面这行

socket　

=

/home/data/mysql/mysqlsock

修改MySQL启动脚本/etc/rcd/initd/mysql

修改

datadir=/var/lib/mysql

修改成：

datadir=home/data/mysql

重新启动MySQL服务

/etc/rcd/initd/mysql　start

或reboot命令重启Linux

解压拷贝到B机的文件，然后利用利用mysql -u root -p进入mysql数据库，使用create database test创建所要还原的数据库名称，use test;切换到所要还原的数据库，然后利用source /share/testsql（source后面跟上所解压的数据库所在的路径）进行数据库还原。

查看已经安装的服务

rpm –qa|grep -i mysql

-i 作用是不区分大小写

yum remove mysql mysql-server mysql-libs compat-mysql51

rm -rf /var/lib/mysql

rm /etc/mycnf

查看是否还有mysql软件：

rpm -qa|grep mysql

有的话继续删除

可以看到有两个安装包

MySQL-server-5619-1linux_glibc25x86_64rpm

MySQL-client-5619-1linux_glibc25x86_64rpm

删除这两个服务(去掉后缀)

rpm –e MySQL-client-5619-1linux_glibc25x86_64

rpm -e MySQL-server-5619-1linux_glibc25x86_64

查看残留的目录：

whereis mysql

然后删除mysql目录：

rm –rf /usr/lib64/mysql

删除相关文件：

rm –rf /usr/mycnf

rm -rf /root/mysql_sercret

最关键的：

rm -rf /var/lib/mysql

如果这个目录如果不删除，再重新安装之后，密码还是之前的密码，不会重新初始化！

网上查了很久都没有文章提到这个，最后还是自己摸索找出来的。

卸载完成！怎么确定是不是真的卸载干净了呢？

一是看安装输出：

如果没有卸载干净，安装server时输入只有两行：

[root @localhost opt]# rpm -ivh MySQL-server-5619-1linux_glibc25x86_64rpm

Preparing ########################################### [100%]

1:MySQL-server ########################################### [100%]

卸载干净了安装输入如下：

[root @localhost opt]# rpm -ivh MySQL-server-5619-1linux_glibc25x86_64rpm

Preparing ########################################### [100%]

1:MySQL-server ########################################### [100%]

2014-09-23 07:22:43 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated Please use --explicit_defaults_for_timestamp server option (see documentation for more details)

2014-09-23 07:22:43 26041 [Note] InnoDB: Using atomics to ref count buffer pool pages

2014-09-23 07:22:43 26041 [Note] InnoDB: The InnoDB memory heap is disabled

2014-09-23 07:22:43 26041 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2014-09-23 07:22:43 26041 [Note] InnoDB: Compressed tables use zlib 123

2014-09-23 07:22:43 26041 [Note] InnoDB: Using Linux native AIO

2014-09-23 07:22:43 26041 [Note] InnoDB: Using CPU crc32 instructions

2014-09-23 07:22:43 26041 [Note] InnoDB: Initializing buffer pool, size = 1280M

2014-09-23 07:22:43 26041 [Note] InnoDB: Completed initialization of buffer pool

2014-09-23 07:22:43 26041 [Note] InnoDB: The first specified data file /ibdata1 did not exist: a new database to be created!

2014-09-23 07:22:43 26041 [Note] InnoDB: Setting file /ibdata1 size to 12 MB

2014-09-23 07:22:43 26041 [Note] InnoDB: Database physically writes the file full: wait

2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file /ib_logfile101 size to 48 MB

2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file /ib_logfile1 size to 48 MB

2014-09-23 07:22:45 26041 [Note] InnoDB: Renaming log file /ib_logfile101 to /ib_logfile0

2014-09-23 07:22:45 26041 [Warning] InnoDB: New log files created, LSN=45781

2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer not found: creating new

2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer created

2014-09-23 07:22:45 26041 [Note] InnoDB: 128 rollback segment(s) are active

2014-09-23 07:22:45 26041 [Warning] InnoDB: Creating foreign key constraint system tables

2014-09-23 07:22:45 26041 [Note] InnoDB: Foreign key constraint system tables created

2014-09-23 07:22:45 26041 [Note] InnoDB: Creating tablespace and datafile system tables

2014-09-23 07:22:45 26041 [Note] InnoDB: Tablespace and datafile system tables created

2014-09-23 07:22:45 26041 [Note] InnoDB: Waiting for purge to start

2014-09-23 07:22:45 26041 [Note] InnoDB: 5619 started; log sequence number 0

A random root password has been set You will find it in '/root/mysql_secret'

2014-09-23 07:22:46 26041 [Note] Binlog end

2014-09-23 07:22:46 26041 [Note] InnoDB: FTS optimize thread exiting

2014-09-23 07:22:46 26041 [Note] InnoDB: Starting shutdown

2014-09-23 07:22:48 26041 [Note] InnoDB: Shutdown completed; log sequence number 1625977

2014-09-23 07:22:48 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated Please use --explicit_defaults_for_timestamp server option (see documentation for more details)

2014-09-23 07:22:48 26065 [Note] InnoDB: Using atomics to ref count buffer pool pages

2014-09-23 07:22:48 26065 [Note] InnoDB: The InnoDB memory heap is disabled

2014-09-23 07:22:48 26065 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2014-09-23 07:22:48 26065 [Note] InnoDB: Compressed tables use zlib 123

2014-09-23 07:22:48 26065 [Note] InnoDB: Using Linux native AIO

2014-09-23 07:22:48 26065 [Note] InnoDB: Using CPU crc32 instructions

2014-09-23 07:22:48 26065 [Note] InnoDB: Initializing buffer pool, size = 1280M

2014-09-23 07:22:48 26065 [Note] InnoDB: Completed initialization of buffer pool

2014-09-23 07:22:48 26065 [Note] InnoDB: Highest supported file format is Barracuda

2014-09-23 07:22:48 26065 [Note] InnoDB: 128 rollback segment(s) are active

2014-09-23 07:22:48 26065 [Note] InnoDB: Waiting for purge to start

2014-09-23 07:22:48 26065 [Note] InnoDB: 5619 started; log sequence number 1625977

2014-09-23 07:22:48 26065 [Note] Binlog end

2014-09-23 07:22:48 26065 [Note] InnoDB: FTS optimize thread exiting

2014-09-23 07:22:48 26065 [Note] InnoDB: Starting shutdown

2014-09-23 07:22:50 26065 [Note] InnoDB: Shutdown completed; log sequence number 1625987

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 >

以上就是关于centos mysql 修改数据库目录全部的内容，包括:centos mysql 修改数据库目录、centos mysql数据库如何还原】、centos中怎么删除mysql数据库等相关内容解答，如果想了解更多相关内容，可以关注我们，你们的支持是我们更新的动力！