Hi everyone,
Hope you’re doing well.
Today is a special day for me. I’m really happy to announce the release of the BETA version of my tool: AutoUpgrade-Composer
Context
I’ve been working with Oracle Database for more than 20 years, and I’m part of the Oracle community — sharing knowledge on my blog since 2010 (when I was nominated ACE for the first time) and speaking at technical conferences since 2011.
I’ve always been lucky to work on teams with amazing professionals. Some of them are well known in the community for creating tools. That has always impressed me.
Recently, I had the chance to see the release of a new tool: CPAT Composer, developed by Marcus Doeringer. It is really awesome and easy to use.
This gave me the idea to start working on a new tool.
Why AutoUpgrade-Composer?
AutoUpgrade is a tool developed by the team led by Mike Dietrich. When the tool was released, back on April 2019, the goal was to make the Upgrade of databases easier. They nailed it! Upgrading databases became an easier and automated task. You can read about the release of AutoUpgrade on Mike Dietrich’s blog: https://mikedietrichde.com/2019/04/29/the-new-autoupgrade-utility-in-oracle-19c/
Since its release, AutoUpgrade has become more powerful with every build. Oracle added Patching capability in 2022 and made a great enhancement in 2024.
Long story short: AutoUpgrade is now the main tool for Upgrade, Patching, and (maybe) Migrations.
Every AutoUpgrade execution requires a Configuration File. With all these capabilities, there’s a large number of possible parameters and scenarios that can be added to the Configuration File — which can be confusing if you’re new to this world.
With that in mind, and inspired by the amazing job of my namesake, I created AutoUpgrade-Composer. The goal is to help you create your AutoUpgrade Configuration files in minutes!
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 has some “sections”.
On the top of the page, we have the version. I will always try to follow the same version as the AutoUpgrade tool.
With that said, every time a new version of the AutoUpgrade tool is launched, I will work on identifying changes in their changelog — such as the addition or removal of parameters, capabilities/features, or bug fixes that require changing any parameter.
As of now, you are seeing v.25.3-b40. The “b” stands for BETA, and the 40 means all changed I did so far. Once the STABLE version is released, you will no longer see the “b”.
In the screenshot below, we have the option to toggle to light theme (or to dark theme if you are seeing the tool on light theme).
You also can Load a Configuration previously generated by this tool.
You can specify a Global Log Directory for AutoUpgrade.
In the screenshot below, we have the Database Configurations for Patch operations:
You have the first tab: patch1, you can add more patch operations (for more databases) if you want by clicking the (+) button. If you add one by mistake, you can remove it by clicking the “x” on the tab. You cannot remove the first tab.
Then you can specify:
- SID: the SID of the DB being patched;
- SID Log Dir: the log directory to be used by the patchN (patch1) operation.
- Source Home: the source Oracle Home where DB is currently running.
- Target Home: the new Oracle Home where DB will run after patched.
- Microsoft Windows: this switch is used to show specific parameters when running the operation on Microsoft Windows.
In the screenshot below, we have the Generated Config:
You can COPY it to use in your environment or download the file.
In the screenshot below, we have the instructions on how to run AutoUpgrade:
The values above can change depending on the mode you choose.
If you choose to download patches, you may see an additional section showing how to configure the AutoUpgrade Keystore.
If you’re running on Microsoft Windows, you may have an additional section explaining how to load the Windows Credentials.
In the last screenshot, you have the references:
On this screenshot you have the following references:
- Using AutoUpgrade for Oracle Database Upgrades: link to official documentation about AutoUpgrade.
- AutoUpgrade Patching: link to official documentation about AutoUpgrade Patching capability.
- AutoUpgrade Tool Reference Note (Doc ID 2485457.1): link to My Oracle Support (Metalink) reference note for AutoUpgrade Tool. You can download the latest version of AutoUpgrade on this link.
- Oracle Database Upgrades and Migrations YouTube Channel: the official Youtube channel for Oracle Database Upgrades and Migrations team.
- Then, we have the link to Product Managers’ blogs/sites:
Why is on BETA?
I’m working hard on this tool to help you create your configuration files for AutoUpgrade easily. I still have several parameters to consider adding on the tool to make your life easier.
Also, I’m working on the Upgrade part, which I’m planning to release by mid-June, when the tool will be in the STABLE version – no longer BETA.
Anyway, I really appreciate any feedback you have about the tool, any parameter you think I might be missing for now. You can comment on this post, or you can DM me on LinkedIn.
One more thing: I’m validating everything in my lab. But always test before changing or deploying in Production!
Will All Options Be Explained?
Definitely! Stay tuned on my blog, I will prepare several blog posts showing how to perform the operations, exploring different parameters and scenarios!
Acknowledgments
I’d like to dedicate this section of the blog post to say a big THANK YOU to the people listed below:
- Community:
- Maicon Carneiro: for testing and helping me out finding issues, suggesting layout and usability changes;
- Cesar Carvalho: for testing and helping me out finding issues.
- André Renato: for sending Configuration Files used on real-world scenarios and suggesting some changes.
- Mario Barduchi: for sending Configuration Files used on real-world scenarios and suggesting some changes.
- Oracle Database Upgrades and Migrations team:
- Alex Zaballa: for the discussions, brainstorming and recommendations on how to build the tool.
- Rodrigo Jorge: for the discussions, brainstorming and recommendations on how to build the tool.
So, stay tuned for the next releases of the tool. Soon, we’ll have the Upgrade section available. Also, stay tuned on my blog, I’ll start exploring all the possible options we might have.
Hope it helps!
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.
Obrigado pela iniciativa.
Thank you Alysson!