Part of the MySQL Community Advent Calendar 2022, I wrote three articles on how to analyze queries and generate a slow query log for MySQL Database Service on OCI: https://blogs.oracle.com/mysql/post/analyzing-queries-in-mysql-database-service https://blogs.oracle.com/mysql/post/generate-slow-query-log-mysql-heatwave-part1 https://blogs.oracle.com/mysql/post/generate-slow-query-log-mysql-heatwave-part2 In these post, we were generating a slow query log in text or JSON directly in Object Storage. For today’s post, we will […]

In my previous post about InnoDB Stalls on Empty Free List, I used a test environment that might look a little artificial : a table larger than the InnoDB Buffer Pool but fitting in the Linux Page Cache.  This configuration allows serving very quickly what MySQL thinks are IOs because these are hit in the filesystem cache.  In this post, I explain why this environment is not

Table modifications are a common task for database administrators. In this blog, I’ll explain how to alter tables online in a controlled manner that does not disrupt application users or cause application downtime.

One of the tools in Percona Toolkit is pt-online-schema-change, a utility that alters the structure of a table without interfering with the reads or writes. The tool creates an empty copy of the table to alter and modify as desired before copying the rows from the original table into the new one.

When the copying is finished, it removes the original table and replaces it with the new one. Any changes made to data in the original tables during the copy process will be reflected in the new table as the tool creates triggers on …

We recently released Read Replica for MySQL HeatWave Database Service. Read Replicas are read-only copies of the MySQL DB system in the same region. When you add Read Replicas, they are automatically distributed accross Availability Domains and/or Fault Domains. Each MySQL DB instance can have up to 18 read replicas. Read Replicas use MySQL Asynchronous […]

Oracle recently released Read Replica for MySQL Database Service (also known as MySQL HeatWave, with or without the use of HeatWave accelerator for OLTP and OLAP).

Read Replicas are read-only copies of the MySQL DB system in the same region. When you add Read Replicas, they are automatically distributed accross Availability Domains and/or Fault Domains.

Each MySQL DB instance can have up to 18 read replicas.

Read Replicas use MySQL Asynchronous Replication with parallel workers. And when you create the first Read Replica, a Read Replica Load Balancer is created, which distributes read traffic among the read replicas.

Not all shapes are compatible with Read Replicas, the …

I’ve said it before and I’ll say it again; I can only hope you enjoy reading the OpenLampTech developer newsletter as much as I do. Once again this week we have a fantastic newsletter for you (and me). Enjoy and please share the publication to help spread the word that OpenLampTech is the media coverage for MySQL, PHP, and the LAMP stack landscapes!

The Newsletter for PHP and MySQL Developers

Receive a copy of my ebook, “10 MySQL Tips For Everyone”, absolutely free when you subscribe to the OpenLampTech newsletter.

In OpenLampTech issue #56, we have curated and original content covering:

• A fantastic developer Interview
• 7 …

Percona Tech Days are free, half-day events dedicated to the most popular open source database technologies: PostgreSQL, MongoDB and MySQL. This talk for MySQL was related to MySQL Encryption with…

The post Securing MySQL: Data Encryption with Percona Server and Vault first appeared on Change Is Inevitable.

In the previous part, we created our application and our 2 functions. Now we need to create an API Gateway to be able to call these functions from outside OCI. Using a third party scheduler, our laptop, etc… Before creating the gateway, we need to create some policy to allow the API Gateway to call […]

In my previous post, I explained how to deal with Performance_Schema and Sys to identify the candidates for Query Optimization but also to understand the workload on the database. In this article, we will see how we can create an OCI Fn Application that will generate a slow query log from our MySQL Database Service […]

In this blog, I’m going to discuss how to easily skip the replication errors in GTID (Global Transaction Identifier)-based replication.

In the MySQL world, if replication is broken we all use the famous SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; to skip the replication error. It always works if it’s a traditional binlogs events-based replication and is helpful to quickly resume the replication. But does this same method work for GTID-based replication? Let’s see.

In GTID-based replication, skipping a replication error in a broken replica is not as simple as binlogs-based replication. We have one old blog post — Repair MySQL 5.6 GTID replication by injecting empty transactions —where one of our colleagues showed us one way to skip and fix the replication.

Let’s get into action and …