MySQL 8.0 is scheduled for Finish of Life (EOL) in April 2026. In keeping with this milestone, we beforehand introduced in this Oracle weblog put up that each one present MySQL HeatWave situations working model 8.0 can be mechanically upgraded to the most recent supported 8.4 launch after April 2026.
Nonetheless, understanding the operational realities and planning cycles of our clients, we’re extending help for MySQL 8.0 situations in MySQL HeatWave till April 2027. This extension permits organizations extra time to speak, coordinate, and execute improve plans in partnership with Oracle’s gross sales and help groups. Throughout this extension, present 8.0 situations will stay absolutely purposeful and obtain crucial safety patches, guaranteeing enterprise continuity and information safety as you transition to newer variations.
What does the MySQL 8.0 EOL extension imply?
1. Present 8.0 MySQL HeatWave situations stay operational and safe
Current MySQL HeatWave situations working a model decrease than 8.0.46 will proceed to function. Within the upkeep cycle in June 2026, all situations working 8.0 will likely be mechanically upgraded to eight.0.46. This measure ensures that each one supported 8.0 situations profit from crucial safety and stability updates till the ultimate transition to newer MySQL variations. Oracle will apply solely important safety patches to each the OS and MySQL database till April 2027. This strategy ensures your information stays secure whilst you put together for an improve.
2. New 8.0 Cases and Main Operations Restricted
To help a constant improve path, sure actions involving MySQL 8.0 are not allowed:
- Creating a brand new 8.0 occasion isn’t permitted.
- Altering your occasion form (e.g., from MySQL.2 to MySQL.4) isn’t allowed for situations working 8.0 model.
- Restoring backups to create new 8.0 situations triggers an computerized improve—any restored backup will lead to an occasion working the most recent MySQL 8.4 model.
- Including 8.0 primarily based learn replicas to any DB techniques isn’t supported.
3. Computerized Upgrades Publish April 2027
After April 2027, any remaining MySQL HeatWave 8.0 situations will likely be mechanically upgraded to MySQL 8.4 LTS throughout their subsequent upkeep window, following Oracle Cloud Internet hosting and Supply insurance policies (see particulars).
How is Oracle Supporting Clients?
Early Notifications and Steering
- Console Notifications: You’ll see a distinguished banner within the Oracle Cloud Console, reminding you of the upcoming EOL and linking to sources for seamless upgrades.
- Direct Communications: Common Cloud Notification (CN) will alert affected clients. Messages will likely be despatched month-to-month from February to April, quarterly in August and January, then month-to-month from February to April because the timeline progresses.
Complete Self-Service and Help
- Information Articles & FAQs: Oracle offers up-to-date documentation to help your transition:
What Ought to Clients Do Subsequent?
- Assessment and Plan: Collaborate along with your Oracle gross sales and help groups to develop an improve plan forward of the April 2027 computerized improve window.
- Keep Knowledgeable: Look ahead to notifications within the console and by way of e mail and overview the sources linked above for particulars.
- Act Early: Proactively upgrading to MySQL 8.4 ensures continued entry to the most recent options and stability.
Abstract
Extending the EOL for MySQL 8.0 in MySQL HeatWave to April 2027 provides loads of time for considerate planning and execution of upgrades. Oracle will help this transition with ongoing safety, clear communication, and devoted improve sources. For extra data and frequent updates, confer with the supplied KM articles or attain out to your Oracle help consultant.
