Database Solutions

  MySQL InnoDB Cluster vs Oracle RAC: Which to Choose? As a Database Administrator, I have seen organizations struggle with one recurring question: Should we choose a cost-effective distributed database solution or invest in a premium enterprise-grade clustering architecture? Two technologies that frequently appear in this discussion are MySQL InnoDB Cluster and Oracle Real Application Clusters . Both solutions provide high availability, scalability, and fault tolerance, but they are designed with different goals, architectures, and operational complexities in mind. Choosing the wrong platform can lead to performance bottlenecks, unnecessary licensing costs, or operational challenges. This blog explains the differences between MySQL InnoDB Cluster and Oracle RAC from a DBA’s perspective, including architecture, performance, scalability, administration, cost, and ideal use cases. Understanding the Technologies What is MySQL InnoDB Cluster? MySQL InnoDB Cluster is Oracle’s ...

Configure BiDirectional MySQL Replication (Master-Master) Now a days HA(High Availability) and DR(Disaster Recovery) Solutions are mandatory and required for mission critical databases. In  MySQL  world , DR solution are provided using the Replication (Master-Master). In this blog, We will discuss about setting up new  Master-Master setup. 1) Preparing Master Server 1(mysqlmaster01) : 1.a) Make Changes in my.cnf file.  cp -pr /etc/my.cnf /etc/my.cnf_<ddmmyyyy> Add below lined to my.cnf vi /etc/my.cnf server-id=1 log-bin gtid_mode=ON enforce-gtid-consistency auto-increment-increment = 2 auto-increment-offset = 1 expire_logs_days = 10 relay-log = /var/lib/mysql/relaylog/mysql-relay relay-log-recovery binlog_format=mixed replicate-do-db=mysqldb   1.b) Restart MYSQL server to make changed effective. service mysqld restart  1.c) Verify binary logs: SHOW MASTER LOGS; Show master Status; ls -lrt /var/log/*bin* 1.d) Create Replication user in Master Server 1:...

Switchover in MySQL Replication(Master-Slave) Setup  Performing DR Switch is regular activity for DBA for DR Testing. In this blog , We will show/discuss about how to switchover MySQL Replication (Master-Slave) Setup. Below are the steps followed for the MySQL Replication Switchover: 1) Stop All application servers/application. 2) Check Slave and Master status on the Slave(mysqlslave01) and Master server(mysqmaste01):   Log in to Master server (mysqmaste01): mysql> Flush logs; mysql> SHOW MASTER Status\G *************************** 1. row ***************************              File: mysql-bin.000002          Position: 28624712      Binlog_Do_DB: mysqldb  Binlog_Ignore_DB: Executed_Gtid_Set: 61fa835b-2c75-11e6-987c-005056b7fda8:1-4104 1 row in set (0.00 sec) Log into Slave server (mysqlslave01): Make sure slave running without log-slave-upda...

Configuring MySQL Replication Setup(Master-Slave) Now a days HA(High Availability) and DR(Disaster Recovery) Solutions are mandatory and required for mission critical databases. In  MySQL  world , DR solution are provided using the Replication (Master-Slave), (Master-Master) and a solution for doing switchover and failover if required. In this blog, We will discuss about setting up new  Master-Slave setup. 1) Preparing Master Server (mysqlmaster01) : 1.a) Make changes in my.cnf file. cp -pr /etc/my.cnf /etc/my.cnf_DDMMYYYY Add below line to my.cnf vi /etc/my.cnf log-bin gtid_mode=ON enforce-gtid-consistency relay-log-recovery binlog_format=mixed server-id=1 binlog-do-db=mysqldb   1.b) Restart MYSQL server to make changes effective. service mysqld restart  1.c) Verify binary logs: SHOW MASTER LOGS; Show master Status; ls -lrt /var/log/*bin* 1.d) Create Replication user in Master Server:   mysql> CREATE USER 'repl'@'198.168.0.2' IDENTIFIED BY '**********...