False Alerts for the 'Innodb Tablespace Cannot Automatically Expand' Rule in MySQL Enterprise Monitor (MEM) (Doc ID 1324209.1)

Last updated on MARCH 08, 2017

Applies to:

MySQL Enterprise Monitor - Version: 2.3 and later   [Release: 2.3 and later ]
Information in this document applies to any platform.

Symptoms

On : 2.3 version, Advisors/Rules/Graphs

ACTUAL BEHAVIOR
---------------
MEM is giving false alerts regarding the InnoDB autoextend capabilities.

EXPECTED BEHAVIOR
-----------------------
MEM should be giving correct information based on what the database variables are showing.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
  1. Add a high number of servers to be monitored by MEM so it exceeds the default MaxActive connections for the pool (or reduce max_connections for MySQL Server). This is found in the $INSTALL_DIR/apache-tomcat/webapps/ROOT/WEB-INF/config.properties file. The $INSTALL_DIR string will be replaced by the full path to your installation of MySQL Enterprise Monitor.
  2. Make sure that InnoDB configuration has autoextend capabilities defined using the innodb_autoextend_increment variable.
  3. Restart MEM and wait for the false alerts to come in.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot trust the alerts that are being displayed, and alerts may occur at inappropriate times for false reasons.

Changes

There were well over 100 servers being monitored by MEM.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms