To keep Oracle Database Appliance running with the latest software, check for and apply the latest Oracle Database Appliance patch bundles when they are released.
Topics:
Oracle Database Appliance patching is done using the quarterly Oracle Database Appliance Patch Bundle.
The Oracle Database Appliance Patch Bundle includes enhancements and fixes. The patch bundle provides all relevant patches for the entire system (bare metal or virtualized platform), 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) and Oracle Database Bundle Patch (BP)
Oracle Auto Service Request (Oracle ASR)
Oracle Grid Infrastructure
Oracle Automatic Storage Management (Oracle ASM)
Oracle Automatic Storage Management Cluster File System (Oracle ACFS)
Oracle Trace File Analyzer
Intelligent Platform Management Interface (IPMI)
The patch bundle consists of three logical groups of patches:
Table 1-1 Patch Components and Purposes
Patch Component | Objects Patched |
---|---|
SERVER ( |
The SERVER component patch is mandatory. Updates the Oracle Linux operating system, Oracle ILOM, BIOS, Hardware Management Pack, IPMI, OAK, Oracle ASR, and local disks. For virtualized environment, the patch includes the The Server patch also includes Oracle Grid Infrastructure (GI) stack, including Oracle ASM, Oracle ACFS , and Oracle Trace File Analyzer. |
STORAGE ( |
The STORAGE component patch is recommended. Updates the shared storage disk firmware and Controller Firmware for HDD, SSD, Controller, and Expander. |
DB ( |
The DATABASE component patch is optional. Updates the Oracle Database RDBMS stack. |
Note:
You must apply patch bundle components in this order:
SERVER (server
)
STORAGE (storage
)
DB (database
)
Oracle Database Appliance Patch Bundle Guidelines
You can carry out rolling upgrades with both the server
and DB
patches.
You must patch the server
component before patching the storage
and DB
components. You can defer patching the DB
component. You must schedule downtime and restart the system for the storage
patch. However, you can usually defer running the storage patch until a scheduled maintenance window. Patching the DB
component does not require system downtime.
Caution:
Apply the server
patch before you apply the storage
patch. Apply the server
patch to each node before you apply any other patches. You must restart each server node after it is patched. The server
patch restarts a server node. The storage
patch restarts both nodes.
If you have Oracle Database running using High Availability options such as Oracle Real Application Clusters (RAC), then there is no downtime required while the patches are being installed. Oracle Appliance Manager verifies that the host meets all prerequisites to prevent you from installing patches in the wrong order. For example, you cannot install the database
patch before you install the server
patch. When applied, the output displayed by the patch process advises you if the patch is being installed on one or both nodes. For older patches that only install on a single node, you must run the command oakcli update -patch
on the second node.
Supported and Recommended Appliance Manager Software Versions
The Oracle Database Appliance Release Notes include information about the latest Oracle Database Appliance patch bundle and the supported versions for the components. 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 1-2 Minimum Supported Appliance Manager Software Versions
Oracle Database Appliance Hardware Model | Minimum Supported Software Version |
---|---|
X5-2 |
12.1.2.5.0 |
X4-2 |
12.1.2.5.0 |
X3-2 |
12.1.2.5.0 |
V1 |
12.1.2.5.0 |
Understand how to patch an existing Oracle Database Appliance to the latest version.
Oracle Database Appliance Patch Bundle releases include software and firmware updates for Oracle Database Appliance.
Caution:
If you have Oracle Database 11.2 or 12.1 that is using Oracle Automatic Storage Management (Oracle ASM) and you want to upgrade to a higher release of Oracle Database, then you must be on at least Oracle Database Appliance 12.1.2.12.0 and Database Home 12.1.0.2.170814. Known issues with Oracle Automatic Storage Management (Oracle ASM) on earlier versions are preventing the REDO diskgroup from mounting for databases.
The upgrade path for Oracle Database 11.2 or 12.1 Oracle ASM is as follows:
If you are on Oracle Database Appliance version 12.1.2.6.0 or later, then upgrade to 12.1.2.12 or higher before upgrading your database.
If you are on Oracle Database Appliance version 12.1.2.5 or earlier, then upgrade to 12.1.2.6.0, and then upgrade again to 12.1.2.12 or higher before upgrading your database.
For all database versions and storage, if you are using Oracle Database Appliance version 12.1.2.5.0 or earlier, you must upgrade to 12.1.2.6.0 before upgrading to a higher version of Oracle Database Appliance. Changes introduced in the earlier release re-group the components and control the rolling of Oracle Database Appliance patching from one node to another.
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.
Oracle Database Appliance Patch Bundles are released on a quarterly schedule. Oracle Database Appliance Release Notes provide information about the latest Oracle Database Appliance Patch Bundle.
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.
Overview of the Patch Upgrade
Before patching Oracle Database Appliance, verify that a database is successfully deployed on Oracle Database Appliance. Run the oakcli orachk
command to confirm that the initial deployment completed successfully.
The patch bundle upgrade consists of the following steps:
Download the Oracle Database Appliance Patch Bundle from My Oracle Support.
Copy and unpack the patch bundle.
Verify components that require patching.
Patch the server.
(Optional) Patch the shared storage.
Patch Oracle Database.
Validate the patch update.
Related Topics
Review these topics to prepare for and install the Oracle Database Appliance Patch Bundle.
Topics:
oakcli unpack -package
to unpack the patch bundle.oakcli update -patch
) to patch the server. You can use automatic (rolling) or manual patching.oakcli show version -detail
to verify that all components of the Oracle Database Appliance patch installation are updated.Decide how you want to patch Oracle Database Appliance.
You can patch Oracle Database Appliance using either automatic rolling patching, or manual rolling patching. Review the steps for each procedure, and decide which option you want to use. For each option, the steps are the same, except for the server patch.
For both options, the storage patch requires a system restart of Oracle Database Appliance after completing the storage patch update. However, you can defer the update to a maintenance window.
Automatic Rolling Patching Option
The advantage of automatic rolling patching is that it is simple to do, in that you start the patch, and the patch process completes automatically. However, services and clients may experience delays during node restarts.
Automatic rolling patching consists of the following steps:
Download the Oracle Database Appliance Patch Bundle from My Oracle Support.
Copy and unpack the patch bundle to both Oracle Database Appliance nodes.
Verify the components that require patching.
From Node 0, start the patch. The automatic patch option performs the server patch update on Node 1, and restarts Node 1. It then patches the server on Node 0, and restarts Node 0.
(optional) Patch the shared storage components. This patch requires a system restart, but you can usually defer the restart.
Patch Oracle Databases. No restart is required.
Validate the Oracle Database and Oracle Grid Infrastructure patch installation.
Manual Rolling Patching Option
The advantage of manual rolling patching is that you can first migrate the services and clients from one node to another before the node restarts, and then manually patch the second node. This migration can be more graceful than a failover, so it can minimize interruptions to ongoing transactions.
Manual rolling patching consists of the following steps:
Download the Oracle Database Appliance Patch Bundle from My Oracle Support.
Copy and unpack the patch bundle to both Oracle Database Appliance nodes.
Verify the components that require patching.
Complete the patch manually in a two-step process.
Log in to Node 0, and patch the server on Node 0 by running the oakcli
patch command using the --local
option.
Wait until the patch operation completes, and Node 0 is available.
Log in to Node 1, and patch the server on Node 1 by running the oakcli
patch command using the --local
option.
(optional) Patch the shared storage. This patch requires a system restart, but you can usually defer the restart.
Patch Oracle Databases. No restart is required.
Validate the Oracle Database and Oracle Grid Infrastructure patch installation.
Use this procedure to download the Oracle Database Appliance Patch Bundle.
Caution:
If you have Oracle Database 11.2 or 12.1 that is using Oracle Automatic Storage Management (Oracle ASM) and you want to upgrade to a higher release of Oracle Database, then you must be on at least Oracle Database Appliance 12.1.2.12.0 and Database Home 12.1.0.2.170814. Known issues with Oracle Automatic Storage Management (Oracle ASM) on earlier versions are preventing the REDO diskgroup from mounting for databases.
The upgrade path for Oracle Database 11.2 or 12.1 Oracle ASM is as follows:
If you are on Oracle Database Appliance version 12.1.2.6.0 or later, then upgrade to 12.1.2.12 or higher before upgrading your database.
If you are on Oracle Database Appliance version 12.1.2.5 or earlier, then upgrade to 12.1.2.6.0, and then upgrade again to 12.1.2.12 or higher before upgrading your database.
For all database versions and storage, if you are using Oracle Database Appliance version 12.1.2.5.0 or earlier, you must upgrade to 12.1.2.6.0 before upgrading to a higher version of Oracle Database Appliance. Changes introduced in the earlier release re-group the components and control the rolling of Oracle Database Appliance patching from one node to another.
Caution:
Only use either an Oracle Database Appliance Patch Bundle, or if you are an SAP customer, an SAP patch bundle downloaded from the SAP Service Marketplace. 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.
Copy the patch to your server, and use oakcli unpack -package
to unpack the patch bundle.
On Oracle Database Appliance systems, all patching commands are executed as root
user.
After you copy the patch to the required location, run the command oakcli unpack -package
. This command extracts (unzips) the patch bundle, and copies the patch bundle contents into the patch repository. Use the following syntax to specify the complete path to the patch bundle file, where path
is the absolute path to the patch file:
# oakcli unpack -package absolute_package_name
Note:
Before patching Oracle Database Appliance, verify that a database is successfully deployed on Oracle Database Appliance. Run the commandoakcli orachk
to confirm that the initial deployment completed successfully.Use command-line interface commands to check for any problems before you start the patch upgrade and to verify the components that require patching.
Before installing the patch, run commands to verify that Oracle Database Appliance is ready to patch.
Use the oakcli validate
command on Node 0 to identify any possible problems in your environment, such as missing dependencies or other conflicts that can cause issues with patch installation. Conflicts can be introduced if you customize the standard configuration. Several validation parameters are available.
To review the components that require patching, run the oakcli update -patch release --verify
command. The output lists the components that require patching. If a component is listed as Up-to-date for the supported version that you indicate with the -ver
flag, then that component does not require patching.
Related Topics
Use Oracle Appliance Manager (oakcli update -patch
) to patch the server. You can use automatic (rolling) or manual patching.
Caution:
If you have Oracle Database 11.2 or 12.1 that is using Oracle Automatic Storage Management (Oracle ASM) and you want to upgrade to a higher release of Oracle Database, then you must be on at least Oracle Database Appliance 12.1.2.12.0 and Database Home 12.1.0.2.170814. Known issues with Oracle Automatic Storage Management (Oracle ASM) on earlier versions are preventing the REDO diskgroup from mounting for databases.
The upgrade path for Oracle Database 11.2 or 12.1 Oracle ASM is as follows:
If you are on Oracle Database Appliance version 12.1.2.6.0 or later, then upgrade to 12.1.2.12 or higher before upgrading your database.
If you are on Oracle Database Appliance version 12.1.2.5 or earlier, then upgrade to 12.1.2.6.0, and then upgrade again to 12.1.2.12 or higher before upgrading your database.
For all database versions and storage, if you are using Oracle Database Appliance version 12.1.2.5.0 or earlier, you must upgrade to 12.1.2.6.0 before upgrading to a higher version of Oracle Database Appliance. Changes introduced in the earlier release re-group the components and control the rolling of Oracle Database Appliance patching from one node to another.
Before patching, download the Oracle Database Appliance Patch Bundle from My Oracle Support, copy the patch to both nodes and unpack the bundles. Oracle recommends running commands to validate readiness for patching.
Note:
Before patching Oracle Database Appliance, verify that a database is successfully deployed on Oracle Database Appliance. Run theoakcli orachk
command to confirm that the initial deployment completed successfully.Automatic Server Patch Procedure
The automatic server patching process is a rolling upgrade that automatically patches Node 0 after patching Node 1. This automatic procedure enables Oracle Grid Infrastructure to continue to be up and running on one of the nodes during patching.
Download the Oracle Database Appliance server patch bundle from My Oracle Support to Node 0.
Log in to Node 0 as the root user.
Run the command oakcli update -patch version --server
, where version
is the Patch Bundle version. Either patch automatically or locally.
#/opt/oracle/oak/bin/oakcli update -patch 12.2.1.1.0 --server
This command patches the server on Node 1. After that patch update is complete, it then automatically patches Node 0
Observe the patch status reports.
As the patch runs, it displays output that advises you of the installation progress. Part of the server patch update requires node 1 to be restarted, then node 0 to be restarted. Wait until Node 0 shuts down and completes restarting before proceeding to the next step.
Manual Server Patch Procedure
You can manually control patching the nodes. The manual server patching process requires you to log in to a node and run Oracle Appliance Manager (oakcli) using a local node server patch update. After you complete the patch procedure on the first node, log into the second node, and patch the second node.
Download the Oracle Database Appliance server patch bundle from My Oracle Support to Node 0.
Log in to Node 0 as the root user.
Run the Oracle Appliance Manager command oakcli update -patch version --server --local
, where version
is the Patch Bundle version.
#/opt/oracle/oak/bin/oakcli update -patch 12.2.1.1.0 --server --local
The Oracle Appliance Manager command carries out the patch on Node 0. As the patch runs, it displays output that advises you of the installation progress.
Oracle Appliance Manager prompts you to restart the node. Restart the node, and wait until Node 0 shuts down and completes restarting before proceeding to the next step.
Log out of Node 0, and log in to Node 1 as the root user.
Run Oracle Appliance Manager on Node 1 using the --local
flag to patch the server.
For example:
#/opt/oracle/oak/bin/oakcli update -patch 12.2.1.1.0 --server --local
Oracle Appliance Manager prompts you to restart the node. Restart the node, and wait until Node 0 shuts down and completes restarting.
When both servers are patched and restarted, proceed to the next step.
Related Topics
Use this procedure to patch the shared storage now, or during a maintenance window.
Patching the storage requires downtime when shared components are being patched and might require rebooting the nodes.
The storage patch updates shared storage, including the Controller (Control_EXT
), SSD (SSD_SHARE
), HDD (HDD_SHARE
), and Expander. While not required, Oracle recommends patching storage.
Do not apply the storage patch until the server is successfully patched on both nodes.
Before patching, run the command oakcli update -patch release --verify
, where release
is the Patch Bundle version, and review the output:
If "Up-to-date" appears in the Proposed Patch Version for the Control_EXT, SSD_SHARE, and HDD_SHARE storage components, then you do not need to apply the storage patch.
If any of the storage components require updating, then stop the Oracle stack on both nodes before patching.
Start the storage patching command only on the first node (Node 0). The command patches storage for both nodes at the same time.
Apply the Oracle Database Appliance Patch Bundle to update Oracle Database on Node 0 and Node 1.
Run the command oakcli show version -detail
to verify that all components of the Oracle Database Appliance patch installation are updated.
oakcli show version -detail
, the output shows the installed version and that the supported versions are Up-to-date. If you unpack the patch bundle (oakcli unpack -pack) and then run the command oakcli show version -detail
before applying the patch, the output shows that the supported versions are No-update.To confirm that your Oracle Grid Infrastructure and Oracle Database software components are updated, run the following command:
# /opt/oracle/oak/bin/oakcli show version -detail Mon May 23 03:31:48 PST 2017 Reading the metadata. It takes a while... System Version Component Name Installed Version Supported Version -------------- --------------- ------------------ ----------------- 12.2.1.1.0 Controller_INT 4.650.00-7176 Up-to-date Controller_EXT 13.00.00.00 Up-to-date Expander 0291 Up-to-date SSD_SHARED { [ c2d20,c2d21,c2d22, A29A Up-to-date c2d23 ] [ c2d0,c2d1,c2d2,c2d A29A Up-to-date 3,c2d4,c2d5,c2d6,c2d 7,c2d8,c2d9,c2d10,c2 d11,c2d12,c2d13,c2d1 4,c2d15,c2d16,c2d17, c2d18,c2d19 ] } SSD_LOCAL A29A Up-to-date ILOM 4.0.0.22.r120818 Up-to-date BIOS 41017100 Up-to-date IPMI 1.8.12.4 Up-to-date HMP 2.4.1.0.4-1.el6.x86_64 Up-to-date OAK 12.2.1.1.0 Up-to-date OL 6.8 Up-to-date GI_HOME 12.1.0.2.170418(2400 Up-to-date 6101,23854735) DB_HOME 12.1.0.2.170418(2305 Up-to-date 4246,23054327)
Reimage Oracle Database Appliance to perform a bare metal restore of Oracle Database Appliance.
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.
Use the OS ISO Image to restore the OS to the "shipped from factory" state. Use only when necessary. 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.
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.
Re-imaging with older release of Oracle Database Appliance software does not rollback the firmware version.
Use the Oracle Integrated Lights Out Manager (ILOM) interface to reimage the Oracle Database Appliance node.
Download the Oracle Database Appliance Bare Metal ISO image on your local machine.
Download patch 12999313 for the Oracle Database Appliance Bare Metal ISO Image to prepare for a bare metal restore for Oracle Database Appliance.
Related Topics
Re-image Oracle Database Appliance to perform a bare metal restore of Oracle Database Appliance.
Bare metal restore uses Oracle Integrated Lights Out Manager (ILOM) to reimage the Oracle Database Appliance node. For Oracle Database Appliance models earlier than X5-2, go to My Oracle Support and locate MOS Note 1373599.1.
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.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.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.
Related Topics