Table of Contents
This chapter lists the changes to the Oracle Enterprise Manager for MySQL Database product, beginning with the most recent release. Each release section covers added or changed functionality, bug fixes, and known issues, if applicable.
Functionality Added or Changed
Oracle Enterprise Manager for MySQL Database includes support for the system and status variables added in MySQL 5.7.x. For more information on these variables, see What Is New in MySQL 5.7.
Metrics and Compliance Rules have been added for MySQL Enterprise Audit
Oracle Enterprise Manager for MySQL Database includes support for the variables and status counters of MySQL Enterprise Audit. For more information on these variables, see MySQL Enterprise Audit.
Metrics and Compliance Rules have been added for the MySQL Enterprise Firewall
The following MySQL Enterprise Firewall system and status variables are available:
System Variables:
mysql_firewall_max_query_size
mysql_firewall_mode
mysql_firewall_trace
Status Variables:
Firewall_access_denied
Firewall_access_granted
Firewall_cached_entries
For more information on these variables, see MySQL Enterprise Firewall.
Bugs Fixed
As of this release, the Agent sets
sql_mode=NO_AUTO_CREATE_USER in addition to
STRICT_TRANS_TABLES and
NO_ENGINE_SUBSTITUTION. This is set to
prevent repeated occurrences of the following error from MySQL
5.7.x:
Warning | 3129 | Unsetting sql mode
'NO_AUTO_CREATE_USER' is deprecated. It will be made read-only
in a future release.
Bug #21127348
Section 1.1, “Prerequisites” listed
SUPER as one of the privileges required by
the Oracle Enterprise Manager Agent. SUPER
is not required.
If a boolean attribute's value was not present, it was reported as False.
As of this release, if the value is not present, nothing is displayed.
No values were retrieved for
innodb_max_dirty_pages_pct and
innodb_max_dirty_pages_pct_lwm variables on
MySQL 5.7.7, or higher. NaN was displayed instead.
The Slave Has Been Stopped metric reported that replication had stopped although replication was running normally.
Functionality Added or Changed
The compliance framework for MySQL Configuration Metrics is added in this release. See Chapter 6, MySQL Compliance Framework for more information.
The following metrics are added in this release. These are computed metrics which evaluate based on pre-defined thresholds.
Replication Master Activity
Exceeded Binary Log Space Limit
Replication Slave Activity
Slave Error: Unknown or Incorrect Time Zone
Slave Execution Position Behind Read Position
Slave Has Been Stopped
Slave Has Experienced A Replication Error
Slave Has Problem Communicating With Master
Slave Has Stopped Replicating
Slave I/O Thread Not Running
Slave Relay Log Space
Slave Seconds Behind Master
Slave SQL Thread Not Running
Slave Waiting To Free Relay Log Space
Response
Status (up/down)
Binary Logs Summary
Binary Log File Count
Binary Log Space
Connection Activity
Failed Attempted Connections To The Server
DML Statement Activity
Prepared Statements Not Being Closed
Prepared Statements Not Being Used Effectively
Handler Activity
Indexes Not Being Used Efficiently
Instance Activity
MySQL Server Has Been Restarted
InnoDB Activity
InnoDB Buffer Cache Sub-Optimal Hit
InnoDB Buffer Pool Writes Bottleneck
InnoDB Log Waits Bottleneck
Performance Schema Activity
Host Cache Size
Table Activity
Table Cache Not Optimal
Table Lock Contention
Temporary Disk Table
Threads Activity
Connection Limit Usage (Rate)
Thread Pooling Not Enabled
Too Many Concurrent Queries Running
Trx Statement Activity
XA Distributed Transaction Support For InnoDB
Bugs Fixed
All thresholds used the > (greater than) operator. This is replaced with != (not equal to).