If you have read my blog before, you know that I have shown a couple of ways of getting data from an Oracle database and into something more approachable, such as a text-file or even, surprise, MariaDB (or MySQL for that matter). Not that the Oracle database really likes you doing this and some tweaking is necessary. One way I have shown before to do this is by using triggers, a UDF, UPD-communication and a simple server, this was a series of blogposts starting with this one: Replication from Oracle to MariaDB the simple way. Another means is to exports data from Oracle in some text format, something Oracle really doesn't like you do it, it really likes to keep the data to itself, but yours …[Read more]
What is Change Data Capture and why do we need it?
Change Data Capture (CDC) tracks data changes (usually close to realtime). In MySQL, the easiest and probably most efficient way to track data changes is to use binary logs. However, other approaches exist. For example:
- General log or Audit Log Plugin (which logs all queries, not just the changes)
- MySQL triggers (not recommended, as it can slow down the application — more below)
One of the first implementations of CDC for …[Read more]
MySQL 8.0.0 was released today. It has been some time in the making, shrouded in a veil of secrecy for over one year. We knew, from listening to the gossip and looking at the few available previews, some of what was going to bring. So, for the observant users, its main features may not come as a surprise. For the rest of you, here's a quick roundup:
- No MyISAM tables anymore! The grant tables are now InnoDB, meaning that grant operations are now atomic.
- A real data dictionary. This change is less visible than the previous one. The data dictionary tables are hidden and only a subset of the data is available through information_schema views. The reason for the hidden tables is to allow a stable interface through several versions. I am …
Oracle released MySQL 5.7.15 recently, earlier than
expected. The reason for this "unexpected" release is not clear
to me, but it could happen because of a couple of security
related internal bug reports that got fixed:
- "It was possible to write log files ending with
.cnfthat later could be parsed as option files. The general query log and slow query log can no longer be written to a file ending with
.cnf. (Bug #24388753)
- Privilege escalation was possible by exploiting the way
REPAIR TABLEused temporary files. (Bug #24388746)"
Let me concentrate on the most important fixes to bugs and problems reported by Community users. …[Read more]
First, I want to thank everybody for attending the August 25 webinar. The recording and slides for the webinar are available here. Below is the list of your questions that I wasn’t able to answer during the webinar, with responses:
Q: Hi Sveta. One question: how is it possible to get N previous events using the SHOW BINLOG EVENTS command? For example, the position is 999 and I want to analyze the previous five events. Is it possible?
A: Not, there is no such option. You cannot get the previous five events using
SHOW BINLOG EVENTS
Some time ago, feedback was requested on new replication default after MySQL 5.7. Some of the suggested default are:
relay-log-info-repository = TABLE (previous default FILE) relay-log-recovery = ON (previous default OFF) master-info-repository = TABLE (previous default FILE) sync-master-info = 1,000 (previous default 10,000) sync-relay-log = 1,000 (previous default 10,000)
I agree on the
Group Replication introduces a new way to do replication in MySQL. With great features such as multi-master replication it brings a range of exciting deployment scenarios where some difficult problems become much easier to solve. Group Replication also brings a new set of options that may need to be configured to extract the highest performance from the underlying computing resources.…
The MySQL Utilities Team is pleased to announce a new GA release
of MySQL Utilities. This release includes a number of
improvements for usability, stability, and a few enhancements for
better compatibility with MySQL 5.7. A complete list of all
improvements can be found in our release notes.
This release represents a stable release of the product and is a significant improvement from the 1.5 release. Along with defect patches, we also include the following enhancements.
- Support for MySQL 5.7
- New! Binlog Utilities:
- mysqlbinlogpurge - purge old binary logs
- mysqlbinlogrotate - rotate the binary log
- mysqlbinlogmove - relocate binary log files
- New! Replication Utilities:
Hi everyone, its been a while since the last release of Group
Replication. During this period we have been working hard to
improve the plugin and give you a better user experience. Focused
on solving several existing bugs, address performance issues and
experience we renamed some variables, introduced new ones and changed some of the plugin policies.…