Infrastructure at your Service

Introduction

19c will soon be available for your ODAs. But you may not be ready. Here is how to patch your ODA from 18.3 to 18.8, the very latest 18c release. This patch has here been applied on X7-2M hardware.

Download the patch files

Patch number is 30518425. This patch is composed of 2 zipfiles you will copy on your ODA.

Check free space on disk

Applying a patch requires several GB, please check free space on /, /opt and /u01 before starting. These filesystems should have about 20% free space. If needed, /u01 and /opt filesystems can be extended online, based on Linux VG/LV. For example if you need an additional 20GB in /opt:

lvextend -L +20G /dev/mapper/VolGroupSys-LogVolOpt
resize2fs /dev/mapper/VolGroupSys-LogVolOpt

Check processes

It’s also recommended to check what’s running on your ODA before patching, you’ll do the same check after patching is complete:

ps -ef | grep pmon
oracle     863     1  0 Feb22 ?        00:00:06 ora_pmon_UBTMUR
oracle    8014     1  0  2019 ?        00:03:06 ora_pmon_TSTDEV
oracle    9901     1  0 Feb22 ?        00:00:11 ora_pmon_DEVUT2
grid     14044     1  0  2019 ?        00:22:39 asm_pmon_+ASM1
grid     17118     1  0  2019 ?        00:18:18 apx_pmon_+APX1
oracle   22087 19584  0 11:02 pts/0    00:00:00 grep pmon

ps -ef | grep tnslsnr
grid     15667     1  0  2019 ?        01:43:48 /u01/app/18.0.0.0/grid/bin/tnslsnr ASMNET1LSNR_ASM -no_crs_notify -inherit
grid     15720     1  0  2019 ?        02:26:42 /u01/app/18.0.0.0/grid/bin/tnslsnr LISTENER -no_crs_notify -inherit
oracle   22269 19584  0 11:02 pts/0    00:00:00 grep tnslsnr
grid     26884     1  0  2019 ?        00:01:24 /u01/app/18.0.0.0/grid/bin/tnslsnr LISTENER1523 -inherit
grid     94369     1  0  2019 ?        00:01:16 /u01/app/18.0.0.0/grid/bin/tnslsnr LISTENER1522 -inherit

Check current version in use

Start to check current version on all components:

odacli describe-component

System Version
---------------
18.3.0.0.0

Component                                Installed Version    Available Version
---------------------------------------- -------------------- --------------------
OAK                                       18.3.0.0.0            up-to-date
GI                                        18.3.0.0.180717       up-to-date
DB {
[ OraDB12201_home1 ]                      12.2.0.1.180717       up-to-date
[ OraDB11204_home1 ]                      11.2.0.4.180717       up-to-date
}
DCSAGENT                                  18.3.0.0.0            up-to-date
ILOM                                      4.0.4.21.r126801      up-to-date
BIOS                                      41040100              up-to-date
OS                                        6.10                  up-to-date
FIRMWARECONTROLLER                        QDV1RE14              up-to-date
FIRMWAREDISK                              0121                  0112

Some components version could be higher than those available at time of previous patch/deployment. In this example, starting version is 18.3.0.0.0: this version as a straight path to 18.8.0.0.0.

Duration of the patch may vary depending on the components to be patched. I strongly advise you to check the target version for each component in the documentation, for an ODA X7-2M here is the url.

For this ODA, and compared to currently deployed components versions, no OS update is embedded in the patch, meaning that it will shortened the patching time.

Preparing the patch

Copy the patch files on disk in a temp directory. Then unzip the files and update the repository:

cd /u01/tmp
unzip p30518425_188000_Linux-x86-64_1of2.zip
unzip p30518425_188000_Linux-x86-64_1of2.zip
rm -rf p30518425_188000_Linux-x86-64_*
odacli update-repository -f /u01/tmp/oda-sm-18.8.0.0.0-200124-server1of2.zip
odacli update-repository -f /u01/tmp/oda-sm-18.8.0.0.0-200124-server2of2.zip
odacli list-jobs | head -n 3;  odacli list-jobs | tail -n 3
ID                                       Description                      Created                             Status
---------------------------------------- -------------------------------- ----------------------------------- ---------
7127c3ca-8fb9-4ac9-810d-b7e1aa0e32c5     Repository Update                February 24, 2020 01:13:53 PM CET   Success
5e294f03-3fa8-48ae-b193-219659bec4de     Repository Update                February 24, 2020 01:14:09 PM CET   Success

