In the second article of the series uncovering how to get started with MySQL, we talk about the ways of connecting to MySQL Server. You can connect to MySQL Server using MySQL Client, dbForge Studio for MySQL, and MySQL Workbench. In this article, we consider each method in detail. Connecting to MySQL Using the MySQL Command-Line ClientConnecting to […]
10 Older Entries »
Error 'Table 'EMPLOYEES.POSITION' doesn't exist' on query.
Default database: 'employees'. Query: 'ALTER TABLE
EMPLOYEES.POSITION ADD COLUMN phone VARCHAR(15)' Interesting
, table exist on slave server . But we are getting above error
frequently and unable to broken the replication because database
size is too big
We are having environment as GTID replication setup with windows server (Master) to Ubuntu Linux machine (Slave) . When we dig into all the findings , concluded its may be with case sensitivity issue . Lower_case_table_names variable value is same on both servers . But as per MySQL documents Database and table names are not case-sensitive in Windows , but are case-sensitive in most varieties of Unix.Column,index,stored routine, and event names are …
We are running 5 node percona cluster on Ubuntu 16.04, and its configured with master-slave replication. Suddenly we got an alert for replica broken from slave server, which was earlier configured with normal replication
We have tried to sync the data and configure the replication, unable to fix that immediately due to huge transactions and GTID enabled servers. So we have decided to follow with innobackupex tool, and problem fixed in 2 hours
Followed all the steps from percona doc and shared the experience in my environment
Steps involving to repair the broken Replication :
1.Backup master server 2.Prepare the backup 3.Restore and Configure the Replication 4Check Replication Status
Author: Robert Agar
The role of a corporate database administrator has evolved tremendously since the introduction of relational databases in the late 1970s. A DBA from the early 1980s would be totally unprepared for the complexities that face database professionals in 2019. It’s a completely different world and the skillset required has radically changed.
The heightened focus on the value of a company’s accumulated data has made DBAs more important to the business goals of an organization than ever before. Keeping this valuable resource safe and accessible is one of the modern DBA’s primary responsibilities. Many diverse methods are required to fulfill these duties, and a DBA must be comfortable using them all to address problems encountered in day-to-day activities.
Common Issues Faced by DBAs
The laundry list of issues that DBAs must deal with regularly is a long one. …[Read more]
This blog post focuses on MySQL 5.7's newly improved features of security validation and password expiration.
The post Security Validation and Password Expiration in MySQL 5.7 appeared first on Datavail.
We remember when we first started auditing MySQL servers, there were very few tools available. In one of our early big gigs, we were battling serious performance issues for a client. At the time, tuning-primer.sh was about the only tool available that could be used to diagnose performance bottlenecks. Fortunately, with a lot of manual interpolation of the raw data it presented, we were able to find the issue with the server and suggest how to resolve them. For that we are very thankful. It was a first step in analyzing MySQL status variables, minimizing the number of formulas to learn and calculate by hand. Obviously doing it by hand takes forever!
Now fast-forward to today. Unfortunately, not much has changed. Many DBAs and developers are still using open source tools such as tuning-primer, mysqltuner.pl, mysqlreport, and so on. Don’t get the wrong; those tools have …[Read more]
With Galera (Percona Cluster or MariaDB Cluster), it is sometimes advisable to not route traffic to a node during a backup due to the node already being under a heavier load. In these situations, it may be wise to not route traffic there until the backup is complete.
Since the default /usr/bin/clustercheck script did not have the option of doing this, we created a modified version. The below script looks for the presence of the xtrabackup tool running in the process list. If it is found, the clustercheck script returns the appropriate exit code (502) which signals the load balancer to not route traffic its way. The script could easily be modified to look for the presence of programs/tools in the process list.
We hope others will find it useful.
#!/bin/bash # clustercheck.sh # # Script to make a proxy (ie HAProxy) capable of monitoring Percona XtraDB Cluster nodes properly # # Modified by Itchy …[Read more]
10 Older Entries »