Database Out of Place Patching Through runInstaller #JoelKallmanDay

-

Step 2 - Patch My Breath Away. (DB OOP Patching)

I’ve moved my blog from https://insanedba.blogspot.com to https://dincosman.com Please update your bookmarks and follow/subscribe at the new address for all the latest updates and content. More up-to-date content of this post may be available there.

I will patch all my database servers database software from 19.16 to 19.20. As there are more than 20 servers to patch, we will use fleet patching. First, I will patch a 2-node cluster database homes by using out-of-place (OOP) patching methodology through runInstaller in silent mode.
Later, I will use patched database homes to create a gold image for fleet patching of all database homes.

Setup List:
 * Database 19.3 Base Release (LINUX.X64_193000_db_home.zip)
 * Database 19.20 RU (p35320081_190000_Linux-x86-64.zip)
 * Grid 19.20 August MRP involves DB August MRP. (p35656840_1920000DBRU_Linux-x86-64.zip)
 * OJVM 19.20 Patch (p35354406_190000_Linux-x86-64.zip)
 * DPBP 19.20 Datapump Bundle Patch (p35512813_1920000DBRU_Generic.zip)
 * Spatial 19.20 Bundle Patch (p35602358_1920000DBRU_Linux-x86-64.zip)
 * DB 555.1 Recommended One-off (p35372179_1920000DBRU_Linux-x86-64.zip)
 * DB 555.1 Recommended One-off (p30787757_1920000DBRU_Linux-x86-64.zip)
 * Opatch Latest Version (p6880880_122010_Linux-x86-64.zip)

Database Out of Place Patching


Preparation Phase:


We replaced scp binary with the below commands not to hit "[FATAL] [INS-06006] Passwordless SSH connectivity not set up between the following node(s):" error related to Openssh_8 shipped with Oracle Linux 8 according to INS-06006 GI RunInstaller Fails If OpenSSH Is Upgraded to 8.x (Doc ID 2555697.1)

Deploying new software to all nodes with a single command. (DBRU + DB MRP + OJVM + DPBP + Spatial Bundle + One-offs)

Now, new database home software is ready to go. We will just execute root.sh scripts on all nodes.

As we make use of unified auditing on all databases, we will relink unified auditing with the on option with the below command before switching to the new home.

Now it is time to switch to the new homes. Just before the switch;
    * Do not forget to update all your shell scripts, .bashrc etc files to refer to the new db home.
    * Copy tnsnames.ora and sqlnet.ora from the old db home to the new db home.
    * Copy glogin.sqlfrom the old db home to the new db home.
   * Make sure that your wallet path is not dependent on your old db home, if it is, just copy to a different path and update your sqlnet.ora.
Final step, modify your database homes with srvctl command and startup your databases from the new home node by node. Below is a sample.

Hope it helps.

Comments

Post a Comment

Popular posts from this blog

Oracle Grid Release Update by using Ansible Playbooks

-
Image
Ansible is a friend in need and a friend indeed for DBAs. I’ve moved my blog from https://insanedba.blogspot.com to https://dincosman.com Please update your bookmarks and follow/subscribe at the new address for all the latest updates and content. More up-to-date content of this post may be available there. In this blog post, I will mention about Redhat Ansible and show how you can patch your grid infrastructure by using it. Ansible is an open source, command-line IT automation software application written in Python. It can configure systems, deploy software, and orchestrate advanced workflows to support application deployment, system updates, and more. Ansible's main strengths are simplicity and ease of use. It is a little bit similar to dcli commands in Exadata environments, but much more powerful as you may run playbooks which consist of different tasks. Ansible stands out from other configuration management tools because it doesn't need agents installed on target host...
Read more

Oracle Database Release Update by Using Ansible Playbooks

-
Image
Ansible to Rule Them All I’ve moved my blog from https://insanedba.blogspot.com to https://dincosman.com Please update your bookmarks and follow/subscribe at the new address for all the latest updates and content. More up-to-date content of this post may be available there. In the previous post " Oracle Grid Software Patching by using Ansible Playbooks" , I mentioned how Ansible orchestration can be used to make Oracle Grid Software Patching a cleaner and simpler process. Now I will also patch database software using Ansible Playbooks. In this post,  I will use the blt01 host as the ansible host. The target environment is a two-node RAC database (gns01, gns02). I will patch the grid software to 19.22 using the out-of-place methodology with no downtime.  Although there are lots of useful blog posts about how you may use Ansible for automating tasks, there is not much about complete Oracle database software patching.  Ansible is simply installed by running "y...
Read more

How to Upgrade PostgreSQL, PostGIS and Patroni in Air-Gapped Environments

-
Image
Upgrade Your PostgreSQL Database: Major Steps and Minor Touches I’ve moved my blog from https://insanedba.blogspot.com to https://dincosman.com Please update your bookmarks and follow/subscribe at the new address for all the latest updates and content. More up-to-date content of this post may be available there. In this blog post, I will show how a complete PostgreSQL environment major update can be done. Minor upgrades are not a tough task; they are no different from a standard Linux package upgrade. As my production environment serves in an airgapped-environment, I will complete all the major upgrades with no internet connection. I've downloaded all the required whl and .rpm packages before the upgrade. Before starting, a short description of major and minor PostgreSQL upgrades is provided below: Major Upgrade: Upgrading PostgreSQL to a new major version, such as moving from 10 to 11 or 12 to 13. Major upgrades bring significa...
Read more