Patch the dcs components

Patching the dcs components is easy. Now it’s a 3-step process:

/opt/oracle/dcs/bin/odacli update-dcsagent -v 18.8.0.0.0
/opt/oracle/dcs/bin/odacli update-dcsadmin -v 18.8.0.0.0
/opt/oracle/dcs/bin/odacli update-dcscomponents -v 18.8.0.0.0
{
  "jobId" : "f36c44b3-4eb8-4a43-a323-d28a9836de74",
  "status" : "Success",
  "message" : null,
  "reports" : null,
  "createTimestamp" : "February 24, 2020 14:04:01 PM CET",
  "description" : "Job completed and is not part of Agent job list",
  "updatedTime" : "February 24, 2020 14:04:01 PM CET"
}
odacli list-jobs | tail -n 3
b8d474ab-3b5e-4860-a9f4-3d73497d6d4c     DcsAgent patching                                                           February 24, 2020 1:58:54 PM CET    Success
286b36a2-c1fc-48b9-8c99-197e24b6c8ba     DcsAdmin patching                                                           February 24, 2020 2:01:52 PM CET    Success

Note that the latest update is not a job in the list.

Check proposed version to patch to

Now the describe-component should propose the real available versions bundled in the patch:

odacli describe-component
System Version
---------------
18.8.0.0.0
 
Component                                Installed Version    Available Version
---------------------------------------- -------------------- --------------------
OAK                                       18.3.0.0.0            18.8.0.0.0
GI                                        18.3.0.0.180717       18.8.0.0.191015
DB {
[ OraDB12201_home1 ]                      12.2.0.1.180717       12.2.0.1.191015
[ OraDB11204_home1 ]                      11.2.0.4.180717       11.2.0.4.191015
}
DCSAGENT                                  18.8.0.0.0            up-to-date
ILOM                                      4.0.4.21.r126801      4.0.4.47.r131913
BIOS                                      41040100              41060600
OS                                        6.10                  up-to-date
FIRMWARECONTROLLER                        QDV1RE14              qdv1rf30
FIRMWAREDISK                              0121                  up-to-date

OS and firmwaredisk components don’t need to be patched.

Pre-patching report

Let’s check if patching has the green light:

odacli create-prepatchreport -s -v 18.8.0.0.0
odacli describe-prepatchreport -i 12d61cda-1cef-40b9-ad7d-8e087007da23

 
Patch pre-check report
------------------------------------------------------------------------
                 Job ID:  12d61cda-1cef-40b9-ad7d-8e087007da23
            Description:  Patch pre-checks for [OS, ILOM, GI]
                 Status:  SUCCESS
                Created:  February 24, 2020 2:05:41 PM CET
                 Result:  All pre-checks succeeded
 

 
Node Name
---------------
dbiora07
 
Pre-Check                      Status   Comments
------------------------------ -------- --------------------------------------
__OS__
Validate supported versions     Success   Validated minimum supported versions
Validate patching tag           Success   Validated patching tag: 18.8.0.0.0
Is patch location available     Success   Patch location is available
Verify OS patch                 Success   There are no packages available for
                                          an update
 
__ILOM__
Validate supported versions     Success   Validated minimum supported versions
Validate patching tag           Success   Validated patching tag: 18.8.0.0.0
Is patch location available     Success   Patch location is available
Checking Ilom patch Version     Success   Successfully verified the versions
Patch location validation       Success   Successfully validated location
 
__GI__
Validate supported GI versions  Success   Validated minimum supported versions
Validate available space        Success   Validated free space under /u01
Verify DB Home versions         Success   Verified DB Home versions
Validate patching locks         Success   Validated patching locks

ODA is ready.

Patching infrastructure and GI

First the Trace File Analyzer should be stopped, then the update-server could be run:

/etc/init.d/init.tfa stop
odacli update-server -v 18.8.0.0.0
odacli describe-job -i 4d6aab0e-18c4-4bbd-8c16-a39c8a14f992
 Job details
----------------------------------------------------------------
                     ID:  4d6aab0e-18c4-4bbd-8c16-a39c8a14f992
            Description:  Server Patching
                 Status:  Success
                Created:  February 24, 2020 2:15:32 PM CET
                Message:


Task Name                                Start Time                          End Time                            Status
---------------------------------------- ----------------------------------- ----------------------------------- ----------
Patch location validation                February 24, 2020 2:15:39 PM CET    February 24, 2020 2:15:39 PM CET    Success
dcs-controller upgrade                   February 24, 2020 2:15:39 PM CET    February 24, 2020 2:15:42 PM CET    Success
Patch location validation                February 24, 2020 2:15:42 PM CET    February 24, 2020 2:15:42 PM CET    Success
dcs-cli upgrade                          February 24, 2020 2:15:42 PM CET    February 24, 2020 2:15:43 PM CET    Success
Creating repositories using yum          February 24, 2020 2:15:43 PM CET    February 24, 2020 2:15:53 PM CET    Success
Creating repositories using yum          February 24, 2020 2:15:53 PM CET    February 24, 2020 2:15:53 PM CET    Success
Creating repositories using yum          February 24, 2020 2:15:53 PM CET    February 24, 2020 2:15:53 PM CET    Success
Creating repositories using yum          February 24, 2020 2:15:53 PM CET    February 24, 2020 2:15:53 PM CET    Success
Creating repositories using yum          February 24, 2020 2:15:53 PM CET    February 24, 2020 2:15:53 PM CET    Success
Creating repositories using yum          February 24, 2020 2:15:53 PM CET    February 24, 2020 2:15:53 PM CET    Success
Creating repositories using yum          February 24, 2020 2:15:53 PM CET    February 24, 2020 2:15:53 PM CET    Success
Updating YumPluginVersionLock rpm        February 24, 2020 2:15:53 PM CET    February 24, 2020 2:15:54 PM CET    Success
Applying OS Patches                      February 24, 2020 2:15:54 PM CET    February 24, 2020 2:26:44 PM CET    Success
Creating repositories using yum          February 24, 2020 2:26:44 PM CET    February 24, 2020 2:26:45 PM CET    Success
Applying HMP Patches                     February 24, 2020 2:26:45 PM CET    February 24, 2020 2:27:35 PM CET    Success
Patch location validation                February 24, 2020 2:27:35 PM CET    February 24, 2020 2:27:35 PM CET    Success
oda-hw-mgmt upgrade                      February 24, 2020 2:27:35 PM CET    February 24, 2020 2:28:04 PM CET    Success
OSS Patching                             February 24, 2020 2:28:04 PM CET    February 24, 2020 2:28:04 PM CET    Success
Applying Firmware Disk Patches           February 24, 2020 2:28:05 PM CET    February 24, 2020 2:28:11 PM CET    Success
Applying Firmware Expander Patches       February 24, 2020 2:28:11 PM CET    February 24, 2020 2:28:16 PM CET    Success
Applying Firmware Controller Patches     February 24, 2020 2:28:16 PM CET    February 24, 2020 2:29:02 PM CET    Success
Checking Ilom patch Version              February 24, 2020 2:29:03 PM CET    February 24, 2020 2:29:05 PM CET    Success
Patch location validation                February 24, 2020 2:29:05 PM CET    February 24, 2020 2:29:06 PM CET    Success
Save password in Wallet                  February 24, 2020 2:29:07 PM CET    February 24, 2020 2:29:07 PM CET    Success
Apply Ilom patch                         February 24, 2020 2:29:07 PM CET    February 24, 2020 2:42:35 PM CET    Success
Copying Flash Bios to Temp location      February 24, 2020 2:42:35 PM CET    February 24, 2020 2:42:35 PM CET    Success
Starting the clusterware                 February 24, 2020 2:42:35 PM CET    February 24, 2020 2:44:53 PM CET    Success
clusterware patch verification           February 24, 2020 2:55:27 PM CET    February 24, 2020 2:55:47 PM CET    Success
Patch location validation                February 24, 2020 2:55:47 PM CET    February 24, 2020 2:56:37 PM CET    Success
Opatch updation                          February 24, 2020 2:57:32 PM CET    February 24, 2020 2:57:36 PM CET    Success
Patch conflict check                     February 24, 2020 2:57:36 PM CET    February 24, 2020 2:58:27 PM CET    Success
clusterware upgrade                      February 24, 2020 2:58:27 PM CET    February 24, 2020 3:21:18 PM CET    Success
Updating GiHome version                  February 24, 2020 3:21:18 PM CET    February 24, 2020 3:21:53 PM CET    Success
Update System version                    February 24, 2020 3:22:26 PM CET    February 24, 2020 3:22:27 PM CET    Success
preRebootNode Actions                    February 24, 2020 3:22:27 PM CET    February 24, 2020 3:23:14 PM CET    Success
Reboot Ilom                              February 24, 2020 3:23:14 PM CET    February 24, 2020 3:23:14 PM CET    Success

Server reboots 5 minutes after the patch ends. On my X7-2M this operation lasted 1h15.

Let’s check the component’s versions:

odacli describe-component
System Version
---------------
18.8.0.0.0
 
Component                                Installed Version    Available Version
---------------------------------------- -------------------- --------------------
OAK                                       18.8.0.0.0            up-to-date
GI                                        18.8.0.0.191015       up-to-date
DB {
[ OraDB12201_home1 ]                      12.2.0.1.180717       12.2.0.1.191015
[ OraDB11204_home1 ]                      11.2.0.4.180717       11.2.0.4.191015
}
DCSAGENT                                  18.8.0.0.0            up-to-date
ILOM                                      4.0.4.21.r126801      4.0.4.47.r131913
BIOS                                      41040100              41060600
OS                                        6.10                  up-to-date
FIRMWARECONTROLLER                        QDV1RE14              qdv1rf30
FIRMWAREDISK                              0121                  up-to-date

Neither ILOM nor BIOS have been updated. This is a bug.

Solve the ILOM and BIOS not patched

An additional procedure is needed (provided by MOS), crsctl needs to be stopped then BIOS patched manually:

/u01/app/18.0.0.0/grid/bin/crsctl stop crs
ipmiflash -v write ILOM-4_0_4_47_r131913-ORACLE_SERVER_X7-2.pkg force script config delaybios warning=0

Versions should now be fine:

odacli describe-component

System Version
---------------
18.8.0.0.0

Component                                Installed Version    Available Version
---------------------------------------- -------------------- --------------------
OAK                                       18.8.0.0.0            up-to-date
GI                                        18.8.0.0.191015       up-to-date
DB {
[ OraDB12201_home1 ]                      12.2.0.1.180717       12.2.0.1.191015
[ OraDB11204_home1 ]                      11.2.0.4.180717       11.2.0.4.191015
}
DCSAGENT                                  18.8.0.0.0            up-to-date
ILOM                                      4.0.4.47.r131913      up-to-date
BIOS                                      41060600              up-to-date
OS                                        6.10                  up-to-date
FIRMWARECONTROLLER                        QDV1RE14              qdv1rf30
FIRMWAREDISK                              0121                  up-to-date

Patching the storage

Patching of the storage is much faster than patching the “server”:

odacli update-storage -v 18.8.0.0.0

odacli describe-job -i a97deb0d-2e0b-42d9-8b56-33af68e23f15
 
Job details
----------------------------------------------------------------
                     ID:  a97deb0d-2e0b-42d9-8b56-33af68e23f15
            Description:  Storage Firmware Patching
                 Status:  Success
                Created:  February 24, 2020 3:33:10 PM CET
                Message:
 
Task Name                                Start Time                          End Time                            Status
---------------------------------------- ----------------------------------- ----------------------------------- ----------
Applying Firmware Disk Patches           February 24, 2020 3:33:11 PM CET    February 24, 2020 3:33:19 PM CET    Success
Applying Firmware Controller Patches     February 24, 2020 3:33:19 PM CET    February 24, 2020 3:40:53 PM CET    Success
preRebootNode Actions                    February 24, 2020 3:40:53 PM CET    February 24, 2020 3:40:54 PM CET    Success
Reboot Ilom                              February 24, 2020 3:40:54 PM CET    February 24, 2020 3:40:54 PM CET    Success

Another auto reboot is done after this step.

Patching the dbhomes

Time for patching the dbhomes depends on the number of dbhomes and number of databases. In this example, 2 dbhomes are deployed:

odacli list-dbhomes


ID                                       Name                 DB Version                               Home Location                                 Status                 
---------------------------------------- -------------------- ---------------------------------------- --------------------------------------------- -------                 ---
8a2f98f8-2010-4d26-a4b3-2bd5ad8f0b98     OraDB12201_home1     12.2.0.1.180717                          /u01/app/oracle/product/12.2.0.1/dbhome_1     Configured
8a494efd-e745-4fe9-ace7-2369a36924ff     OraDB11204_home1     11.2.0.4.180717                          /u01/app/oracle/product/11.2.0.4/dbhome_1     Configured

odacli update-dbhome -i 8a494efd-e745-4fe9-ace7-2369a36924ff -v 18.8.0.0.0 
odacli describe-job -i 7c5589d7-564a-4d8b-b69a-1dc50

Job details
----------------------------------------------------------------
                     ID:  7c5589d7-564a-4d8b-b69a-1dc50162a4c6
            Description:  DB Home Patching: Home Id is 8a2f98f8-2010-4d26-a4b3-2bd5ad8f0b98
                 Status:  Success
                Created:  February 25, 2020 9:18:49 AM CET
                Message:  WARNING::Failed to run the datapatch as db TSTY_RP7 is not running##WARNING::Failed to run the datapatch as db EXPY_RP7 is not registered with
clusterware##WARNING::Failed to run datapatch on db DEVM12_RP7Failed to run Utlrp script##WARNING::Failed t
 
Task Name                                Start Time                          End Time                            Status
---------------------------------------- ----------------------------------- ----------------------------------- ----------
Validating dbHome available space        February 25, 2020 9:18:59 AM CET    February 25, 2020 9:18:59 AM CET    Success
clusterware patch verification           February 25, 2020 9:19:21 AM CET    February 25, 2020 9:19:31 AM CET    Success
Patch location validation                February 25, 2020 9:19:31 AM CET    February 25, 2020 9:19:31 AM CET    Success
Opatch updation                          February 25, 2020 9:19:31 AM CET    February 25, 2020 9:19:32 AM CET    Success
Patch conflict check                     February 25, 2020 9:19:32 AM CET    February 25, 2020 9:19:32 AM CET    Success
db upgrade                               February 25, 2020 9:19:32 AM CET    February 25, 2020 9:19:32 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:19:32 AM CET    February 25, 2020 9:19:35 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:19:35 AM CET    February 25, 2020 9:20:18 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:20:18 AM CET    February 25, 2020 9:20:55 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:20:55 AM CET    February 25, 2020 9:20:55 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:20:55 AM CET    February 25, 2020 9:20:56 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:20:56 AM CET    February 25, 2020 9:21:33 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:21:33 AM CET    February 25, 2020 9:21:40 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:21:40 AM CET    February 25, 2020 9:21:46 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:21:46 AM CET    February 25, 2020 9:21:57 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:21:57 AM CET    February 25, 2020 9:22:32 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:22:32 AM CET    February 25, 2020 9:23:12 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:23:12 AM CET    February 25, 2020 9:23:53 AM CET    Success
Update System version                    February 25, 2020 9:23:53 AM CET    February 25, 2020 9:23:53 AM CET    Success
updating the Database version            February 25, 2020 9:24:03 AM CET    February 25, 2020 9:24:08 AM CET    Success
updating the Database version            February 25, 2020 9:24:08 AM CET    February 25, 2020 9:24:14 AM CET    Success
updating the Database version            February 25, 2020 9:24:14 AM CET    February 25, 2020 9:24:18 AM CET    Success
updating the Database version            February 25, 2020 9:24:18 AM CET    February 25, 2020 9:24:23 AM CET    Success
updating the Database version            February 25, 2020 9:24:23 AM CET    February 25, 2020 9:24:28 AM CET    Success
updating the Database version            February 25, 2020 9:24:28 AM CET    February 25, 2020 9:24:33 AM CET    Success
updating the Database version            February 25, 2020 9:24:33 AM CET    February 25, 2020 9:24:38 AM CET    Success
updating the Database version            February 25, 2020 9:24:38 AM CET    February 25, 2020 9:24:45 AM CET    Success
updating the Database version            February 25, 2020 9:24:45 AM CET    February 25, 2020 9:24:51 AM CET    Success
updating the Database version            February 25, 2020 9:24:51 AM CET    February 25, 2020 9:24:56 AM CET    Success
updating the Database version            February 25, 2020 9:24:56 AM CET    February 25, 2020 9:25:02 AM CET    Success
updating the Database version            February 25, 2020 9:25:02 AM CET    February 25, 2020 9:25:08 AM CET    Success

