AutoUpgrade stores your MOS credentials and other secrets in its own keystore.
It’s convenient to create an auto-login keystore. Otherwise, AutoUpgrade prompts for the keystore password every time it needs a secret. But the auto-login keystore only works on the computer where it was created.
Unless you create a shared keystore. Let’s see how.
Shared Keystore
- If you have an existing AutoUpgrade auto-login keystore, remove it:
rm /home/oracle/autoupgrade-patching/keystore/cwallet.sso*- Only remove the auto-login keystore files.
- They are prefixed
cwallet.sso. - The keystore location is defined by the config file entry
global.keystore.
- Start the AutoUpgrade password console:
java -jar autoupgrade.jar -config get-patches.cfg -patch -load_password - AutoUpgrade prompts for the keystore password:
Processing config file ... Loading AutoUpgrade Patching keystore Enter wallet password: - Create a shared keystore using the
savecommand:MOS> save Select auto-login mode for the AutoUpgrade Patching keystore [YES|NO|SHARED]: SHARED- Enter
SHAREDwhen prompted for the auto-login keystore mode.
- Enter
- Exit the password console:
MOS> exit - You can now use the auto-login keystore on other computers.
Security
A shared keystore is a secure way to store your credentials, although it is not as secure as a regular keystore.
Be sure to protect your keystores, shared or not, by having restrictive file permissions and perhaps even file system auditing.
That’s It
Automation is key these days, and this enhancement makes AutoUpgrade fit better with that ambition.
If there’s anything we can do to make AutoUpgrade even better for automation, drop a comment below.
Happy patching!
Databases Are Fun 
Hi Daniel, I just tried setting up a shared keystore as described.I’m using the latest available version of autoupgrade 26.5.260807.When saving the MOS credentials, the prompt did offers the answers “[YES|NO]” for autologin.However, I was able to enter the value SHARED succesfully.
Now, I tried to download the recommended set of patches using the follwing config:
global.global_log_dir=C:\oracle\autoupgrade-patching\log global.keystore=C:\oracle\autoupgrade-patching\keystore global.folder=C:\oracle\autoupgrade\patches patch1.target_version=19patch1.patch=RECOMMENDED
patch1.platform=WINDOWS.X64
I get this:
Es liegen Bedingungen vor, die eine erfolgreiche Ausführung von AutoUpgrade Patching verhindern Oracle-Patchdateien werden heruntergeladen Download query failed *Failed to retrieve ARU release ID needed for download Multiple ARU (Automated Release Update) release IDs were returned ([60000000010115002133, 600000000252372]) when only one was expected from the Pattern: {1}
I successively changed the patch parameter to RU, OJVM, DPBP, I narrowed it to DPBP causing the error mentioned above.
Best regards,Michael
LikeLike
Hi,
It’s odd that “SHARED” is missing as an option in the password prompt. I’m unable to reproduce it – the “SHARED” option shows when I use it (on Mac and Linux). I’ll find a colleague with Windows and give it a try.
I need to look into why AutoUpgrade finds duplicate patches when looking for DPBP. For now, you can use this patch specification instead:
patch1.patch=OPATCH,RU,OJVM,CSPU,39796431
39796431 is the patch number for the Data Pump bundle patch on Windows.
Regards,
Daniel
LikeLike
Hi Daniel,
Thanks for the quick reply!
Download worked. I wasn’t able to find the Data Pump bundle patch in MOS.
Regards,
Michael
LikeLike