Oracle 19c RAC Database Out of Place Patching

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

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)

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 with 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 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 on option with the below command before switching to new home.

Now it is time to switch new homes. Just before switch;

• Do not forget to update all your shell scripts, .bashrc etc files to refer new db home. 
• Copy tnsnames.ora and sqlnet.ora from old db home to new db home.
• Copy glogin.sql from old db home to new db home.
• Make sure that your wallet path is not dependent to 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 new home node by node. Below is a sample.

Edited on 10th May 2025:
When patching with out-of-place patching, some directory objects (dba_directories) managed internally by Oracle are not properly configured to the new Oracle Home. Although an enhancement request was submitted (Enh 35988020 – DATAPATCH SHOULD INVOKE UTLFIXDIRS.SQL), as of the 19.26 RU, it is still not available in the patch inventory.

Therefore, each time you patch using the out-of-place method, you should manually run utlfixdirs.sql to correct these directory references. Refer to DBMS_OPTIM_BUNDLE and Out-Of-Place Patching blog post of Mike Dietrich for more information.

SQL> @$ORACLE_HOME/rdbms/admin/utlfixdirs.sql

Container: CDB$ROOT

Current  ORACLE_HOME: /u01/app/oracle/product/19.26/dbhome_1
Original ORACLE_HOME: /u01/app/oracle/product/19.3/dbhome

DATA_PUMP_DIR
...OLD: /u01/app/oracle/product/19.3/dbhome/rdbms/log/
...NEW: /u01/app/oracle/product/19.26/dbhome_1/rdbms/log/
ORACLE_HOME
...OLD: /u01/app/oracle/product/19.3/dbhome
...NEW: /u01/app/oracle/product/19.26/dbhome_1
ORACLE_OCM_CONFIG_DIR
...OLD: /u01/app/oracle/product/19.3/dbhome/ccr/state
...NEW: /u01/app/oracle/product/19.26/dbhome_1/ccr/state
ORACLE_OCM_CONFIG_DIR2
...OLD: /u01/app/oracle/product/19.3/dbhome/ccr/state
...NEW: /u01/app/oracle/product/19.26/dbhome_1/ccr/state
SDO_DIR_ADMIN
...OLD: /u01/app/oracle/product/19.3/dbhome/md/admin
...NEW: /u01/app/oracle/product/19.26/dbhome_1/md/admin
XMLDIR
...OLD: /u01/app/oracle/product/19.3/dbhome/rdbms/xml
...NEW: /u01/app/oracle/product/19.26/dbhome_1/rdbms/xml
XSDDIR
...OLD: /u01/app/oracle/product/19.3/dbhome/rdbms/xml/schema
...NEW: /u01/app/oracle/product/19.26/dbhome_1/rdbms/xml/schema

PL/SQL procedure successfully completed.

Additionally, if you encounter an issue with the DBMS_OPTIM_BUNDLE package – such as the following error: ORA-20002: Error stat’ing file bundlefcp_DBBP.xml
You can recreate the package by executing the dbmsoptim.sql and prvtoptim.plb scripts located in the Oracle Home’s rdbms/admin directory.

SQL> execute dbms_optim_bundle.getbugsforbundle;
BEGIN dbms_optim_bundle.getbugsforbundle; END;

*
ERROR at line 1:
ORA-20002: ORA-20002: ORA-20002: Error stat'ing file bundlefcp_DBBP.xml,
getDocument Error, getBugsforBundle Error
ORA-06512: at "SYS.DBMS_OPTIM_BUNDLE", line 2087
ORA-06512: at line 1


SQL> @?/rdbms/admin/dbmsoptim.sql

Session altered.


Package created.

No errors.

Session altered.

SQL> @?/rdbms/admin/prvtoptim.plb

Session altered.


Type created.


Type created.


PL/SQL procedure successfully completed.


Package body created.

No errors.

Session altered.

Hope it helps.

See you on Step 3 – Patching in the Deep. (Oracle Grid Patching using Fleet Maintenance).