odacli update-dbhome -i 8a2f98f8-2010-4d26-a4b3-2bd5ad8f0b98 -v 18.8.0.0.0 
odacli describe-job -i fbed248a-1d0d-4972-afd2-8b43ac8ad514

 Job details
----------------------------------------------------------------
                     ID:  fbed248a-1d0d-4972-afd2-8b43ac8ad514
            Description:  DB Home Patching: Home Id is 8a494efd-e745-4fe9-ace7-2369a36924ff
                 Status:  Success
                Created:  February 25, 2020 9:39:54 AM CET
                Message:  WARNING::Failed to run the datapatch as db CUR7_RP7 is not registered with clusterware##WARNING::Failed to run the datapatch as db SRS7_RP7 is not registered with clusterware##WARNING::Failed to run the datapatch as db CUX7_RP7 is not regi
 
Task Name                                Start Time                          End Time                            Status
---------------------------------------- ----------------------------------- ----------------------------------- ----------
Validating dbHome available space        February 25, 2020 9:40:05 AM CET    February 25, 2020 9:40:05 AM CET    Success
clusterware patch verification           February 25, 2020 9:40:07 AM CET    February 25, 2020 9:40:12 AM CET    Success
Patch location validation                February 25, 2020 9:40:12 AM CET    February 25, 2020 9:40:17 AM CET    Success
Opatch updation                          February 25, 2020 9:40:49 AM CET    February 25, 2020 9:40:51 AM CET    Success
Patch conflict check                     February 25, 2020 9:40:51 AM CET    February 25, 2020 9:41:07 AM CET    Success
db upgrade                               February 25, 2020 9:41:07 AM CET    February 25, 2020 9:43:27 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:43:27 AM CET    February 25, 2020 9:43:27 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:43:27 AM CET    February 25, 2020 9:43:27 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:43:27 AM CET    February 25, 2020 9:43:27 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:43:27 AM CET    February 25, 2020 9:43:28 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:43:28 AM CET    February 25, 2020 9:43:28 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:43:28 AM CET    February 25, 2020 9:43:28 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:43:28 AM CET    February 25, 2020 9:43:28 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:43:28 AM CET    February 25, 2020 9:43:29 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:43:29 AM CET    February 25, 2020 9:43:29 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:43:29 AM CET    February 25, 2020 9:43:29 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:43:29 AM CET    February 25, 2020 9:43:29 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:43:29 AM CET    February 25, 2020 9:43:30 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:43:30 AM CET    February 25, 2020 9:43:30 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:43:30 AM CET    February 25, 2020 9:43:30 AM CET    Success
SqlPatch upgrade                         February 25, 2020 9:43:30 AM CET    February 25, 2020 9:43:33 AM CET    Success
Update System version                    February 25, 2020 9:43:33 AM CET    February 25, 2020 9:43:33 AM CET    Success
updating the Database version            February 25, 2020 9:43:35 AM CET    February 25, 2020 9:43:37 AM CET    Success
updating the Database version            February 25, 2020 9:43:37 AM CET    February 25, 2020 9:43:39 AM CET    Success
updating the Database version            February 25, 2020 9:43:39 AM CET    February 25, 2020 9:43:42 AM CET    Success
updating the Database version            February 25, 2020 9:43:42 AM CET    February 25, 2020 9:43:45 AM CET    Success
updating the Database version            February 25, 2020 9:43:45 AM CET    February 25, 2020 9:43:48 AM CET    Success
updating the Database version            February 25, 2020 9:43:48 AM CET    February 25, 2020 9:43:50 AM CET    Success
updating the Database version            February 25, 2020 9:43:50 AM CET    February 25, 2020 9:43:52 AM CET    Success
updating the Database version            February 25, 2020 9:43:52 AM CET    February 25, 2020 9:43:54 AM CET    Success
updating the Database version            February 25, 2020 9:43:54 AM CET    February 25, 2020 9:43:56 AM CET    Success
updating the Database version            February 25, 2020 9:43:56 AM CET    February 25, 2020 9:43:58 AM CET    Success
updating the Database version            February 25, 2020 9:43:58 AM CET    February 25, 2020 9:44:01 AM CET    Success
updating the Database version            February 25, 2020 9:44:01 AM CET    February 25, 2020 9:44:04 AM CET    Success
updating the Database version            February 25, 2020 9:44:04 AM CET    February 25, 2020 9:44:06 AM CET    Success
updating the Database version            February 25, 2020 9:44:06 AM CET    February 25, 2020 9:44:08 AM CET    Success
updating the Database version            February 25, 2020 9:44:08 AM CET    February 25, 2020 9:44:10 AM CET    Success

