You cannot upgrade a DB system to the latest MySQL version when there are
insufficient IP addresses to maintain and upgrade the DB system.
Using the Console 🔗
Use the Console to resolve the upgrade failure issue caused by insufficient IP addresses.
This task assumes the following:
The affected database is in active state but it is not upgraded to the latest version because all available IP addresses from the customer subnet have been allocated.
Note
HeatWave Service requires two IP addresses per DB system in each subnet;
one to attach to the DB system, the other for use in the maintenance and upgrade
operations on that DB system. Also, the Networking service reserves three IP addresses in each
subnet.
Once the backup is complete, do one of the following:
Open the subnet and edit the subnet mask to accomodate more
IP addresses. See To edit a
subnet.
Restore the backup to a new DB system and select a new
subnet with a larger IP range and then delete the failed DB system. See
Restoring From a Backup and Deleting a DB System.
Resolving Version Inconsistencies 🔗
When an upgrade does not run to completion, it can cause version inconsistencies among different instances of a high availability DB system or a standalone DB system and its read replicas.
If the upgrade of any instance (read replica or DB system) fails, the instance is rolled back and the upgrade operation is aborted. However, any instances that have been upgraded successfully before the error will remain and the DB system reports that it contains version inconsistencies.
The DB system should be fully operational despite the version inconsistency, but the inconsistencies should be resolved as soon as time permits.
The step to resolve the version inconsistency is to run the upgrade again with the same target version. When the upgrade is retried, it only upgrades instances that have not been upgraded. Instances that have already been upgraded to the target version are not upgraded again.