Documentation Home
MySQL Shell Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 0.5Mb
PDF (A4) - 0.5Mb

MySQL Shell Release Notes  /  Changes in MySQL Shell 8.0.35 (2023-10-25, General Availability)

Changes in MySQL Shell 8.0.35 (2023-10-25, General Availability)

AdminAPI Bugs Fixed

  • Using -- clusterset listRouters on the command line, without providing a parameter for listRouters, resulted in the following error in MySQL Shell 8.0.34:

            ERROR: Argument #1 is expected to be a string

    (Bug #35747208)

    References: This issue is a regression of: Bug #35068427.

Utilities Added or Changed Functionality

  • Instance dump utility now excludes the mysql_firewall schema if ocimds: true. (Bug #35805866)

  • MySQL Shell was updated for compatibility with the privilege changes made in MySQL HeatWave Service.

    The following privileges were added to MySQL HeatWave Service:








    The following privileges were removed from MySQL HeatWave Service



    For more information on MySQL HeatWave Service privileges, see Default MySQL Privileges. (Bug #35668544)

  • Operations resulting in the curl errors 52: CURLE_GOT_NOTHING and 56: CURLE_RECV_ERROR are retried for all supported cloud vendors, for all utilities which support them. (Bug #35659057)

  • MySQL Shell dump and load utilities now support the Oracle Cloud Infrastructure Object Storage Dedicated Endpoints format for Pre-Authenticated Request (PAR) URLs:

    For more information, see OCI Object Storage Dedicated Endpoints.

    MySQL Shell continues to support the legacy PAR URL format:

    (Bug #35548572)

  • util.checkForServerUpgrade() has been updated to check for columns which have foreign keys referencing columns in tables using different database storage engines, such as MyISAM. (Bug #35155064)

Utilities Bugs Fixed

  • Under certain circumstances, when loading a file larger than maxBytesPerTransaction, (or 1.5 * bytesPerChunk if maxBytesPerTransaction was not used) a memory leak could occur. (Bug #35600174)

  • As of MySQL Server 8.1.0, MySQL HeatWave Service contains a schema named mysql_audit. As a result, the dump and load utilities encountered a duplicate object error when copying data from one DB System to another.

    As of this release, with the ocimds option enabled, dumpInstance() automatically excludes the mysql_audit schema. (Bug #35550282)

  • If an AWS HEAD request failed with an authorization error, it was not retried. As of this release if such a request fails with a 400 HTTP error, it is retried.

    Additionally, if the refresh process for AWS credentials has a defined expiration time, the refresh process is triggered 5 minutes before the required time. (Bug #35468541)

  • util.debug.collectDiagnostics() failed if run on an InnoDB Cluster created with an older version of MySQL Shell. An error similar to the following was generated:

    An error occurred during data collection. Partial output deleted.
    debug.collectDiagnostics: ClassicSession.run_sql: Table 
    'mysql_innodb_cluster_metadata.v2_cs_clustersets' doesn't exist (MySQL Error 1146)

    As of this release, util.debug.collectDiagnostics() collects diagnostics information even if tables are missing. (Bug #35468106)

  • util.debug.collectDiagnostics() threw an exception if the server was configured to write error logs to stderr. For example, if mysqld was started with --console. (Bug #35318770)

  • The MySQL Shell upgrade checker utility flagged views as corrupt in MySQL 5.7 versions up to 5.7.39. This issue occurred for views whose from clause contained a table schema prefix with a group by clause. (Bug #111813, Bug #35635009)

  • The utility, checkForServerUpgrade, did not recognize INTERSECT as a reserved word.

    INTERSECT was reserved in MySQL Server 8.0.31. (Bug #110824, Bug #35335813)

Bugs Fixed

  • The Windows installer for MySQL Shell upgrades did not recognise the existing MySQL Shell installation, overwrote that installation, and created a separate uninstall entry in Add/Remove Programs without removing the existing entry. (Bug #35869936)

  • Errors generated by stored procedures were not returned over classic MySQL protocol connections. (Bug #35549008)