odacli list-dbhomes
ID                                       Name                 DB Version                               Home Location                                 Status
---------------------------------------- -------------------- ---------------------------------------- --------------------------------------------- ----------
8a2f98f8-2010-4d26-a4b3-2bd5ad8f0b98     OraDB12201_home1     12.2.0.1.191015                          /u01/app/oracle/product/12.2.0.1/dbhome_1     Configured
8a494efd-e745-4fe9-ace7-2369a36924ff     OraDB11204_home1     11.2.0.4.191015                          /u01/app/oracle/product/11.2.0.4/dbhome_1     Configured

The 2 dbhomes are updated. Failures on Sqlpatch upgrade should be analyzed, but remember that standby databases cannot be upgraded as their dictionary is not available.

Let’s check on primary 12c (and later) databases if everything is OK:

su – oracle
. oraenv <<< DEVC12
sqlplus / as sysdba
set serverout on
exec dbms_qopatch.get_sqlpatch_status;
...
Patch Id : 28163133
        Action : APPLY
        Action Time : 27-MAY-2019 16:02:11
        Description : DATABASE JUL 2018 RELEASE UPDATE 12.2.0.1.180717
        Logfile :
/u01/app/oracle/cfgtoollogs/sqlpatch/28163133/22313390/28163133_apply_DEVC12_201
9May27_16_02_00.log
        Status : SUCCESS
 
Patch Id : 30138470
        Action : APPLY
        Action Time : 24-FEB-2020 17:10:35
        Description : DATABASE OCT 2019 RELEASE UPDATE 12.2.0.1.191015
        Logfile :
/u01/app/oracle/cfgtoollogs/sqlpatch/30138470/23136382/30138470_apply_DEVC12_202
0Feb24_17_09_56.log
        Status : SUCCESS

PL/SQL procedure successfully completed.
 exit

Let’s check if everything is also OK on 11g databases;

su – oracle
. oraenv <<< DEVC11
sqlplus / as sysdba
select * from dba_registry_history;
ACTION_TIME
---------------------------------------------------------------------------
ACTION                         NAMESPACE
------------------------------ ------------------------------
VERSION                                ID BUNDLE_SERIES
------------------------------ ---------- ------------------------------
COMMENTS
--------------------------------------------------------------------------------
...
17-MAY-19 11.18.48.769476 AM
APPLY                          SERVER
11.2.0.4                           180717 PSU
PSU 11.2.0.4.180717
 
