Yesterday at DOAG conference I announced it already in our Upgrade and Migration Round Table – and just a few hours later my team mates made the New AutoUpgrade version 20211115 (Nov 2021) available for download.
How to download AutoUpgrade?
Always download the most recent version of AutoUpgrade via MOS Note: 2485457.1 – AutoUpgrade Tool.
Just click on this link in the MOS Note:
Why do you need a new version?
A good number of issues being logged to us via blogs, tweets, SRs and eMails can be solved with the current version of AutoUpgrade. So please check your installed version:
$ java -jar autoupgrade.jar -version build.version 21.2.210721 build.hash 680914c build.date 2021/07/21 11:14:54 build.max_target_version 21 build.supported_target_versions 12.2,18,19,21 build.type production
In this case, I will need to download the newer version since the build.date is older than the newest one on MOS. Simply copy the downloaded version into your $ORACLE_HOME/rdbms/admin directory and overwrite the previous version.
What’s new in the November 2021 version?
At the bottom of the MOS note you’ll find the change.log file listing all the enhancements, changes and fixes. In this case it lists:
build.hash 081e3f7 build.version 21.3.211115 build.date 2021/11/15 11:57:54 build.max_target_version 21 build.supported_target_versions 12.2,18,19,21 build.type production 23 bug fixes since v21.2 release Tag: V21.3 Description: This is the release for 21.3 MOS Change in behavior: AUPG-2538 - Remove check AWR_DBIDS_PRESENT as problem is no longer valid AUPG-2559 - Set REMOTE_LOGIN_PASSWORDFILE = NONE during upgrade AUPG-2579 - Validate java version 8 is used when executing AutoUpgrade Ehancements: AUPG-2581 - Added config option manage_standbys_clause to override standby=none BUG-33418493 - Make sure CDB$ROOT is in normal mode when processing Pdbs Added checks: AUPG-2520 - Added noncdbtopdb KEYSTORE_CONFLICK check to validate wallet location Bugs: AUPG-2411 - Zip utility failing with NullPointerException error AUPG-2426 - Incorrect message logged for user defined post upgrade action AUPG-2435 - srvctl remove database -force switch is different for 18.104.22.168 AUPG-2436 - Autoupgrade was not copying the timezone files to all the RAC nodes AUPG-2444 - RAC ssh commands fails due to an unexpected banner configured AUPG-2450 - preupgrade postfixups option should not check for plug-in violations AUPG-2465 - Exception raised when finding an unknown cause for plug-in violations AUPG-2473 - Additional logging added for customer support AUPG-2478 - Ignore setting protection on files that have been deleted AUPG-2509 - Exception on TARGET_CDB_COMPATIBILITY check if target Pdb name exists AUPG-2521 - Windows TNS_ADMIN was being set to the wrong value AUPG-2535 - Unable to skip a check AUPG-2540 - NO_KEYSTORE_FILES check fails due to lack of sysdba privilege in asmcmd AUPG-2541 - MIN_RECOVERY_AREA_SIZE check raises a NullPointerException if parameter not present in the during_upgrade pfile AUPG-2552 - Warning shown while querying the invalid object count AUPG-2587 - Intermittent issue between mandatory_upgrade_changes/rlp_param check AUPG-2585 - db_flash_cache_size can have multiple values SR 3-27598368991
Time to download the newest version of AutoUpgrade via MOS Note: 2485457.1!
Hey Mike, thanks for the great work. We are using latest script, and having issue that upgrade fails because not all instances are up in the cluster. Its saying cannot proceed because other instances are down. This is how we run these database by design, only one instance is running and others are disabled in crs. Is there a way how to override and pass this validations pls? Cheers Ed
you please need to collect all logs with:
java -jar autoupgrade.jar -config yourconfig.cfg -zip
and upload it to an SR.
Does this version support upgrading a 12.2 PDB to 19c PDB on ExaCC Gen1 platform (all RAC, all TDE, lots of engineered settings)? (Opened SR nine days ago, no response so far.) autoupgrade immediately failed with “ORA-46680: master keys of the container database must be exported on autoupgrade of PDB”
please see my mates’ Daniel blog posts:
PS: Early next year a new version of AU will take care on all these steps automatically – we will “regress” it in late January before releasing it.
You have a great site, which I’ve only stumbled across a bit over 3 months ago.
Following your advice to use autoupgrade.jar (20211115 version) for any upgrade I’ve been attempting to upgrade a 22.214.171.124.0 Non-CDB to 19c (19.13) Non-CDB (on Solaris) and its been failing. I have an SR open on it (for a couple of weeks), but I’m hoping you might have some insight into what might be the issue.
Run autoupgrade.jar in analyze mode, no issues works great. Run autoupgrade.jar in deploy mode everything works fine up through shutting down the 126.96.36.199.0 database. But when it attempts to actually start the upgrade, by starting the database with the 19c binaries it fails with the following errors:
SP2-0640: Not connected
UPG-1401#Opening Database idev in upgrade mode failed
ORA-12560: TNS:protocol adapter error
Any insight would be appreciated. And thanks in advance.
can you share the SR number with me please?
Are you using separate OS owners for the Oracle homes?
Or is the listener running out from a home with a different owner?
I would need to see the autoupgrade logs (java -jar autoupgrade.jar -config yourconfig.cfg -zip).
Did you upload them to the SR already?
happy new year!
I am wondering the golden gate 188.8.131.52 still functioning correctly after upgrade only source database or it has to be both source and target database?
it should – just make sure that your OGG version is certified with the database release you are upgrading to.
Otherwise you may need to upgrade your OGG version as well.
thank you Mike! how can i restore command console (upg>) after timeout while doing upgrade? i would like to invoke it conveniently after the session timeout.
first you can modify the timeouts if you need to.
And you can get back to the command console with the same command you used to call AutoUPgrade:
what is the different between autoupgrade tools?I know that the new tool contains fixs and implement! I am using the old one working fine but the new download as oracle recommended ” to get the new autoupgrade tool ” did not work.
see the change.log at the bottom of the MOS note where you download it – this lists all differences.
does autoupgrade tool works with multiple instances on window? do i have to treat each instance as individual database? so in the config file i have to specify each instance individually?
it works with Multiple Instances on Win as well.
Hi Mike ,
how do I configure the auto upgrade parameter for multiple instances ?any special configuration for multiple instance or just like single instance one?
very simple: use different prefixes such as:
Hi Mike, Can autoupgrade be used w/o the source binary $ORACLE_HOME (e.g. 12c)? If for example, we restore a copy of the 12c datafiles from backup to a new machine and perform the upgrade on the new machine ? This is done to keep a working source database in case of issues during the upgrade cutover.
yes of course – please see here:
Hi Mike, started looking into upgrading from 184.108.40.206.0 to 19 and so far I’ve done the ‘analyze’ part which looks good. However, I feel completely stupid as I can’t find out where the new version 19 comes from. Does autoupgrade.jar install the new version 19c? Do I have to install this version up-front? I don’t see this described anywhere in plain english. Thanks for any help.
you must install 19c and patch it upfront – see here:
And use the most recent RU please: