RE: Question on database fleet maintenance patching

From: <>
Date: Mon, 30 Dec 2019 06:49:53 -0800
Message-ID: <019701d5bf20$6baa76d0$42ff6470$>

Completely agree that a well tested automation patching is better than humans performing the patching.    

From: <> On Behalf Of Noveljic Nenad Sent: Monday, December 30, 2019 1:35 AM
To:; Subject: RE: Question on database fleet maintenance patching  

A mature automation checks everything at the end and gives the unambiguous feedback if the patching was successful. I even went so far to automatically perform the rollback on failure. The risk of “going awry” can be massively reduced by testing the process on a production clone.  

Patching (and even upgrade) process is kicked off by the application people per self-service. A DBA is on-call to cover the worst case scenario, which, by the way, has never happened. As Mladen mentioned, there were some issues after Oracle changed their patching process, but there are workarounds (see, for example, ). These are kind of issues that should be discovered on test databases.  

I’d definitely trust this well-tested automation more than a human, especially when patching lots of databases.  

Best regards,  


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.  

Please consider the environment before printing this e-mail.

Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.

Important Notice
This message is intended only for the individual named. It may contain confidential or privileged information. If you are not the named addressee you should in particular not disseminate, distribute, modify or copy this e-mail. Please notify the sender immediately by e-mail, if you have received this message by mistake and delete it from your system. Without prejudice to any contractual agreements between you and us which shall prevail in any case, we take it as your authorization to correspond with you by e-mail if you send us messages by e-mail. However, we reserve the right not to execute orders and instructions transmitted by e-mail at any time and without further explanation. E-mail transmission may not be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also processing of incoming e-mails cannot be guaranteed. All liability of Vontobel Holding Ltd. and any of its affiliates (hereinafter collectively referred to as "Vontobel Group") for any damages resulting from e-mail use is excluded. You are advised that urgent and time sensitive messages should not be sent by e-mail and if verification is required please request a printed version. Please note that all e-mail communications to and from the Vontobel Group are subject to electronic storage and review by Vontobel Group. Unless stated to the contrary and without prejudice to any contractual agreements between you and Vontobel Group which shall prevail in any case, e-mail-communication is for informational purposes only and is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. The legal basis for the processing of your personal data is the legitimate interest to develop a commercial relationship with you, as well as your consent to forward you commercial communications. You can exercise, at any time and under the terms established under current regulation, your rights. If you prefer not to receive any further communications, please contact your client relationship manager if you are a client of Vontobel Group or notify the sender. Please note for an exact reference to the affected group entity the corporate e-mail signature. For further information about data privacy at Vontobel Group please consult <> .

Received on Mon Dec 30 2019 - 15:49:53 CET

Original text of this message