Update Grid Infrastructure Using Fleet Maintenance #JoelKallmanDay

-

Step 3 - Patching in the Deep. (Grid Patching using Fleet Maintenance)

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 grid infrastructure from 19.16 to 19.20. As there are more than 20 servers to patch, we will use fleet patching. First i have patched a 2 node cluster grid infrastructure by using out of place ( OOP ) patching  methodology through gridSetup.sh in silent mode in Step 1 - Patch Me If You Can (Grid OOP Patching)

    Now i will use patched grid homes to create a gold image for fleet patching of all grid homes.

Some useful references:


Update Grid Infrastructure using Cloud Control

    First create a location on Software Library in EMCC. We will use it as a destination for storing gold image. 
      *&span>Provisioning and Patching > Sofware Library 
* Name : Gold Image Profiles
* Description : Gold Image Profiles for Database and Grid Infrastructure
* Name : 19c
* Description : Version 19c Images

   We will create a response file, but at first we need the manual oop(out of place) patched grid home (target name) to refer in response file.

    Here is the content of the response file.

    It is time to create grid gold image.
    
    Now we will subscribe to this gold image for oracluster2. (This is the cluster we want to patch with fleet maintenance)(This step can also be done from GUI/BUI, EMCC 13.5 RU16).

    We will deploy gold image to target cluster. (This step can also be done from GUI/BUI, EMCC 13.5).

    We have skipped CVU (Cluster Verification Utility) checks, otherwise it is detecting the processes running from current old/grid homes. Also if you encounter an error like "Reason: Error retrieving input stream for file entry 'setup_stageArea_RACP.pl'".  Just reimport  sofware library metadata with the command: emcli reimport_swlib_metadata.

    It is time to switch to new grid home in rolling manner. With the below command, cluster will be updated to gold image version and the Grid Infrastructure targets running from old Oracle grid home will be migrated to NEWLY Patched Oracle grid home node by node with no downtime.

    All grid/cluster patching has been completed as easy as taking candy from a baby. Listener.ora and glogin.sql files are copied to new grid home.  We will just update all our shell scripts, .bashrc etc files to refer new grid home. Also after patching completed, in EMCC - under Add targets  menu, rediscover your updated hosts and promote newly discovered targets associated with the new grid home.
    
    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