ODA upgrade
12.1.2.12 to 18.3.0.0
There are two options to upgrade ODA to the latest version.
1. re-image system with the latest binary -
re-imaging ODA is required to re-create the whole structure of your environment and it’s complicated
2. Upgrade from 12.1.2.12 - 18.3.0.0.
I have tried to cover as many issues as possible to make this upgrade smooth. Okay, let's try to get ready for the challenge.
As a first step, we will gather all the required details about the ODA
environment. It’s very important to understand the environment. Then can
only get ready with patching plan.
This is just the start of moving to 19.9.0.0. We found this below mention
plan from looking at the oracle documents link.
Eg: server version, hardware version and its bare metal or virtual
environment.
Section 1: Gather ODA server information
Find the ODA hardware version.
######### Find ODA version: [root@ecl-oda-DOM0-0 ~]# ipmitool sunoem cli 'show System' | grep model model = ODA X5-2 component_model = ORACLE SERVER X5-2 [root@ecl-oda-DOM0-0 ~]# [root@ecl-oda-DOM0-1 ~]# ps -ef | grep pmon root 5577 4433 0 13:57 pts/2 00:00:00 grep pmon [root@ecl-oda-DOM0-1 ~]# ipmitool sunoem cli 'show System' | grep model model = ODA X5-2 component_model = ORACLE SERVER X5-2 [root@ecl-oda-DOM0-1 ~] Find Server version: [root@ecl-odabase-0 delshare]# oakcli show server Power State : On Open Problems : 0 Model : ODA X5-2 Type : Rack Mount Part Number : 33765810+1+1 Serial Number : 1535NMF006 Primary OS : Not Available ILOM Address : 10.11.99.202 ILOM MAC Address : 00:10:E0:8D:5E:AC Description : Oracle Database Appliance X5-2 1535NMF006 Locator Light : Off Actual Power Consumption : 288 watts Ambient Temperature : 15.750 degree C Open Problems Report : System is healthy[root@ecl-odabase-0 delshare]# oakcli show server Power State : On Open Problems : 0 Model : ODA X5-2 Type : Rack Mount Part Number : 33765810+1+1 Serial Number : 1535NMF006 Primary OS : Not Available ILOM Address : 10.11.99.202 ILOM MAC Address : 00:10:E0:8D:5E:AC Description : Oracle Database Appliance X5-2 1535NMF006 Locator Light : Off Actual Power Consumption : 288 watts Ambient Temperature : 15.750 degree C Open Problems Report : System is healthy Find hardware version: [root@ecl-odabase-0 delshare]# oakcli show env_hw VM-ODA_BASE ODA X5-2 [root@ecl-odabase-0 delshare]# Check for running vm’s and repositories : If the environment is virtualized you will need to note down the vm names and repository names before patching. These repositories are ACFS mount points , which stores allocated to store virtual machine and virtual disks. ======================================= Check the running VMS and respository ======================================= [root@ecl-odabase-0 PATCH]# oakcli show vm NAME NODENUM MEMORY VCPU STATE REPOSITORY kali_server 0 4196M 2 ONLINE kali_test qualyssrv 0 4196M 2 ONLINE qualys [root@ecl-odabase-0 PATCH]# [root@ecl-odabase-0 PATCH]# oakcli show repo NAME TYPE NODENUM FREE SPACE STATE SIZE kali_test shared 0 94.78% ONLINE 512000.0M kali_test shared 1 94.78% ONLINE 512000.0M odarepo1 local 0 N/A N/A N/A odarepo2 local 1 N/A N/A N/A qualys shared 0 98.44% ONLINE 204800.0M qualys shared 1 98.44% ONLINE 204800.0M vmdata shared 0 99.99% ONLINE 4068352.0M vmdata shared 1 N/A UNKNOWN N/A vmsdev shared 0 99.99% ONLINE 1509376.0M vmsdev shared 1 N/A UNKNOWN N/Abefore downloading and getting ready for patching we need to find what is the oda version.
This is very important steps for patch preparation.
########### Check running ODA details [root@ecl-odabase-0 PATCH]# oakcli show version -detail Reading the metadata. It takes a while... System Version Component Name Installed Version Supported Version -------------- --------------- ------------------ ----------------- 12.1.2.12.0 Controller_INT 4.650.00-7176 Up-to-date Controller_EXT 13.00.00.00 Up-to-date Expander 0018 Up-to-date SSD_SHARED { [ c1d20,c1d21,c1d22, A29A Up-to-date c1d23,c1d44,c1d45,c1 d46,c1d47 ] [ c1d16,c1d17,c1d18, A29A Up-to-date c1d19,c1d40,c1d41,c1 d42,c1d43 ] } HDD_LOCAL A7E0 Up-to-date HDD_SHARED { [ c1d0,c1d1,c1d2,c1d PAG1 Up-to-date 3,c1d4,c1d5,c1d6,c1d 7,c1d8,c1d9,c1d10,c1 d11,c1d12,c1d13,c1d1 4,c1d15,c1d28 ] [ c1d24,c1d25,c1d26, A3A0 Up-to-date c1d27,c1d29,c1d30,c1 d31,c1d32,c1d33,c1d3 4,c1d35,c1d36,c1d37, c1d38,c1d39 ] } ILOM 3.2.9.23 r116695 Up-to-date BIOS 30110000 Up-to-date IPMI 1.8.12.4 Up-to-date HMP 2.3.5.2.8 Up-to-date OAK 12.1.2.12.0 Up-to-date OL 6.8 Up-to-date OVM 3.4.3 Up-to-date GI_HOME 12.1.0.2.170814(2660 Up-to-date 9783,26609945) DB_HOME 12.1.0.2.170814(2660 Up-to-date 9783,26609945) [root@ecl-odabase-0 PATCH]#Section 2: Patching preparation steps
ODA patching you have to follow the http://docs.oracle.com .
There is no meta link note that covers all the patching steps.
go to http://docs.oracle.com and navigate engineered system page.
Then select the Oracle Database Appliance :
Navigate earlier release pages to find out the patching plan from 19.11 document, our plan is to upgrade ODA to 12.1.2.12 - 19.8.0.0.
This is how we can get 19.9.0.0 from 12.1.2.12.
12.1.2.12 - > 18.3.0.0
18.3.0.0 - > 18.8.0.0
18.8.0.0 - > 19.8.0.0
19.8.0.0 - > 19.9.0.0Left column shows the patch version , right column shows from version we should be in to upgrade ODA.
Table 3-1 Minimum Patch Requirements for Oracle Database Appliance Releases
Now plan is to upgrade ODA 12.1.2.12 to 18.3.0.0. steps are there in 18.3document section.
18.3 patches can be download from below mention link https://updates.oracle.com/Orion/PatchDetails/process_form?patch_num=28864520
2.1 Address known issues.
Always go and check the known issue pages for 18.3 , For this patching we have to apply acfs patch before starting the patching.
We need to apply patch 29608813 before upgrading ODA to 18.3 as proactive action to avoid that bug
Upgrading to 18.x from 12.x Can Automatically Result in ADVM Processes Consuming Excessive CPU and IO During Automatic Resilvering (Doc ID 2525427.1).
Also found very useful link which has most of the ODA upgrade issues ODA Upgrade « Timur Akhmadeev's blog (wordpress.com)
2.1.1 Applying acfs patch
Before applying the patch check the currently running acfs mount points
[root@ecl-odabase-0 ACFS_BUG]# /sbin/acfsutil registry | grep -i 'Mount Point' Mount Point: /u02/app/oracle/oradata/datastore Mount Point: /u02/app/oracle/oradata/datcdbdev Mount Point: /u01/app/sharedrepo/kali_test Mount Point: /u01/app/sharedrepo/qualys Mount Point: /u01/app/sharedrepo/vmdata Mount Point: /u02/app/oracle/oradata/flashdata Mount Point: /u01/app/oracle/fast_recovery_area/datastore Mount Point: /db_backup Mount Point: /delshare Mount Point: /prdmgtshare Mount Point: /u01/app/oracle/fast_recovery_area/rcocdbdev Mount Point: /u01/app/sharedrepo/vmsdev Mount Point: /u01/app/oracle/oradata/datastore Mount Point: /u01/app/oracle/oradata/rdocdbdev [root@ecl-odabase-0 ACFS_BUG]#To apply the patch we need to stop the acfs mount points , so before unmouting we need to stop the associate acfs repositories.
Stop the currently running vm’s and repository:
sequence of stopping for repository:
1. vm
2. repository
oakcli stop vm <vm_name>
oakcli stop repo <repo_name> -node <0|1>
Once the vm and repositories are stopped we can umount acfs mount points.
/bin/umount /u02/app/oracle/oradata/datastore /bin/umount /u02/app/oracle/oradata/datcdbdev /bin/umount /u01/app/sharedrepo/kali_test /bin/umount /u01/app/sharedrepo/qualys /bin/umount /u01/app/sharedrepo/vmdata /bin/umount /u02/app/oracle/oradata/flashdata /bin/umount /u01/app/oracle/fast_recovery_area/datastore /bin/umount /db_backup /bin/umount /delshare /bin/umount /prdmgtshare /bin/umount /u01/app/oracle/fast_recovery_area/rcocdbdev /bin/umount /u01/app/sharedrepo/vmsdev /bin/umount /u01/app/oracle/oradata/datastore /bin/umount /u01/app/oracle/oradata/rdocdbdevCheck the current opatch version before applying the patch , if the patch is older than 12.1.0.1.7 upgrade the opatch.
The version output of the previous command should be 12.1.0.1.7 or later.######### ecl-odabase-0 DB: ======== [oracle@ecl-odabase-0 ~]$ /u01/app/oracle/product/12.1.0.2/dbhome_2/OPatch/opatch version OPatch Version: 12.2.0.1.8 OPatch succeeded. [oracle@ecl-odabase-0 ~]$ Grid ===== [grid@ecl-odabase-0 ~]$ /u01/app/12.1.0.2/grid/OPatch/opatch version OPatch Version: 12.2.0.1.8 OPatch succeeded. [grid@ecl-odabase-0 ~]$ ########### ecl-odabase-1 DB: ======= [oracle@ecl-odabase-1 ~]$ /u01/app/oracle/product/12.1.0.2/dbhome_2/OPatch/opatch version OPatch Version: 12.2.0.1.8 OPatch succeeded. [oracle@ecl-odabase-1 ~]$ Grid ======= [grid@ecl-odabase-1 ~]$ /u01/app/12.1.0.2/grid/OPatch/opatch version OPatch Version: 12.2.0.1.8 OPatch succeeded. [grid@ecl-odabase-1 ~]$Checking the patch conflict check using opatch auto :
/u01/app/12.1.0.2/grid/OPatch/opatchauto apply /u01/PATCH/ACFS_BUG/29608813/29608813 -oh /u01/app/12.1.0.2/grid -analyzeApply Patch:
/u01/app/12.1.0.2/grid/OPatch/opatch apply -oh /u01/app/12.1.0.2/grid -local /u01/PATCH/ACFS_BUG/29608813/29608813verification : run below mention commands to validate the patch:
================= Validation ================= export GI=/u01/app/12.1.0.2/grid export OH=/u01/app/oracle/product/12.1.0.2 /u01/app/12.1.0.2/grid/OPatch/opatch lsinventory -oh $GI | grep ^Patch << to collect data at end. /u01/app/oracle/product/12.1.0.2/OPatch/opatch lsinventory -oh $OH | grep ^Patch << to collect data at end.expected output:
[grid@ecl-odabase-1 ~]$ /u01/app/12.1.0.2/grid/OPatch/opatch lsinventory -oh $GI | grep ^Patch Patch 29608813 : applied on Thu Aug 12 14:37:26 EDT 2021 Patch description: "ACFS Interim patch for 29608813" Patch 26609945 : applied on Fri Sep 08 15:31:12 EDT 2017 Patch description: "OCW Patch Set Update : 12.1.0.2.170814 (26609945)" Patch 26477255 : applied on Fri Sep 08 15:30:03 EDT 2017 Patch 25897615 : applied on Fri Sep 08 15:29:29 EDT 2017 Patch 25034396 : applied on Fri Sep 08 15:28:56 EDT 2017 Patch 26609783 : applied on Fri Sep 08 15:28:07 EDT 2017 Patch description: "Database Patch Set Update : 12.1.0.2.170814 (26609783)" Patch 21436941 : applied on Fri Sep 08 15:25:34 EDT 2017 Patch description: "WLM Patch Set Update: 12.1.0.2.5 (21436941)" Patch level status of Cluster nodes : [grid@ecl-odabase-1 ~]$ [grid@ecl-odabase-0 ~]$ /u01/app/12.1.0.2/grid/OPatch/opatch lsinventory -oh $GI | grep ^Patch Patch 29608813 : applied on Thu Aug 12 14:03:11 EDT 2021 Patch description: "ACFS Interim patch for 29608813" Patch 26609945 : applied on Fri Sep 08 15:31:12 EDT 2017 Patch description: "OCW Patch Set Update : 12.1.0.2.170814 (26609945)" Patch 26477255 : applied on Fri Sep 08 15:30:03 EDT 2017 Patch 25897615 : applied on Fri Sep 08 15:29:29 EDT 2017 Patch 25034396 : applied on Fri Sep 08 15:28:56 EDT 2017 Patch 26609783 : applied on Fri Sep 08 15:28:07 EDT 2017 Patch description: "Database Patch Set Update : 12.1.0.2.170814 (26609783)" Patch 21436941 : applied on Fri Sep 08 15:25:34 EDT 2017 Patch description: "WLM Patch Set Update: 12.1.0.2.5 (21436941)" Patch level status of Cluster nodes : [grid@ecl-odabase-0 ~]$2.3 Space check.
First of all we need to ensure we have enough space on /, /u01 and /opt file systems. At least 20 GB should be available. If not, we can do some cleaning or extend the LVM partitions.
Usage of below mention mount points :
1. unpacking is happening in /opt mount point
2. Grid and db patching and upgrades are happening in /u01 mount.
3. OS upgrade is happening in / mount point.
######### Space check First of all we need to ensure we have enough space on /, /u01 and /opt file systems. At least 20 GB should be available. If not, we can do some cleaning or extend the LVM partitions. df -h / /u01 /opt [root@ecl-odabase-1 PATCH]# df -h / /u01 /tmp /opt Filesystem Size Used Avail Use% Mounted on /dev/xvda2 55G 34G 18G 66% / /dev/xvdb1 92G 55G 33G 63% /u01 /dev/xvda2 55G 34G 18G 66% / /dev/xvda2 55G 34G 18G 66% / [root@ecl-odabase-1 PATCH]#2.4 Unpacking patches and upgrade repository
Use below mention commands to unpack 18.3.0.0 patches to /opt mount point.
Make sure you have download patching from below mention metalink :Download the Oracle Database Appliance Server Patch for the ODACLI/DCS stack (patch 28864520)# oakcli unpack -package /tmp/p28864520_183000_Linux-x86-64_1of3.zip # oakcli unpack -package /tmp/p28864520_183000_Linux-x86-64_2of3.zip # oakcli unpack -package /tmp/p28864520_183000_Linux-x86-64_3of3.zip /u01/PATCH # oakcli unpack -package /u01/PATCH/p28864520_183000_Linux-x86-64_1of3.zip # oakcli unpack -package /u01/PATCH/p28864520_183000_Linux-x86-64_2of3.zip # oakcli unpack -package /u01/PATCH/p28864520_183000_Linux-x86-64_3of3.zipExpected output:
[root@ecl-odabase-0 PATCH]# oakcli unpack -package /u01/PATCH/p28864520_183000_Linux-x86-64_1of3.zip Unpacking will take some time, Please wait... Successfully unpacked the files to repository. [root@ecl-odabase-0 PATCH]# oakcli unpack -package /u01/PATCH/p28864520_183000_Linux-x86-64_2of3.zip Unpacking will take some time, Please wait... Successfully unpacked the files to repository. [root@ecl-odabase-0 PATCH]# oakcli unpack -package /u01/PATCH/p28864520_183000_Linux-x86-64_3of3.zip Unpacking will take some time, Please wait... Successfully unpacked the files to repository.Once the unpacking is successful update the repository with latest patches.
oakcli update -patch 18.3.0.0.0 --verifySection 3: Patching
3.1 Server patching.
Patching is devided into two parts .
1. Server patching - This will patch several components.
2. Storage patching.
Also this patching steps will execute patches on domu and dom0 as well.
Before starting the patching make sure to stop the vm and repo to which helps patching process to run smoothly , even if we forgot the stop vm’s and repo before the patching , below command will take care of stopping the vm and repo, But the stopping these components are time consuming.
Always make sure you will execute this patching commands from node01.
Note :
Sequnece before patching :
First stop vms and then the repositoryscript /tmp/output.txt - record all the steps/opt/oracle/oak/bin/oakcli update -patch 18.3.0.0.0 --serveryou can verify the patching steps from below mention location.
Log location:
/opt/oracle/oak/log/ecl-odabase-0/patch/18.3.0.0.0 - LOGS3.1.1 Troubleshooting patching issues.
We faced issue while running the patching on , suddenly session got terminated after complete patching on few components in node02.
ERROR : Ran '/usr/bin/ssh -l root ecl-odabase-0 /opt/oracle/oak/pkgrepos/System/18.3.0.0.0/bin/prepatch -v 18.3.0.0.0 --infra' and it returned code(1) and output is: INFO: 2021-08-13 09:47:31: Checking for available free space on /, /boot, /tmp, /u01 and /opt INFO: 2021-08-13 09:47:43: Infra prepatch..... INFO: 2021-08-13 09:47:43: Performing a dry run for OS patching INFO: 2021-08-13 09:48:02: There are no conflicts. OS upgrade could be successful INFO: 2021-08-13 09:48:06: Checking if patch 29520544 is installed on the grid home INFO: 2021-08-13 09:48:10: Patch 29520544 is installed on the grid home WARNING: 2021-08-13 09:48:39: FAILED to update the inventory WARNING: 2021-08-13 09:48:40: FAILED to update the inventory WARNING: 2021-08-13 09:48:41: FAILED to update the inventory WARNING: 2021-08-13 09:48:42: Failed to get the good disks to read the partition sizes WARNING: 2021-08-13 09:48:42: Failed to get the valid Disk partition sizes to modify the oak conf. 0 INFO: Shutdown of local VM and Repo on both nodes. ERROR: OAKD on local node is not available. INFO: Failed to stop all resources on local node. ERROR: 2021-08-13 09:49:44: Failed to stop all resources on local node. INFO: Exiting... error atand errnum=<1> ERROR : Command = /usr/bin/ssh -l root ecl-odabase-0 /opt/oracle/oak/pkgrepos/System/18.3.0.0.0/bin/prepatch -v 18.3.0.0.0 --infra did not complete successfully. Exit code 1 #Step -1# Exiting... ERROR: Unable to apply the patch To overcome this we used below mention work around and restarted the patching process.
ODA ODAVP Applying the Bundle Patch 12.2.1.4 FAILS - 'CRS version [12.1.0.2.0] is incompatible for OAK 12.1/12.2/18.1' (Doc ID 2454218.1)
First check the /opt/oracle/oak/install/oakdrun file on both the nodes.
if one node shows that it's in upgrade mode, we need to change that to non-cluster mode on both the nodes and start the oakd service.echo "non-cluster" > /opt/oracle/oak/install/oakdrun/etc/init.d/init.oakd startps -ef | grep oakd3.2 Storage patching.
Once you verified the server patching is completed by running below command on both the servers.
if the support version shows as up to date we can move with storage patching.
oakcli show version -detail -- verification ######### NODE - 01 [root@ecl-odabase-0 grid]# oakcli show version -detail Reading the metadata. It takes a while... System Version Component Name Installed Version Supported Version -------------- --------------- ------------------ ----------------- 18.3.0.0.0 Controller_INT 4.650.00-7176 Up-to-date Controller_EXT 13.00.00.00 Up-to-date Expander 0018 Up-to-date SSD_SHARED { [ c1d20,c1d21,c1d22, A29A Up-to-date c1d23,c1d44,c1d45,c1 d46,c1d47 ] [ c1d16,c1d17,c1d18, A29A Up-to-date c1d19,c1d40,c1d41,c1 d42,c1d43 ] } HDD_LOCAL A7E0 Up-to-date HDD_SHARED { [ c1d0,c1d1,c1d2,c1d PAG1 Up-to-date 3,c1d4,c1d5,c1d6,c1d 7,c1d8,c1d9,c1d10,c1 d11,c1d12,c1d13,c1d1 4,c1d15,c1d28 ] [ c1d24,c1d25,c1d26, A3A0 Up-to-date c1d27,c1d29,c1d30,c1 d31,c1d32,c1d33,c1d3 4,c1d35,c1d36,c1d37, c1d38,c1d39 ] } ILOM 4.0.2.26.b r125868 Up-to-date BIOS 30130500 Up-to-date IPMI 1.8.12.4 Up-to-date HMP 2.4.1.0.14 Up-to-date OAK 18.3.0.0.0 Up-to-date OL 6.10 Up-to-date OVM 3.4.4 Up-to-date GI_HOME 18.3.0.0.180717 Up-to-date DB_HOME 12.1.0.2.170814 12.1.0.2.180717 [root@ecl-odabase-0 grid]# [root@ecl-odabase-0 grid]# ######### NODE - 02 [root@ecl-odabase-1 ~]# oakcli show version -detail Reading the metadata. It takes a while... System Version Component Name Installed Version Supported Version -------------- --------------- ------------------ ----------------- 18.3.0.0.0 Controller_INT 4.650.00-7176 Up-to-date Controller_EXT 13.00.00.00 Up-to-date Expander 0018 Up-to-date SSD_SHARED { [ c1d20,c1d21,c1d22, A29A Up-to-date c1d23,c1d44,c1d45,c1 d46,c1d47 ] [ c1d16,c1d17,c1d18, A29A Up-to-date c1d19,c1d40,c1d41,c1 d42,c1d43 ] } HDD_LOCAL A7E0 Up-to-date HDD_SHARED { [ c1d4,c1d24,c1d25,c PAG1 Up-to-date 1d26,c1d27,c1d28,c1d 29,c1d30,c1d31,c1d32 ,c1d33,c1d34,c1d35,c 1d36,c1d37,c1d38,c1d 39 ] [ c1d0,c1d1,c1d2,c1d A3A0 Up-to-date 3,c1d5,c1d6,c1d7,c1d 8,c1d9,c1d10,c1d11,c 1d12,c1d13,c1d14,c1d 15 ] } ILOM 4.0.2.26.b r125868 Up-to-date BIOS 30130500 Up-to-date IPMI 1.8.12.4 Up-to-date HMP 2.4.1.0.14 Up-to-date OAK 18.3.0.0.0 Up-to-date OL 6.10 Up-to-date OVM 3.4.4 Up-to-date GI_HOME 18.3.0.0.180717 Up-to-date DB_HOME 12.1.0.2.170814 12.1.0.2.180717 [root@ecl-odabase-1 ~]#Then can start the storage patching using below commands. In 18.3 we do not have any storage upgrade , but we are still running this command to make sure we are up to date with storage.
before storage patching we need to stop vm and repo.
1. First stop the vm
2. second stop the repo.
/opt/oracle/oak/bin/oakcli update -patch version --storage3.3 Database Patching
Now we have completed most of the components , only thing left is database . Here we are applying the latest psu patches for 12.1.0.2.180717 database.
Let's check the running oracle homes in oda environment.
*************************************************************************************** ####################################################################################### *************** Database Patching ######## show homes [root@ecl-odabase-0 ~]# oakcli show dbhomes Oracle Home Name Oracle Home version Home Location Home Edition ---------------- ------------------- ------------ ------------ OraDb12102_home1 12.1.0.2.180717 /u01/app/oracle/product/12.1.0.2/dbhome_1 Enterprise OraDb12102_home2 12.1.0.2.180717 /u01/app/oracle/product/12.1.0.2/dbhome_2 Enterprise [root@ecl-odabase-0 ~]# ######### check running databases [root@ecl-odabase-0 tmp]# oakcli show databases Name Type Storage HomeName HomeLocation Edition Type Version ----- ------ -------- -------------- ---------------- ------------ ---------- willow RAC ACFS OraDb12102_home1 /u01/app/oracle/product/12.1.0.2/dbhome_1 Enterprise 12.1.0.2.170814 mango RAC ACFS OraDb12102_home2 /u01/app/oracle/product/12.1.0.2/dbhome_2 Enterprise 12.1.0.2.170814 CDBDEV RAC ACFS OraDb12102_home2 /u01/app/oracle/product/12.1.0.2/dbhome_2 Enterprise 12.1.0.2.170814run the below mention command to patch database to latest psu:
/opt/oracle/oak/bin/oakcli update -patch 18.3.0.0.0 --database3.4 Verification
Once the server patching is complete you can run below mention command to verify.
This will display all the component are patched or not. expected output
oakcli show version -detailoakcli update -patch 18.3.0.0.0 --verify########################### After patching ######### NODE - 01 [root@ecl-odabase-0 grid]# oakcli show version -detail Reading the metadata. It takes a while... System Version Component Name Installed Version Supported Version -------------- --------------- ------------------ ----------------- 18.3.0.0.0 Controller_INT 4.650.00-7176 Up-to-date Controller_EXT 13.00.00.00 Up-to-date Expander 0018 Up-to-date SSD_SHARED { [ c1d20,c1d21,c1d22, A29A Up-to-date c1d23,c1d44,c1d45,c1 d46,c1d47 ] [ c1d16,c1d17,c1d18, A29A Up-to-date c1d19,c1d40,c1d41,c1 d42,c1d43 ] } HDD_LOCAL A7E0 Up-to-date HDD_SHARED { [ c1d0,c1d1,c1d2,c1d PAG1 Up-to-date 3,c1d4,c1d5,c1d6,c1d 7,c1d8,c1d9,c1d10,c1 d11,c1d12,c1d13,c1d1 4,c1d15,c1d28 ] [ c1d24,c1d25,c1d26, A3A0 Up-to-date c1d27,c1d29,c1d30,c1 d31,c1d32,c1d33,c1d3 4,c1d35,c1d36,c1d37, c1d38,c1d39 ] } ILOM 4.0.2.26.b r125868 Up-to-date BIOS 30130500 Up-to-date IPMI 1.8.12.4 Up-to-date HMP 2.4.1.0.14 Up-to-date OAK 18.3.0.0.0 Up-to-date OL 6.10 Up-to-date OVM 3.4.4 Up-to-date GI_HOME 18.3.0.0.180717 Up-to-date DB_HOME 12.1.0.2.170814 Up-to-date [root@ecl-odabase-0 grid]# [root@ecl-odabase-0 grid]# ######### NODE - 02 [root@ecl-odabase-1 ~]# oakcli show version -detail Reading the metadata. It takes a while... System Version Component Name Installed Version Supported Version -------------- --------------- ------------------ ----------------- 18.3.0.0.0 Controller_INT 4.650.00-7176 Up-to-date Controller_EXT 13.00.00.00 Up-to-date Expander 0018 Up-to-date SSD_SHARED { [ c1d20,c1d21,c1d22, A29A Up-to-date c1d23,c1d44,c1d45,c1 d46,c1d47 ] [ c1d16,c1d17,c1d18, A29A Up-to-date c1d19,c1d40,c1d41,c1 d42,c1d43 ] } HDD_LOCAL A7E0 Up-to-date HDD_SHARED { [ c1d4,c1d24,c1d25,c PAG1 Up-to-date 1d26,c1d27,c1d28,c1d 29,c1d30,c1d31,c1d32 ,c1d33,c1d34,c1d35,c 1d36,c1d37,c1d38,c1d 39 ] [ c1d0,c1d1,c1d2,c1d A3A0 Up-to-date 3,c1d5,c1d6,c1d7,c1d 8,c1d9,c1d10,c1d11,c 1d12,c1d13,c1d14,c1d 15 ] } ILOM 4.0.2.26.b r125868 Up-to-date BIOS 30130500 Up-to-date IPMI 1.8.12.4 Up-to-date HMP 2.4.1.0.14 Up-to-date OAK 18.3.0.0.0 Up-to-date OL 6.10 Up-to-date OVM 3.4.4 Up-to-date GI_HOME 18.3.0.0.180717 Up-to-date DB_HOME 12.1.0.2.170814 Up-to-date [root@ecl-odabase-1 ~]#Section 4 : Post Patching
Once everything is complete check oracle cluster is running and database are in open state.
ps -ef | grep d.binps -ef | grep pmonsqlplus / as sysdbaselect open_mode,database_role from gv$database;
No comments:
Post a Comment