I Use This!
High Activity

News

Analyzed 5 days ago. based on code collected 13 days ago.
Posted 16 days ago by Kent Boortz
Dear MySQL users, MySQL Shell 1.0.8 RC is the first release candidate of the MySQL for MySQL Shell 1.0 series. The MySQL Shell is an interactive JavaScript, Python and SQL command-line interface, supporting development and administration for ... [More] the MySQL Server. The MySQL Shell includes the X DevAPI that enables developers to use a new Create Read Update Delete (CRUD) API. MySQL Shell is a component of the MySQL Server. This release introduces support for the creation and management of MySQL InnoDB clusters from MySQL servers with the AdminAPI. By taking advantage of the new Group Replication technology, InnoDB clusters provide an integrated solution for high availability and scalability for InnoDB based MySQL databases, without requiring advanced MySQL expertise. And with MySQL Router 2.1, applications can take advantage of a highly available and scalable MySQL InnoDB cluster with minimal or no changes in their code. This is a Developer Release, so we are looking forward to getting your feedback on the MySQL Shell as well as the new API and all the other new features. The MySQL Shell provides * MySQL High Availability and Scaling API: AdminAPI * Both Interactive and Batch operations * JavaScript, Python, and SQL language modes * Document and Relational Models * CRUD Document and Relational API: DevAPI * Output results in Traditional Table, JSON, and Tab Separated formats * And much more To download the MySQL Shell http://dev.mysql.com/downloads/shell To learn more about MySQL Shell, a component of the MySQL Server, see http://dev.mysql.com/doc/refman/5.7/en/mysql-shell.html To learn more about using MySQL as a document store, see http://dev.mysql.com/doc/refman/5.7/en/document-store.html For MySQL Shell Tutorials JavaScript - http://dev.mysql.com/doc/refman/5.7/en/mysqlx-shell-tutorial-javascript.html Python - http://dev.mysql.com/doc/refman/5.7/en/mysqlx-shell-tutorial-python.html User documentation for the X DevAPI http://dev.mysql.com/doc/x-devapi-userguide/en/index.html For more information about how the X DevAPI is implemented in MySQL Shell, and its usage, see https://dev.mysql.com/doc/dev/mysqlsh-api-javascript/ https://dev.mysql.com/doc/dev/mysqlsh-api-python/ User documentation for InnoDB cluster which can be administered using the AdminAPI included with MySQL Shell: https://dev.mysql.com/doc/mysql-innodb-cluster/en/ ====================================================================== Changes in MySQL Shell 1.0.8 (2017-03-06) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * The URI is now a positional argument when starting MySQL Shell at the command line. (Bug #25077429) * In the MySQL Shell Python X DevAPI implementation the mysqlx and mysql modules have been moved into the new mysqlsh module. This changes the way you import the modules, now you should issue: mysql-py> from mysqlsh import mysql mysql-py> from mysqlsh import mysqlx (Bug #25030138) * XSessions have been removed, which means the --x command option is deprecated. The default session is now a NodeSession. (Bug #24958348, Bug #83553) * The stored sessions functionality has been removed. (Bug #24949016, Bug #83530) * MySQL Shell version 1.0.8 includes the newly released AdminAPI available in JavaScript and Python which enables you to set up and manage InnoDB clusters. It provides a modern fluent API which wraps the complexity associated with configuring, provisioning and managing an InnoDB cluster, without sacrificing power, flexibility or security. Bugs Fixed * When using Python mode, assigning a key element that was identified as a type could cause an unexpected halt. The fix ensures that keys which are strings are correctly identified as such as are interpreted as keys. (Bug #25191539) * Attempting to create a connection with the wrong user or password on Linux resulted in an Error Unknown option trace_protocol message being displayed. The fix ensures that the correct ERROR: 1045 (28000): Access denied for user error is displayed. (Bug #25071433, Bug #83759) * Statements that were not executed, for example due to a syntax error, were not being added to the command history. This has been improved so that any statement is added to the command history and can be accessed using the up and down cursor keys. Additionally the internal MySQL Shell are now added to the command history. (Bug #24967864) References: See also: Bug #24669771. * When MySQL Shell had an open connection and was in SQL mode, pressing Control-C caused an unexpected halt. (Bug #24812731) References: See also: Bug #24663772, Bug #23065126. * The output of the \help command has been updated to include all of the available global objects. (Bug #24764191) * When using the shell.prompt() function, providing an invalid type was not generating the appropriate error. (Bug #24763825) * The way MySQL Shell processes commands has been improved to properly handle spaces in the command line, and support was added for quoted parameters when spaces are used. To pass a parameter with spaces surround it with double quotes, and if double quotes are part of the parameter they can be escaped using \". (Bug #24762017) * Primitive numeric types and booleans were not being automatically converted between each other following the Python type conversion rules. The fix ensures that a statement such as dba.verbose=1 is valid, in other words when a == b is true, then b is assignable to a as is typical in Python. (Bug #24744707) * Using --log-level=5 or greater wrote passwords to the log as plain text. (Bug #24735878) * The --log-level command option can now use named log levels such as debug3. (Bug #24735532) * When an SQL statement followed the terminating character of an SQL comment that ended with */ it could result in unexpected behavior because the first character of the statement following the comment was being ignored. The fix ensures inline comments in SQL statements are correctly parsed. (Bug #24671436) * Results output when using the --json option now go inside of a JSON object. (Bug #24575611) * When using the help, space characters at the end of a line were causing the requested help topic to not be found. (Bug #24522689) * When using SQL mode the usage of single quotes in escaping has been made consistent with the handing in MySQL, for example SELECT '''' as a;. (Bug #24380669, Bug #82381) * The help for XSession was suggesting SQL mode was available which was incorrect. (Bug #23065163) * When using SQL mode the command history was removing the semicolon from the end of previously issued lines (Bug #21390737) On behalf of the MySQL Release Team Kent Boortz [Less]
Posted 16 days ago by Kent Boortz
Dear MySQL users, MySQL Shell 1.0.8 RC is the first release candidate of the MySQL for MySQL Shell 1.0 series. The MySQL Shell is an interactive JavaScript, Python and SQL command-line interface, supporting development and administration for ... [More] the MySQL Server. The MySQL Shell includes the X DevAPI that enables developers to use a new Create Read Update Delete (CRUD) API. MySQL Shell is a component of the MySQL Server. This release introduces support for the creation and management of MySQL InnoDB clusters from MySQL servers with the AdminAPI. By taking advantage of the new Group Replication technology, InnoDB clusters provide an integrated solution for high availability and scalability for InnoDB based MySQL databases, without requiring advanced MySQL expertise. And with MySQL Router 2.1, applications can take advantage of a highly available and scalable MySQL InnoDB cluster with minimal or no changes in their code. This is a Developer Release, so we are looking forward to getting your feedback on the MySQL Shell as well as the new API and all the other new features. The MySQL Shell provides * MySQL High Availability and Scaling API: AdminAPI * Both Interactive and Batch operations * JavaScript, Python, and SQL language modes * Document and Relational Models * CRUD Document and Relational API: DevAPI * Output results in Traditional Table, JSON, and Tab Separated formats * And much more To download the MySQL Shell http://dev.mysql.com/downloads/shell To learn more about MySQL Shell, a component of the MySQL Server, see http://dev.mysql.com/doc/refman/5.7/en/mysql-shell.html To learn more about using MySQL as a document store, see http://dev.mysql.com/doc/refman/5.7/en/document-store.html For MySQL Shell Tutorials JavaScript - http://dev.mysql.com/doc/refman/5.7/en/mysqlx-shell-tutorial-javascript.html Python - http://dev.mysql.com/doc/refman/5.7/en/mysqlx-shell-tutorial-python.html User documentation for the X DevAPI http://dev.mysql.com/doc/x-devapi-userguide/en/index.html For more information about how the X DevAPI is implemented in MySQL Shell, and its usage, see http://dev.mysql.com/doc/dev/mysqlsh-devapi/ User documentation for InnoDB cluster which can be administered using the AdminAPI included with MySQL Shell: https://dev.mysql.com/doc/mysql-innodb-cluster/en/ ====================================================================== Changes in MySQL Shell 1.0.8 (2017-03-06) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * The URI is now a positional argument when starting MySQL Shell at the command line. (Bug #25077429) * In the MySQL Shell Python X DevAPI implementation the mysqlx and mysql modules have been moved into the new mysqlsh module. This changes the way you import the modules, now you should issue: mysql-py> from mysqlsh import mysql mysql-py> from mysqlsh import mysqlx (Bug #25030138) * XSessions have been removed, which means the --x command option is deprecated. The default session is now a NodeSession. (Bug #24958348, Bug #83553) * The stored sessions functionality has been removed. (Bug #24949016, Bug #83530) * MySQL Shell version 1.0.8 includes the newly released AdminAPI available in JavaScript and Python which enables you to set up and manage InnoDB clusters. It provides a modern fluent API which wraps the complexity associated with configuring, provisioning and managing an InnoDB cluster, without sacrificing power, flexibility or security. Bugs Fixed * When using Python mode, assigning a key element that was identified as a type could cause an unexpected halt. The fix ensures that keys which are strings are correctly identified as such as are interpreted as keys. (Bug #25191539) * Attempting to create a connection with the wrong user or password on Linux resulted in an Error Unknown option trace_protocol message being displayed. The fix ensures that the correct ERROR: 1045 (28000): Access denied for user error is displayed. (Bug #25071433, Bug #83759) * Statements that were not executed, for example due to a syntax error, were not being added to the command history. This has been improved so that any statement is added to the command history and can be accessed using the up and down cursor keys. Additionally the internal MySQL Shell are now added to the command history. (Bug #24967864) References: See also: Bug #24669771. * When MySQL Shell had an open connection and was in SQL mode, pressing Control-C caused an unexpected halt. (Bug #24812731) References: See also: Bug #24663772, Bug #23065126. * The output of the \help command has been updated to include all of the available global objects. (Bug #24764191) * When using the shell.prompt() function, providing an invalid type was not generating the appropriate error. (Bug #24763825) * The way MySQL Shell processes commands has been improved to properly handle spaces in the command line, and support was added for quoted parameters when spaces are used. To pass a parameter with spaces surround it with double quotes, and if double quotes are part of the parameter they can be escaped using \". (Bug #24762017) * Primitive numeric types and booleans were not being automatically converted between each other following the Python type conversion rules. The fix ensures that a statement such as dba.verbose=1 is valid, in other words when a == b is true, then b is assignable to a as is typical in Python. (Bug #24744707) * Using --log-level=5 or greater wrote passwords to the log as plain text. (Bug #24735878) * The --log-level command option can now use named log levels such as debug3. (Bug #24735532) * When an SQL statement followed the terminating character of an SQL comment that ended with */ it could result in unexpected behavior because the first character of the statement following the comment was being ignored. The fix ensures inline comments in SQL statements are correctly parsed. (Bug #24671436) * Results output when using the --json option now go inside of a JSON object. (Bug #24575611) * When using the help, space characters at the end of a line were causing the requested help topic to not be found. (Bug #24522689) * When using SQL mode the usage of single quotes in escaping has been made consistent with the handing in MySQL, for example SELECT '''' as a;. (Bug #24380669, Bug #82381) * The help for XSession was suggesting SQL mode was available which was incorrect. (Bug #23065163) * When using SQL mode the command history was removing the semicolon from the end of previously issued lines (Bug #21390737) On behalf of the MySQL Release Team Kent Boortz [Less]
Posted 17 days ago by Karen Langford
Dear MySQL users, MySQL Enterprise Backup v4.1.0, a new version of the online MySQL backup tool, is now available for download from the My Oracle Support (MOS) website as our latest GA release. This release will be available on eDelivery (OSDC) ... [More] after the next upload cycle. MySQL Enterprise Backup is a commercial extension to the MySQL family of products. MySQL Enterprise Backup 4.1.0 supports only the MySQL Server 5.7.9 and above. For any earlier versions of the MySQL server, please use MySQL Enterprise Backup 3.12 instead. A brief summary of the changes in MySQL Enterprise Backup (MEB) version 4.1.0 is given below. Changes in MySQL Enterprise Backup 4.1.0 (2017-03-03) Functionality Added or Changed * MySQL Enterprise Backup now supports the --ssl-mode option, which enables you to specify the security state of the connection to the server. It replaces the client side --ssl and --ssl-verify-server-cert options, which are now deprecated. See the description of the --ssl-mode option in MySQL 5.7 Reference Manual (http://dev.mysql.com/doc/refman/5.7/en/) for details. (Bug #23508228) * A new option, --skip-final-rescan, makes mysqlbackup skip the final rescan for InnoDB tables that are modified by DDL operations after the database has been locked near the end of a backup operation. This potentially shortens the duration for the lock and reduces the backup's impact on the server's normal operation. See the description for --skip-final-rescan for details. (Bug #21094221) * The output by mysqlbackup, which goes to the stderr stream and the message log, has now been improved to include the timestamps and thread IDs for all steps taken by mysqlbackup, in order to provide more information for debugging purposes. (Bug #20142619) * During the final stage of a backup when MySQL Enterprise Backup tried to temporarily put the database into a read-only state using the FLUSH TABLES WITH READ LOCK statement in order to copy non-InnoDB files, if a long query was running on the server at the same time, the FLUSH TABLES WITH READ LOCK statement could be taking too long to finish, holding up further queries and eventually bringing down the server. A new mysqlbackup option --lock-wait-timeout can now be used to specify the timeout in seconds for the FLUSH TABLES WITH READ LOCK statement. If the timeout is exceeded, the statement is failed and the lock on the tables is released, so that queries held up by the lock can then be executed. mysqlbackup then retries the statement and continues with the backup. Default value for --lock-wait-timeout is 60 [seconds]. (Bug #14339483) * A full set of exit codes have now been implemented for MySQL Enterprise Backup. Also, a new mysqlbackup command, print-message, returns an exit message for any given exit code supplied with the new option --error-code. See Exit codes of MySQL Enterprise Backup (http://dev.mysql.com/doc/mysql-enterprise-backup/4.1/en/ meb-exitcodes.html) for details. * To increase the performance for hot backups, mysqlbackup now shortens the final phase of the backups by resizing the MyISAM key cache before it locks the database with a FLUSH TABLES WITH READ LOCK statement. The resize triggers a flush of the MyISAM key cache, which reduces the time it takes to run the FLUSH TABLES WITH READ LOCK statement. The MyISAM key cache size is changed back to its original value afterward. * Apply-log operations can now be performed with multiple worker threads in parallel, which can improve performance for the operations. The number of threads to be used can be specified with the --process-thread option. * The copying of redo log files into backups has been made faster, shortening the overall backup time in some cases and making it less likely that a backup fails because a redo log file has been overwritten before it is copied. * MySQL Enterprise Backup now supports optimistic incremental backup, in which mysqlbackup scans only those InnoDB data files that have been modified since the last backup for changed pages and then saves them into the incremental backup. It potentially makes incremental backups faster, and is performed by specifying --incremental=optimistic. See Full-scan versus Optimistic Incremental Backup (http://dev.mysql.com/doc/mysql-enterprise-backup/4.1/ en/mysqlbackup.incremental.html#mysqlbackup.optimis tic.incremental) for details. * In order to minimize the impact of a hot backup on the MySQL server, the copying of the buffer pool dump files and some of the metadata files is now performed before the final phase of the backup in which the server instance is locked. This shortens the duration for the lock and reduces the backup's impact on the server's normal operation. Also, to minimize the resource used on a backup, the copying of the buffer pool dump files is no longer performed for partial and offline backups, for which the buffer pool dump is usually not very useful. Bugs Fixed * The Release number for the RPM packages of MySQL Enterprise Backup always said "1," instead of giving the release number of the Linux distribution for which the package was built. (Bug #25538798) * An apply-log or apply-incremental-backup operation failed when, during the time the backup was created, any tables have been dropped and then recreated with the same name for more than once. (Bug #25334929) * When creating a full image backup with the --no-locking option, mysqlbackup failed to write the binary log information to the backup history table and the backup_variables.txt file. The result was that when creating an incremental image backup based on the full backup, the attempt to copy the binary log files from the server into the incremental image backup (which is the default behavior) would fail, causing the incremental backup to stop. With this fix, the binary log information is no longer missing after the full backup, so the incremental image backup no longer fails." (Bug #25296324) References: See also: Bug #19915713. * A backup became corrupted if, during the backup process, a DDL operation that took advantage of MySQL server's online DDL feature (http://dev.mysql.com/doc/refman/5.7/en/innodb-online-ddl .html) occurred. This was because mysqlbackup did not support the server feature---and it still does not. This fix avoids the error by having mysqlbackup turn the server's system variable old_alter_table to "1" at the beginning of a backup if it is "0," so that any DDL operations that take place during the backup are handled with the old table copy method. mysqlbackup then turns the variable back to "0" near the end of the backup operation. Notice that in cases where mysqlbackup quits unexpectedly and does not turn old_alter_table back to its original value, the user will have to turn the value back to "0" manually on the server, in order to return the server to its original configuration. This should be performed if the statement "Server system variable 'old_alter_table' was set to '0'. Setting it to '1'" appears in the early output of mysqlbackup, but the statement "Setting server system variable 'old_alter_table' back to '0'" does not appear before mysqlbackup quits. (Bug #25217215) * A backup operation sometimes failed due to corruption of the copied redo log, and the corruption occurred because checksum validation for redo logs was not activated for mysqlbackup. This fix restores the checksum function, so that the validation is performed when innodb_log_checksums=ON on the backed up server. When a chuck of redo log data fails the validation, mysqlbackup tries to reread the data from the server. However, redo log checksum validation is not performed for offline backups, and online backups fail when the value of innodb_log_checksums is switched off on the server when the backup is in progress. (Bug #25057394) * In some cases (for example,when the backup could not be validated, or when the backup directory could not be created), mysqlbackup threw an error when an operation failed without creating a message log file. With this fix, a message log file is created in those cases. (Bug #24678204) * mysqlbackup logged double entries with wrong information into the backup_history table for optimistic backups. (Bug #24502876) * Backups for a slave server in a multi-source replication setup using the --slave-info option failed. (Bug #24444950) References: See also: Bug #21830316. * If a backed up server was configured with innodb_undo_tablespaces being non-zero, during a backup, mysqlbackup emitted meaningless warning messages about the tablespaces already existing in the cache. This fix removes those messages. (Bug #24400230) * During an apply-log or a copy-back-and-apply-log operation on a backup with encrypted InnoDB tables, if no value was specified for the --encrypt-password option used, the operation failed with the complaint that no encryption password was specified. With this fix, mysqlbackup asks the user for the encryption password when it is in the same situation. (Bug #24364442) * An apply-log operation failed for a backup of a server that contained tablespaces outside of its data directory. It was because those tablespaces, unlike tablespsaces in the data directory, were not loaded by mysqlbackup before the apply-log operation started. This fix ensures all tablespaces are loaded. (Bug #22026145) * When running the backup-and-apply-log command without a connection to the MySQL server, mysqlbackup could not know the correct binary log file name and binary log position for the backup; yet, at the end of the backup-and-apply-log operation, mysqlbackup still printed out some values for the binary log file name and position, which were random in nature. (Bug #21623089) Thanks, On behalf MySQL RE team at Oracle -Sreedhar S [Less]
Posted 23 days ago by Gipson Pulla
Dear MySQL Users, MySQL Connector/J 5.1.41, a maintenance release of the production 5.1 branch has been released. Connector/J is the Type-IV pure-Java JDBC driver for MySQL. Version 5.1.41 is suitable for use with many MySQL server versions ... [More] , including 4.1, 5.0, 5.1, 5.4 and 5.5. MySQL Connector Java is available in source and binary form from the Connector/J download pages at http://dev.mysql.com/downloads/connector/j/5.1.html and mirror sites as well as Maven-2 repositories. MySQL Connector Java (Commercial) is already available for download on the My Oracle Support (MOS) website. This release will be available on eDelivery (OSDC) in next month's upload cycle. As always, we recommend that you check the "CHANGES" file in the download archive to be aware of changes in behavior that might affect your application. MySQL Connector/J 5.1.41 includes the following general bug fixes and improvements, also available in more detail on http://dev.mysql.com/doc/relnotes/connector-j/en/news-5-1-41.html Changes in MySQL Connector/J 5.1.41 (2017-02-28) Version 5.1.41 is a maintenance release of the production 5.1 branch. It is suitable for use with MySQL server versions 5.5, 5.6, and 5.7. It supports the Java Database Connectivity (JDBC) 4.2 API. Bugs Fixed * Connections failed with MySQLSyntaxErrorException: Unknown character set when connectionCollation=ISO-8859-13. This was due to a wrong logic in Connector/J's internal charset mapping, which has now been fixed. (Bug #25504578) * When loading classes through some external class loaders, com.mysql.jdbc.Util threw an NoClassDefFoundError. This was caused by Class.getPackage() returning null when some external class loaders were used. This fix replaces those calls of Class.getPackage() with calls of the new method Class.getName(), which return package names that are extracted from the fully-qualified class names. (Bug #25048543, Bug #83052) * In the manifest for the Connector/J JAR file, the Import-Package directive specified version numbers for the javax.net.ssl package. The specification was unnecessary, and it caused the configuration of an SSL connection to a MySQL server to fail in an OSGi environment. The version requirement has now been removed. (Bug #24942672, Bug #82826) * In a Fabric setup, when multiple threads required to have hashes computed, an ArrayIndexOutOfBoundsException might be thrown from inside HashShardMapping. This fix prevents the issue by having HashShardMapping.getShardIndexForKey() synchronized. (Bug #24289730, Bug #82203) * When the configuration property cacheResultSetMetadata was set to true, a ping query using a PreparedStatement failed with a NullPointerException. This fix moves the ping query to an earlier stage of the statement execution, which prevents the exception. (Bug #23535001, Bug #81706) * The setFabricShardTable() method failed to parse qualified table names (in the format of database_name.table_name), which causes SQLExceptions to be thrown. (Bug #23264511, Bug #81108) * A race condition occurred when a call of Connection.setNetworkTimeout() was followed closely by a call of Connection.close(), and a NullPointerException might result if the connection was closed before the executor supplied to setNetworkTimeout() was able to set the timeout, as the executor would run into a null mysqlConnection object. This fix removed the race condition. (Bug #21181249, Bug #75615) * With the connection properties cacheServerConfiguration=true and elideSetAutoCommits=true, any new connection to the server obtained after the first connection was established had the variable autoCommit equaled false, even if the value of the variable was true on the server. That was because the value of autoCommit was not properly initialized when a new connection was established, and this fix corrects that. Also, since release 5.1.41, the functionality of the property elideSetAutoCommits has been disabled due to Bug# 66884. Any value given for the property is now ignored by Connector/J. (Bug #17756825, Bug #70785) * When using Tomcat and a web application that utilized Connector/J was down, Tomcat was unable to stop the AbandonedConnectionCleanupThread started internally by Connector/J, leading to multiple instances of the thread when the web application was restarted; or, Tomcat was able to stop the thread but unable to restart it on reload of the web application. Different combinations of Tomcat's default settings, usage of Tomcat's ServletContextListener feature, and locations of the Connector/J jar could result in the undesired behaviors, as well as warning messages in the Tomcat error log saying it was unable to stop the thread and a memory leak was likely. The implementation of AbandonedConnectionCleanupThread has now been improved, so that there are now four ways for developers to deal with the situation: + When the default Tomcat configuration is used and the Connector/J jar is put into a local library directory, the new built-in application detector in Connector/J now detects the stopping of the web application within 5 seconds and kills AbandonedConnectionCleanupThread. Any unnecessary warnings about the thread being unstoppable are also avoided. If the Connector/J jar is put into a global library directory, the thread is left running until the JVM is unloaded. + When Tomcat's context is configured with the attribute clearReferencesStopThreads="true", Tomcat is going to stop all spawned threads when the application stops unless Connector/J is being shared with other web applications, in which case Connector/J is now protected against an inappropriate stop by Tomcat; the warning about the non-stoppable thread is still issued into Tomcat's error log. + When a ServletContextListener is implemented within each web application that calls AbandonedConnectionCleanupThread.checkedShutdown() on context destruction, Connector/J now, again, skips this operation if the driver is potentially shared with other applications. No warning about the thread being unstoppable is issued to Tomcat's error log in this case. + When AbandonedConnectionCleanupThread.uncheckedShutdown() is called, the AbandonedConnectionCleanupThread is closed even if Connector/J is shared with other applications. However, it may not be possible to restart the thread afterwards. (Bug #17035755, Bug #69526) References: See also: Bug #14570236, Bug #16443387. On Behalf of MySQL/ORACLE RE Team Gipson Pulla [Less]
Posted 28 days ago by Nawaz Nazeer ahamed
Dear MySQL users, MySQL Connector/Net 6.10.1 beta is the second release which supports Scaffold-DbContext, that enables the creation of corresponding model classes from an existing database that are compatible with Entity Framework (EF) Core 1.1. ... [More] To download MySQL Connector/Net 6.10.1 beta, see the "Development Releases" tab at http://dev.mysql.com/downloads/connector/net/ Changes in MySQL Connector/Net 6.10.1 (2017-02-22, Beta) Known limitations of this release: * The output classes cannot exist prior to using the EF Core database first feature. * The target database must have a table with a primary key. * The target database cannot contain one or more views. * The JSON data exchange format is not supported by the EF Core database first feature. * No error message is provided when a table given as input does not exist in the database and a model context is created without any table by the EF Core database first feature. * The EF Core database first feature does not support the following data types: + BINARY + VARBINARY + MEDIUMBLOB + LONGBLOB + SET + DATE + TIME + YEAR * DbContext within an application can emit an unhandled exception. Due to this limitation, MySQL Connector/Net 6.9.9 is the preferred version to use with EF6. Functionality Added or Changed * Added database first support, also known as Scaffold-DbContext, which enables the creation of corresponding model classes from an existing database that are compatible with Entity Framework (EF) Core 1.1. Bugs Fixed * EF Core: Using the Contains method in an expression with a variable generated an exception. (Bug #25394204, Bug #84505) * EF Core: Using the Skip and Take methods in an assignment generated an exception. (Bug #25382036, Bug #84453) Nuget packages are available at: https://www.nuget.org/packages/MySql.Data/6.10.1-beta https://www.nuget.org/packages/MySql.Web/6.10.1-beta https://www.nuget.org/packages/MySql.Data.Entity/6.10.1-beta https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore/6.10.1-beta https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore.Design/6.10.1-beta Enjoy and thanks for the support! On behalf of the MySQL Release Team, Nawaz Nazeer Ahamed [Less]
Posted about 1 month ago by Daniel Horecki
Dear MySQL users, The MySQL developer tools team announces 6.3.9 as our GA release for MySQL Workbench 6.3. For the full list of changes in this revision, visit http://dev.mysql.com/doc/relnotes/workbench/en/changes-6-3.html For discussion ... [More] , join the MySQL Workbench Forums: http://forums.mysql.com/index.php?152 Download MySQL Workbench 6.3.9 GA now, for Windows, Mac OS X 10.10+, Oracle Linux 7, Fedora 24 and 25, Ubuntu 16.04 and 16.10 or sources, from: http://dev.mysql.com/downloads/tools/workbench/ Enjoy! Changes in MySQL Workbench 6.3.9 (2017-02-07, General Availability) Functionality Added or Changed * Support was added for many MySQL 8.0 features. Note that configuration-file support for MySQL 8.0 is not available and a warning banner is displayed during attempted use. (Bug #24908593, Bug #83422) * With MySQL 5.7, several new instruments were added to the performance section including the following for Memory Usage: Total Memory, Top Memory by Event, Top Memory by User, Top Memory by Host, Top Memory by Thread, User Resource Usage, and the following for User Resource Usage: Overview, I/O Statistics, and Statement Statistics. (Bug #21491775) * With MySQL 5.7, GTID_MODE can now be set online. (Bug #20712931) * Workbench is now aware of the innodb_optimize_point_storage option that was added in MySQL Server 5.7.5, and later removed in MySQL Server 5.7.6. Note that MySQL Server 5.7.9 was the first 5.7 GA release. (Bug #20661496) * Mroonga storage engine support is now available for tables. (Bug #20058280, Bug #74367) * A new DDL tab was added to show the complete create statement of a table or view. Click the table inspector (info) button next to the table or view in the Schemas Navigator to display the new information. (Bug #19889537, Bug #74554) * Dropped support for DBDesigner 4. * Dropped Fabric support. * Dropped support for MySQL 5.1. Minimum version is now MySQL 5.5. * Changed to C++11. * Changed to GTK 3 on Linux. * OS X: Version 10.7 (Lion) and 10.8 (Mountain Lion) support was dropped. Now supporting 10.9 (Mavericks), 10.10 (Yosemite), 10.11 (El Capitan), and 10.12 (Sierra). * Windows: Zip packages and 32-bit binaries are no longer published. The .NET Framework version 4.5 is now required. * Linux: Fedora 23 support dropped and Fedora 25 support added. Oracle Linux 6 support was dropped. * The option to specify an alternative application data directory, instead of the default location, was added. * The JSON editor was improved with better parsing and error checking. * A new Log Level preference (under Others) was added to alter the log verbosity level. As before, this can still be set by passing in the log-level (http://dev.mysql.com/doc/workbench/en/wb-command-line-op tions.html) command-line argument into Workbench at runtime, and doing so overrides the Log Level setting. * The bundled sakila_full.mwb model now uses a dedicated 5.7 version to allow for 5.7 specific features, regardless of the version setting in the preferences. * Full MySQL 5.7 language support was added, which affects grammar, syntax highlighting, preferences, behavior, and more. * The Home screen was modified: the connections, models, and starters were split into individual pages. Bugs Fixed * With multiple tabs open in the SQL Editor, using the context-sensitive menu to close all other tabs caused MySQL Workbench to exit unexpectedly. (Bug #25466086, Bug #84643) * Objects sorted in the schema inspector and then selected for an operation, such as Drop Table, generated a statement for the wrong object. (Bug #25464011, Bug #84697) * MySQL Workbench supports the option to require a CA certificate or identity validation. (Bug #25408639) * If a full backup added warning messages to the backup log file, then running an incremental backup later failed. (Bug #25315796) * No JSON tab appeared for the Open Value in Editor command if the field contained an empty array. (Bug #25222455, Bug #84106) * Schema names were not escaped properly in resulting DROP TRIGGER statements when a trigger was created or edited. (Bug #25036458, Bug #83655) * In some cases, executing a query caused MySQL Workbench to become unresponsive when the host was macOS Sierra. (Bug #25036263, Bug #83658) * Having a single quotation mark (') in the text field of a table caused the MySQL Schema Transfer wizard to fail. (Bug #24978403, Bug #83616) * Simple and complex queries executed from SQL Editor failed to complete and return control to MySQL Workbench. This behavior was observed for both local and remote queries and was often intermittent. (Bug #24977018, Bug #82951) * Deleting rows while connected to a remote server caused the connection to fail and for MySQL Workbench to exit unexpectedly. (Bug #24947899, Bug #81019) * The Selected schema drop-down list in the New Schema Privilege Definition dialog failed to display newly added schema names unless MySQL Workbench was restarted. (Bug #24798254, Bug #83111) * The bundled OpenSSL library was upgraded to version 1.0.2J. (Bug #24753390) * Tooltips failed to operate properly in the Visual Explain panel. (Bug #24577687, Bug #82816) * Deleting selected rows from the Result Grid caused MySQL Workbench to become unresponsive. (Bug #24411733, Bug #82466) * Connecting to the server resulted in the following exception: Parameter is not valid. (Bug #24394987) * Queries returning more than 1000 rows on an SSH connection to AWS failed and caused MySQL Workbench to become unresponsive. (Bug #24330588, Bug #82291) * Adding a password with the Store in Vault option caused Workbench to fail and exit. (Bug #23987798, Bug #82190) * Opening a saved .mwb model file with MySQL Workbench generated the following error intermittently: Error unserializing GRT data string too long. The same file, when opened directly from the file system, started MySQL Workbench and displayed the model correctly. (Bug #23857478, Bug #80017) * Query statements executed from the SQL Editor did not remain selected when the focus returned to the query area. (Bug #23760790, Bug #79580) * The schema navigator incorrectly opened a previously viewed database, instead of the one selected, after the schema filter in the Navigator panel was used to find and list multiple databases. (Bug #23760745, Bug #71699) * Selecting TCP/IP over SSH for existing or new connections caused MySQL Workbench to fail and exit. (Bug #23743373, Bug #82113) * Changes made with the Options File editor were committed to my.cnf correctly, but also generated an error. (Bug #23741731, Bug #82102) * Stored procedures containing valid CASE statements reported syntax errors when created or edited. (Bug #23617646, Bug #81932) * Graphs in the performance dashboard reported negative values when the server instance was stopped and restarted during the analysis. (Bug #23103677, Bug #81067) * The Migration Wizard successfully migrated the schema, but failed to migrate the data, when the data source was SQL Anywhere 16 using ODBC. (Bug #22987681, Bug #79140) * Selecting too many tables when attempting to reverse engineer an EER diagram caused MySQL Workbench to fail and exit. This fix sets the permitted threshold to 1000 objects and displays a warning message when the number of objects exceeds the threshold. (Bug #22828056, Bug #80516) * The import operation failed to import valid CSV files. (Bug #22817059, Bug #80472) * New connections configured with the Standard TCP/IP over SSH connection method failed and caused MySQL Workbench to become unresponsive or to exit. (Bug #22728573, Bug #80359) * EER diagram tables were locked to a fixed location in the window for some .mwb files. This fix enables users to unlock the tables within the diagram and to persist those changes by first changing the size of the diagram (click Model, Diagram Properties and Size) and then saving the file. (Bug #22722596, Bug #71533) * Performance reports generated by the Export button did not enclose in quotes and escape any string values in the CSV file, making it difficult to read the output when the strings contained commas. (Bug #22700858) * Check for Updates from the Help menu failed to detect new releases. (Bug #22578656, Bug #80074) * The Filter Rows value set in the Result Grid of a query was not reapplied when the query was changed or refreshed. (Bug #22566018, Bug #80050) * When running large queries over an SSH tunnel, MySQL Workbench became unresponsive. (Bug #22494755, Bug #79840) * The Export Data operation emitted an unhandled exception when the user connecting to the server lacked privileges on the mysql schema, but had full privileges on the database identified by the operation. (Bug #22478388, Bug #79807) * Adding or editing fields in the Table Templates window for a user-defined template caused MySQL Workbench to fail and exit. (Bug #22449752, Bug #79721) * Data exported from the Inserts tab of a table in an EER diagram generated invalid JSON syntax. (Bug #22381735, Bug #79673) * Some GRANT statements were parsed incorrectly. (Bug #22370783) * The Audit Inspector failed to initialize in MySQL Workbench when the locations of the audit log file and data directory were different. (Bug #22277384) * GEOMETRY table data failed to export properly into CSV file format and failed to export at all into JSON file format (with an error). (Bug #22269646) * Stopping a query before it finished executing often caused MySQL Workbench to stop working. (Bug #22071120, Bug #78881) * The placeholder row (last row of the Result Grid with NULL values) was hidden when new rows were inserted and applied. (Bug #22065173, Bug #78294) * Saving a reverse-engineered model caused MySQL Workbench to fail and exit. (Bug #21980722, Bug #78357) * The cost and data process information added to "EXPLAIN JSON" in MySQL Server 5.7.2 can now be viewed in Workbench. (Bug #21848024) * The autocomplete feature did not offer suggestions as expected. The CTRL+SPACEBAR keyboard shortcut can be used to activate this feature. (Bug #21685267, Bug #78185) * Some help text was hidden from the Schema Editor in the EER Diagram. (Bug #21630661, Bug #78021) * When MySQL Workbench performed a copy-back restore operation, it reported incorrectly to the mysqlbackup log that a copy-back-and-apply-log operation was performed. (Bug #21496475) * The require_secure_transport system variable that was added in MySQL Server 5.7.8 is now supported and can be modified using MySQL Workbench. This variable enables administrators to require all client connections to the server to be made using some form of secure transport. (Bug #21484632) * A dialog showing the wait time of an attempted connection now displays earlier for improved visibility. (Bug #21264710) * Some routine database operations caused MySQL Workbench to fail and exit intermittently. (Bug #21231450, Bug #77286) * The slash character (/) when used in the name of a new connection separated a group from the real connection name by default without first notifying the user. This fix gives the user an option to keep the slash character and create a connection group or to replace all slash characters in the connection name with underscore characters. (Bug #21158191, Bug #77175) * In a query, UNION and UNION ALL statements that contained data from different tables or different databases returned data in the Result Grid that could be edited and applied to the wrong table. This fix returns read-only data that cannot be edited directly for such queries. (Bug #21046384, Bug #76964) * The identifier quote character (`) was missing from the DROP statement when an attempt was made to drop the existing trigger on a database with an illegal character in the name. A syntax error resulted. (Bug #20978108, Bug #76869) * The property values of a table in an EER diagram could not be edited from the Properties Editor. (Bug #20930134) * Stored procedures containing valid query syntax produced syntax errors. (Bug #20929172, Bug #76761) * Some characters could not be inserted into cells of the result grid and displayed the following text-truncation error message: Inserted data has been truncated as the control's limit was reached. Please use the value editor instead for editing such large text data. (Bug #20927915, Bug #76760) * SQL Editor did not permit the use of DUAL in a derived-table subquery. (Bug #20800341) * When the resultset grid in SQL Editor was set to a font type and size that exceeded the default row height, the output from a query hid a portion the row content instead of increasing the row height to accommodate the font value. (Bug #20794106, Bug #76520) * The binlog_group_commit_sync_delay and binlog_group_commit_sync_no_delay_count options that were added in MySQL Server 5.7.5 are now supported, and can be modified using Workbench. (Bug #20712947) * Russian language connection names failed to load and display properly in the home screen. (Bug #20697403, Bug #76015) * The innodb_page_size MySQL Server system variable can now be changed to either 32k or 64k in Workbench, in addition to the current options. Support for these larger innodb_page_size values was added in MySQL Server 5.7.6. The default value in MySQL 5.7 is 16k. (Bug #20661249) * Executing the current statement of a query by using the CTRL+ALT+ENTER keyboard shortcut (Vertical Text Output) partially or fully hid the output. (Bug #20573658, Bug #75959) * When closing a tab in the SQL Editor, the focus always returned to the first tab regardless of the number of tabs open. This fix returns focus to the preceding tab (to the left) of the closed tab. (Bug #20351753, Bug #75490) * A valid server connection was required before a script or model file could be viewed or edited. (Bug #20326028, Bug #75452) * Starting MySQL Workbench from the command line with an optional argument of a script or model file required the absolute (or fully qualified) path name of the file. (Bug #20268606, Bug #75305) * SQL Editor identified syntax errors in valid statements that executed properly. (Bug #20116982, Bug #74183) * Font sizes were increased in the Home screen for improved readability. (Bug #19982157, Bug #74721) * The MySQL Table Editor did not display the name of a selected table within an EER diagram when the editor was first opened. (Bug #19693466, Bug #74102) * Because the sys schema is installed by default as of MySQL server 5.7.7, MySQL Workbench now checks for and uses it. Otherwise, MySQL Workbench (as it has since 6.1) provides the option to install it. References: See also: Bug #71207. On behalf of the MySQL Workbench and the MySQL/ORACLE RE Team Daniel Horecki [Less]
Posted about 2 months ago by Jocelyn Ramilison
Dear MySQL users, MySQL MySQL Utilities 1.6.5 is a GA version of 1.6 release series. It can be used for production environments. MySQL Utilities version 1.6.5 GA is compatible with MySQL Server versions 5.5 and greater. Python v2.6 and v2.7 are ... [More] supported. It is available for download from: http://dev.mysql.com/downloads/tools/utilities/ A brief summary of changes is listed below. Please check the CHANGES.txt file inside the distribution for a more complete list of changes. MySQL Utilities provides a collection of command-line utilities that are used for maintaining and administering MySQL servers, including: • Admin Utilities (Clone, Copy, Compare, Diff, Export, Import, User Management) • Replication Utilities (Setup, Configuration, Verification) • General Utilities (Disk Usage, Redundant Indexes, Manage Meta & Audit Data) • And more Changes in MySQL Utilities 1.6.5 (2017-01-25) Bugs Fixed * Corrected a problem when using a --exec-before script that failed causing the mysqlfailover utility to fail silently. (Bug #25030151) * Added corrections to the message text of some utilities to eliminate typographical errors. (Bug #24742356, Bug #83173) * The mysqldbcopy utility failed to copy views that refer other views in the list of databases to be copied. (Bug #24657793) * Corrected an issue when using anonymous hosts. (Bug #24624716, Bug #82636) * The mysqlfrm utility failed to parse some .frm files properly. This fix ensures that the utility can parse tables with many columns in the field list. (Bug #24613794, Bug #82907) * The mysqldbcopy utility failed to copy tables with a primary key set to zero and with AUTO_INCREMENT applied. This fix enables the copy and export of auto-increment columns with an initial value of zero. For export, the user is warned to turn on the NO_AUTO_VALUE_ON_ZERO mode for the import and suggested SQL statements to enable the mode are provided. For copy, the mode is turned on automatically and turned off after the copy. (Bug #23598948, Bug #81866) * Permits IPv4 address parsing to include values of 0-255 rather than 0-254. Thanks to Erol Guven for the patch. (Bug #23578714, Bug #81834) * Tables with BLOB data in fields marked NOT NULL restricted the operation of the mysqldbcopy utility. This fix enables the utility to copy these tables by temporarily altering the columns on the destination to remove the NOT NULL option and then to restore it after the copy. (Bug #23335753, Bug #81553) * Corrected an issue with reading strings from configuration files when run with Python 2.6. (Bug #22738248) * Corrected the error message stating the --discover-slaves-login option is not used with the failover command for the mysqlrpladmin utility. (Bug #22616847, Bug #80082) * Corrected the problem when socket files are used in replication utilities. Previously, the port defaulted to 3306 instead of the actual port for the servers. The code now retrieves the port from the connected servers so that connections of slaves are directed to the correct port. (Bug #22543116) * Added context to errors resulting from server startup for the mysqlserverclone utility. Messages recommend using the -vvv option to find the actual error from the server startup sequence. (Bug #22457829) * The mysqlfrm utility failed when the --verbosity option was used. This fix replaces the --verbosity option with --verbose, the correct option name, and uses it consistently in error messages and code. (Bug #22254445, Bug #79382) * The mysqlserverinfo utility required connection parameters to show all MySQL servers running on the local host. This fix removes that restriction when the --show-servers option is specified. (Bug #22215626, Bug #79135) * Corrected a problem in the mysqldbimport utility where specifying the --skip option with a valid type failed to skip the intended object or objects during the operation. (Bug #22155217, Bug #79128) * The mysqldbcopy utility failed to copy grants for anonymous users. (Bug #22093518, Bug #78940) * Improved the --quiet option to silence all informational messages for the mysqldbcompare utility. (Bug #22093453, Bug #78938) * Corrected a problem using a single database name in the mysqldiff utility when comparing the same database on two servers. (Bug #21764003) * The DEB packages did not create the required /usr/share/pyshared/mysql directory. (Bug #21626041, Bug #78054) * Added error handling to ensure only one slave is specified for the --slave option for the mysqlreplicate, mysqlrplcheck, and mysqlrplms utilities. (Bug #21497923) * Enabled the use of the --exclude option for the mysqlrplsync utility. (Bug #21270853, Bug #77359) * Corrected a logic error when detecting and setting READ_ONLY mode on the candidate server during promotion for failover. (Bug #21201454, Bug #76522) * When the mysqldiff utility compared columns for indexes, it failed to take into account cardinality changes. That is, if the cardinality of one column differed from the corresponding column in the compared table, the index was considered different. This fix eliminates unnecessarily changes to indexes by the utility when cardinality differences are detected. (Bug #20857151, Bug #76619) * Removed password() function usage in the MySQL Utilities library for MySQL 5.7.6 or later. (Bug #20807296) * The mysqlfailover utility did not remove the failover_console table correctly on exit when run with the --daemon=start option. (Bug #20524886) * Improved the --force option for the mysqldiff utility to allow checks to continue when missing objects are detected. (Bug #20511130, Bug #75822) * Removed an extraneous difference in GRID format output of the mysqldbcompare utility when column sizes differ. (Bug #18763591) * Corrected PEP8 warnings and errors on the utilities code base. (Bug #18755438) * Corrected an issue in which the mysqldbexport utility produced output with inconsistent table and database names. (Bug #18733683) Reporting Bugs -------------- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy! On Behalf of the MySQL/ORACLE RE Team Hery Ramilison [Less]
Posted 2 months ago by Andy Bang
We are pleased to announce that MySQL Enterprise Monitor 3.2.6 is now available for download on the My Oracle Support (MOS) web site. This is a maintenance release that includes a few enhancements and fixes a number of bugs. You can find more ... [More] information on the contents of this release in the change log: http://dev.mysql.com/doc/relnotes/mysql-monitor/3.2/en/news-3-2-6.html (also included at the end of this note for convenience) You will find binaries for the new release on My Oracle Support: https://support.oracle.com Choose the "Patches & Updates" tab, and then choose the "Product or Family (Advanced Search)" side tab in the "Patch Search" portlet. IMPORTANT: MySQL Enterprise Monitor (MEM) 3.3 offers many significant improvements over MEM 3.2 and we highly recommend that you consider upgrading. More information on MEM 3.3 is available here: What's New in MySQL Enterprise Monitor 3.3 http://dev.mysql.com/doc/mysql-monitor/3.3/en/mem-comparison-3-2.html MySQL Enterprise Monitor http://www.mysql.com/products/enterprise/monitor.html MySQL Enterprise Monitor Frequently Asked Questions http://dev.mysql.com/doc/mysql-monitor/3.3/en/mem-faq.html MySQL Enterprise Monitor Change History http://dev.mysql.com/doc/relnotes/mysql-monitor/3.3/en/ Please open a bug or a ticket on My Oracle Support to report problems, request features, or give us general feedback about how this release meets your needs. If you are not a MySQL Enterprise customer and want to try the Monitor and Query Analyzer using our 30-day free customer trial, go to http://www.mysql.com/trials, or contact Sales at http://www.mysql.com/about/contact. Useful URLs * My Oracle Support - http://support.oracle.com/ * What's New in 3.2 - https://dev.mysql.com/doc/mysql-monitor/3.2/en/mem-comparison-3-2.html * Change log - http://dev.mysql.com/doc/relnotes/mysql-monitor/3.2/en/ * Installation documentation - http://dev.mysql.com/doc/mysql-monitor/3.2/en/mem-installing.html * Complete documentation - http://dev.mysql.com/doc/mysql-monitor/3.2/en/ * Product information - http://www.mysql.com/products/enterprise/monitor.html * FAQs - http://dev.mysql.com/doc/mysql-monitor/3.2/en/mem-faq.html * Download - http://support.oracle.com/ Thanks and Happy Monitoring! - The MySQL Enterprise Tools Development Team ========== Changes in MySQL Enterprise Monitor 3.2.6 Functionality Added or Changed * The value defined in Show entries on the Event Handlers page is saved as default. (Bug #24347638) * The bundled JRE was updated to 1.8.0_112 for both the Agent and Service Manager. * The OpenSSL libraries used by the MySQL Enterprise Monitor installers and MySQL Enterprise Monitor Aggregator have been upgraded to 1.0.2j. * The Slave Master Info/Relay Log Info Not Crash Safe is removed in this version. Its functionality is rolled into the Replication Configuration advisor. * The specific operating system version is now displayed in the Host Details section of the MySQL Instances dashboard. * The MySQL database, bundled with the MySQL Enterprise Service Manager, has been upgraded to MySQL 5.6.35. Bugs Fixed * Under certain circumstances, the asset selector list would not load on the Assets tab of the Groups page. (Bug #25051693) * Under certain circumstances, if a notification group contained one or more invalid email addresses, the notification failed. As of this release, the invalid address exception generated by the email server is handled correctly, the invalid email address is removed, and the notification is resent. If the notification group contains multiple invalid addresses, they are removed and the message resent until either the notification is sent or no email addresses remain. Errors are logged to the Action Log. (Bug #25037204) * If the backup directory was set to the same directory as the installation directory, the upgrade installer removed the installation, and the upgrade process failed. As of this release, the installers check if the backup directory is set to the same directory as the installation directory. This issue affected the upgrade installers for the MySQL Enterprise Service Manager, MySQL Enterprise Monitor Agent, and the MySQL Enterprise Monitor Proxy and Aggregator. (Bug #25027413, Bug #25078184, Bug #25078204) * The Show n entries drop-down menu on the Query Analyzer page was too small. This affected the Google Chrome browser, only. (Bug #24948388) * Comma-separated external role definitions were not correctly parsed on the Roles page. (Bug #24918199) * The External Role field on the Roles and Settings pages, was too small. (Bug #24917944) * The fields on the Encryption Settings tab of the Add MySQL Instance or Edit Instances dialogs did not reflect the actual configuration. (Bug #24833411) * The Group Settings tab on the Edit Instance dialog was too small to properly display its contents. (Bug #24481474) * Resume Event Handler dialog was too small for its contents. (Bug #24481411) * Duplicate actions were taken, and notifications sent, if multiple event handlers used the same advisor. As of this release, duplicate actions and notifications are combined into a single action or notification. However, each event handler is logged as handling the event. (Bug #24341371) * The Line and Stack graph controls were not displayed for graphs with many series. (Bug #22378850) * The auto-update parameter of the MySQL Enterprise Service Manager configuration utilities, config.sh, did not behave as expected. * Fields of the Add Instance dialog, for unmonitored instances, did not auto-populate with the correct, agent, hostname, or port number. [Less]
Posted 2 months ago by Andy Bang
We are pleased to announce that MySQL Enterprise Monitor 3.1.6 is now available for download on the My Oracle Support (MOS) web site. This is a maintenance release that includes a few enhancements and fixes a number of bugs. You can find more ... [More] information on the contents of this release in the change log: http://dev.mysql.com/doc/relnotes/mysql-monitor/3.1/en/news-3-1-6.html (also included at the end of this note for convenience) You will find binaries for the new release on My Oracle Support: https://support.oracle.com Choose the "Patches & Updates" tab, and then choose the "Product or Family (Advanced Search)" side tab in the "Patch Search" portlet. IMPORTANT: MySQL Enterprise Monitor (MEM) 3.3 offers many significant improvements over MEM 3.1 and MEM 3.2 and we highly recommend that you consider upgrading. More information on MEM 3.3 is available here: What's New in MySQL Enterprise Monitor 3.3 http://dev.mysql.com/doc/mysql-monitor/3.3/en/mem-comparison-3-2.html MySQL Enterprise Monitor http://www.mysql.com/products/enterprise/monitor.html MySQL Enterprise Monitor Frequently Asked Questions http://dev.mysql.com/doc/mysql-monitor/3.3/en/mem-faq.html MySQL Enterprise Monitor Change History http://dev.mysql.com/doc/relnotes/mysql-monitor/3.3/en/ Please open a bug or a ticket on My Oracle Support to report problems, request features, or give us general feedback about how this release meets your needs. If you are not a MySQL Enterprise customer and want to try the Monitor and Query Analyzer using our 30-day free customer trial, go to http://www.mysql.com/trials, or contact Sales at http://www.mysql.com/about/contact. Useful URLs * My Oracle Support - http://support.oracle.com/ * What's New in 3.1 - https://dev.mysql.com/doc/mysql-monitor/3.1/en/mem-comparison-3-1.html * Change log - http://dev.mysql.com/doc/relnotes/mysql-monitor/3.1/en/ * Installation documentation - http://dev.mysql.com/doc/mysql-monitor/3.1/en/mem-installing.html * Complete documentation - http://dev.mysql.com/doc/mysql-monitor/3.1/en/ * Product information - http://www.mysql.com/products/enterprise/monitor.html * FAQs - http://dev.mysql.com/doc/mysql-monitor/3.1/en/mem-faq.html * Download - http://support.oracle.com/ Thanks and Happy Monitoring! - The MySQL Enterprise Tools Development Team ========== Changes in MySQL Enterprise Monitor 3.1.6 Functionality Added or Changed * The configuration menu item Event Handling was renamed Event Handlers. * The bundled JRE was updated to 1.8.0_112 for both the Agent and Service Manager. * The OpenSSL libraries used by the MySQL Enterprise Monitor installers and MySQL Enterprise Monitor Aggregator have been upgraded to 1.0.2j. * The specific operating system version is now displayed in the Host Details section of the MySQL Instances dashboard. * The MySQL database, bundled with the MySQL Enterprise Service Manager, has been upgraded to MySQL 5.6.35. Bugs Fixed * Under certain circumstances, the asset selector list would not load on the Assets tab of the Groups page. (Bug #25051693) * Under certain circumstances, if a notification group contained one or more invalid email addresses, the notification failed. As of this release, the invalid address exception generated by the email server is handled correctly, the invalid email address is removed, and the notification is resent. If the notification group contains multiple invalid addresses, they are removed and the message resent until either the notification is sent or no email addresses remain. Errors are logged to the Action Log. (Bug #25037204) * If the backup directory was set to the same directory as the installation directory, the upgrade installer removed the installation, and the upgrade process failed. As of this release, the installers check if the backup directory is set to the same directory as the installation directory. This issue affected the upgrade installers for the MySQL Enterprise Service Manager, MySQL Enterprise Monitor Agent, and the MySQL Enterprise Monitor Proxy and Aggregator. (Bug #25027413, Bug #25078184, Bug #25078204) * The Show n entries drop-down menu on the Query Analyzer page was too small. This affected the Google Chrome browser, only. (Bug #24948388) * Comma-separated external role definitions were not correctly parsed on the Roles page. (Bug #24918199) * The External Role field on the Roles and Settings pages, was too small. (Bug #24917944) * The fields on the Encryption Settings tab of the Add MySQL Instance or Edit Instances dialogs did not reflect the actual configuration. (Bug #24833411) * The Group Settings tab on the Edit Instance dialog was too small to properly display its contents. (Bug #24481474) * Resume Event Handler dialog was too small for its contents. (Bug #24481411) * Duplicate actions were taken, and notifications sent, if multiple event handlers used the same advisor. As of this release, duplicate actions and notifications are combined into a single action or notification. However, each event handler is logged as handling the event. (Bug #24341371) * The Line and Stack graph controls were not displayed for graphs with many series. (Bug #22378850) * The auto-update parameter of the MySQL Enterprise Service Manager configuration utilities, config.sh, did not behave as expected. * Fields of the Add Instance dialog, for unmonitored instances, did not auto-populate with the correct, agent, hostname, or port number. [Less]
Posted 2 months ago