Skip to main content

MySQL 8.0.17 Community Edition installation for Red Hat Linux and Cent OS:

MySQL 8.0.17 Community Edition installation for Red Hat Linux and Cent OS:

01. Disable Firewall:
# systemctl stop firewalld
# systemctl disable firewalld
02. Set Selinux to permissive:
#vi /etc/sysconfig/selinux, and replace word enforcing to permissive
Content of file /etc/sysconfig/selinux:
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#     enforcing - SELinux security policy is enforced.
#     permissive - SELinux prints warnings instead of enforcing.
#     disabled - No SELinux policy is loaded.
SELINUX=permissive
# SELINUXTYPE= can take one of three values:
#     targeted - Targeted processes are protected,
#     minimum - Modification of targeted policy. Only selected processes are protected.
#     mls - Multi Level Security protection.
SELINUXTYPE=targeted
03. Remove Maria DB:
#yum remove mariadb-libs.x86_64
04. Download MySQL software for Red Hat Linux:
Visit Link - https://dev.mysql.com/downloads/mysql/, select Red Hat Linux for operating system and download all packages.
05. Execute following commands to install MySQL software and libraries
#yum install mysql-community-common-8.0.17-1.el7.x86_64.rpm
#yum install mysql-community-libs-8.0.17-1.el7.x86_64.rpm
#yum install mysql-community-libs-compat-8.0.17-1.el7.x86_64.rpm
#yum install mysql-community-client-8.0.17-1.el7.x86_64.rpm
#yum install mysql-community-embedded-compat-8.0.17-1.el7.x86_64.rpm
#yum install mysql-community-devel-8.0.17-1.el7.x86_64.rpm
#yum install mysql-community-server-8.0.17-1.el7.x86_64.rpm
#yum install mysql-shell-8.0.17-1.el7.x86_64.rpm
#yum install mysql-connector-python-8.0.11-1.el7.x86_64.rpm
#yum install mysql-connector-python-cext-8.0.11-1.el7.x86_64.rpm
#yum install mysql-utilities-1.6.5-1.el7.noarch.rpm
Labels:

Comments

Post a Comment

Popular posts from this blog

MySQL InnoDB cluster troubleshooting | commands

Cluster Validation: select * from performance_schema.replication_group_members; All members should be online. select instance_name, mysql_server_uuid, addresses from  mysql_innodb_cluster_metadata.instances; All instances should return same value for mysql_server_uuid SELECT @@GTID_EXECUTED; All nodes should return same value Frequently use commands: mysql> SET SQL_LOG_BIN = 0;  mysql> stop group_replication; mysql> set global super_read_only=0; mysql> drop database mysql_innodb_cluster_metadata; mysql> RESET MASTER; mysql> RESET SLAVE ALL; JS > var cluster = dba.getCluster() JS > var cluster = dba.getCluster("<Cluster_name>") JS > var cluster = dba.createCluster('name') JS > cluster.removeInstance('root@<IP_Address>:<Port_No>',{force: true}) JS > cluster.addInstance('root@<IP add>,:<port>') JS > cluster.addInstance('root@ <IP add>,:<port> ') JS > dba.getC...
Post a Comment
Read more

MySQL slave Error_code: 1032 | MySQL slave drift | HA_ERR_KEY_NOT_FOUND

MySQL slave Error_code: 1032 | MySQL slave drift: With several MySQL, instance with master slave replication, I have one analytics MySQL, environment which is larger in terabytes, compared to other MySQL instances in the environment. Other MySQL instances with terabytes of data are running fine master, slave replication. But this analytics environment get started generating slave Error_code :1032. mysql> show slave status; Near relay log: Error_code: 1032; Can't find record in '<table_name>', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log <name>-bin.000047, end_log_pos 5255306 Near master section: Could not execute Update_rows event on table <db_name>.<table_name>; Can't find record in '<table_name>', Error_code: 1032; Can't find record in '<table_name>', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log <name>-bin.000047, end_l...
2 comments
Read more

InnoDB cluster Remove Instance Force | Add InnoDB instance

InnoDB cluster environment UUID is different on node: To fix it stop group replication, remove instance (use force if require), add instance back Identify the node which is not in sync: Execute following SQL statement on each node and identify the node has different UUID on all nodes. mysql> select * from mysql_innodb_cluster_metadata.instances; Stop group replication: Stop group replication on the node which does not have same UUID on all nodes. mysql > stop GROUP_REPLICATION; Remove instances from cluster: Remove all secondary node from the cluster and add them back if require. $mysqlsh JS >\c root@<IP_Address>:<Port_No> JS > dba.getCluster().status() JS > dba.getCluster () <Cluster:cluster_name> JS > var cluster = dba.getCluster("cluster_name"); JS >  cluster.removeInstance('root@<IP_Address>:<Port_No>'); If you get "Cluster.removeInstance: Timeout reached waiting......" JS > cluster.removeInstance(...
2 comments
Read more