6 Patching Oracle Database Appliance
To keep Oracle Database Appliance running with the latest software, check for and apply Oracle Database Appliance patch bundles when they are released.
- About Patching Oracle Database Appliance
Use the Oracle Database Appliance Patch Bundle to patch your appliance. - About Patching Pre-Checks
Patching pre-checks are designed to detect and flag problems that might be encountered during patching. - Minimizing Downtime When Patching Oracle Database Appliance
Understand best practices to minimize downtime when you apply patches to your Oracle Database Appliance deployment. - Patching Oracle Database Appliance Bare Metal Systems Using the Command-Line
Follow these steps to apply patches to your Oracle Database Appliance bare metal deployment and existing Oracle Database homes, using CLI commands. - Patching Oracle Database Appliance Bare Metal Systems Using the Browser User Interface
Upload the Oracle Database Appliance Server Patch to the patch repository, deploy the patch bundle using the Browser User Interface, and then update the DCS agent and components using CLI commands. - Updating Oracle Database Appliance Repository with Database Clone Files For Bare Metal Systems
Follow these steps to update the Oracle Database Appliance repository with Oracle Database clone files for the latest release using CLI commands. - Patching Existing Database Homes on Bare Metal Systems Using the Browser User Interface
Use the Browser User Interface to patch database homes to the latest release on bare metal systems. - Patching Non-Provisioned Oracle Database Appliance Systems
Oracle Database Appliance supports patching of non-provisioned single-node or high availablity systems by runningodacli update-server
command. - Applying Additional Patches and Updates on Bare Metal Systems
Configure additional patch repositories and patch your operating system and databases to ensure that your deployment has the latest updates and security fixes. - Cleaning Up the Patch Repository
Use the Browser User Interface or Command Line Interface to delete obsolete or old patches from the repository. - About Upgrading to a Different Database Home
Understand how to upgrade to a different database home using either the Browser User Interface orodacli
commands.
About Patching Oracle Database Appliance
Use the Oracle Database Appliance Patch Bundle to patch your appliance.
Patches offer new features and may improve the functionality of existing features.
About Out of Place Patching
See Also:
Oracle Fleet Patching and Provisioning Administrator's Guide and Oracle Clusterware Administrator's Guide in the Oracle Database 19c Documentation LibraryAbout MySQL Server and DCS Agent
Starting with Oracle Database Appliance release 19.10, DCS Agent uses
MySQL server as its metadata store. MySQL server is automatically installed and
configured, during provisioning, when creating the appliance. Similarly, during
patching, the odacli update-dcscomponents
command automatically
installs and configures MySQL server. MySQL server processes do not run with
root
operating system user account. Instead, MySQL server
processes run with a new operating system user account called
odamysql
. Note that the odamysql
operating
system user is created only for ownership purposes and the odamysql
user account owns only the MySQL directories. The odamysql
operating system user cannot log into the appliance. The odamysql
operating system user account for MySQL ensures role separation between the user
owning Oracle databases on the appliance and the metadata used for DCS
operations.
About Oracle Database Appliance Patch Bundles
The Oracle Database Appliance Patch Bundle contains the latest patches for DCS Admin, DCS Components, OAK, Oracle ILOM, firmware, Oracle Grid Infrastructure, Oracle Database homes, enhancements, and fixes.
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. See the Oracle Database Appliance Release Notes for the upgrade paths.
Caution:
Do not patch Oracle Database Appliance using generic patches for Oracle Grid Infrastructure 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 the metadata maintained by Oracle Database Appliance is not updated, and you cannot complete future patch updates. If you apply out-of-cycle Oracle Database Release Update (RU), then ensure that you also follow the recommendations described in the Readme for the RU.The patch bundle provides all relevant patches for the entire system, including the following:
-
BIOS
-
Hardware drivers
-
Hardware Management Pack (HMP) and firmware drivers for various components
-
Oracle Appliance Manager
-
Oracle Linux
-
Oracle VM Server
-
Java Runtime Environment (JRE)
-
Oracle Integrated Lights Out Manager (Oracle ILOM)
-
Oracle Auto Service Request (Oracle ASR)
-
Oracle Intelligent Platform Management Interface (Oracle IPMI)
-
Network Card Patches for relevant hardware models
About 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 RDMA packages (oracle-rdma-release)
For storage, do not apply any RPM updates.
Parent topic: Patching Oracle Database Appliance
About Patching Pre-Checks
Patching pre-checks are designed to detect and flag problems that might be encountered during patching.
The pre-checks view the state of the appliance, including the version and hardware specific upgrades, verify that the necessary conditions and checks are complete before attempting an upgrade, and identify conditions that might cause an upgrade to fail. You can avoid potential patching problems by correcting the conditions and resolving the issues before applying the patch.
The pre-checks commands are available on Oracle Database Appliance release 12.2.1.2.0 or later. Update the DCS agent to support the pre-checks commands.
Components Verified by Patching Pre-Checks
Check | Component Verified |
---|---|
System patching pre-checks |
Checks that the DCS agent is online on all nodes Checks that there is sufficient space for the update Validates the minimum agent version and validates the patching tag Confirms that a valid patch is in the repository and calculates the patch bundle |
Server patching pre-checks |
Confirms that Oracle Grid Infrastructure patch is installed Confirms that Oracle Clusterware is running on all nodes Checks whether the clone is registered Checks whether the clone file is present in the repository Checks the available disk space Confirms that the yum repository directory exists Performs a Performs a test (dry run) yum update to check for dependencies in the RPMs |
DBHome patching pre-checks |
Confirms that the Oracle Grid Infrastructure is installed Confirms that Oracle Clusterware is running on all nodes Confirms that the Oracle Grid Infrastructure is upgraded before upgrading other components Validates that there is sufficient space available in local mount Checks whether the clone is registered Checks whether the clone file is present in the repository Performs a patch conflict check and determines if a rollback of database patches is required |
Storage pre-checks |
Validates storage patch location and tag Validates Oracle ASM disk groups status |
Parent topic: Patching Oracle Database Appliance
Minimizing Downtime When Patching Oracle Database Appliance
Understand best practices to minimize downtime when you apply patches to your Oracle Database Appliance deployment.
Oracle Database Appliance does not apply patches in a rolling manner for high-availability systems. However, there are recommendations to minimize downtime during patching.
Recommendations for Minimizing Downtime During Patching
- To minimize database patching downtime, it is recommended that you use Oracle RAC or Oracle RAC One Node on an Oracle Database Appliance high-availability system.
- If available, use Oracle Data Guard and patch the standby system first. After you patch the standby system, switch the workload to the standby system, patch the primary system, and then switch the workload back to the primary system.
- Always use Oracle Database Appliance Backup and Recovery (ODABR) to back up the system disks to ensure easy restore, if the patching operation fails. ODABR restores the system disk to pre-patching state.
- The
odacli update-storage
command has a--rolling
option for storage devices (SSD, HDD, NVMe) to minimize patching downtime. There could be other shared storage component firmware that require a system restart. Oracle Database Appliance storage patching can be deferred, but it is not recommended.
See Also:
Oracle Database High Availability Overview and Best Practices Guide in the Oracle Database 19c Documentation LibraryParent topic: Patching Oracle Database Appliance
Patching Oracle Database Appliance Bare Metal Systems Using the Command-Line
Follow these steps to apply patches to your Oracle Database Appliance bare metal deployment and existing Oracle Database homes, using CLI commands.
Note:
Run the commands in this topic in the same order as documented. Run theodacli
update-dcsadmin
, odacli update-dcscomponents
, and
odacli update-dcsagent
commands before running the
odacli update-server
command.
Related Topics
Parent topic: Patching Oracle Database Appliance
Patching Oracle Database Appliance Bare Metal Systems Using the Browser User Interface
Upload the Oracle Database Appliance Server Patch to the patch repository, deploy the patch bundle using the Browser User Interface, and then update the DCS agent and components using CLI commands.
Updating the Patch Repository Using the Browser User Interface
-
Download the Oracle Database Appliance patches from My Oracle Support and save them in a directory on the appliance. See the Oracle Database Appliance Release Notes for a list of available patches and links to download the patches.
-
Log into the Browser User Interface with the oda-admin user name and password.
https://Node0–host-ip-address:7093/mgmt/index.html
-
Click Patch Manager.
-
In the Update Patch Repository page, enter the absolute file path and patch name, then click Update Repository to start the update repository job. You can list more than one file to update to the repository with a comma separated list, without spaces, or you can update each file, one at a time.
-
Click Activity to monitor the progress. When the job completes successfully, the Patch Repository is updated.
Updating the DCS Admin and DCS Components After Updating the Repository and Before Patching
Before patching your appliance using the Browser User Interface, you must update the DCS admin and DCS components manually, through CLI commands.
Follow these steps:
- Update DCS
admin:
[root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-dcsadmin -v 19.11.0.0.0
- Confirm that the update is
successful:
[root@oda1 opt]# /opt/oracle/dcs/bin/odacli describe-job -i job_ID
- Update the DCS
components:
[root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-dcscomponents -v 19.11.0.0.0
If the DCS components are updated, then the message"status" : "Success"
is displayed on the command line. For failed updates, fix the error and then proceed with the update.Note:
You must log into the Browser User Interface again after running theodacli update-dcscomponents
command.
Running Patching Prechecks and Patching Agent, Server, and Storage Using the Browser User Interface
-
Do not have any jobs running or pending during the update window.
-
Click the Appliance tab, and then click Patch Manager in the Browser User Interface.
-
Wait for the Component Details to load. If you just updated the Patch Repository, click Refresh in the Component Details section of the page.
After the patch is uploaded to the Patch Repository, the Component Details on the page are updated with the Installed Version and Available Version for each component.
-
On the Patch Manager page, click Refresh to refresh the Component Details. Select Update Server, then click Apply Patch to begin the job to patch the server components. Select Precheck to run patching prechecks. You must run the patching prechecks before updating the server and other components.
The DCS agent is automatically updated whenever the Server or Storage components are updated.
When the job finishes, go to the next step. Click Activity for job status.
-
On the Patch Manager page, click Refresh to refresh the Component Details. Select Update Storage, then click Apply Patch to begin the job to patch the storage components. Select Precheck if you want to run patching prechecks.
For high-availability environment, you can select the Rolling check box to perform rolling patching of storage components.
-
Click Activity to monitor the progress, and verify that the job completes successfully.
All patching-related information is logged in the dcs-agent
log file at /opt/oracle/dcs/log/dcs-agent.log
.
Parent topic: Patching Oracle Database Appliance
Updating Oracle Database Appliance Repository with Database Clone Files For Bare Metal Systems
Follow these steps to update the Oracle Database Appliance repository with Oracle Database clone files for the latest release using CLI commands.
Parent topic: Patching Oracle Database Appliance
Patching Existing Database Homes on Bare Metal Systems Using the Browser User Interface
Use the Browser User Interface to patch database homes to the latest release on bare metal systems.
Patching Non-Provisioned Oracle Database Appliance Systems
Oracle Database Appliance supports patching of non-provisioned single-node or
high availablity systems by running odacli update-server
command.
odacli create-appliance
command by reimaging the system using the
bare metal ISO image of Oracle Database release 19.10 or later. Then patch the system
with the server patches of the same release as the bare metal ISO image by running the
odacli update-server
command. When you reimage your system, the DCS
infrastructure is updated automatically.
- Reimage the Oracle Database Appliance using the bare metal ISO image for Oracle Database Appliance release 19.10 or later.
- Update the repository with the server patch for the Oracle Database Appliance release you want to patch to, for example 19.10 or later.
- For running
odacli update-server
on Oracle Database Appliance imaged with ISO of release 19.10:odacli update-server -v 19.10.0.0.0 -sko -f
For Oracle Database Appliance release 19.10, you can use the
-f
option to override precheck failures and complete the server patching. - For running
odacli update-server
on Oracle Database Appliance imaged with ISO of release 19.11 or later, follow these steps:- Create the pre-patch report for the
odacli update-server
command by specifying the-s
option.odacli create-prepatchreport -v 19.11.0.0.0 -s
Fix the warnings and errors mentioned in the report and proceed with the server patching.
- Update the
server:
odacli update-server -v 19.11.0.0.0 -f
For Oracle Database Appliance release 19.11, you can use the
-sko
option to skip ORAchk failures and proceed with the server patching, and the-f
option to override precheck failures and complete the server patching.
- Create the pre-patch report for the
Related Topics
Parent topic: Patching Oracle Database Appliance
Applying Additional Patches and Updates on Bare Metal Systems
Configure additional patch repositories and patch your operating system and databases to ensure that your deployment has the latest updates and security fixes.
- Enabling Kernel Updates
Oracle Ksplice enables you to update your systems with the latest kernel security and bug fix updates. - Applying Out-of-Cycle Database Patches
The out-of-cycle patching feature enables administrators to patch databases in the Oracle Database Appliance deployment with the latest Oracle Database Release Update, outside of the Oracle Database Appliance releases.
Parent topic: Patching Oracle Database Appliance
Enabling Kernel Updates
Oracle Ksplice enables you to update your systems with the latest kernel security and bug fix updates.
See Also:
Oracle Linux Ksplice User's Guide for information about configuring Oracle Ksplice at:https://docs.oracle.com/cd/E37670_01/E39380/html/ksplice-enhanced-offline.html
Applying Out-of-Cycle Database Patches
The out-of-cycle patching feature enables administrators to patch databases in the Oracle Database Appliance deployment with the latest Oracle Database Release Update, outside of the Oracle Database Appliance releases.
Note:
The OPatch commands and procedures described in this topic are examples, and may need modifications based on a specific Oracle Database Release Update (RU). Always refer to the Readme of the Oracle Database Release Update (RU) for additional commands and steps.Note:
It is strongly recommended that you patch your deployment through the Oracle Database Appliance releases, whenever possible.Note:
You can apply out-of-cycle patches to both baremetal and Virtualized Platform deployments using this procedure.Using OPatchauto to Manually Patch Oracle Database Release 12c and Later
- Confirm that the
dcs-agent
and other components are updated to the latest release.# odacli describe-component # odacli list-dbhomes
- Update OPatch to the latest version, if available:
- Download the latest OPatch version from My Oracle Support.
- Copy the files to the local host and extract them to the
ORACLE_HOME/OPatch
directory. - Update the OPatch tool as
oracle
user./bin/rm -rf $ORACLE_HOME/OPatch/ su - oracle -c /usr/bin/unzip -q -o OPatch_zip_location/p6880880_122010_Linux-x86-64.zip -d $ORACLE_HOME
- Download the latest database patches from My Oracle Support and
copy the files to the local
host.
scp patchfilename root@hostname:directory
- Unzip patches to an empty directory, for example,
/tmp/patchesDir
asoracle
user.This creates sub directories under
/tmp/patchesDir
with bug numbers. If the patch you are applying is a Release Update (RU), then the patch directory has multiple sub-directories./usr/bin/unzip -o location_of_patches/p29301631_180000_Linux-x86-64.zip -d /tmp/patchesDir
- For Oracle Database Appliance High-Availability deployments, set up SSH Keys for secure connection.
- Analyze the
patches.
$ORACLE_HOME/OPatch/opatchauto apply directory_with_patches_extracted -analyze -oh $ORALCE_HOME -log /tmp/opatchAutoAnalyzePatch.log
- As
root
user, apply the patches.$ORACLE_HOME/OPatch/opatchauto apply directory_to_extract_patches -oh $ORACLE_HOME -inplace
- When patching is completed on both nodes, run
utlrp.sql
andcatcon.pl
scripts to recompile invalid objects in the database. - Update the registry to ensure that system component values are
registered.
# odacli update-registry -n dbhome -f
Cleaning Up the Patch Repository
Use the Browser User Interface or Command Line Interface to delete obsolete or old patches from the repository.
About Cleaning Up the Patch Repository
After patching Oracle Database Appliance with the latest patches, old unused clone files may remain and consume space in the repository. Cleanup repository deletes the unused clone/patch files to reclaim space. You can clean up the repository using the Browser User Interface or ODACLI commands.
Cleaning Up the Patch Repository Using ODACLI command
# odacli cleanup-patchrepo [-cl clones] | [-v version [-comp component]]| [-l local|-n NodeID]
Specify the clone file names and the node from which you want to delete the old patches.
For details about the command options, see the chapter Oracle Database Appliance Command-Line Interface.
Cleaning Up the Patch Repository Using the Browser User Interface
- In the Browser User Interface, click Patch Manager.
- Click the Cleanup Repository tab, and then click Refresh to list the available patches in the repository.
- Select the Components, such as old Oracle Grid Infrastructure or Oracle Database clone files that you want to clean up from the repository, and the Patch Version, for example, an older release of Oracle Database Appliance.
- Click Cleanup Clone Files to clean up clone files for selected
components from the repository at
/opt/oracle/oak/pkgrepos/orapkgs/clones/
. - Click Cleanup Repository to submit the cleanup repository job.
- Click Activity to monitor the progress. When the job completes successfully, the Patch Repository is updated.
Related Topics
Parent topic: Patching Oracle Database Appliance
About Upgrading to a Different Database Home
Understand how to upgrade to a different database home using either the
Browser User Interface or odacli
commands.
Prerequisites for Upgrading Database Homes
- Oracle Database 18c to 19c
- Oracle Database 12.2 to 19c
- Oracle Database 12.1 to 19c
- Oracle Database 12.2 to 18c
- Oracle Database 12.1 to 18c
- Oracle Database 12.1 to 12.2
Before upgrading to a different database home, upload the Oracle Database clone files for the database version, to the repository, and then create the database home. See Patching Oracle Database Appliance Using the CLI for the procedure to update the repository with the latest Oracle Database clone files.
About Upgrading Database Homes Using the Browser User Interface
Follow these steps to upgrade to a different database home using the Browser User Interface.
- Log into the Browser User Interface with the
oda-admin user name and
password.
https://Node0–host-ip-address:7093/mgmt/index.html
- Click the Database tab, and then select a database, click Actions, and then click Upgrade.
- Verify that the database upgrade job completes successfully.
About Upgrading Database Homes Using the Command-Line Interface
Run the following command to upgrade to a different database home using the CLI:
odacli upgrade-database -i Comma separated list of database ids -from source dbhome id -to destination dbhome id [-j] [-h]
For more information about the options for the upgrade-database
command, see the chapter Oracle Database Appliance Command-Line
Interface.
Related Topics
Parent topic: Patching Oracle Database Appliance