Changes in MySQL Shell 8.4.6 (2025-07-22; LTS Release)$$$Note$$$These release notes were created with the assistance of HeatWave GenAI.$$$$$$Utilities Bugs Fixed$$$$$$Bugs Fixed$$$$$$Utilities Bugs Fixed$$$util.dumpInstance returned the following error when run against MySQL HeatWave DB Systems:$$$$$$ERROR: User admin@% is granted restricted privilege: OPTION_TRACKER_OBSERVER $$$(fix this with strip_restricted_grants compatibility option)$$$The list of privileges has been updated to include OPTION_TRACKER_OBSERVER. (Bug #37958876)$$$$$$The load dump utility failed if the target MySQL instance did not have Performance Schema enabled. An error similar to the following was returned:$$$$$$ERROR: [Worker006]: Error opening connection to MySQL: MySQL Error 1683 (HY000): $$$ps_current_thread_id: The Performance Schema is not enabled.$$$As of this release; if the call to ps_current_thread_id() fails for any reason; it is logged; but does not cause the load to stop. (Bug #37867455)$$$$$$References: See also: Bug #36197620.$$$$$$MySQL Shell logging has been improved for LOAD DATA warnings generated by util.importTable and util.loadDump. Previously; LOAD DATA warnings were printed to the terminal and were difficult to locate in the log. For example:$$$$$$Warning: schema@table@123.tsv.zst error 1062: Duplicate entry$$$1234567 for key table.PRIMARY$$$These messages have been improved; making them easier to find in the log. For example:$$$$$$Warning: An error has been reported while loading data into$$$`schema`.`table` from schema@table@123.tsv.zst file; error 1062:$$$Duplicate entry 1234567 for key table.PRIMARY$$$(Bug #37800574)$$$$$$The MySQL REST Service-specific account; ocirest; is automatically excluded when dumping with ocmids:true; or loading into MySQL HeatWave DB Systems. (Bug #37792183)$$$$$$The Upgrade Checker utility returned a false positive for partial keys in schemas referencing full keys in other schemas. (Bug #37651453)$$$$$$Bugs Fixed$$$Kerberos authentication is now supported on macOS. The authentication_kerberos_client plugin is now bundled on macOS installations of MySQL Shell. (Bug #37777584)$$$$$$MySQL Shell could crash when dumping a table with a functional; or virtual; index.$$$$$$The following error was returned:$$$$$$Segmentation fault (core dumped)$$$(Bug #37770454)

Changes in MySQL Shell 8.0.43 (2025-07-22; General Availability)$$$Note$$$These release notes were created with the assistance of HeatWave GenAI.$$$$$$Utilities Bugs Fixed$$$$$$Bugs Fixed$$$$$$Utilities Bugs Fixed$$$util.dumpInstance returned the following error when run against MySQL HeatWave DB Systems:$$$$$$ERROR: User admin@% is granted restricted privilege: OPTION_TRACKER_OBSERVER $$$(fix this with strip_restricted_grants compatibility option)$$$The list of privileges has been updated to include OPTION_TRACKER_OBSERVER. (Bug #37958876)$$$$$$MySQL Shell logging has been improved for LOAD DATA warnings generated by util.importTable and util.loadDump. Previously; LOAD DATA warnings were printed to the terminal and were difficult to locate in the log. For example:$$$$$$Warning: schema@table@123.tsv.zst error 1062: Duplicate entry$$$1234567 for key table.PRIMARY$$$These messages have been improved; making them easier to find in the log. For example:$$$$$$Warning: An error has been reported while loading data into$$$`schema`.`table` from schema@table@123.tsv.zst file; error 1062:$$$Duplicate entry 1234567 for key table.PRIMARY$$$(Bug #37800574)$$$$$$The MySQL REST Service-specific account; ocirest; is automatically excluded when dumping with ocmids:true; or loading into MySQL HeatWave DB Systems. (Bug #37792183)$$$$$$Bugs Fixed$$$Kerberos authentication is now supported on macOS. The authentication_kerberos_client plugin is now bundled on macOS installations of MySQL Shell. (Bug #37777584)$$$$$$

Changes in MySQL Shell 8.0.42 (2025-04-15; General Availability)$$$Utilities Added or Changed Functionality$$$$$$Utilities Bugs Fixed$$$$$$Bugs Fixed$$$$$$Utilities Added or Changed Functionality$$$The mysql_option_tracker_persister role is now excluded from the dump when ocimds: true and is excluded when loading a dump into a MySQL HeatWave DB System. (Bug #37457569)$$$$$$Utilities Bugs Fixed$$$Dump and load operations failed randomly due to a bug in the bundled Curl package.$$$$$$Curl is upgraded to 8.12.1 in this release. (Bug #37576066)$$$$$$Bugs Fixed$$$Under certain circumstances MySQL Shell could crash during auto-completion on options such as shell.options.history.auto. (Bug #37528585)

Changes in MySQL Shell 8.0.42 (2025-04-15; General Availability)$$$Utilities Added or Changed Functionality$$$$$$Utilities Bugs Fixed$$$$$$Bugs Fixed$$$$$$Utilities Added or Changed Functionality$$$The mysql_option_tracker_persister role is now excluded from the dump when ocimds: true and is excluded when loading a dump into a MySQL HeatWave DB System. (Bug #37457569)$$$$$$Utilities Bugs Fixed$$$Dump and load operations failed randomly due to a bug in the bundled Curl package.$$$$$$Curl is upgraded to 8.12.1 in this release. (Bug #37576066)$$$$$$Bugs Fixed$$$Under certain circumstances MySQL Shell could crash during auto-completion on options such as shell.options.history.auto. (Bug #37528585)

Changes in MySQL Shell 8.0.42 (2025-04-15; General Availability)$$$Utilities Added or Changed Functionality$$$$$$Utilities Bugs Fixed$$$$$$Bugs Fixed$$$$$$Utilities Added or Changed Functionality$$$The mysql_option_tracker_persister role is now excluded from the dump when ocimds: true and is excluded when loading a dump into a MySQL HeatWave DB System. (Bug #37457569)$$$$$$Utilities Bugs Fixed$$$Dump and load operations failed randomly due to a bug in the bundled Curl package.$$$$$$Curl is upgraded to 8.12.1 in this release. (Bug #37576066)$$$$$$Bugs Fixed$$$Under certain circumstances MySQL Shell could crash during auto-completion on options such as shell.options.history.auto. (Bug #37528585)

Changes in MySQL Shell 8.0.42 (2025-04-15; General Availability)$$$Utilities Added or Changed Functionality$$$$$$Utilities Bugs Fixed$$$$$$Bugs Fixed$$$$$$Utilities Added or Changed Functionality$$$The mysql_option_tracker_persister role is now excluded from the dump when ocimds: true and is excluded when loading a dump into a MySQL HeatWave DB System. (Bug #37457569)$$$$$$Utilities Bugs Fixed$$$Dump and load operations failed randomly due to a bug in the bundled Curl package.$$$$$$Curl is upgraded to 8.12.1 in this release. (Bug #37576066)$$$$$$Bugs Fixed$$$Under certain circumstances MySQL Shell could crash during auto-completion on options such as shell.options.history.auto. (Bug #37528585)

Changes in MySQL Shell 8.4.4 (2025-01-21; LTS Release)$$$AdminAPI Bugs Fixed$$$$$$Utilities Added or Changed Functionality$$$$$$Utilities Bugs Fixed$$$$$$Functionality Added or Changed$$$$$$Bugs Fixed$$$$$$AdminAPI Bugs Fixed$$$replicationLag of ReplicaSet.status() returned null if replication was idle.$$$$$$As of this release; the following changes were made:$$$$$$replicationLag is set to null if the replication connection; or SQL thread; is not running.$$$$$$replicationLag is set to applier_queue_applied when the last queued transaction matches the last applied transaction; or the applying transaction count is 0 (zero).$$$$$$(Bug #35914505)$$$$$$It was not possible to remove a member from a ReplicaSet using ReplicaSet.removeInstance() with the force option enabled; if the member was in an ERROR state. (Bug #35282392)$$$$$$The ReplicaSet metadata schema table; INSTANCES; was not populated properly when upgrading the metadata schema to version 2.2.0. As a result; MySQL Router did not recognize the topology and rejected connections to it. (Bug #116231; Bug #37101286)$$$$$$Utilities Added or Changed Functionality$$$The schema MYSQL_AUTOPILOT is excluded by dump and load operations with ocimds:true. (Bug #37278169)$$$$$$As of this release; the upgrade checker utility writes all compatibility issues and fixes to the log file; instead of only writing to the console. (Bug #37154456)$$$$$$Utilities Bugs Fixed$$$If convertBsonTypes was enabled; the JSON import utility failed when importing negative BSON values.$$$$$$An error similar to the following was returned:$$$$$$ ValueError: Unexpected data; expected to find an integer string processing extended JSON for $numberInt at offset 25$$$(Bug #37243264)$$$$$$Amazon RDS made the following changes in 8.0.36:$$$$$$It is no longer possible to grant BACKUP_ADMIN.$$$$$$It is no longer possible to lock MySQL system tables.$$$$$$As a result; consistent dumps from Amazon RDS are not possible.$$$$$$As of this release; if locking the MySQL system tables fails with an Access Denied error; a warning is printed and the dump continues.$$$$$$Additionally; for non-Amazon RDS instances; if the user has the BACKUP_ADMIN privilege and LOCK INSTANCE FOR BACKUP succeeds; the MySQL system tables are not locked. (Bug #37226153)$$$$$$Under certain circumstances; such as a large amount of data chunking; the maxRate dump option did not properly limit the throughput due to a gap between the start of the dump and the start of the data dump. As of this release; maxRate is used only when data is being dumped. (Bug #37216767)$$$$$$MySQL Shell could hang when running a dump with consistent: true under an account which lacked privileges to execute FLUSH TABLES WITH READ LOCK.$$$$$$As of this release; query events are checked only if they contain data; and GRANT and REVOKE statements are flagged as unsafe. (Bug #37158908)$$$$$$Functionality Added or Changed$$$As of this release; the Google V8 JavaScript engine is replaced by Oracle GraalVM. (Bug #34370637)$$$$$$Bugs Fixed$$$In MySQL Shell 8.0.40; RPM installation failed on Oracle Linux 8 due to a dependency on Python 3.9. As of this release; MySQL Shell bundles Python 3.13. (Bug #37479400)$$$$$$Under certain circumstances; a Ctrl+c key combination could lead to a deadlock. (Bug #35998250)

Changes in MySQL Shell 8.0.41 (2025-01-21; General Availability)$$$Utilities Added or Changed Functionality$$$$$$Utilities Bugs Fixed$$$$$$Functionality Added or Changed$$$$$$Bugs Fixed$$$$$$Utilities Added or Changed Functionality$$$The schema MYSQL_AUTOPILOT is excluded by dump and load operations with ocimds:true. (Bug #37278169)$$$$$$As of this release; the upgrade checker utility writes all compatibility issues and fixes to the log file; instead of only writing to the console. (Bug #37154456)$$$$$$Utilities Bugs Fixed$$$If convertBsonTypes was enabled; the JSON import utility failed when importing negative BSON values.$$$$$$An error similar to the following was returned:$$$$$$ ValueError: Unexpected data; expected to find an integer string processing extended JSON for $numberInt at offset 25$$$(Bug #37243264)$$$$$$Under certain circumstances; such as a large amount of data chunking; the maxRate dump option did not properly limit the throughput due to a gap between the start of the dump and the start of the data dump. As of this release; maxRate is used only when data is being dumped. (Bug #37216767)$$$$$$MySQL Shell could hang when running a dump with consistent: true under an account which lacked privileges to execute FLUSH TABLES WITH READ LOCK.$$$$$$As of this release; query events are checked only if they contain data; and GRANT and REVOKE statements are flagged as unsafe. (Bug #37158908)$$$$$$Functionality Added or Changed$$$As of this release; the Google V8 JavaScript engine is replaced by Oracle GraalVM. (Bug #34370637)$$$$$$Bugs Fixed$$$In MySQL Shell 8.0.40; RPM installation failed on Oracle Linux 8 due to a dependency on Python 3.9. As of this release; MySQL Shell bundles Python 3.13. (Bug #37479400)$$$$$$It was not possible to start MySQL Shell on Oracle Linux 8 running on ARM platforms if PAGE_SIZE was set to 64K. An error similar to the following was displayed:$$$$$$mysqlsh: error while loading shared libraries: $$$libantlr4-runtime.so.4.10.1: ELF load command alignment $$$not page-aligned$$$(Bug #36792750)

Changes in MySQL Shell 8.4.3 (2024-10-15; LTS Release)$$$AdminAPI Bugs Fixed$$$$$$Utilities Added or Changed Functionality$$$$$$Utilities Bugs Fixed$$$$$$Bugs Fixed$$$$$$AdminAPI Bugs Fixed$$$Running a rescan() operation on a Replica Cluster; could result in a warning that group_replication_view_change_uuid is required; but not configured. This occurred in a mixed version ClusterSet; where the primary Cluster is on version 8.3.0; or higher; and the replicas were on versions lower than 8.3.0. The check for group_replication_view_change_uuid was incorrectly performed on the primary Cluster instead of the target Replica Cluster. (Bug #36657936)$$$$$$If clone-based recovery failed while adding an instance; the instance and Cluster could be left in an inconsistent state; returning multiple errors; and unrecoverable by rescan(). It was not possible to remove the instance with remove_instance(); either.$$$$$$add_instance() did not properly handle clone-related errors and did not stop Group Replication if errors were detected.$$$$$$As of this release; add_instance() handles clone-related errors; reverts the state of the target instance and stops Group Replication on that instance. (Bug #36657628)$$$$$$Running AdminAPI operations against MySQL 5.7 instances resulted in an error; due to an attempt to run a query on a non-existent Performance Schema table.$$$$$$As of this release; error handling is included to account for such issues. (Bug #36652642)$$$$$$It was possible to define duplicate instance definitions in the replicationSources list of the Cluster.add_replica_instance() operation. The operation failed with an error.$$$$$$As of this release; the replicationSources list is validated for such duplicates in all operations which use it. The operation fails with an informative error. (Bug #36614218)$$$$$$AdminAPI commands which add or rejoin instances to Clusters using Clone did not check the existing members for compatibility. If no compatible members were available; Group Replication fell back to incremental recovery which can fail if Clone was the only supported provisioning method. An unexpected and unhelpful error was returned.$$$$$$As of this release; the following commands have been updated to check compatibility and provide appropriate feedback:$$$$$$ReplicaSet.add_instance()$$$$$$ReplicaSet.rejoin_instance()$$$$$$Cluster.add_replica_instance()$$$$$$Cluster.rejoin_instance()$$$$$$ClusterSet.create_replica_cluster()$$$$$$For a donor to be considered compatible for a recipient:$$$$$$They must be running on the same operating system.$$$$$$They must be running on the same platform.$$$$$$The versions must be compatible:$$$$$$Both must be version 8.0.17; or higher.$$$$$$If both are version 8.0.37; or higher; only their major and minor versions need match. For example; 8.4.0 and 8.4.3.$$$$$$For versions 8.0.17; or higher; and lower than 8.0.37; the major; minor; and patch numbers must match.$$$$$$(Bug #36054619; Bug #36682741)$$$$$$Utilities Added or Changed Functionality$$$As of this release; the MYSQL_OPTION schema is excluded by the dump utilities when ocimds: true and is automatically excluded when loading a dump into a MySQL HeatWave DB System. (Bug #37023079)$$$$$$The compatibility option; unescape_wildcard_grants; is added in this release. When enabled; this strips escape characters in grants on schemas; replacing escaped \_ and \% wildcards in schema names with _ and % wildcard characters. When the partial_revokes system variable is enabled; the \ character is treated as a literal; which could lead to unexpected results. It is strongly recommended to check each such grant before enabling this option. (Bug #36524862)$$$$$$The index creation step of a load operation now includes percentage completion information. (Bug #35495220)$$$$$$Utilities Bugs Fixed$$$The upgrade checker utility returned a false positive for foreign keys defined on tables in the Cluster metadata schema. (Bug #36975599)$$$$$$Under certain circumstances; using zstd compression; the dump utilities could generate corrupt

Changes in MySQL Shell 8.0.40 (2024-10-15; General Availability)$$$Utilities Added or Changed Functionality$$$$$$Utilities Bugs Fixed$$$$$$Bugs Fixed$$$$$$Utilities Added or Changed Functionality$$$As of this release; the MYSQL_OPTION schema is excluded by the dump utilities when ocimds: true and is automatically excluded when loading a dump into a MySQL HeatWave DB System. (Bug #37023079)$$$$$$Utilities Bugs Fixed$$$Under certain circumstances; using zstd compression; the dump utilities could generate corrupted data files. (Bug #36836188)$$$$$$Attempting to run the dump or copy utilities from MySQL Shell 8.0.x against a more recent version of the server; such as 8.4.0; could result in a syntax error.$$$$$$Many breaking changes have been made to MySQL syntax and configuration between 8.0.37 and 8.4.x; and higher; such as replacing SHOW MASTER STATUS with SHOW BINARY LOG STATUS; for example. There were also many removals. See the release notes for those server versions for more information.$$$$$$As of this release; the dump and copy utilities raise an error when such incompatibilities are detected and recommend the appropriate MySQL Shell upgrade.$$$$$$Important$$$It is always recommended to use the latest version of MySQL Shell.$$$$$$(Bug #36701854)$$$$$$Bugs Fixed$$$MySQL Shell failed to start if installed by MSI on Microsoft Windows 11 with Visual Studio Redistributable version 14.3x or lower. On Windows platforms; MySQL Shell requires Visual Studio Redistributable version 14.4x or higher.$$$$$$See Microsoft Visual C++ Redistributable latest supported downloads. (Bug #37049411)$$$$$$The MySQL Shell MSI progress dialogs displayed numbered placeholders instead of the installation values. (Bug #37033676)$$$$$$When running MySQL Shell over SSH; if a command was entered on the command line; but not executed; closing the SSH session could result in the command being executed without user input. (Bug #36861912)$$$$$$The URI parser threw an exception if the URI contained an unescaped @ character. (Bug #36105235)

Changes in MySQL Shell 8.0.38 (2024-07-01; General Availability)$$$AdminAPI Bugs Fixed$$$$$$Utilities Bugs Fixed$$$$$$Bugs Fixed$$$$$$AdminAPI Bugs Fixed$$$MySQL Shell closed unexpectedly when calling certain AdminAPI functions on EL7 platforms. (Bug #36651010)$$$$$$dba.reboot_cluster_from_complete_outage() disabled super_read_only on the primary member of an INVALIDATED Cluster. As a result; clients continued to perform updates and introduce errant transactions.$$$$$$As of this release; dba.reboot_cluster_from_complete_outage() enables super_read_only on the primary member and disables the Group Replication action mysql_disable_super_read_only_if_primary. (Bug #36562916)$$$$$$If an attempt to create a Replica Cluster failed due to a timeout and the revert also failed due to a timeout; the Replica Cluster could be left in an inconsistent state; ONLINE; but not associated with the ClusterSets metadata. This specific issue was caused by low values for wait_timeout and interactive_timeout.$$$$$$The following changes were made:$$$$$$wait_timeout is checked and; if set to a value lower than the default of 8 hours; is set to 8 hours.$$$$$$Cluster.rescan() is extended with a new option; repairMetadata which can be enabled to resolve inconsistencies in the Clusters metadata.$$$$$$Cluster.dissolve() can now be used on Clusters in this inconsistent state.$$$$$$(Bug #36495756)$$$$$$Utilities Bugs Fixe

AdminAPI Bugs Fixed$$$MySQL Shell closed unexpectedly when calling certain AdminAPI functions on EL7 platforms. (Bug #36651010)$$$$$$dba.reboot_cluster_from_complete_outage() disabled super_read_only on the primary member of an INVALIDATED Cluster. As a result; clients continued to perform updates and introduce errant transactions.$$$$$$As of this release; dba.reboot_cluster_from_complete_outage() enables super_read_only on the primary member and disables the Group Replication action mysql_disable_super_read_only_if_primary. (Bug #36562916)$$$$$$If an attempt to create a Replica Cluster failed due to a timeout and the revert also failed due to a timeout; the Replica Cluster could be left in an inconsistent state; ONLINE; but not associated with the ClusterSets metadata. This specific issue was caused by low values for wait_timeout and interactive_timeout.$$$$$$The following changes were made:$$$$$$wait_timeout is checked and; if set to a value lower than the default of 8 hours; is set to 8 hours.$$$$$$Cluster.rescan() is extended with a new option; repairMetadata which can be enabled to resolve inconsistencies in the Clusters metadata.$$$$$$Cluster.dissolve() can now be used on Clusters in this inconsistent state.

Bugs Fixed$$$MySQL Shell returned a socket-specific connection message to the localhost although the connection was TCP and to a remote host. This occurred if a socket path was specified either in the configuration file or on the command line.$$$$$$As of this release; the transport to use is determined by the right-most parameter on the command line. (Bug #112115; Bug #35751281)

AdminAPI Bugs Fixed$$$Rebooting a replica cluster from complete outage could result in the cluster rejoining the ClusterSet; but not the instance members of the replica cluster. This happened only if the primary cluster was under heavy load or the replica cluster was missing transactions from the ClusterSet. (Bug #35444244)$$$$$$If the X Protocol port was changed for a cluster member and that member restarted; the AdminAPI did not update the metadata with the new port number; leading to connection errors and so on.$$$$$$As of this release; cluster.status() checks for port changes and cluster.rescan() updates the metadata with the new port number. (Bug #35410360)$$$$$$During a failover of a ClusterSet replication channel; the ClusterSet.status() value clusterSetReplicationStatus reported ERROR and globalStatus returned OK_NOT_REPLICATING. Errors and warnings relating to misconfigured or stopped channels were also returned. These statuses and errors were misleading as the channel was attempting to connect to another source or replica.$$$$$$As of this release; clusterSetReplicationStatus returns CONNECTING; and globalStatus returns OK while a channel connection attempt is ongoing. If there is an error; it is ignored until the channel state updates to either ON or OFF.$$$$$$Additionally; the ReplicaSet.status() field; status; also returns CONNECTING. (Bug #34614769)$$$$$$Utilities Bugs Fixed$$$Under certain circumstances; util.loadDump() could fail when retrieving a file from AWS S3; even though the file was downloadable by other means.$$$$$$As of this release; if CURL errors occur; such as 52: CURLE_GOT_NOTHING or 56 (CURLE_RECV_ERROR); utils.loadDump() retries the download. (Bug #35362775)$$$$$$If an exception occurred while importing a single; uncompressed file with util.import_table(); MySQL Shell crashed. (Bug #35313366)$$$$$$The upgrade checker utility did not check stored procedures and routines for the deprecated qualifier syntax .tbl_name. (Bug #35046623)$$$$$$If chunking was enabled for a dump of tables; but the primary key or unique index used to chunk the table contained an ENUM column; some of the tables rows were not exported to the dump. This occurred if the ENUM columns values were not ordered alphabetically.$$$$$$As of this release; primary keys or unique indexes which contain one or more ENUM columns; are ignored when selecting an index for chunking. (Bug #110352; Bug #35180061)$$$$$$Functionality Added or Changed$$$MySQL Shell now supports the --loose prefix.$$$$$$For more information on this prefix; see Program Option Modifiers. (Bug #110141; Bug #35112454)$$$$$$Bugs Fixed$$$The MySQL configuration utility mysql_config_editor was not bundled with MySQL Shell 8.0.33. (Bug #35459202)$$$$$$References: This issue is a regression of: Bug #34097411.$$$$$$MySQL Shell command line did not correctly handle missing optional arguments. A NULL value was used instead of a valid value; resulting in an error. (Bug #109827; Bug #35068427)$$$$$$