Here is described the procedure to upgrade the ODA to the Bundle Patch 12.1.2.6.0.
This Bundle contains a BIG change because it replaces Oracle Enterprise Linux 5.11 with the version 6.7.
One critical requirement: this patch can only be installed on top of 12.1.2.5.0, to check the exisitng ODA version run:
# /opt/oracle/oak/bin/oakcli show version Version 12.1.2.5.0
The patch can be downloaded from MOS selecting the following note: 22328442 ORACLE DATABASE APPLIANCE PATCH BUNDLE 12.1.2.6.0 (Patch)
And now let’s start with the installation:
- Upload the patch on both ODA_Base (Dom1) on /tmp
- Remove any Extra RPM installed by the user on the ODA_Base
- Unpack both ZIP files of the patch on both ODA_Base using the following oakcli command:
[root@oda_base01 / ] # cd /tmp/Patch_12.1.2.6.0 [root@oda_base01 patch]# oakcli unpack -package /tmp/patch/p22328442_121260_Linux-x86-64_1of2.zip Unpacking takes a while, pls wait.... Successfully unpacked the files to repository. [root@oda_base01 patch]# [root@oda_base01 patch]# [root@oda_base01 patch]# oakcli unpack -package /tmp/patch/p22328442_121260_Linux-x86-64_2of2.zip Unpacking takes a while, pls wait.... Successfully unpacked the files to repository. [root@oda_base01 patch]#
Verify the patch compatibility on both ODA_Base with the following check:
[root@oda_base01 patch]# oakcli update -patch 12.1.2.6.0 -verify
INFO: 2016-03-31 17:07:29: Reading the metadata file now...
Component Name Installed Version Proposed Patch Version
--------------- ------------------ -----------------
Controller_INT 4.230.40-3739 Up-to-date
Controller_EXT 06.00.02.00 Up-to-date
Expander 0018 Up-to-date
SSD_SHARED {
[ c1d20,c1d21,c1d22, A29A Up-to-date
c1d23 ]
[ c1d16,c1d17,c1d18, A29A Up-to-date
c1d19 ]
}
HDD_LOCAL A720 Up-to-date
HDD_SHARED P554 Up-to-date
ILOM 3.2.4.42 r99377 3.2.4.52 r101649
BIOS 30040200 30050100
IPMI 1.8.12.0 1.8.12.4
HMP 2.3.2.4.1 2.3.4.0.1
OAK 12.1.2.5.0 12.1.2.6.0
OL 5.11 6.7
OVM 3.2.9 Up-to-date
GI_HOME 12.1.0.2.5(21359755, 12.1.0.2.160119(2194
21359758) 8354,21948344)
DB_HOME {
[ OraDb11204_home1 ] 11.2.0.4.8(21352635, 11.2.0.4.160119(2194
21352649) 8347,21948348)
[ OraDb12102_home2,O 12.1.0.2.5(21359755, 12.1.0.2.160119(2194
raDb12102_home1 ] 21359758) 8354,21948344)
}
[root@oda_base01 patch]#
Validate the Upgrade to OEL6 checking:
- The minimum required version
- The space requirement
- The list of valid ol5 rpms.
[root@oda_base01 patch]# oakcli validate -c ol6upgrade -prechecks INFO: Validating the OL6 upgrade -prechecks INFO: 2016-04-09 17:11:41: Checking for minimum compatible version SUCCESS: 2016-04-09 17:11:41: Minimum compatible version check passed INFO: 2016-04-09 17:11:41: Checking available free space on /u01 INFO: 2016-04-09 17:11:41: Free space on /u01 is 39734588 1K-blocks SUCCESS: 2016-04-09 17:11:41: Check for available free space passed INFO: 2016-04-09 17:11:42: Checking for additional RPMs SUCCESS: 2016-04-09 17:11:42: Check for additional RPMs passed INFO: 2016-04-09 17:11:42: Checking for expected RPMs installed INFO: 2016-04-09 17:11:42: Please take backup of ODA_BASE. Ensure ODA_BASE, Share Repos and all the VMs are shutdown cleanly before taking backup. INFO: 2016-04-09 17:11:42: You may use eg tar -cvzf oakDom1.<node>.tar.gz /OVS/Repositories/odabaseRepo/VirtualMachines/oakDom1. SUCCESS: 2016-04-09 17:11:42: All the expected ol5 RPMs are installed SUCCESS: Node is ready for upgrade [root@oda_base01 patch]#
Apply the patch to the first node using the flag -local
[root@oda_base01 patch]# /opt/oracle/oak/bin/oakcli update -patch 12.1.2.6.0 --infra -local INFO: Local patch is running on the Node <0> INFO: *************************************************** INFO: ** Please do not patch both nodes simultaneously ** INFO: *************************************************** INFO: DB, ASM, Clusterware may be stopped during the patch if required INFO: Local Node may get rebooted automatically during the patch if necessary Do you want to continue: [Y/N]?: Y INFO: User has confirmed for the reboot INFO: 2016-04-09 17:14:22: Checking for minimum compatible version SUCCESS: 2016-04-09 17:14:22: Minimum compatible version check passed INFO: 2016-04-09 17:14:22: Checking available free space on /u01 INFO: 2016-04-09 17:14:22: Free space on /u01 is 39733684 1K-blocks SUCCESS: 2016-04-09 17:14:22: Check for available free space passed INFO: 2016-04-09 17:14:22: Checking for additional RPMs SUCCESS: 2016-04-09 17:14:22: Check for additional RPMs passed INFO: 2016-04-09 17:14:22: Checking for expected RPMs installed INFO: 2016-04-09 17:14:22: Please take backup of ODA_BASE. Ensure ODA_BASE, Share Repos and all the VMs are shutdown cleanly before taking backup. INFO: 2016-04-09 17:14:22: You may use eg tar -cvzf oakDom1.<node>.tar.gz /OVS/Repositories/odabaseRepo/VirtualMachines/oakDom1. SUCCESS: 2016-04-09 17:14:22: All the expected ol5 RPMs are installed INFO: All the VMs except the ODABASE will be shutdown forcefully if needed Do you want to continue : [Y/N]? : Y INFO: Running pre-install scripts INFO: Running prepatching on local node INFO: Completed pre-install scripts INFO: local patching code START INFO: Stopping local VMs, repos and oakd... INFO: Shutdown of local VM, Repo and OAKD on node <0>. INFO: Stopping OAKD on the local node. INFO: Stopped Oakd on local node INFO: Waiting for processes to sync up... INFO: Oakd running on remote node INFO: Stopping local VMs... INFO: Stopping local shared repos... INFO: Patching Dom0 components INFO: Patching dom0 components on Local Node... <12.1.2.6.0> INFO: 2016-04-09 17:27:02: Attempting to patch the HMP on Dom0... SUCCESS: 2016-04-09 17:27:08: Successfully updated the device HMP to the version 2.3.4.0.1 on Dom0 INFO: 2016-04-09 17:27:08: Attempting to patch the IPMI on Dom0... INFO: 2016-04-09 17:27:08: Successfully updated the IPMI on Dom0 INFO: 2016-04-09 17:27:08: Attempting to patch OS on Dom0... INFO: 2016-04-09 17:27:18: Clusterware is running on local node INFO: 2016-04-09 17:27:18: Attempting to stop clusterware and its resources locally SUCCESS: 2016-04-09 17:29:12: Successfully stopped the clusterware on local node SUCCESS: 2016-04-09 17:31:36: Successfully updated the device OVM to 3.2.9 INFO: Patching ODABASE components INFO: Patching Infrastructure on the Local Node... INFO: 2016-04-09 17:31:38: ------------------Patching OS------------------------- INFO: 2016-04-09 17:31:38: OSPatching : Patching will start from step 0 INFO: 2016-04-09 17:31:38: OSPatching : Performing the step 0 INFO: 2016-04-09 17:31:39: OSPatching : step 0 completed ================================================================================== INFO: 2016-04-09 17:31:39: OSPatching : Performing the step 1 INFO: 2016-04-09 17:31:39: OSPatching : step 1 completed ================================================================================== INFO: 2016-04-09 17:31:39: OSPatching : Performing the step 2 INFO: 2016-04-09 17:31:42: OSPatching : step 2 completed. ================================================================================== INFO: 2016-04-09 17:31:42: OSPatching : Performing the step 3 INFO: 2016-04-09 17:31:51: OSPatching : step 3 completed ================================================================================== INFO: 2016-04-09 17:31:51: OSPatching : Performing the step 4 INFO: 2016-04-09 17:31:51: OSPatching : step 4 completed. ================================================================================== INFO: 2016-04-09 17:31:51: OSPatching : Performing the step 5 INFO: 2016-04-09 17:31:52: OSPatching : step 5 completed ================================================================================== INFO: 2016-04-09 17:31:52: OSPatching : Performing the step 6 INFO: 2016-04-09 17:31:52: OSPatching : Installing OL6 RPMs. Please wait... INFO: 2016-04-09 17:35:05: OSPatching : step 6 completed ================================================================================== INFO: 2016-04-09 17:35:05: OSPatching : Performing the step 7 INFO: 2016-04-09 17:37:36: OSPatching : step 7 completed ================================================================================== INFO: 2016-04-09 17:37:36: OSPatching : Performing the step 8 INFO: 2016-04-09 17:37:37: OSPatching : step 8 completed ================================================================================== INFO: 2016-04-09 17:37:37: OSPatching : Performing the step 9 INFO: 2016-04-09 17:38:14: OSPatching : step 9 completed ================================================================================== INFO: 2016-04-09 17:38:14: OSPatching : Performing the step 10 INFO: 2016-04-09 17:38:50: OSPatching : step 10 completed ================================================================================== INFO: 2016-04-09 17:38:50: OSPatching : Performing the step 11 INFO: 2016-04-09 17:38:50: OSPatching : step 11 completed ================================================================================== INFO: 2016-04-09 17:38:50: OSPatching : Performing the step 12 INFO: 2016-04-09 17:38:50: Checking for expected RPMs installed SUCCESS: 2016-04-09 17:38:51: All the expected ol6 RPMs are installed INFO: 2016-04-09 17:38:51: OSPatching : step 12 completed ================================================================================== SUCCESS: 2016-04-09 17:38:51: Successfully upgraded the OS INFO: 2016-04-09 17:38:52: ----------------------Patching IPMI--------------------- INFO: 2016-04-09 17:38:52: IPMI is already upgraded or running with the latest version INFO: 2016-04-09 17:38:52: ------------------Patching HMP------------------------- INFO: 2016-04-09 17:38:53: HMP is already Up-to-date INFO: 2016-04-09 17:38:53: /usr/lib64/sun-ssm already exists. INFO: 2016-04-09 17:38:53: ----------------------Patching OAK--------------------- SUCCESS: 2016-04-09 17:39:27: Successfully upgraded OAK INFO: 2016-04-09 17:39:31: ----------------------Patching JDK--------------------- SUCCESS: 2016-04-09 17:39:36: Successfully upgraded JDK INFO: local patching code END INFO: patching summary on local node SUCCESS: 2016-04-09 17:39:39: Successfully upgraded the HMP on Dom0 SUCCESS: 2016-04-09 17:39:39: Successfully updated the device OVM SUCCESS: 2016-04-09 17:39:39: Successfully upgraded the OS INFO: 2016-04-09 17:39:39: IPMI is already upgraded INFO: 2016-04-09 17:39:39: HMP is already updated SUCCESS: 2016-04-09 17:39:39: Successfully updated the OAK SUCCESS: 2016-04-09 17:39:39: Successfully updated the JDK INFO: Running post-install scripts INFO: Running postpatch on local node INFO: Dom0 Needs to be rebooted, will be rebooting the Dom0 Broadcast message from root@oda_base01 (unknown) at 17:40 ... The system is going down for power off NOW!
Validate the steps with the infrastructure post patch checks:
[root@oda_base01 ~]# /u01/app/12.1.0.2/grid/bin/crsctl check crs CRS-4638: Oracle High Availability Services is online CRS-4537: Cluster Ready Services is online CRS-4529: Cluster Synchronization Services is online CRS-4533: Event Manager is online [root@oda_base01 ~]# /opt/oracle/oak/bin/oakcli validate -c ol6upgrade -postchecks INFO: Validating the OL6 upgrade -postchecks INFO: 2016-04-09 19:50:40: Current kernel is OL6 INFO: 2016-04-09 19:50:43: Checking for expected RPMs installed SUCCESS: 2016-04-09 19:50:43: All the expected ol6 RPMs are installed
Apply the patch to the second node using the flag -local
[root@oda_base02 patch]# /opt/oracle/oak/bin/oakcli update -patch 12.1.2.6.0 --infra -local INFO: Local patch is running on the Node <1> INFO: *************************************************** INFO: ** Please do not patch both nodes simultaneously ** INFO: *************************************************** INFO: DB, ASM, Clusterware may be stopped during the patch if required INFO: Local Node may get rebooted automatically during the patch if necessary Do you want to continue: [Y/N]?: Y INFO: User has confirmed for the reboot INFO: 2016-04-09 19:58:07: Checking for minimum compatible version SUCCESS: 2016-04-09 19:58:07: Minimum compatible version check passed INFO: 2016-04-09 19:58:07: Checking available free space on /u01 INFO: 2016-04-09 19:58:07: Free space on /u01 is 45790328 1K-blocks SUCCESS: 2016-04-09 19:58:07: Check for available free space passed INFO: 2016-04-09 19:58:07: Checking for additional RPMs SUCCESS: 2016-04-09 19:58:07: Check for additional RPMs passed INFO: 2016-04-09 19:58:07: Checking for expected RPMs installed INFO: 2016-04-09 19:58:08: Please take backup of ODA_BASE. Ensure ODA_BASE, Share Repos and all the VMs are shutdown cleanly before taking backup. INFO: 2016-04-09 19:58:08: You may use eg tar -cvzf oakDom1.<node>.tar.gz /OVS/Repositories/odabaseRepo/VirtualMachines/oakDom1. SUCCESS: 2016-04-09 19:58:08: All the expected ol5 RPMs are installed INFO: All the VMs except the ODABASE will be shutdown forcefully if needed Do you want to continue : [Y/N]? : Y INFO: Running pre-install scripts INFO: Running prepatching on local node INFO: Completed pre-install scripts INFO: local patching code START INFO: Stopping local VMs, repos and oakd... INFO: Shutdown of local VM, Repo and OAKD on node <1>. INFO: Stopping OAKD on the local node. INFO: Stopped Oakd on local node INFO: Waiting for processes to sync up... INFO: Oakd running on remote node INFO: Stopping local VMs... INFO: Stopping local shared repos... INFO: Patching Dom0 components INFO: Patching dom0 components on Local Node... <12.1.2.6.0> INFO: 2016-04-09 20:04:26: Attempting to patch the HMP on Dom0... SUCCESS: 2016-04-09 20:04:33: Successfully updated the device HMP to the version 2.3.4.0.1 on Dom0 INFO: 2016-04-09 20:04:33: Attempting to patch the IPMI on Dom0... INFO: 2016-04-09 20:04:33: Successfully updated the IPMI on Dom0 INFO: 2016-04-09 20:04:33: Attempting to patch OS on Dom0... INFO: 2016-04-09 20:04:43: Clusterware is running on local node INFO: 2016-04-09 20:04:43: Attempting to stop clusterware and its resources locally SUCCESS: 2016-04-09 20:08:20: Successfully stopped the clusterware on local node SUCCESS: 2016-04-09 20:10:44: Successfully updated the device OVM to 3.2.9 INFO: Patching ODABASE components INFO: Patching Infrastructure on the Local Node... INFO: 2016-04-09 20:10:48: ------------------Patching OS------------------------- INFO: 2016-04-09 20:10:48: OSPatching : Patching will start from step 0 INFO: 2016-04-09 20:10:48: OSPatching : Performing the step 0 INFO: 2016-04-09 20:10:51: OSPatching : step 0 completed ================================================================================== INFO: 2016-04-09 20:10:51: OSPatching : Performing the step 1 INFO: 2016-04-09 20:10:51: OSPatching : step 1 completed ================================================================================== INFO: 2016-04-09 20:10:51: OSPatching : Performing the step 2 INFO: 2016-04-09 20:10:53: OSPatching : step 2 completed. ================================================================================== INFO: 2016-04-09 20:10:53: OSPatching : Performing the step 3 INFO: 2016-04-09 20:11:00: OSPatching : step 3 completed ================================================================================== INFO: 2016-04-09 20:11:00: OSPatching : Performing the step 4 INFO: 2016-04-09 20:11:00: OSPatching : step 4 completed. ================================================================================== INFO: 2016-04-09 20:11:00: OSPatching : Performing the step 5 INFO: 2016-04-09 20:11:00: OSPatching : step 5 completed ================================================================================== INFO: 2016-04-09 20:11:00: OSPatching : Performing the step 6 INFO: 2016-04-09 20:11:00: OSPatching : Installing OL6 RPMs. Please wait... INFO: 2016-04-09 20:14:25: OSPatching : step 6 completed ================================================================================== INFO: 2016-04-09 20:14:25: OSPatching : Performing the step 7 INFO: 2016-04-09 20:16:58: OSPatching : step 7 completed ================================================================================== INFO: 2016-04-09 20:16:58: OSPatching : Performing the step 8 INFO: 2016-04-09 20:16:59: OSPatching : step 8 completed ================================================================================== INFO: 2016-04-09 20:16:59: OSPatching : Performing the step 9 INFO: 2016-04-09 20:17:35: OSPatching : step 9 completed ================================================================================== INFO: 2016-04-09 20:17:35: OSPatching : Performing the step 10 INFO: 2016-04-09 20:18:11: OSPatching : step 10 completed ================================================================================== INFO: 2016-04-09 20:18:11: OSPatching : Performing the step 11 INFO: 2016-04-09 20:18:11: OSPatching : step 11 completed ================================================================================== INFO: 2016-04-09 20:18:11: OSPatching : Performing the step 12 INFO: 2016-04-09 20:18:12: Checking for expected RPMs installed SUCCESS: 2016-04-09 20:18:12: All the expected ol6 RPMs are installed INFO: 2016-04-09 20:18:12: OSPatching : step 12 completed ================================================================================== SUCCESS: 2016-04-09 20:18:12: Successfully upgraded the OS INFO: 2016-04-09 20:18:12: ----------------------Patching IPMI--------------------- INFO: 2016-04-09 20:18:13: IPMI is already upgraded or running with the latest version INFO: 2016-04-09 20:18:13: ------------------Patching HMP------------------------- INFO: 2016-04-09 20:18:15: HMP is already Up-to-date INFO: 2016-04-09 20:18:15: /usr/lib64/sun-ssm already exists. INFO: 2016-04-09 20:18:15: ----------------------Patching OAK--------------------- SUCCESS: 2016-04-09 20:18:53: Successfully upgraded OAK INFO: 2016-04-09 20:18:56: ----------------------Patching JDK--------------------- SUCCESS: 2016-04-09 20:19:02: Successfully upgraded JDK INFO: local patching code END INFO: patching summary on local node SUCCESS: 2016-04-09 20:19:06: Successfully upgraded the HMP on Dom0 SUCCESS: 2016-04-09 20:19:06: Successfully updated the device OVM SUCCESS: 2016-04-09 20:19:06: Successfully upgraded the OS INFO: 2016-04-09 20:19:06: IPMI is already upgraded INFO: 2016-04-09 20:19:06: HMP is already updated SUCCESS: 2016-04-09 20:19:06: Successfully updated the OAK SUCCESS: 2016-04-09 20:19:06: Successfully updated the JDK INFO: Running post-install scripts INFO: Running postpatch on local node INFO: Dom0 Needs to be rebooted, will be rebooting the Dom0 Broadcast message from root@oda_base02 (unknown) at 20:20 ... The system is going down for power off NOW!
From the first ODA_Base apply the fix to the InfiniBand connection:
[root@oda_base01 ~]# python /opt/oracle/oak/bin/infiniFixSetup.py IB Fix requires nodes reboot. Do you want to continue? [Y/N] : Y INFO: Checking version for IB Fix setup INFO: Checking whether IB Fix setup is already done or not INFO: Checking default HAVIP for IB Fix setup INFO: Setting up IB fix INFO: Enabling IB fix and rebooting all nodes.... [root@oda_base01 ~]# Broadcast message from root@oda_base01 (unknown) at 20:40 ... The system is going down for power off NOW!
Check the correct application of the InfiniBand patch, the value of the file below should be 1
[root@oda_base01 ~]# view /opt/oracle/oak/conf/ib_fix 1
Installation of the Grid Infrastructure patch, two available methods:
- Full Downtime
- Rolling Upgrade
The example below show the first method
[root@oda_base01 ~]# oakcli update -patch 12.1.2.6.0 --gi Please enter the 'SYSASM' password : (During deployment we set the SYSASM password to 'welcome1'): Please re-enter the 'SYSASM' password: INFO: Running pre-install scripts INFO: Running prepatching on node 0 INFO: Running prepatching on node 1 INFO: Completed pre-install scripts ... ... INFO: Stopped Oakd ... ... ...... SUCCESS: All nodes in /opt/oracle/oak/temp_clunodes.txt are pingable and alive. INFO: 2016-04-09 22:32:16: Setting up SSH for grid User ...... SUCCESS: All nodes in /opt/oracle/oak/temp_clunodes.txt are pingable and alive. INFO: 2016-04-09 22:32:34: Patching the GI Home on the Node oda_base01 ... INFO: 2016-04-09 22:32:34: Updating OPATCH... INFO: 2016-04-09 22:32:36: Rolling back GI on oda_base01 (if necessary)... INFO: 2016-04-09 22:32:39: Rolling back GI on oda_base02 (if necessary)... INFO: 2016-04-09 22:32:46: Patching the GI Home on the Node oda_base01 INFO: 2016-04-09 22:34:02: Performing the conflict checks... SUCCESS: 2016-04-09 22:34:16: Conflict checks passed for all the Homes INFO: 2016-04-09 22:34:16: Checking if the patch is already applied on any of the Homes INFO: 2016-04-09 22:34:28: Home is not Up-to-date SUCCESS: 2016-04-09 22:37:01: Successfully stopped the Database consoles SUCCESS: 2016-04-09 22:37:18: Successfully stopped the EM agents INFO: 2016-04-09 22:37:23: Applying patch on /u01/app/12.1.0.2/grid Homes INFO: 2016-04-09 22:37:23: It may take upto 15 mins. Please wait... SUCCESS: 2016-04-09 22:50:57: Successfully applied the patch on the Home : /u01/app/12.1.0.2/grid SUCCESS: 2016-04-09 22:51:24: Successfully started the Database consoles SUCCESS: 2016-04-09 22:51:40: Successfully started the EM Agents INFO: 2016-04-09 22:51:41: Patching the GI Home on the Node oda_base02 ... INFO: 2016-04-09 23:16:27: ASM is running in Flex mode INFO: GI patching summary on node: oda_base01 SUCCESS: 2016-04-09 23:16:28: Successfully applied the patch on the Home /u01/app/12.1.0.2/grid INFO: GI patching summary on node: oda_base02 SUCCESS: 2016-04-09 23:16:28: Successfully applied the patch on the Home /u01/app/12.1.0.2/grid INFO: GI versions: installed <12.1.0.2.160119> expected <12.1.0.2.160119> INFO: Running post-install scripts INFO: Running postpatch on node 1... INFO: Running postpatch on node 0... ... ... INFO: Started Oakd
Installation of the RDBMS patch, two available methods:
- Full Downtime
- Rolling Upgrade
The example below show the first method
[root@oda_base01 ~]# oakcli update -patch 12.1.2.6.0 --database INFO: Running pre-install scripts INFO: Running prepatching on node 0 INFO: Running prepatching on node 1 INFO: Completed pre-install scripts ... ... ...... SUCCESS: All nodes in /opt/oracle/oak/temp_clunodes.txt are pingable and alive. INFO: 2016-04-09 23:27:31: Getting all the possible Database Homes for patching ... INFO: 2016-04-09 23:27:42: Patching 11.2.0.4 Database Homes on the Node oda_base01 Found the following 11.2.0.4 homes possible for patching: HOME_NAME HOME_LOCATION --------- ------------- OraDb11204_home1 /u01/app/oracle/product/11.2.0.4/dbhome_1 [Please note that few of the above Database Homes may be already up-to-date. They will be automatically ignored] Would you like to patch all the above homes: Y | N ? : Y INFO: 2016-04-09 23:29:17: Setting up SSH for the User oracle ...... SUCCESS: All nodes in /opt/oracle/oak/temp_clunodes.txt are pingable and alive. INFO: 2016-04-09 23:29:35: Updating OPATCH Fixing home : /u01/app/oracle/product/11.2.0.4/dbhome_1...done INFO: 2016-04-09 23:30:33: Performing the conflict checks... SUCCESS: 2016-04-09 23:30:43: Conflict checks passed for all the Homes INFO: 2016-04-09 23:30:43: Checking if the patch is already applied on any of the Homes INFO: 2016-04-09 23:30:47: Home is not Up-to-date SUCCESS: 2016-04-09 23:31:13: Successfully stopped the Database consoles SUCCESS: 2016-04-09 23:31:31: Successfully stopped the EM agents INFO: 2016-04-09 23:31:36: Applying the patch on oracle home : /u01/app/oracle/product/11.2.0.4/dbhome_1 ... SUCCESS: 2016-04-09 23:32:52: Successfully applied the patch on the Home : /u01/app/oracle/product/11.2.0.4/dbhome_1 SUCCESS: 2016-04-09 23:32:52: Successfully started the Database consoles SUCCESS: 2016-04-09 23:33:08: Successfully started the EM Agents INFO: 2016-04-09 23:33:17: Patching 11.2.0.4 Database Homes on the Node oda_base02 INFO: 2016-04-09 23:40:45: Running the catbundle.sql INFO: 2016-04-09 23:40:52: Running catbundle.sql on the Database XXXXXXX INFO: 2016-04-09 23:41:29: Running catbundle.sql on the Database YYYYYYY INFO: 2016-04-09 23:42:07: Running catbundle.sql on the Database ZZZZZZZ INFO: 2016-04-09 23:42:42: Running catbundle.sql on the Database WWWWWWW ... INFO: 2016-04-09 23:47:56: Patching 12.1.0.2 Database Homes on the Node oda_base01 Found the following 12.1.0.2 homes possible for patching: HOME_NAME HOME_LOCATION --------- ------------- OraDb12102_home1 /u01/app/oracle/product/12.1.0.2/dbhome_1 OraDb12102_home2 /u01/app/oracle/product/12.1.0.2/dbhome_2 [Please note that few of the above Database Homes may be already up-to-date. They will be automatically ignored] Would you like to patch all the above homes: Y | N ? : Y INFO: 2016-04-09 23:49:11: Updating OPATCH INFO: 2016-04-09 23:49:55: Performing the conflict checks... SUCCESS: 2016-04-09 23:50:21: Conflict checks passed for all the Homes INFO: 2016-04-09 23:50:21: Checking if the patch is already applied on any of the Homes INFO: 2016-04-09 23:50:28: Home is not Up-to-date SUCCESS: 2016-04-09 23:50:47: Successfully stopped the Database consoles SUCCESS: 2016-04-09 23:51:04: Successfully stopped the EM agents INFO: 2016-04-09 23:51:10: Applying patch on /u01/app/oracle/product/12.1.0.2/dbhome_1,/u01/app/oracle/product/12.1.0.2/dbhome_2 Homes INFO: 2016-04-09 23:51:10: It may take upto 30 mins. Please wait... SUCCESS: 2016-04-09 23:54:20: Successfully applied the patch on the Home : /u01/app/oracle/product/12.1.0.2/dbhome_1,/u01/app/oracle/product/12.1.0.2/dbhome_2 SUCCESS: 2016-04-09 23:54:20: Successfully started the Database consoles SUCCESS: 2016-04-09 23:54:37: Successfully started the EM Agents INFO: 2016-04-09 23:54:47: Patching 12.1.0.2 Database Homes on the Node oda_base02 INFO: DB patching summary on node: oda_base01 SUCCESS: 2016-04-01 00:03:19: Successfully applied the patch on the Home /u01/app/oracle/product/11.2.0.4/dbhome_1 SUCCESS: 2016-04-01 00:03:19: Successfully applied the patch on the Home /u01/app/oracle/product/12.1.0.2/dbhome_1,/u01/app/oracle/product/12.1.0.2/dbhome_2 INFO: DB patching summary on node: oda_base02 SUCCESS: 2016-04-01 00:03:20: Successfully applied the patch on the Home /u01/app/oracle/product/11.2.0.4/dbhome_1 SUCCESS: 2016-04-01 00:03:20: Successfully applied the patch on the Home /u01/app/oracle/product/12.1.0.2/dbhome_1,/u01/app/oracle/product/12.1.0.2/dbhome_2
Post patching validation:
[root@oda_base01 ~]# /opt/oracle/oak/bin/oakcli validate -d
INFO: oak system information and Validations
RESULT: System Software inventory details
Reading the metadata. It takes a while...
System Version Component Name Installed Version Supported Version
-------------- --------------- ------------------ -----------------
12.1.2.6.0
Controller_INT 4.230.40-3739 Up-to-date
Controller_EXT 06.00.02.00 Up-to-date
Expander 0018 Up-to-date
SSD_SHARED {
[ c1d20,c1d21,c1d22, A29A Up-to-date
c1d23 ]
[ c1d16,c1d17,c1d18, A29A Up-to-date
c1d19 ]
}
HDD_LOCAL A720 Up-to-date
HDD_SHARED P554 Up-to-date
ILOM 3.2.4.42 r99377 Up-to-date
BIOS 30040200 Up-to-date
IPMI 1.8.12.4 Up-to-date
HMP 2.3.4.0.1 Up-to-date
OAK 12.1.2.6.0 Up-to-date
OL 6.7 Up-to-date
OVM 3.2.9 Up-to-date
GI_HOME 12.1.0.2.160119(2194 Up-to-date
8354,21948344)
DB_HOME {
[ OraDb11204_home1 ] 11.2.0.4.160119(2194 Up-to-date
8347,21948348)
[ OraDb12102_home2,O 12.1.0.2.160119(2194 Up-to-date
raDb12102_home1 ] 8354,21948344)
}
RESULT: System Information:-
Manufacturer:Oracle Corporation
Product Name:ORACLE SERVER X5-2
Serial Number:1548NM102F
RESULT: BIOS Information:-
Vendor:American Megatrends Inc.
Version:30040200
Release Date:04/29/2015
BIOS Revision:4.2
Firmware Revision:3.2
SUCCESS: Controller p1 has the IR Bypass mode set correctly
SUCCESS: Controller p2 has the IR Bypass mode set correctly
INFO: Reading ilom data, may take short while..
INFO: Read the ilom data. Doing Validations
RESULT: System ILOM Version: 3.2.4.42 r99377
RESULT: System BMC firmware version 3.02
RESULT: Powersupply PS0 V_IN=230 Volts IN_POWER=180 Watts OUT_POWER=170 Watts
RESULT: Powersupply PS1 V_IN=230 Volts IN_POWER=190 Watts OUT_POWER=160 Watts
SUCCESS: Both the powersupply are ok and functioning
RESULT: Cooling Unit FM0 fan speed F0=5000 RPM F1=4500 RPM
RESULT: Cooling Unit FM1 fan speed F0=9100 RPM F1=8000 RPM
SUCCESS: Both the cooling unit are present
RESULT: Processor P0 present Details:-
Version:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
Current Speed:2300 MHz Core Enabled:18 Thread Count:36
SUCCESS: All 4 memory modules of CPU P0 ok, each module is of Size:32767 MB Type:Other Speed:2133 MHz manufacturer:Samsung
RESULT: Processor P1 present Details:-
Version:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
Current Speed:2300 MHz Core Enabled:18 Thread Count:36
SUCCESS: All 4 memory modules of CPU P1 ok, each module is of Size:32767 MB Type:Other Speed:2133 MHz manufacturer:Samsung
RESULT: Total Physical System Memory is 132037124 kB
SUCCESS: All OS Disks are present and in ok state
RESULT: Power Supply=24 degrees C
INFO: Checking Operating System Storage
SUCCESS: The OS disks have the boot stamp
RESULT: Device /dev/xvda2 is mounted on / of type ext3 in (rw)
RESULT: Device /dev/xvda1 is mounted on /boot of type ext3 in (rw)
RESULT: Device /dev/xvdb1 is mounted on /u01 of type ext3 in (rw)
RESULT: / has 19218 MB free out of total 55852 MB
RESULT: /boot has 384 MB free out of total 460 MB
RESULT: /u01 has 34501 MB free out of total 93868 MB
INFO: Checking Shared Storage
RESULT: Disk HDD_E0_S00_993971920 path1 status active device sdy with status active path2 status active device sda with status active
SUCCESS: HDD_E0_S00_993971920 has both the paths up and active
RESULT: Disk HDD_E0_S01_993379760 path1 status active device sdz with status active path2 status active device sdb with status active
SUCCESS: HDD_E0_S01_993379760 has both the paths up and active
RESULT: Disk HDD_E0_S02_993993052 path1 status active device sdaa with status active path2 status active device sdc with status active
SUCCESS: HDD_E0_S02_993993052 has both the paths up and active
RESULT: Disk HDD_E0_S03_993310956 path1 status active device sdab with status active path2 status active device sdd with status active
SUCCESS: HDD_E0_S03_993310956 has both the paths up and active
RESULT: Disk HDD_E0_S04_993385276 path1 status active device sdac with status active path2 status active device sde with status active
SUCCESS: HDD_E0_S04_993385276 has both the paths up and active
RESULT: Disk HDD_E0_S05_993388928 path1 status active device sdf with status active path2 status active device sdad with status active
SUCCESS: HDD_E0_S05_993388928 has both the paths up and active
RESULT: Disk HDD_E0_S06_993310572 path1 status active device sdae with status active path2 status active device sdg with status active
SUCCESS: HDD_E0_S06_993310572 has both the paths up and active
RESULT: Disk HDD_E0_S07_991849548 path1 status active device sdh with status active path2 status active device sdaf with status active
SUCCESS: HDD_E0_S07_991849548 has both the paths up and active
RESULT: Disk HDD_E0_S08_992415004 path1 status active device sdag with status active path2 status active device sdi with status active
SUCCESS: HDD_E0_S08_992415004 has both the paths up and active
RESULT: Disk HDD_E0_S09_992392444 path1 status active device sdj with status active path2 status active device sdah with status active
SUCCESS: HDD_E0_S09_992392444 has both the paths up and active
RESULT: Disk HDD_E0_S10_992233592 path1 status active device sdai with status active path2 status active device sdk with status active
SUCCESS: HDD_E0_S10_992233592 has both the paths up and active
RESULT: Disk HDD_E0_S11_992337644 path1 status active device sdl with status active path2 status active device sdaj with status active
SUCCESS: HDD_E0_S11_992337644 has both the paths up and active
RESULT: Disk HDD_E0_S12_993363524 path1 status active device sdm with status active path2 status active device sdak with status active
SUCCESS: HDD_E0_S12_993363524 has both the paths up and active
RESULT: Disk HDD_E0_S13_992394252 path1 status active device sdn with status active path2 status active device sdal with status active
SUCCESS: HDD_E0_S13_992394252 has both the paths up and active
RESULT: Disk HDD_E0_S14_993366344 path1 status active device sdam with status active path2 status active device sdo with status active
SUCCESS: HDD_E0_S14_993366344 has both the paths up and active
RESULT: Disk HDD_E0_S15_993407552 path1 status active device sdp with status active path2 status active device sdan with status active
SUCCESS: HDD_E0_S15_993407552 has both the paths up and active
RESULT: Disk SSD_E0_S16_1313537708 path1 status active device sdq with status active path2 status active device sdao with status active
SUCCESS: SSD_E0_S16_1313537708 has both the paths up and active
RESULT: Disk SSD_E0_S17_1313522352 path1 status active device sdr with status active path2 status active device sdap with status active
SUCCESS: SSD_E0_S17_1313522352 has both the paths up and active
RESULT: Disk SSD_E0_S18_1313531936 path1 status active device sds with status active path2 status active device sdaq with status active
SUCCESS: SSD_E0_S18_1313531936 has both the paths up and active
RESULT: Disk SSD_E0_S19_1313534520 path1 status active device sdt with status active path2 status active device sdar with status active
SUCCESS: SSD_E0_S19_1313534520 has both the paths up and active
RESULT: Disk SSD_E0_S20_1313568492 path1 status active device sdu with status active path2 status active device sdas with status active
SUCCESS: SSD_E0_S20_1313568492 has both the paths up and active
RESULT: Disk SSD_E0_S21_1313571440 path1 status active device sdv with status active path2 status active device sdat with status active
SUCCESS: SSD_E0_S21_1313571440 has both the paths up and active
RESULT: Disk SSD_E0_S22_1313568380 path1 status active device sdw with status active path2 status active device sdau with status active
SUCCESS: SSD_E0_S22_1313568380 has both the paths up and active
RESULT: Disk SSD_E0_S23_1313568480 path1 status active device sdx with status active path2 status active device sdav with status active
SUCCESS: SSD_E0_S23_1313568480 has both the paths up and active
INFO: Doing oak network checks
RESULT: Detected active link for interface eth0 with link speed 10000Mb/s and cable type as TwistedPair
RESULT: Detected active link for interface eth1 with link speed 10000Mb/s and cable type as TwistedPair
WARNING: No Link detected for interface eth2 with cable type as TwistedPair
WARNING: No Link detected for interface eth3 with cable type as TwistedPair
INFO: Checking bonding interface status
RESULT: No Bond Interface Found
SUCCESS: ibbond0 is running 192.168.16.27
It may take a while. Please wait...
INFO : ODA Topology Verification
INFO : Running on Node0
INFO : Check hardware type
SUCCESS : Type of hardware found : X5-2
INFO : Check for Environment(Bare Metal or Virtual Machine)
SUCCESS : Type of environment found : Virtual Machine(ODA BASE)
SUCCESS : Number of External SCSI controllers found : 2
INFO : Check for Controllers correct PCIe slot address
SUCCESS : External LSI SAS controller 0 : 00:04.0
SUCCESS : External LSI SAS controller 1 : 00:05.0
INFO : Check if JBOD powered on
SUCCESS : 1JBOD : Powered-on
INFO : Check for correct number of EBODS(2 or 4)
SUCCESS : EBOD found : 2
INFO : Check for External Controller 0
SUCCESS : Controller connected to correct EBOD number
SUCCESS : Controller port connected to correct EBOD port
SUCCESS : Overall Cable check for controller 0
INFO : Check for External Controller 1
SUCCESS : Controller connected to correct EBOD number
SUCCESS : Controller port connected to correct EBOD port
SUCCESS : Overall Cable check for Controller 1
INFO : Check for overall status of cable validation on Node0
SUCCESS : Overall Cable Validation on Node0
INFO : Check Node Identification status
SUCCESS : Node Identification
SUCCESS : Node name based on cable configuration found : NODE0
INFO : Check JBOD Nickname
SUCCESS : JBOD Nickname set correctly : Oracle Database Appliance - E0
INFO : The details for Storage Topology Validation can also be found in the log file=/opt/oracle/oak/log/oda_base01/storagetopology/StorageTopology-2016-04-01-00:06:34_28446_1789.log
One takeaway
Despite the fact that patching an Oracle Engineered system should be a straight forward task, it is recommended to carefully read the instructions (README), and the MOS notes continuously updated with bug, known issues and other related information.
My Oracle Notes 