To keep Oracle Database Appliance running with the latest software, check for and apply Oracle Database Appliance patch bundles when they are released.
Topics:
update-dcsagent command to update the agent version.update-server command to update the operating system, firmware, Oracle Appliance Kit, Oracle Clusterware, and all other infrastructure components.update-dbhome command to update a specific RDBMS Home to the latest patch bundle version.Oracle Database Appliance patching is done using the quarterly Oracle Database Appliance patch bundle.
The patch set bundle, also known as the Single Instance Bundle (SIB) for Oracle Database Appliance X6-2S, X6–2M, and X6–2L, contains the latest patches for DCS Agent, DCS Controller, OAK , GI and RDBMS 12.1 and 11.2 homes, enhancements, and fixes.
The patch bundle provides all relevant patches for the entire system, including the following:
BIOS
Hardware drivers, Hardware Management Pack (HWM), and firmware drivers for various components
Oracle Appliance Manager
Oracle Linux
Oracle VM
Java Development Kit (JDK)
Oracle Integrated Lights Out Manager (Oracle ILOM)
Oracle Database Patch Set Update (PSU)
Oracle Auto Service Request (Oracle ASR)
Oracle Grid Infrastructure
Intelligent Platform Management Interface (IPMI)
About Oracle Database Appliance Software Updates
To keep Oracle Database Appliance running with the latest software, check for and apply Oracle Database Appliance patch bundles when they are released. As well as offering new features, patches may improve the functionality of existing features.
Caution:
Do not patch Oracle Database Appliance using individual patches for Oracle Grid Infrastructure, Oracle Database, or Oracle Linux. Also do not use individual infrastructure patches, such as firmware patches. You must only use Oracle Database Appliance patches.
If you use patches that are not intended for Oracle Database Appliance, or if you use Opatch, or a similar patching tool, then Oracle Database Appliance inventory is not updated, and you cannot complete future patch updates.
Minimum Supported Appliance Manager Software Versions
The Oracle Database Appliance Release Notes include information about the latest Oracle Database Appliance patch bundle and a list of component versions in the patch bundle. Oracle recommends updating the appliance with the latest Oracle Database Appliance software version to take advantage of new features, fixes, and the latest supported component versions.
Table 6-1 Minimum Supported Appliance Manager Software Versions
| Oracle Database Appliance Hardware Version | Minimum Supported Software Version |
|---|---|
|
X6-2S |
12.1.2.8.0 |
|
X6-2M |
12.1.2.8.0 |
|
X6-2L |
12.1.2.8.1 |
Overview of the Patch Upgrade
Oracle Database Appliance patch set releases include new enhancements, including a comprehensive patching solution for Oracle Database Appliance X6-2S, X6-2M, and X6-2L. You must have a database deployed before updating the repository, agent, server, or database. Do not have any jobs running or pending during the update window.
Note:
If you are using Oracle Database Appliance 12.1.2.7, then you must upgrade thedcs-agent before installing the latest patch set. The dcs-agent upgrade includes changes that enable you to install the patch set bundle. Use the odacli describe-job command to monitor the progress of each patching job.All patching-related information is logged in the dcs-agent log file at /opt/oracle/dcs/log/dcs-agent.log.
Related Topics
Download the Oracle Database Appliance patch set bundle from My Oracle Support and update the repository with the new patches.
Perform the following tasks before updating Oracle Database Appliance:
On a new Oracle Database Appliance machine, confirm that the initial deployment completed successfully and that the public network is configured.
Confirm that you have a database deployed. To verify that the database is successfully deployed, run Oracle ORAchk and ensure that it completes successfully.
Do not have any jobs running or pending during the update window.
Run the update-dcsagent command to update the agent version.
Example 6-1 Updating the DCS Agent Version
Run the following command to update the DCS Agent to version 12.1.2.11.0:
# odacli update-dcsagent -v 12.1.2.11.0 { "jobId" : "77e454d3-eb68-4130-a247-7633f8d6192b", "status" : "Created", "message" : null, "reports" : [ ], "createTimestamp" : "June 9, 2017 10:30:02 AM EDT", "description" : "DcsAgent patching", "updatedTime" : "June 9, 2017 10:30:02 AM EDT" }
Example 6-2 Verifying the DCS Agent Version
The following example uses job ID 77e454d3-eb68-4130-a247-7633f8d6192b from the previous example to get the job details.
# odacli describe-job -i "77e454d3-eb68-4130-a247-7633f8d6192b"
Job details
----------------------------------------------------------------
ID: 77e454d3-eb68-4130-a247-7633f8d6192b
Description: DcsAgent patching
Status: Success
Created: June 9, 2017 10:39:02 AM EDT
Message:
Task Name Start Time
------------------- --------------------------------
dcsagent rpm version checking June 9, 2017 10:39:02 AM EDT
Patch location validation June 9, 2017 10:39:02 AM EDT
Apply dcsagent patch June 9, 2017 10:39:02 AM EDT
(Continued)
End Time Status
------------------------------ ------
June 9, 2017 10:39:02 AM EDT Success
June 9, 2017 10:39:02 AM EDT Success
June 9, 2017 10:39:02 AM EDT Success
Run the update-server command to update the operating system, firmware, Oracle Appliance Kit, Oracle Clusterware, and all other infrastructure components.
Patching information is logged in the dcs-agent log file (/opt/oracle/dcs/log/dcs-agent.log.)
odacli update-server command, update the repository with the latest patch bundle, update the DCS Agent to the latest version, and ensure that the agent is running.Example 6-3 Updating the Server Version
Run the following command to update the server to version 12.1.2.11.0:
# odacli update-server -v 12.1.2.11.0 { "jobId" : ""94685c73-55c2-40b1-a02e-265a23c45642", "status" : "Created", "message" : "Success of Server Update may trigger reboot of node after 4-5 minutes. Please wait till node restart", "reports" : [ ], "createTimestamp" : "June 9, 2017 14:13:45 PM CST", "resourceList" : [ ], "description" : "Server Patching", "updatedTime" : "June 9, 2017 14:13:45 PM CST" }
Example 6-4 Verifying that the Server is on the Updated Version
The following example uses job ID 94685c73-55c2-40b1-a02e-265a23c45642 from the previous example to get the job details and status.
# /opt/oracle/dcs/bin/odacli describe-job -i "94685c73-55c2-40b1-a02e-265a23c45642"
Job details
----------------------------------------------------------------
ID: 94685c73-55c2-40b1-a02e-265a23c45642
Description: Server Patching
Status: Success
Created: June 9, 2017 11:02:30 AM EDT
Message:
Task Name Start Time
------------------------------- ------------------------------
dcscontroller rpm version checking June 9, 2017 11:02:30 AM EDT
Patch location validation June 9, 2017 11:02:31 AM EDT
Apply dcscontroller patch June 9, 2017 11:02:31 AM EDT
dcscli rpm version checking June 9, 2017 11:02:32 AM EDT
Patch location validation June 9, 2017 11:02:32 AM EDT
Apply dcscli patch June 9, 2017 11:02:32 AM EDT
oak rpm version checking June 9, 2017 11:02:33 AM EDT
Patch location validation June 9, 2017 11:02:33 AM EDT
Apply oak patch June 9, 2017 11:02:33 AM EDT
Checking Ilom patch Version June 9, 2017 11:03:02 AM EDT
Patch location validation June 9, 2017 11:03:05 AM EDT
Apply Ilom patch June 9, 2017 11:03:05 AM EDT
Copying Flash Bios to Temp location June 9, 2017 11:03:06 AM EDT
Patch application verification June 9, 2017 11:03:06 AM EDT
Patch location validation June 9, 2017 11:03:09 AM EDT
Opatch updation June 9, 2017 11:04:13 AM EDT
analyzing patch June 9, 2017 11:04:15 AM EDT
Apply gi patch June 9, 2017 11:04:50 AM EDT
Reboot Ilom June 9, 2017 11:16:17 AM EDT
(Continued)
End Time Status
--------------------------- ------
June 9, 2017 11:02:31 AM EDT Success
June 9, 2017 11:02:31 AM EDT Success
June 9, 2017 11:02:32 AM EDT Success
June 9, 2017 11:02:32 AM EDT Success
June 9, 2017 11:02:32 AM EDT Success
June 9, 2017 11:02:33 AM EDT Success
June 9, 2017 11:02:33 AM EDT Success
June 9, 2017 11:02:33 AM EDT Success
June 9, 2017 11:03:02 AM EDT Success
June 9, 2017 11:03:05 AM EDT Success
June 9, 2017 11:03:05 AM EDT Success
June 9, 2017 11:03:06 AM EDT Success
June 9, 2017 11:03:06 AM EDT Success
June 9, 2017 11:03:09 AM EDT Success
June 9, 2017 11:03:14 AM EDT Success
June 9, 2017 11:04:15 AM EDT Success
June 9, 2017 11:04:50 AM EDT Success
June 9, 2017 11:16:08 AM EDT Success
June 9, 2017 11:16:17 AM EDT Success
Run the update-dbhome command to update a specific RDBMS Home to the latest patch bundle version.
After patching, download the latest database end user bundles. You can use the odacli create-database command to create different versions of the database without downloading the latest database end user bundle.
Note:
Oracle recommends downloading the latest database bundle and use it to create any new databases.Example 6-5 Getting a List of Database Home IDs
The following example shows how to get a database home ID using JSON output:
# /opt/oracle/dcs/bin/odacli list-dbhomes -j
[ {
"id" : "ab3cecaf-2223-4726-b95c-488f0aec914a",
"name" : "OraDB12102_home1",
"dbVersion" : "12.1.0.2.161018 (24927502, 24340679)",
"dbHomeLocation" : "/u01/app/oracle/product/12.1.0.2/dbhome_1",
"createTime" : "June 8, 2017 08:46:52 AM PDT",
"state" : {
"status" : "CONFIGURED"
},
"updatedTime" : "June 8, 2017 11:55:55 AM PDT"
}, {
"id" : "d5b01e27-799e-4e8a-bfe6-07a781f79526",
"name" : "OraDB12102_home2",
"dbVersion" : "12.1.0.2.160719 (23739960, 23144544)",
"dbHomeLocation" : "/u01/app/oracle/product/12.1.0.2/dbhome_2",
"createTime" : "June 8, 2017 22:34:31 PM PDT", "state" : {
"status" : "CONFIGURED"
},
"updatedTime" : "June 8, 2017 22:36:59 PM PDT"
} ]
Example 6-6 Updating the Database Home Version
The following example updates database home ID d5b01e27-799e-4e8a-bfe6-07a781f79526 to Oracle Database Appliance version 12.1.2.11.0.
# odacli update-dbhome -i d5b01e27-799e-4e8a-bfe6-07a781f79526 -v 12.1.2.11.0 { "jobId" : "576cdbfa-ece4-4e5f-becd-9bc6e6bf430b", "status" : "Created", "message" : null, "reports" : [ ], "createTimestamp" : "June 9, 2017 11:08:35 AM PDT", "description" : "DbHome Patching: Home Id is d5b01e27-799e-4e8a-bfe6-07a781f79526", "updatedTime" : "June 9, 2017 11:08:35 AM PDT" }
Example 6-7 Verifying that Database Home is Updated
The following example uses job ID 576cdbfa-ece4-4e5f-becd-9bc6e6bf430b from the previous example to get the job details.
# /opt/oracle/dcs/bin/odacli describe-job -i "576cdbfa-ece4-4e5f-becd-9bc6e6bf430b"
Job details
----------------------------------------------------------------
ID: 576cdbfa-ece4-4e5f-becd-9bc6e6bf430b
Description: DbHome Patching: Home Id is d5b01e27-799e-4e8a-bfe6-07a781f79526
Status: Success
Created: June 9, 2017 11:08:35 AM PDT
Message:
Task Name Start Time
--------------------------------- -------------------------------
Patch application verification June 9, 2017 11:08:35 AM PDT
location validation June 9, 2017 11:08:37 AM PDT
updateOpatch June 9, 2017 11:09:41 AM PDT
analyzing patch June 9, 2017 11:09:43 AM PDT
Apply db patch June 9, 2017 11:10:17 AM PDT
(continued)
End Time Status
------------------------------- --------
June 9, 2017 11:08:37 AM PDT Success
June 9, 2017 11:08:42 AM PDT Success
June 9, 2017 11:09:43 AM PDT Success
June 9, 2017 11:10:17 AM PDT Success
June 9, 2017 11:14:13 AM PDT Success
The patch bundle updates provide all relevant patches for the entire system and are designed to work with Oracle Database Appliance and future update patch bundles.
The patch bundle includes relevant patches, including the following:
BIOS
Hardware drivers, Hardware Management Pack (HWM), and firmware drivers
Oracle Appliance Manager
Oracle Linux
Oracle VM
Java Development Kit (JDK)
Oracle Integrated Lights Out Manager (Oracle ILOM)
Oracle Database Patch Set Update (PSU)
Oracle Auto Service Request (Oracle ASR)
Oracle Grid Infrastructure
Intelligent Platform Management Interface (IPMI)
Caution:
Do not patch Oracle Database Appliance using individual patches for Oracle Grid Infrastructure, Oracle Database, and most Oracle Linux RPM updates. Do not use individual infrastructure patches, such as firmware patches. You must only use Oracle Database Appliance patches.
If you use patches that are not intended for Oracle Database Appliance, or if you use Opatch, or a similar patching tool, then you can encounter problems with storage, communication, and applying patch updates in the future.
Updating Oracle Linux RPMs
While not recommended, you can update some Oracle Linux RPMs for database nodes. Do not update or customize Oracle Linux kernel, Oracle Optimal Flexible Architecture, Oracle InfiniBand, or related software. Other software may be installed, updated, or customized. However, the Oracle Database Appliance update may not carry newer version dependencies of customized components. Therefore, you might be required to remove and subsequently reapply site-specific changes to successfully update Oracle Database Appliance in the future.
Caution:
For database nodes, do not update the following:
Oracle Linux Kernel (kernel*)
Oracle Optimal Flexible Architecture (ofa*)
Oracle InfiniBand-related packages (ofed*)
For storage, do not apply any RPM updates.
Using a Different Version of Java Development Kit (JDK)
Oracle Database Appliance depends on a specific version of JDK. If you want to use a different version of JDK for a specific application, then install it in a different directory and only point to it for that application.
Reimage Oracle Database Appliance to perform a bare metal restore of Oracle Database Appliance.
Topics:
Bare metal operating system (OS) re-imaging installs Oracle Database Appliance operating system software on the local (boot) drive.
Bare Metal is a non-virtualized Oracle Database Appliance configuration. Oracle Database Appliance ships from the factory with a bare metal configuration, default ISO image and Appliance Manager installed.
The following are some of the reasons that you might want to reimage to perform a bare metal restore:
Deploy Bare Metal with latest Oracle Database Appliance software.
In some cases, the Oracle Database Appliance machine is shipped from the factory with an earlier release of Oracle Database Appliance software. To deploy the machine with the latest software, you can perform an update or you can reimage the machine.
Roll back to an earlier version of Oracle Database Appliance software.
Reimaging with older release of Oracle Database Appliance software does not rollback the firmware version.
Recover from a catastrophic failure.
You can reimage Oracle Database Appliance to re-install the operating system and restore the appliance.
Use the OS ISO Image to restore the OS to the "shipped from factory" state. Use only when necessary.
Note:
Bare metal OS re-imaging is specific to the node on which the procedure is executed and overwrites the local storage (operating system) on that node. You must reimage both nodes.Reimaging does not patch the firmware or update the component versions, it only re-images the local system disk from an OS perspective. After imaging is completed, redeploy the End User image, then restore from backup, as needed.
Access to the physical machine is not required. Bare metal restore uses Oracle Integrated Lights Out Manager (ILOM) to reimage the Oracle Database Appliance node. Newer ILOM versions require that the Java client be on jre-7-linux-i586.rpm or higher to be able to launch remote console.
Note:
To use Oracle Database Appliance Virtualized Platform, you must reimage Oracle Database Appliance with the virtualized VM ISO image and the VM Template instead of the OS ISO image.Download the Oracle Database Appliance 12.1.2.11.0 Bare Metal ISO image to prepare for a bare metal restore on Oracle Database Appliance X6-2S, X6–2M, and X6–2L.
Before downloading the image, ensure that the initial network connection is configured. To use scp or sftp, you must first set up a static IP address (for example, oda_host) and configure Oracle Database Appliance with that address by using the configure-firstnet command. This command ensures the system is available in your network, enabling you to use the Oracle Appliance Manager Web Console to deploy Oracle Database Appliance.
Reimage Oracle Database Appliance to perform a bare metal restore of Oracle Database Appliance X6-2S, X6-2M, and X6-2L.
Bare metal restore uses Oracle Integrated Lights Out Manager (ILOM) to re-image the Oracle Database Appliance node. Newer ILOM versions require that the Java client be on jre-7-linux-i586.rpm or higher to be able to launch the remote console.
Download the Oracle Database Appliance Bare Metal ISO image to your local machine before you launch the ILOM console.