Hi everyone,
Hope you’re doing well.
On May 13th, I released the BETA version of the AutoUpgrade-Composer Tool. You can read the announcement here: Introducing: The AutoUpgrade-Composer Tool [BETA]
If you’ve read that post, you might remember that during the BETA phase, the tool only supported Patch operations — but with all modes available: Analyze, Fixups, Create Home, Download, and Deploy.
Since I started working on the tool, I designed it to support both Patch and Upgrade capabilities. Upgrade was the first capability available when Oracle released AutoUpgrade, and you can read about that original release on Mike Dietrich’s blog:
https://mikedietrichde.com/2019/04/29/the-new-autoupgrade-utility-in-oracle-19c/
May 13th was a very special day for me with the release of AutoUpgrade-Composer. But today, is also a great day – I’m releasing the first STABLE version for AutoUpgrade-Composer.
Upgrade Capability
As mentioned, today I’m releasing the STABLE version for AutoUpgrade-Composer and enabling the capability to build Configuration Files for Upgrade operations.
I will not go into all the details in this post – that will be covered in a dedicated blog series, which I’ve already started: AutoUpgrade-Composer Posts.
With Upgrade capability on AutoUpgrade-Composer you will now be able to choose from the options below.
How to Access?
You can access AutoUpgrade-Composer:
- From the top menu of my blog:
2. From the Direct URL
https://viniciusdba.com.br/autoupgrade-composer
How to Use?
AutoUpgrade-Composer is organized into sections.
At the top of the page, you will see the current version. I always try to follow the same versioning as the AutoUpgrade tool.
As of now, you are seeing v.25.3-1.
The “-1” at the end indicates an internal change control or minor revision I’m making within the 25.3 version of the tool. It helps track updates or fixes on AutoUpgrade-Composer. So, if I find any issue, the next version will be v.25.3-2, and so on. I’ll only advance to v.25.4 once Oracle releases AutoUpgrade v.25.4.
With that said, every time Oracle releases a new version of the AutoUpgrade tool, I will review their changelog to identify new or removed parameters, new features, or any bug fixes that require configuration changes in the AutoUpgrade-Composer.
In the screenshot below:
- You can toggle between light and dark themes.
- You can load a previously generated configuration by AutoUpgrade-Composer.
- You can choose the Operation Type: Upgrade Database or Patch Database.
- The main tab will change depending on the selected operation type.
- On the right side of the screen, the Generated Config is updated dynamically based on the parameters and values you choose.
With the Generated Config on the right side/column, the Tool is more concise – and it’s great to see it update in real time as you change the parameters. That’s was a special request from Rodrigo Jorge.
Will All Options Be Explained?
Definitely! Stay tuned on my blog, I will publish several blog posts showing how to perform the operations, exploring different parameters and scenarios!
Why Doesn’t the Tool Include All AutoUpgrade Parameters?
Great question — and something I’m actively discussing with Alex Zaballa and Rodrigo Jorge.
AutoUpgrade is a powerful tool. Currently, it has 60 local parameters and 11 global parameters. Some parameters can be used for both Upgrade and Patch, while others are exclusive to one.
I’d love to include all of them in AutoUpgrade-Composer. But there’s an inflection point — the tool was built to help DBAs compose AutoUpgrade configuration files quickly and easily. And there’s a fine line between keeping it simple and making it too complicated.
I’m still thinking — and discussing with Alex and Rodrigo — about implementing a Comprehensive Mode for advanced use cases.
If there’s any parameter that’s important to you and currently missing, don’t hesitate to reach out to me on LinkedIn. I’d be happy to implement it!
Acknowledgments
I want to take a moment to say a big THANK YOU to the people below:
- Oracle Database Upgrades and Migrations team:
- Alex Zaballa: for the discussions, brainstorming, suggestions about layout, usability and recommendations on how to build the tool.
- Rodrigo Jorge: for the discussions, brainstorming, suggestions about layout, usability and recommendations on how to build the tool.
Hope it helps and you enjoy the tool!
Peace,
Vinicius
Disclaimer:
This tool is not supported or developed by Oracle Corporation, nor by my employer, Accenture. It is a personal project intended to help the Oracle community. Usage is free — no fees or costs. Always test before using. Feedback is welcome.
