As you may have read, we launched the new AutoUpgrade 26.6 a week ago which has so many amazing enhancements such as the EM Patches download. But there may be two other hurdles to jump over, and one of them may prevent you from downloading patches. Let me share a quick fix for download issues with AutoUpgrade 26.6

Photo by Ante Samarzija on Unsplash
Weak file permissions will prevent download
I have been trapped by this as well.
A change was required by the platforms we are downloading from. With AutoUpgrade 26.6 we had to enable a new keystore file permission protection. If you populate a new keystore, all is fine out of the box, and nothing needs to be done.
java -jar autoupgrade.jar -config gp.cfg -patch -load_password Processing config file ... Starting AutoUpgrade Patching Password Loader - Type help for available options Creating new AutoUpgrade Patching keystore - Password required Enter password: Enter password again: AutoUpgrade Patching keystore was successfully created MOS> add -user hugo.meier@acme.com Enter your secret/Password: Re-enter your secret/Password: MOS> save Select auto-login mode for the AutoUpgrade Patching keystore [YES|NO|SHARED]: yes MOS> exit
So, when you start from scratch, all is good.
But what if you have already used the AutoUpgrade download before, and you are not refreshing your keystore since your MOS password hasn’t been changed? Then please read on.
When the download does not work anymore?
When you have an existing keystore for AutoUpgrade, you may not be able to download patches anymore unless you do a change on the file permissions. This will happen:
AutoUpgrade Patching 26.6.260925 launched with default internal options Processing config file ... Loading AutoUpgrade Patching keystore AutoUpgrade Patching keystore is loaded Unable to connect to the Oracle Update Advisor service using the provided credentials *No messages received from the Oracle Update Advisor service*
Nothing will be downloaded in this case. And the reason is not obvious – file permissions. From AutoUpgrade 26.6 onwards, this may be seen.
Or you may see this errror:
Oracle Update Advisor service - Connection Failure *Tag mismatch!*
Which is just a different failure for the same root cause.
You can fix it quickly.
Fix the file permissions on the keystore for existing AutoUpgrade keystores using:
cd keystore chmod 600 *
The directory contents then look like this:
-rw------- 1 mdietric staff 0 Oct 6 12:03 ewallet.p12.lck -rw------- 1 mdietric staff 4774 Oct 6 12:03 ewallet.p12 -rw------- 1 mdietric staff 0 Oct 6 12:03 cwallet.sso.lck -rw------- 1 mdietric staff 4886 Oct 6 12:03 cwallet.sso
This is “600” on the files. And this is fine.
You could also do this from one directory level above:
chmod -R 700 ./keystore
Both work fine.
And afterwards, the download works again.
Take special care if you embedded this in automation.
Password length for the keystore
When you reset your protection password for the AutoUpgrade keystore, or when you do it the first time now, then you will see this WARNING:
java -jar autoupgrade.jar -config gp.cfg -patch -load_password Processing config file ... Starting AutoUpgrade Patching Password Loader - Type help for available options Creating new AutoUpgrade Patching keystore - Password required Enter password: Warning: For security reasons, passwords must have at least 16 characters. Enter password again: AutoUpgrade Patching keystore was successfully created
It is actually a warning, not an error. And you still could use your 8-character password to protect the keystore. Still, you will see this above message. In the above window, I typed in my 10-character password, and it worked as well. Of course, longer passwords are better one could argue. We don’t enforce it but we warn you.
Further Links and Information
- DOH: Download EM Patches with AutoUpgrade
- DOH: Security changes in AutoUpgrade 26.6
- New AutoUpgrade Version 26.6 is available
–Mike
Hi Mike, thanks for sharing this. I’m already using AutoUpgrade’s patch-download feature, and my keystore was created with an older AutoUpgrade version. My Oracle environment is on Windows.
Do you know if this AutoUpgrade 26.6 keystore permission issue affects Windows as well, or is it specific to Linux/Unix environments?
Kind regards,
jorge batista
Hi Jorge,
I don’t think that the same happens on Windows since OS file system permissions are handled differently.
Cheers,
Mike
Hi Mike,
Thanks for confirming. I tested AutoUpgrade 26.6 on my Windows environment and encountered no issues with the existing keystore or patch downloads.
Thanks again for your help!
Cheers,
Jorge
Thank you – happy to hear that!
Mike