25-FEB-20 09.57.40.969359 AM
APPLY                          SERVER
11.2.0.4                           191015 PSU
PSU 11.2.0.4.191015
 Patch Id : 26635944
        Action : APPLY
        Action Time : 21-NOV-2017 15:53:49
        Description : OJVM RELEASE UPDATE: 12.2.0.1.171017 (26635944)
        Logfile :
/u01/app/oracle/cfgtoollogs/sqlpatch/26635944/21607957/26635944_apply_G100652_CD
BROOT_2017Nov21_15_53_12.log
        Status : SUCCESS

Optional: update the dbclones

If you now create a new dbhome, it will be based on the previous dbclone. So you may need to provision a new dbclone to avoid that. If you need the latest dbclone for 18c, patch number is 27604558:

cd /u01/tmp
unzip p27604558_188000_Linux-x86-64.zip
odacli update-repository -f /u01/tmp/odacli-dcs-18.8.0.0.0-191226-DB-18.8.0.0.zip

Now you are able to create a new dbhome from this dbclone:

odacli create-dbhome -v 18.8.0.0.191015
odacli list-dbhomes
ID                                       Name                 DB Version                               Home Location                                 Status
---------------------------------------- -------------------- ---------------------------------------- --------------------------------------------- ----------
8a2f98f8-2010-4d26-a4b3-2bd5ad8f0b98     OraDB12201_home1     12.2.0.1.191015                          /u01/app/oracle/product/12.2.0.1/dbhome_1     Configured
8a494efd-e745-4fe9-ace7-2369a36924ff     OraDB11204_home1     11.2.0.4.191015                          /u01/app/oracle/product/11.2.0.4/dbhome_1     Configured
395451e5-12b9-4851-b331-dd3e650e6d11     OraDB18000_home1     18.8.0.0.191015                          /u01/app/oracle/product/18.0.0.0/dbhome_1     Configured

Final checks

Let’s get the final versions:

odacli describe-component
System Version
---------------
18.8.0.0.0
 
Component                                Installed Version    Available Version
---------------------------------------- -------------------- --------------------
OAK                                       18.8.0.0.0            up-to-date
GI                                        18.8.0.0.191015       up-to-date
DB {
[ OraDB12201_home1 ]                      12.2.0.1.191015       up-to-date
[ OraDB11204_home1 ]                      11.2.0.4.191015       up-to-date
[ OraDB18000_home1 ]                      18.8.0.0.191015       up-to-date
}
DCSAGENT                                  18.8.0.0.0            up-to-date
ILOM                                      4.0.4.47.r131913      up-to-date
BIOS                                      41060600              up-to-date
OS                                        6.10                  up-to-date
FIRMWARECONTROLLER                        QDV1RF30              up-to-date
FIRMWAREDISK                              0121                  up-to-date

Looks good. Please also check the running processes and compare them to the initial status.

Cleanse the old patches

It’s now possible to cleanse the old patches, they will never be used again. For this ODA, history was:

Deploy = 12.2.1.2.0 => Patch 12.2.1.4.0 => Patch 18.3.0.0.0 => Patch 18.8.0.0.0

Check the filesystems usage before and after cleansing:

df -h /opt
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroupSys-LogVolOpt
                       79G   61G   15G  81% /opt

df -h /u01
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroupSys-LogVolU01
                      197G  116G   71G  63% /u01

odacli cleanup-patchrepo -cl -comp db,gi -v 12.2.1.2.0
odacli cleanup-patchrepo -cl -comp db,gi -v 12.2.1.4.0
odacli cleanup-patchrepo -cl -comp db,gi -v 18.3.0.0.0


df -h /opt
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroupSys-LogVolOpt
                       79G   39G   37G  51% /opt
df -h /u01
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroupSys-LogVolU01
                      197G  116G   71G  63% /u01

Conclusion

Your ODA is now in the latest 18c version. Future upgrade will be more serious, OS will jump to Linux 7 and Oracle stack to 19.6. Old X4-2 ODAs will be stuck to 18.8. And remember that 19.5 is not a production release.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Jérôme Dubar
Jérôme Dubar

Consultant