It’s time for our next Virtual Classroom Seminar 21: One-Button Patching – and how it will make the life easier for every DBA with AutoUpgrade. So, this seminar is clearly for you. And we plan to constrain it this time to only 60 minutes with a heavy focus on demos.
Photo by Michael Lock on Unsplash
Date, Time and Registration
Episode 21 of our Virtual Classroom Series will happen on:
- October 24, 2024 – 14:00h CET (5:30pm IST – 1:00pm BST – 8am EDT)
Registration Link
Why do YOU have to attend?
Oracle AutoUpgrade has been patching databases for quite some time. Many of you use it already with great success such as a large airline or a leading cloud provider.
Are you ready for the next step in Oracle Database patching?
In this release, Oracle AutoUpgrade also downloads the patches from My Oracle Support or your own patch inventory and builds your Oracle homes according to our best practices. You don’t even need to know individual patch numbers; just specify what you want: The latest Release Update, OJVM, Data Pump Bundle Patch? AutoUpgrade will find and download it for you.
Patching is now even easier. And the best thing: This works with Oracle Database 19c already.
We introduced and launched it at Oracle Cloud World 2024. And in case you weren’t there, this is your chance now.
Tune into our Virtual Classroom Seminar 21 to learn about the next step, One-Button Patching. The Oracle Database Upgrade, Cloud Migration and Patching product management team will show you how easy it works, and you can go ahead and test it right away.
Zero marketing, just tech facts.
Further Links and Information
- Virtual Classroom Seminars
- VC20: Oracle 23ai and Multitenant – Part 2
- VC19: Oracle 23ai and Multitenant – Part 1
–Mike
Hey Mike, I wasn’t able to attend today — had some urgent DBA work to do for a client. Do you have a recording link you can share from today’s Webinar?
Hi Ernst,
will be public on Oct 31, 14:00h CET on https://MikeDietrichDE.com/videos
Slides are already there.
Cheers,
Mike
Hey Mike,
I was trying to patch a database using AutoUpgrade for testing and encountered the following error:
“The sid parameter for prefix patch1 includes a value that is not supported or is not in the required format.”
My database name is something like ABC_Q. Does AutoUpgrade have issues with these types of database names?
Hi Abhi,
SID =/= database name.
You need to specify your SID, not the database’s name please. What is your SID, and be aware that on Unix upper/lowercase matters, too.
Cheers,
Mike
Hi Mike,
We have with great enthusiasm followed the “One-Button Patching” presentation of yesterday.
It was really, really very interesting to see.
Up to now we did almost the same thing with OOP, using Ansible playbooks, but these can be greatly simplified with these developments of Autoupgrade.
So, very promising.
But now the “but” 😉
Ofcourse we immediately tested this new functionality, and unfortunately it errored out.
In runs into an INS-35341 error, caused by the fact that our Linux group for Oracle users is “dbaprd” for production, “dbat01” for test & and “dbad01” for dev systems.
It looks like AutoUpgrade uses the $ORACLE_HOME/rdbms/lib/config.c of the newly installed ORACLE_HOME to determine the used group i.o. looking into the same file of the existing active ORACLE_HOME.
On our active ORACLE_HOME the groups are set correctly for the test system:
.Ldba_string: .string “dbat01”
.Loper_string: .string “dbat01”
.Lasm_string: .string “”
.Lbkp_string: .string “dbat01”
.Ldgd_string: .string “dbat01”
.Lkmt_string: .string “dbat01”
.Lrac_string: .string “dbat01”
On the new installed release this file has some default values:
.Ldba_string: .string “dba”
.Loper_string: .string “oper”
.Lasm_string: .string “”
.Lbkp_string: .string “backupdba”
.Ldgd_string: .string “dgdba”
.Lkmt_string: .string “kmdba”
.Lrac_string: .string “racdba”
Which match the error seen in the logfile:
[FATAL] [INS-35341] The installation user is not a member of the following groups: [dba, backupdba, dgdba, kmdba, racdba]
CAUSE: The installation user account must be a member of all groups required for installation.
How can we overcome this?
Thank you again for the great presentation.
Thanks – we are taking care on it since you dropped me an email in parallel (which works best).
Cheers,
Mike
Hi,
any updates on [FATAL] [INS-35341]
We are working on it, Nael – coming.
Cheers,
Mike
Hi Mike
Are there any updates on [FATAL] [INS-35341]? Also struggling with the same issue.
Hi Will,
we are going to release a new version the coming days which is supposed to fix this.
Cheers,
Mike