Automate Oracle Database Patching with Ansible Playbooks – 19.24

INTRO : Automate Database Patching NOW !

Last week, I have attended the Virtual Classroom #21: One-Button Patching with AutoUpgrade. AutoUpgrade tool’s long-awaited Patching feature has been introduced with version 24.7. While still in Version 1 and not yet feature complete, this new capability promises to enhance the database release update process significantly.

For now, In Version 1 it only supports;

• Single instance homes
• Database homes only
• On Linux only
• Only Oracle Database 19c supported

There is still a way to go, as many other requirements need to be met, such as Data Guard, RAC, Grid, and the same relink operation with the previous home. However, the Database Upgrade Team is working behind the scenes to address these requirements. More information is available on blog post “How to Patch Oracle Database With One Command” by Daniel Overby Hansen.

Until that time, Ansible playbooks are the way to go.

Ansible Playbooks for Automating Oracle Database Patching

My new Ansible playbooks for Oracle Grid and Database patching are now ready for the 19.24 Release Update, including the October MRP, Data Pump Bundle Patch, OJVM and much more.

I prefer to go with a Follower Strategy and choose to follow Release Updates one version behind (n-1) the latest one, and apply the latest MRP (Monthly Release Update) on top. Ansible playbooks will help simplify and automate the patching process.

All Playbooks are available on my Github Repository.

Before rolling up your sleeves, be sure to check my Database Patching Tips notes; I believe you’ll learn something new .

Ansible is not a big deal for an Oracle DBA.

How you can patch your Oracle Grid Infrastructure is explained step by step on my blog post. “Oracle Grid Patching by Using Ansible“. You will just use latest playbooks and It is done.

After patching the Oracle Grid, You may refer to “Oracle Database Patching by Using Ansible” for the Oracle Database Homes.

For large environments with lots of database servers to patch, Automating database patching is not an option, it is a must. It reduces human error and ensures consistency across environments. By streamlining the patching process, organizations can quickly apply critical updates and security fixes, minimizing downtime and vulnerability to threats. Automation also frees up valuable time for database administrators, allowing them to focus on other important tasks. Moreover, it helps maintain compliance with regulatory requirements by ensuring timely updates.

Another approach is using Fleet Patching and Provisioning. FPP actually targets large environments, such as Exadata or cloud setups. I am using both Ansible and FPP efficently. However, it’s clear that AutoUpgrade’s One Button Patching has the potential to be a game changer in the near future, simplifying and streamlining the process even further

Hope it helps.