RE: Question on database fleet maintenance patching

From: <>
Date: Tue, 24 Dec 2019 08:55:42 -0800
Message-ID: <506501d5ba7b$032110a0$096331e0$>

What errors were you seeing with datapactch as my patching of each quarter with 12.2 I had no failures.

If you did see failures in testing of the patch you should have adjusted your Ansible code.

Automation like anything else is not static. Someone will always have to read the Oracle readmes and adjust the code if Oracle makes changes like they do every 3 yrs or so.      

From: <> On Behalf Of Mladen Gogala Sent: Tuesday, December 24, 2019 2:59 AM To:
Cc:; Subject: Re: Question on database fleet maintenance patching  

I have written an ansible playbook but that doesn't help when the "datapatch" utility bombs. And that happens regularly with 12.2

Ansible is the same type of utility as chef or puppet.  

On Mon, Dec 23, 2019, 20:45 < <> > wrote:

I have written Puppet code to fully patch Oracle databases with all steps being automated.

The whole point of automation is to make it a completely repeatable process and eliminate the need for humans for patching. There is much more valuable work for the humans than patching.

Patching takes about 15 minutes along with be able to patch multiple systems at a time so a singular human is much more efficient.    

From: <> < <> > On Behalf Of Clay Jackson (cjackson) Sent: Monday, December 23, 2019 4:33 PM
To: <> Subject: RE: Question on database fleet maintenance patching  

Well, I suppose you could use some sort of automation/orchestration tool; there are lots out there, from DBMS_JOB to Puppet/Chef and lots of others.  

But, do you REALLY want to trust patching your databases that presumably contain data of greater than zero value to some automated process? I’ve seen too many patch processes “go awry” to want to trust automation.  

That said, of course you SHOULD have some sort of script that you run repeatedly (avoid typos or sequencing errors); but, automation as in “unattended” would not be my choice.  

Just my $.02…..    

Clay Jackson

Database Solutions Sales Engineer


office 949-754-1203 mobile 425-802-9603  

From: <> < <> > On Behalf Of Tharmarajah, Sam Sent: Monday, December 23, 2019 2:24 PM
To: <> Subject: Question on database fleet maintenance patching  

CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.  

Hi All,  

We have been asked to reduce the number of personals involved during our quarterly database patching. I was looking into using the fleet maintenance. Upon doing a POC, I notice the process of deploying the software job, awaits for manual step run and confirmation at three different points (new oracle home dir creation, pre -root run section and post run section), in spite of providing the normal and privileged credentials . We are wondering if there is a way to have these steps be run as part of the process automatically, instead of running manually.  


./emcli db_software_maintenance -performOperation -name="deploy195" -purpose=DEPLOY_DB_SOFTWARE -target_type=oracle_database <> -normal_credential=FLEETMGR_STANDARD:SYSMAN -privilege_credential=FLEETMGR_PRIVILEGED:SYSMAN -input_file="data:/oracle/local/config/xyz.inp"  

The .inp file



The databases we are trying patch is 19.x

We have EM 13.3c  

Our advance thanks for all your thoughts and suggestions.  



Received on Tue Dec 24 2019 - 17:55:42 CET

Original text of this message