1. X11 Deployment and User’s Guide
  2. Patching Oracle Database Appliance

8 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.

Patches offer new features and may improve the functionality of existing features.

About Out of Place Patching

Starting with Oracle Database Appliance release 19.11, Oracle Database Appliance uses the out-of-place patching model. This means that a new software Oracle home is created when patching an Oracle Grid Infrastructure or Oracle Database home. Starting with Oracle Database Appliance release 19.11, the patches for Oracle Grid Infrastructure and Oracle Database are available as images. All procedures remain the same.

About 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, 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:

  • Oracle Database Appliance server

  • BIOS

  • Hardware drivers

  • Hardware Management Pack (HMP) and firmware drivers for various components

  • Oracle Appliance Manager

  • Oracle Linux

  • 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 Oracle Database Appliance. 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 Oracle Database Appliance, 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 Prechecks

Patching prechecks are designed to detect and flag problems that might be encountered during patching.

The prechecks 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 prechecks commands are available on Oracle Database Appliance release 12.2.1.2.0 or later. Update the DCS Agent to ensure that the latest updated prechecks are available when you run these commands.

Components Verified by Patching Prechecks

Check Component Verified
System patching prechecks

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
Validate Nexus Reset Estes-Ext Failed
This server patching precheck is displayed for ORCL-EXT-SAS3 controller with model number 0x0097. This precheck verifies that controllers NVDATA is updated to 0e.01.00.0d version. If Estes-Ext is not updated to I_T Nexus Reset, then an error is displayed.
SAS3 controller requires Nexus Reset. 
DCS-10293: Current System has ORCL-EXT-SAS3 controller 
which requires the firmware update to enable NEXUS RESET. 
To perform the firmware update, run 
/opt/oracle/oak/pkgrepos/ 
firmwarecontroller/lsilogic/0x0097/ 
16.00.08.00/it_nexus_reset.sh 
on both nodes.
Server patching prechecks
For operating system:
  • Validates supported versions
  • Validates minimum supported versions
  • Validates patching tag
  • Validates whether patch location is available
  • Verifies OS patch
  • Validates command execution
For Oracle ILOM:
  • Validates supported versions
  • Validates minimum supported versions
  • Validates patching tag
  • Validates whether patch location is available
  • Checks for Oracle ILOM patch version
  • Validates Patch location
  • Validates command execution
  • Validates connectivity to Oracle ILOM
For Oracle Grid Infrastructure:
  • Validates supported Oracle Grid Infrastructure versions
  • Validates available space
  • Validates whether Oracle Clusterware is running
  • Validates patching tag
  • Validates whether system is provisioned
  • Validates whether Oracle ASM is online
  • Validates the minimum agent version
  • Validates the central inventory
  • Validates patching locks
  • Validates whether clones location exists
  • Validates DB start dependencies
  • Validates DB stop dependencies
  • Validates command execution
For Oracle ORAchk:
  • Runs the ORAchk tool that performs operating system level prechecks.
  • Validates command execution
For server:
  • Validates whether server patching can be performed in local mode or not
  • Validates command execution

Confirms that the bare metal system is upgraded, in the case of DB systems.

Verifies and confirms that the database start/stop dependencies are correct.

Confirms that patching locks are not present.

Verifies that the central inventory is accurate.
Database home patching prechecks

Confirms that Oracle Grid Infrastructure is installed

Confirms that the DCS Agent is at the required version

Confirms that Oracle Clusterware is running on all nodes

Confirms that Oracle Grid Infrastructure is upgraded

Validates that there is sufficient disk space available

Checks if the disk group for database homes on Oracle ACFS is configured

Checks whether the clone file is present in the repository

Checks whether the /u01/app/odaorabase directory exists. If the directory exists, then the check confirms that there is a valid symbolic link.

Database home patching with out-of-place patching prechecks

The check creates a database home and verifies that all databases can be moved from the source home to new home.

This check validates that the --local option can be used for the database home.

Storage prechecks

Validates storage patch location and tag

Validates patching location and tag

Validates command execution

Validates Oracle ASM disk groups status

Validates rolling patch (for high-availability deployment)

Parent topic: Patching Oracle Database Appliance

About Enabling NUMA on Oracle Database Appliance

Understand how you can enable NUMA on bare metal, KVM, and DB Systems on Oracle Database Appliance.

NUMA (Non-Uniform Memory Access) can help facilitate efficient use of the underlying NUMA hardware. On Oracle Database Appliance, you can enable NUMA for databases on bare metal and DB systems, CPU pools, and for KVM applications.

About Enabling NUMA During Provisioning of Oracle Database Appliance

When you provision Oracle Database Appliance with release 19.26, NUMA is automatically enabled on the database, DB system and CPU pools. Hence, when you create a database, DB system, or CPU pool on an Oracle Database Appliance release 19.26 deployment, NUMA is automatically enabled and no additional configuration is required. NUMA is not enabled by default for application VMs.

About Enabling NUMA After Patching Oracle Database Appliance

NUMA is enabled by default starting with Oracle Database Appliance release 19.12. When you patch to Oracle Database Appliance release 19.26 from 19.11 or earlier, the odacli update-server command sets NUMA at the system level. New databases created after patching are NUMA-enabled. For existing databases, enable NUMA by running the command alter system set "enable_numa_support"=true on the database.

After patching the bare metal system to release 19.26 from 19.11 or earlier, as a one-time activity, you must run the command odacli remap-cpupools to enable NUMA on all existing CPU pools (BM, VM, dbsystem).

For existing DB systems, run the command odacli modify-dbsystem --enable-numa to enable NUMA for the dbsystem and the database of the DB system.

NUMA is not enabled by default for application VMs. For new and existing application VMs, run the command odacli modify-vm --enable-numa to enable NUMA for the VM configuration. You must also enable NUMA for the components inside the VM such as operating system and application running inside the VM. The command odacli modify-dbsystem --enable-numa is only supported on application VMs with even number of CPU cores so that CPU cores can be evenly distributed to NUMA nodes. In Oracle Database Appliance, one CPUcore is equal to 2 vCPU.

See the topic Patching Oracle Database Appliance Bare Metal Systems Using the Command-Line for more details about the steps to patch your deployment and enable NUMA.

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.

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. For more information, see Patching Oracle Data Guard Databases on Oracle Database Appliance in this guide.
  • 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 and HDD) to minimize patching downtime. There could be other shared storage component firmware that require a system restart and do not support rolling. Oracle Database Appliance storage patching can be deferred, but it is not recommended. Note that the --rolling option cannot be used with the odacli update-storage command on single-node Oracle Database Appliance systems.

Minimizing Downtime using the --local Option During Patching

To minimize downtime, use the --local option with the odacli update-server and odacli update-dbhome commands. Update the DCS components and then run the odacli create-prepatchreport command. There is no downtime during the prepatch process. After analyzing the prepatch report, use the --local option to continue patching Oracle Database Appliance.

Note:

Before patching databases, ensure that the server patching operation on both nodes has completed successfully. Do not run the odacli update-dbhome and odacli update-database commands before the odacli update-server operation completes successfully on both nodes.

See Also:

Oracle Database High Availability Overview and Best Practices Guide in the Oracle Database 19c Documentation Library

Parent topic: Patching Oracle Database Appliance

About Updating Databases and Database Homes

Understand how to update a database and database home using either the Browser User Interface or odacli commands.

About Updating Databases and Database Homes

Oracle Database Appliance provides the following options to patch or update databases and database homes:
  • Patch or update each database home. The database home is patched out-of-place. When patching database home, Oracle Database Appliance automatically provisions a destination database home if needed, records the source database home, target version, and destination database home mapping in the metadata repository, and then moves all databases running in the source database home to the destination database home. Use the odacli update-dbhome command or the BUI to patch all databases from a single source database home to a single destination database home. Use this option if there are no constraints on your system for space usage or for provisioning a new database home.
  • Patch or update selected databases in a database home to a specific database home. You must specify the target database and destination database home when patching. You can use the odacli update-database command or the BUI to patch a specific database to a specific database home or to control when and how many database homes are provisioned. Using the update-database workflow also provides an option to run the operation again, if the patching operation failed. The abort and revert options available with the update-database workflow are not supported when the target database is a single-instance database.

Before patching the database or 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.

Important:

The odacli update-database command that enabled association of a backup configuration with database was deprecated in Oracle Database Appliance release 19.6. Starting with Oracle Database Appliance release 19.17, the odacli update-database command enables database patching and is similar to the patching functionality that the odacli update-dbhome command provides, with a few differences as described in the Oracle Database Appliance Deployment Guide for your hardware model.

Before you run the odacli update-dbhome command, you must create the prepatch report for the database home by running the command odacli create-prepatchreport -d. Similarly, before you run the odacli update-database command, you must create the prepatch report either for the source database home or target database by running the command odacli create-prepatchreport -d or odacli create-prepatchreport -db respectively. The source and destination database homes must be consistent in the prepatch report and when specifying them in the odacli update-database command. If you do not create the prepatch report before the patch operation, then the odacli update-database and odacli update-dbhome commands fail with an error message prompting you to run the patching pre-checks.

For more information about the options for the update-dbhome and odacli update-database commands, see the chapter Oracle Database Appliance Command-Line Interface.

Parent topic: Patching Oracle Database Appliance

Updating ESTES-EXT Firmware Before Patching Oracle Database Appliance Server

Update TMT (Task Management Reset Type) for Estes-Ext before you patch the Oracle Database Appliance server.

Before you patch your Oracle Database Appliance deployment and your existing database homes to the current release, you must update I_T Target Reset of Estes-Ext to I_T Nexus Reset. This update is not included in the regular firmware update. Run the /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/it_nexus_reset.sh script to complete this update before you perform server patching. The patching precheck verifies that controllers NVDATA is updated to 0e.01.00.0d version. If Estes-Ext is not updated to I_T Nexus Reset, then an error is displayed.
Follow these steps:
  1. Ensure that you update the repository with the server zip file for Oracle Database Appliance release 19.26.
  2. Shut down Oracle Grid Infrastructure, Oracle Database, and all applications before you run the update. Ensure that Oracle Clusterware is not running.
  3. Before you patch the Oracle Database Appliance server, run the following command:
    #  /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/sas3flash -listall
Avago Technologies SAS3 Flash Utility
Version 17.00.00.00 (2018.04.02)
Copyright 2008-2018 Avago Technologies. All rights reserved.
 
        Adapter Selected is a Avago SAS: SAS3008(C0)
 
Num   Ctlr            FW Ver        NVDATA        x86-BIOS         PCI Addr
----------------------------------------------------------------------------
 
0  SAS3008(C0)  16.00.08.00    0e.01.00.0c    08.37.00.00     00:3b:00:00
1  SAS3008(C0)  16.00.08.00    0e.01.00.0c    08.37.00.00     00:e3:00:00
 
        Finished Processing Commands Successfully.
        Exiting SAS3Flash.
  4. If the system is already up-to-date, then the following message is displayed:
    #   /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/it_nexus_reset.sh
The I_T Nexus Reset is enabled for the SAS3 controller(s) in this system. No action required.
  5. Run the script.
    # /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/it_nexus_reset.sh

    Use the -force option to run the script without being prompted for answers.

  6. If Oracle Clusterware is running, then the following error is displayed:
    # /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/it_nexus_reset.sh
CRS status found as up and running in this node, please SHUTDOWN the CRS and retry running this script
  7. Shut down Oracle Clusterware and run the script again:
    # /u01/app/19.26.0.0/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
 
# /u01/app/19.26.0.0/grid/bin/crsctl stop crs
...
...
...
 
# /u01/app/19.26.0.0/grid/bin/crsctl check crs
CRS-4639: Could not contact Oracle High Availability Services
 
# /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/it_nexus_reset.sh
##################################################################
Running it_nexus_reset.sh script is going to perform nexus reset
  and does DEEP POWER CYCLE of iLOM
Please enter 'yes' to confirm the Nexus Reset operation,
  enter 'no' to cancel.
##################################################################
Do you wish to continue and rest nexus adapter? (yes/no): yes
Trying perform I_T Nexus Reset
Updating Adapter with index: 0
running /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/sas3flash -c 0 -f /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/Oracle_SAS9300-8e_it_p_000D_ph16.04_nexus.bin
Avago Technologies SAS3 Flash Utility
Version 17.00.00.00 (2018.04.02)
Copyright 2008-2018 Avago Technologies. All rights reserved.
 
        Adapter Selected is a Avago SAS: SAS3008(C0)
 
        Executing Operation: Flash Firmware Image
 
                Firmware Image has a Valid Checksum.
                Firmware Version 16.00.08.00
                Firmware Image compatible with Controller.
 
                Valid NVDATA Image found.
                NVDATA Major Version 0e.01
                Checking for a compatible NVData image...
 
                NVDATA Device ID and Chip Revision match verified.
                NVDATA SubSystem Vendor and SubSystem Device ID match verified.
                NVDATA Versions Compatible.
                Valid Initialization Image verified.
                Valid BootLoader Image verified.
 
                Beginning Firmware Download...
                Firmware Download Successful.
 
                Verifying Download...
 
                Firmware Flash Successful.
 
                Resetting Adapter...
                Adapter Successfully Reset.
 
                NVDATA Version 0e.01.00.0d
        Finished Processing Commands Successfully.
        Exiting SAS3Flash.
running /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/sas3flash -c 0 -o -e 3
Avago Technologies SAS3 Flash Utility
Version 17.00.00.00 (2018.04.02)
Copyright 2008-2018 Avago Technologies. All rights reserved.
 
        Advanced Mode Set
 
        Adapter Selected is a Avago SAS: SAS3008(C0)
 
        Executing Operation: Erase Flash
 
        Erasing Persistent Configuration Pages Region...
 
        Erase Flash Operation Successful!
 
        Finished Processing Commands Successfully.
        Exiting SAS3Flash.
running /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/sas3flash -c 0 -b /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/mpt3x64.rom
Avago Technologies SAS3 Flash Utility
Version 17.00.00.00 (2018.04.02)
Copyright 2008-2018 Avago Technologies. All rights reserved.
 
        Adapter Selected is a Avago SAS: SAS3008(C0)
 
        Executing Operation: Flash BIOS Image
 
                Validating BIOS Image...
 
                BIOS Header Signature is Valid
 
                BIOS Image has a Valid Checksum.
 
                BIOS PCI Structure Signature Valid.
 
                BIOS Image Compatible with the SAS Controller.
 
                Attempting to Flash BIOS Image...
 
                Verifying Download...
 
                Flash BIOS Image Successful.
 
        Finished Processing Commands Successfully.
        Exiting SAS3Flash.
running /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/sas3flash -c 0 -b /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/mptsas3.rom
Avago Technologies SAS3 Flash Utility
Version 17.00.00.00 (2018.04.02)
Copyright 2008-2018 Avago Technologies. All rights reserved.
 
        Adapter Selected is a Avago SAS: SAS3008(C0)
 
        Executing Operation: Flash BIOS Image
 
                Validating BIOS Image...
 
                BIOS Header Signature is Valid
 
                BIOS Image has a Valid Checksum.
 
                BIOS PCI Structure Signature Valid.
 
                BIOS Image Compatible with the SAS Controller.
 
                Attempting to Flash BIOS Image...
 
                Verifying Download...
 
                Flash BIOS Image Successful.
 
        Finished Processing Commands Successfully.
        Exiting SAS3Flash.
running /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/sas3flash -c 0 -b /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/lsisas3f.rom
Avago Technologies SAS3 Flash Utility
Version 17.00.00.00 (2018.04.02)
Copyright 2008-2018 Avago Technologies. All rights reserved.
 
        Adapter Selected is a Avago SAS: SAS3008(C0)
 
        Executing Operation: Flash BIOS Image
 
                Validating BIOS Image...
 
                BIOS Header Signature is Valid
 
                BIOS Image has a Valid Checksum.
 
                BIOS PCI Structure Signature Valid.
 
                BIOS Image Compatible with the SAS Controller.
 
                Attempting to Flash BIOS Image...
 
                Verifying Download...
 
                Flash BIOS Image Successful.
 
        Finished Processing Commands Successfully.
        Exiting SAS3Flash.
Updating Adapter with index: 1
running /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/sas3flash -c 1 -f /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/Oracle_SAS9300-8e_it_p_000D_ph16.04_nexus.bin
Avago Technologies SAS3 Flash Utility
Version 17.00.00.00 (2018.04.02)
Copyright 2008-2018 Avago Technologies. All rights reserved.
 
        Adapter Selected is a Avago SAS: SAS3008(C0)
 
        Executing Operation: Flash Firmware Image
 
                Firmware Image has a Valid Checksum.
                Firmware Version 16.00.08.00
                Firmware Image compatible with Controller.
 
                Valid NVDATA Image found.
                NVDATA Major Version 0e.01
                Checking for a compatible NVData image...
 
                NVDATA Device ID and Chip Revision match verified.
                NVDATA SubSystem Vendor and SubSystem Device ID match verified.
                NVDATA Versions Compatible.
                Valid Initialization Image verified.
                Valid BootLoader Image verified.
 
                Beginning Firmware Download...
                Firmware Download Successful.
 
                Verifying Download...
 
                Firmware Flash Successful.
 
                Resetting Adapter...
                Adapter Successfully Reset.
 
                NVDATA Version 0e.01.00.0d
        Finished Processing Commands Successfully.
        Exiting SAS3Flash.
running /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/sas3flash -c 1 -o -e 3
Avago Technologies SAS3 Flash Utility
Version 17.00.00.00 (2018.04.02)
Copyright 2008-2018 Avago Technologies. All rights reserved.
 
        Advanced Mode Set
 
        Adapter Selected is a Avago SAS: SAS3008(C0)
 
        Executing Operation: Erase Flash
 
        Erasing Persistent Configuration Pages Region...
 
        Erase Flash Operation Successful!
 
        Finished Processing Commands Successfully.
        Exiting SAS3Flash.
running /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/sas3flash -c 1 -b /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/mpt3x64.rom
Avago Technologies SAS3 Flash Utility
Version 17.00.00.00 (2018.04.02)
Copyright 2008-2018 Avago Technologies. All rights reserved.
 
        Adapter Selected is a Avago SAS: SAS3008(C0)
 
        Executing Operation: Flash BIOS Image
 
                Validating BIOS Image...
 
                BIOS Header Signature is Valid
 
                BIOS Image has a Valid Checksum.
 
                BIOS PCI Structure Signature Valid.
 
                BIOS Image Compatible with the SAS Controller.
 
                Attempting to Flash BIOS Image...
 
                Verifying Download...
 
                Flash BIOS Image Successful.
 
        Finished Processing Commands Successfully.
        Exiting SAS3Flash.
running /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/sas3flash -c 1 -b /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/mptsas3.rom
Avago Technologies SAS3 Flash Utility
Version 17.00.00.00 (2018.04.02)
Copyright 2008-2018 Avago Technologies. All rights reserved.
 
        Adapter Selected is a Avago SAS: SAS3008(C0)
 
        Executing Operation: Flash BIOS Image
 
                Validating BIOS Image...
 
                BIOS Header Signature is Valid
 
                BIOS Image has a Valid Checksum.
 
                BIOS PCI Structure Signature Valid.
 
                BIOS Image Compatible with the SAS Controller.
 
                Attempting to Flash BIOS Image...
 
                Verifying Download...
 
                Flash BIOS Image Successful.
 
        Finished Processing Commands Successfully.
        Exiting SAS3Flash.
running /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/sas3flash -c 1 -b /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/lsisas3f.rom
Avago Technologies SAS3 Flash Utility
Version 17.00.00.00 (2018.04.02)
Copyright 2008-2018 Avago Technologies. All rights reserved.
 
        Adapter Selected is a Avago SAS: SAS3008(C0)
 
        Executing Operation: Flash BIOS Image
 
                Validating BIOS Image...
 
                BIOS Header Signature is Valid
 
                BIOS Image has a Valid Checksum.
 
                BIOS PCI Structure Signature Valid.
 
                BIOS Image Compatible with the SAS Controller.
 
                Attempting to Flash BIOS Image...
 
                Verifying Download...
 
                Flash BIOS Image Successful.
 
        Finished Processing Commands Successfully.
        Exiting SAS3Flash.
create script for ILOM deep recycle
chmod 777 /tmp/dcsfiles/
chmod 700 /tmp/dcsfiles//rebootIlom.sh
prepare system for ILOM recyle
Enabling HOST_AUTO_POWER_ON on ILOM
Connected. Use ^D to exit.
-> set /SP/policy HOST_AUTO_POWER_ON=enabled
Set 'HOST_AUTO_POWER_ON' to 'enabled'
 
-> Session closed
Disconnected
Setting set /System/ deep_power_cycle=true
Connected. Use ^D to exit.
-> set /System/ deep_power_cycle=true
Set 'deep_power_cycle' to 'true'
 
-> Session closed
Disconnected
Trigger recycle script in background
  8. Continue patching your server and databases as described in the topic Patching Oracle Database Appliance Bare Metal Systems Using the Command-Line.
  9. Verify that the updates ran successfully. When the system comes up, verify the NVDATA versions and firmware version. 
    # /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/sas3flash -listall
Avago Technologies SAS3 Flash Utility
Version 17.00.00.00 (2018.04.02)
Copyright 2008-2018 Avago Technologies. All rights reserved.
 
        Adapter Selected is a Avago SAS: SAS3008(C0)
 
Num   Ctlr            FW Ver        NVDATA        x86-BIOS         PCI Addr
----------------------------------------------------------------------------
 
0  SAS3008(C0)  16.00.08.00    0e.01.00.0d    08.37.00.00     00:3b:00:00
1  SAS3008(C0)  16.00.08.00    0e.01.00.0d    08.37.00.00     00:e3:00:00
 
        Finished Processing Commands Successfully.
        Exiting SAS3Flash.

Parent 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.

To patch your Oracle Database Appliance deployment and your existing database homes to the current release, you must download the Oracle Database Appliance Server patch, Oracle Grid Infrastructure clone files, and Oracle Database clone files and update the repository on the bare metal system.

Remember:

When you patch your Oracle Database Appliance deployment to the current release, for ORCL-EXT-SAS3 controller with model number 0x0097, the patching precheck verifies that controllers NVDATA is updated to 0e.01.00.0d version. You must update I_T Target Reset of Estes-Ext to I_T Nexus Reset by running the /opt/oracle/oak/pkgrepos/firmwarecontroller/lsilogic/0x0097/16.00.08.00/it_nexus_reset.sh script. For more information, see the topic Updating ESTES-EXT Firmware Before Patching Oracle Database Appliance Server.

Important:

Oracle recommends always patching from within the previous four Oracle Database Appliance releases because these patching paths are tested. If you patch from any earlier Oracle Database Appliance release, then you may encounter errors.

Note:

Run the steps in this procedure in the same order as documented. Run the odacli update-dcsadmin, odacli update-dcscomponents, and odacli update-dcsagent commands before running the odacli update-server command.

Note:

Note that for DCS Agent update to be complete, both the odacli update-dcscomponents and odacli update-dcsagent commands must be run. Ensure that both commands are run in the order specified.

Important:

Ensure that there is sufficient space on your appliance to download the patches.

Important:

If you want to install third-party software on your Oracle Database Appliance, then ensure that the software does not impact the Oracle Database Appliance software. The version lock on Oracle Database Appliance RPMs displays a warning if the third-party software tries to override Oracle Database Appliance RPMs. You must restore the affected RPMs before patching Oracle Database Appliance so that patching completes successfully.

Important:

If you have configured Oracle ASR and are patching your appliance to Oracle Database Appliance release 19.26, then after updating the DCS agent, delete the existing Oracle ASR configuration and reconfigure it, before you run the odacli update-server command to patch your appliance.

Note:

Public network gateway must be responsive to ping requests. Oracle Clusterware uses the public network gateway as ping target to facilitate the VIP failover in Oracle Database Appliance high-availability environment.

See Also:

Enabling Custom SSH Key Management on Oracle Database Appliance in this guide for information on how to manage SSH keys on bare metal systems and DB systems
The Oracle Database Appliance Backup Recovery (ODABR) tool helps recover a system to the pre-patch state, should any potential errors occur during the patching process that may render the system unusable. Download and install the latest version of the Oracle Database Appliance Backup Recovery (ODABR) tool to enable creation of snapshots before patching. See My Oracle Support Note 2466177.1 for the procedure to install ODABR.

https://support.oracle.com/rs?type=doc&id=2466177.1

Follow these steps to apply patches to your Oracle Database Appliance and update existing database homes.
  1. Download the Oracle Database Appliance Server Patch for the ODACLI/DCS stack (patch 37536686), Oracle Grid Infrastructure clone files (patch 30403673), and Oracle Database clone files (patch 30403662) from My Oracle Support to a temporary location on an external client. Refer to the release notes for details about the patch numbers and software for the latest release.
    For example, download the server patch for 19.26:
    p37536686_1926000_Linux-x86-64.zip
  2. Unzip the software — it contains README.html and one or more zip files for the patch.
    unzip p37536686_1926000_Linux-x86-64.zip

    The zip file contains the following software file:

    oda-sm-19.26.0.0.0-date-server.zip
  3. Copy all the software files from the external client to Oracle Database Appliance. For High-Availability deployments, copy the software files to only one node. The software files are copied to the other node during the patching process. Use the scp or sftp protocol to copy the bundle.
    Example using scp command:
    # scp software_file root@oda_host:/tmp
    Example using sftp command:
    # sftp root@oda_host
    Enter the root password, and copy the files.
    put software_file
  4. Update the repository with the server software file: 
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-repository -f /tmp/software_file

    For example, for 19.26: 

    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-repository -f /tmp/oda-sm-19.26.0.0.0-date-server.zip
  5. Confirm that the repository update is successful:
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli describe-job -i job_ID
  6. Update DCS admin:
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-dcsadmin -v 19.26.0.0.0
  7. Update the DCS components:
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-dcscomponents -v 19.26.0.0.0

    The odacli update-dcscomponents command updates the Zookeeper, MySQL, and updates other DCS components such as the DCS Agent, DCS CLI, and DCS Controller on Oracle Database Appliance.

    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 by re-running the odacli update-dcscomponents command. See the topic Resolving Errors When Updating DCS Components During Patching about more information about DCS components checks errors.

    Note:

    Note that for DCS Agent update to be complete, both the odacli update-dcscomponents and odacli update-dcsagent commands must be run. Ensure that both commands are run in the order specified in this procedure.
  8. Update the DCS agent:
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-dcsagent -v 19.26.0.0.0
  9. Update the repository with the Oracle Grid Infrastructure clone file and the Oracle Database clone file: 
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-repository -f /tmp/software_file

    For example, for 19.26: 

    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-repository -f /tmp/odacli-dcs-19.26.0.0.0-date-GI-19.26.0.0.zip
[root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-repository -f /tmp/odacli-dcs-19.26.0.0.0-date-DB-19.26.0.0.zip
  10. Run patching pre-checks. You must run the odacli create-prepatchreport command before you patch your server; otherwise, the odacli update-server command fails with an error message prompting you to run the patching pre-checks. Note that odacli create-prepatchreport supports the -l option, which runs the prechecks on the local node only. However, to be able to patch the system by running the command odacli update-server, the command odacli create-prepatchreport must be run without the -l option, so that the prechecks can be performed on both nodes before patching is started on any of the two nodes.
    Note that there is no downtime when the patching prechecks run.
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli create-prepatchreport -s -v version

    For example, for 19.26: 

    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli create-prepatchreport -s -v 19.26.0.0.0
    Note that running the odacli create-prepatchreport command creates the target Oracle Grid Infrastructure home, which the server patching operation uses.
  11. Verify that the patching pre-checks ran successfully:
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli describe-prepatchreport

    For example:

    [root@oda1 opt]# odacli describe-prepatchreport -i 677d73d2-5eed-46e5-a06f-d5ca2649d36e

Patch pre-check report
------------------------------------------------------------------------
                 Job ID: 677d73d2-5eed-46e5-a06f-d5ca2649d36e
            Description: Patch pre-checks for [OS, ILOM, GI, ORACHKSERVER, SERVER]
                 Status: SUCCESS
                Created: December 8, 2024 3:37:19 PM CST
                 Result: All pre-checks succeeded
Node Name
---------------
n1

Pre-Check Status Comments
------------------------------ -------- --------------------------------------
__OS__
Validate supported versions Success Validated minimum supported versions.
Validate patching tag Success Validated patching tag: 19.26.0.0.0
Is patch location available Success Patch location is available.
Verify OS patch Success Verified OS patch
Validate command execution Success Validated command execution

__ILOM__
Validate ILOM server reachable Success Successfully connected with ILOM
                                          server using public IP and USB
                                          interconnect
Validate supported versions Success Validated minimum supported versions.
Validate patching tag Success Validated patching tag: 19.26.0.0.0.
Is patch location available Success Patch location is available.
Checking Ilom patch Version Success Successfully verified the versions
Patch location validation Success Successfully validated location
Validate command execution Success Validated command execution
 __GI__
Validate GI metadata Success Successfully validated GI metadata
Validate supported GI versions Success Validated minimum supported versions.
Validate available space Success Validated free space under /u01
Is clusterware running Success Clusterware is running
Validate patching tag Success Validated patching tag: 19.26.0.0.0.
Is system provisioned Success Verified system is provisioned
Validate ASM in online Success ASM is online
Validate kernel log level Success Successfully validated the OS log
                                          level
Validate minimum agent version Success GI patching enabled in current
                                          DCSAGENT version
Validate Central Inventory Success oraInventory validation passed
Validate patching locks Success Validated patching locks
Validate clones location exist Success Validated clones location
Validate DB start dependencies Success DBs START dependency check passed
Validate DB stop dependencies Success DBs STOP dependency check passed
Validate space for clones Success Clones volume is already created
volume
Evaluate GI patching Success Successfully validated GI patching
Validate command execution Success Validated command execution
 __ORACHK__
Running orachk Success Successfully ran Orachk
Validate command execution Success Validated command execution

__SERVER__
Validate local patching Success Successfully validated server local
                                          patching
Validate command execution Success Validated command execution
Node Name
---------------
n2

Pre-Check Status Comments
------------------------------ -------- --------------------------------------
__OS__
Validate supported versions Success Validated minimum supported versions.
Validate patching tag Success Validated patching tag: 19.26.0.0.0.
Is patch location available Success Patch location is available.
Verify OS patch Success Verified OS patch
Validate command execution Success Validated command execution

__ILOM__
Validate ILOM server reachable Success Successfully connected with ILOM
                                          server using public IP and USB
                                          interconnect
Validate supported versions Success Validated minimum supported versions.
Validate patching tag Success Validated patching tag: 19.26.0.0.0.
Is patch location available Success Patch location is available.
Checking Ilom patch Version Success Successfully verified the versions
Patch location validation Success Successfully validated location
Validate command execution Success Validated command execution
__GI__
Validate GI metadata Success Successfully validated GI metadata
Validate supported GI versions Success Validated minimum supported versions.
Validate available space Success Validated free space under /u01
Is clusterware running Success Clusterware is running
Validate patching tag Success Validated patching tag: 19.26.0.0.0.
Is system provisioned Success Verified system is provisioned
Validate ASM in online Success ASM is online
Validate kernel log level Success Successfully validated the OS log
                                          level
Validate minimum agent version Success GI patching enabled in current
                                          DCSAGENT version
Validate Central Inventory Success oraInventory validation passed
Validate patching locks Success Validated patching locks
Validate clones location exist Success Validated clones location
Validate DB start dependencies Success DBs START dependency check passed
Validate DB stop dependencies Success DBs STOP dependency check passed
Validate space for clones Success Clones volume is already created
volume
Evaluate GI patching Success Successfully validated GI patching
Validate command execution Success Validated command execution
__ORACHK__
Running orachk Success Successfully ran Orachk
Validate command execution Success Validated command execution

__SERVER__
Validate local patching Success Successfully validated server local
                                          patching
Validate command execution Success Validated command execution

    Use the command odacli describe-prepatchreport to view details of the pre-patch report. Fix the warnings and errors mentioned in the report and proceed with the server patching.

  12. Apply the server update. Note that you can use the --local option with the odacli update-server command to update the local node. 
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-server -v version

    For example, for 19.26: 

    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-server -v 19.26.0.0.0
  13. Confirm that the server update is successful:
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli describe-job -i job_ID

    Note:

    After successful server update, it is recommended that you delete any ODABR snapshot you created before starting the server update. If you want to retain any ODABR snapshot when you update the storage and other components, then consider that the presence of active ODABR snapshots may affect system performance. See My Oracle Support Note 2466177.1 for the procedure to create and delete ODABR snapshots: https://support.oracle.com/rs?type=doc&id=2466177.1
  14. Before you update the storage components, run the odacli create-prepatchreport command with the -st option.
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli create-prepatchreport -st -v version

    For example, for 19.26: 

    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli create-prepatchreport -st -v 19.26.0.0.0
  15. Verify that the patching pre-checks ran successfully:
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli describe-prepatchreport

    For example:

    [root@oda1 opt]# odacli describe-prepatchreport -i 95887f92-7be7-4865-a311-54318ab385f2

Patch pre-check report                                           
------------------------------------------------------------------------
                 Job ID:  95887f92-7be7-4865-a311-54318ab385f2
            Description:  Patch pre-checks for [STORAGE]
                 Status:  SUCCESS
                Created:  December 8, 2024 12:52:37 PM HKT
                 Result:  All pre-checks succeeded

Node Name       
---------------
node1 

Pre-Check                      Status   Comments                              
------------------------------ -------- -------------------------------------- 
__STORAGE__ 
Validate patching tag           Success   Validated patching tag: 19.26.0.0.0.  
Patch location validation       Success   Verified patch location               
Patch tag validation            Success   Verified patch tag                    
Storage patch tag validation    Success   Verified storage patch location       
Verify ASM disks status         Success   ASM disks are online                  
Validate rolling patch          Success   Rolling mode patching allowed as      
                                          there is no expander and controller   
                                          upgrade.                              
Validate command execution      Success   Validated command execution           

Node Name       
---------------
node2 

Pre-Check                      Status   Comments                              
------------------------------ -------- -------------------------------------- 
__STORAGE__ 
Validate patching tag           Success   Validated patching tag: 19.26.0.0.0.  
Patch location validation       Success   Verified patch location               
Patch tag validation            Success   Verified patch tag                    
Storage patch tag validation    Success   Verified storage patch location       
Verify ASM disks status         Success   ASM disks are online                  
Validate rolling patch          Success   Rolling mode patching allowed as      
                                          there is no expander and controller   
                                          upgrade.                              
Validate command execution      Success   Validated command execution

    Use the command odacli describe-prepatchreport to view details of the pre-patch report. The pre-patch report also indicates whether storage patching can be rolling or not, based on whether an Expander or Controller update is also required.

    Fix the warnings and errors mentioned in the report and proceed with the storage components patching.

  16. Update the storage components.
    Specify the --rolling option to patch shared disks in a rolling fashion. Note that if you patch from an Oracle Database Appliance release that requires the expander to be patched, then you cannot use the --rolling option during storage patching.
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-storage -v version --rolling

    For example, for 19.26: 

    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-storage -v 19.26.0.0.0 --rolling
  17. Starting with Oracle Database Appliance release 19.11, Oracle Database homes are not created on the local disk. Oracle Database homes are created on an Oracle ACFS-managed file system. For a database user oracle, the new database homes are created under /u01/app/odaorahome/oracle/.
    If the database home is not already configured on Oracle ACFS, then before patching the database home, configure the database home storage with the odacli configure-dbhome-storage command. For example:
    [root@oda1 opt]# odacli configure-dbhome-storage -dg DATA
    The command does not cause storage allocation or creation of volumes or file systems. The command only sets the disk group location in the metadata.
    For information about managing database homes on Oracle ACFS, see the topic Managing Database Home Storage.
  18. To patch existing Oracle Database Homes to release 19.26, ensure that the repository is updated with the Oracle Database clone files. If you have not updated the repository with the Oracle Database clone files, then update the repository. Note that you must update the DCS agent before you update the repository with the Oracle Database clone files.
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-repository -f /tmp/DB_software_file
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-repository -f /tmp/odacli-dcs-19.26.0.0.0-date-DB-19.26.0.0.zip

    Note:

    You have the option to patch each database home using the odacli update-dbhome command or patch selected databases in a database home to a specific database home using the odacli update-database command.
  19. To patch all databases in a specified database home:
    1. If you want to patch each database home by running the odacli update-dbhome command, then create the prepatch report first. Run the patching pre-checks and review the prepatch report. You must run the odacli create-prepatchreport command before you patch your Oracle Database homes; otherwise, the odacli update-dbhome command fails with an error message prompting you to run the patching pre-checks.
      [root@oda1 opt]# /opt/oracle/dcs/bin/odacli create-prepatchreport --dbhome --dbhomeid DB_Home_ID -v release_number
[root@oda1 opt]# odacli describe-prepatchreport -i Job_ID
      [root@oda1 opt]# /opt/oracle/dcs/bin/odacli create-prepatchreport --dbhome --dbhomeid d03d5187-1c20-470a-9d51-49a0d6f60772 -v 19.26.0.0.0
[root@oda1 opt]# odacli describe-prepatchreport -i 6f040374-d271-4711-a7db-e6c04597ad69

Patch pre-check report                                           
------------------------------------------------------------------------
                 Job ID:  6f040374-d271-4711-a7db-e6c04597ad69
            Description:  Patch pre-checks for [DB, ORACHKDB]: DbHome is OraDB19000_home1
                 Status:  SUCCESS
                Created:  December 8, 2024 8:59:48 AM HKT
                 Result:  All pre-checks succeeded

Node Name       
---------------
node1 

Pre-Check                      Status   Comments                              
------------------------------ -------- -------------------------------------- 
__DB__ 
Validate DB Home ID             Success   Validated DB Home ID:                 
                                          d03d5187-1c20-470a-9d51-49a0d6f60772  
Validate patching tag           Success   Validated patching tag: 19.26.0.0.0.  
Is system provisioned           Success   Verified system is provisioned        
Validate minimum agent version  Success   Validated minimum agent version       
Is GI upgraded                  Success   Validated GI is upgraded              
Validate available space for    Success   Validated free space required under   
db                                        /u01/app/odaorahome                   
Validate dbHomesOnACFS          Success   User has configured diskgroup for     
configured                                Database homes on ACFS                
Validate Oracle base            Success   Successfully validated Oracle Base    
Is DB clone available           Success   Successfully validated clone file     
                                          exists                                
Evaluate DBHome patching with   Success   Successfully validated updating       
RHP                                       dbhome with RHP.  and local patching  
                                          is possible                           
Validate command execution      Success   Validated command execution           

__ORACHK__ 
Running orachk                  Success   Successfully ran Orachk               
Validate command execution      Success   Validated command execution           

Node Name       
---------------
node2 

Pre-Check                      Status   Comments                              
------------------------------ -------- -------------------------------------- 
__DB__ 
Validate DB Home ID             Success   Validated DB Home ID:                 
                                          d03d5187-1c20-470a-9d51-49a0d6f60772  
Validate patching tag           Success   Validated patching tag: 19.26.0.0.0.  
Is system provisioned           Success   Verified system is provisioned        
Validate minimum agent version  Success   Validated minimum agent version       
Is GI upgraded                  Success   Validated GI is upgraded              
Validate available space for    Success   Validated free space required under   
db                                        /u01/app/odaorahome                   
Validate dbHomesOnACFS          Success   User has configured diskgroup for     
configured                                Database homes on ACFS                
Validate Oracle base            Success   Successfully validated Oracle Base    
Is DB clone available           Success   Successfully validated clone file     
                                          exists                                
Evaluate DBHome patching with   Success   Successfully validated updating       
RHP                                       dbhome with RHP.                      
Validate command execution      Success   Validated command execution           

__ORACHK__ 
Running orachk                  Success   Successfully ran Orachk               
Validate command execution      Success   Validated command execution
      If the disk group for database homes on Oracle ACFS is not set up as described in step 17, then the prepatch report lists the error The system is not set up to create database homes on ACFS. Run the odacli configure-dbhome-storage command to configure the disk group for database homes on Oracle ACFS.
      Note that running the odacli create-prepatchreport command creates the target Oracle Grid Infrastructure home, which the database patching operation uses.
    2. If the pre-patch report does not show any errors, then update the database home to the latest release. You need not use the -f option with the odacli update-dbhome command. Note that you can use the --local option with the odacli update-dbhome command to update the local node. 
      [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-dbhome --id DB_Home_ID -v release_number

      For example, for 19.26: 

      [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-dbhome --id 7c67c5b4-f585-4ba9-865f-c719c63c0a6e -v 19.26.0.0.0
  20. To patch a specific database to a specific database home:
    1. If you want patch selected databases in a database home to a specific database home using the odacli update-database command, then create the prepatch report first. Run the patching pre-checks and review the prepatch report. You must run the odacli create-prepatchreport command before you patch your Oracle database; otherwise, the odacli update-database command fails with an error message prompting you to run the patching pre-checks.
      [root@oda1 opt]# /opt/oracle/dcs/bin/odacli create-prepatchreport -db -dbid DATABASE_ID -to a68f9947-DB_HOME_ID

      For example, for 19.26: 

      [root@oda1 ~]# odacli describe-prepatchreport -i efa93519-a365-4e9a-9f25-ad3c653cccef

Patch pre-check report
------------------------------------------------------------------------
                 Job ID: efa93519-a365-4e9a-9f25-ad3c653cccef
            Description: Patch pre-checks for [SINGLEDB, ORACHKSINGLEDB]: Target DB is db10181, Destination DbHome is OraDB19000_home8
                 Status: SUCCESS
                Created: December 8, 2024 11:19:03 AM PDT
                 Result: All pre-checks succeeded

Node Name
---------------
node1

Pre-Check Status Comments
------------------------------ -------- --------------------------------------
__SINGLEDB__
Is system provisioned Success Verified system is provisioned
Validate dbHomesOnACFS Success User has configured disk group for
configured Database homes on ACFS
Validate Oracle base Success Successfully validated Oracle Base
Evaluate DB clone availability Success Successfully validated clone file
                                          exists
Evaluate DB patching with RHP Success Successfully validated patching DB
                                          with RHP.
Validate command execution Success Validated command execution

__ORACHK__
Running orachk Success Successfully ran Orachk
Validate command execution Success Validated command execution

Node Name
---------------
node2

Pre-Check Status Comments
------------------------------ -------- --------------------------------------
__SINGLEDB__
Is system provisioned Success Verified system is provisioned
Validate dbHomesOnACFS Success User has configured disk group for
configured Database homes on ACFS
Validate Oracle base Success Successfully validated Oracle Base
Evaluate DB clone availability Success Successfully validated clone file
                                          exists
Evaluate DB patching with RHP Success Successfully validated patching DB
                                          with RHP.
Validate command execution Success Validated command execution

__ORACHK__
Running orachk Success Successfully ran Orachk
Validate command execution Success Validated command execution
    2. If the pre-patch report does not show any errors, then update the databases to the latest release. 
      [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-database -i database_ID/-n database_name -to destination_dbhome_ID

      For example, for 19.26: 

      [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-database -i c05458c7-0f1d-4260-8e62-003b3ec26d74/-n db10181 -to dc98eaa9-289c-4710-a898-ca6287a07a9c 
[root@oda1 ~]# odacli describe-job -i d442a7d4-594f-48e2-8b02-9124811bb7b4

Job details
----------------------------------------------------------------
                     ID: d442a7d4-594f-48e2-8b02-9124811bb7b4
            Description: DB Patching: database ID is c05458c7-0f1d-4260-8e62-003b3ec26d74
                 Status: Success
                Created: December 8, 2024 3:23:43 PM PDT
                Message:

Task Name Node Name Start Time End Time Status
---------------------------------------- ------------------------- ----------------------------------- ----------------------------------- ----------
Creating wallet for DB Client node1 December 8, 2024 3:24:42 PM PDT December 8, 2024 3:24:42 PM PDT Success
Patch databases by RHP node1 December 8, 2024 3:24:42 PM PDT December 8, 2024 3:29:34 PM PDT Success
Updating database metadata node2 December 8, 2024 3:29:34 PM PDT December 8, 2024 3:29:34 PM PDT Success
Set log_archive_dest for Database node1 December 8, 2024 3:29:34 PM PDT December 8, 2024 3:29:37 PM PDT Success
Generating and saving BOM node1 December 8, 2024 3:29:37 PM PDT December 8, 2024 3:31:44 PM PDT Success
Generating and saving BOM node2 December 8, 2024 3:29:37 PM PDT December 8, 2024 3:31:44 PM PDT Success
TDE parameter update node2 December 8, 2024 3:32:25 PM PDT December 8, 2024 3:32:25 PM PDT Success
  21. Confirm that the patch jobs are successful:
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli list-jobs
  22. If you are patching your appliance from Oracle Database Appliance release 19.11 or earlier, then run the following steps. You must also run these steps if your appliance was previously patched to Oracle Database Appliance release 19.12 or later, but you did not run these steps when patching to release 19.12.
    1. After patching the bare metal systems and database homes, enable NUMA (Non-Uniform Memory Access) on existing databases of release 19.12 or earlier, by running the following SQL*Plus command:
      SQL> alter system set "_enable_numa_support"=true scope=spfile sid='*';

      Restart the database after running the command to ensure that the changes take effect.

      For more information about enabling NUMA, see the topic About Enabling NUMA on Oracle Database Appliance.

    2. If you have deployed DB systems, VMs, or CPU pools, perform the following steps:
      1. Run the odacli remap-cpupools command:
        [root@oda1 opt]# /opt/oracle/dcs/bin/odacli remap-cpupools

        If the odacli remap-cpupools command fails with the error DCS-10001:Internal error encountered: Not enough physical CPUs available for CPU Pool 'cpupool_name' on node 'node_name', run the odacli remap-cpupools command again with the --use_reserved-cores option. For information about the command options, see the chapter Oracle Database Appliance Command-Line Interface for KVM.

      2. If you have DB systems in your deployment, then run the odacli modify-dbsystem command. If you have VMs in your KVM deployment and you want to enable NUMA for the VMs, then run the odacli modify-vm --enable-numa command for VMs. That is:

        For DB systems:

        odacli modify-dbsystem --enable-numa

        For VMs:

        odacli modify-vm --enable-numa

    Note:

    For bare metal systems and DB systems on Oracle Database Appliance X7-2S and X8-2S, the database init.ora parameter _enable_numa_support is set to FALSE even when NUMA is enabled. This is expected because these hardware models are single socket systems.

Related Topics

Parent topic: Patching Oracle Database Appliance

Patching Oracle Database Appliance DB Systems Using the Command-Line

Follow these steps to apply patches to your Oracle Database Appliance DB system deployment and existing Oracle Database home in the DB system, using CLI commands.

To patch your Oracle Database Appliance DB systems deployment and your existing database homes to the current release, you must download the Oracle Database Appliance Server Patch and update the bare metal system repository.

Note:

Run the commands in this topic in the same order as documented. Run the odacli update-dcsadmin, odacli update-dcscomponents, and odacli update-dcsagent commands before running the odacli update-server command.

Note:

Note that for DCS agent update to be complete, both the odacli update-dcscomponents and odacli update-dcsagent commands must be run. Ensure that both commands are run in the order specified.

Note:

Public network gateway must be responsive to ping requests. Oracle Clusterware uses the public network gateway as ping target to facilitate the VIP failover in Oracle Database Appliance high-availability environment.
Ensure that you have patched your Oracle Database Appliance bare metal deployment to release 19.26 before you patch your DB system.
Follow these steps to apply patches to your Oracle Database Appliance DB system deployment and update the existing database home in the DB system.
  1. Ensure that the Oracle Database Appliance Server Patch for the ODACLI/DCS stack, Oracle Grid Infrastructure clone files, and Oracle Database clone files are available in the repository. Run the odacli list-availablepatches command in the bare metal system to view whether the clone files are available in the system.
    [root@oda1 opt]# odacli list-availablepatches
  2. Connect to the DB system.
  3. Update DCS admin:
    [root@dbsystem1 opt]# /opt/oracle/dcs/bin/odacli update-dcsadmin -v 19.26.0.0.0
  4. Update the DCS components:
    [root@dbsystem1 opt]# /opt/oracle/dcs/bin/odacli update-dcscomponents -v 19.26.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 by re-running the odacli update-dcscomponents command. See the topic Resolving Errors When Updating DCS Components During Patching about more information about DCS components checks errors.

    Note:

    Note that for DCS agent update to be complete, both the odacli update-dcscomponents and odacli update-dcsagent commands must be run. Ensure that both commands are run in the order specified.
  5. Update the DCS agent:
    [root@dbsystem1 opt]# /opt/oracle/dcs/bin/odacli update-dcsagent -v 19.26.0.0.0
  6. Run patching pre-checks. You must run the odacli create-prepatchreport command before you patch your server; otherwise, the odacli update-server command fails with an error message prompting you to run the patching pre-checks.
    [root@dbsystem1 opt]# /opt/oracle/dcs/bin/odacli create-prepatchreport -s -v version

    For example, for 19.26: 

    [root@dbsystem1 opt]# /opt/oracle/dcs/bin/odacli create-prepatchreport -s -v 19.26.0.0.0
  7. Verify that the patching pre-checks ran successfully:
    [root@dbsystem1 opt]# /opt/oracle/dcs/bin/odacli describe-prepatchreport

    For example:

    [root@dbsystem1 ~]# odacli describe-prepatchreport -i f7e6fb22-1fc0-4aa1-937c-9669dbbb8ae6

Patch pre-check report                                           
------------------------------------------------------------------------
                 Job ID:  f7e6fb22-1fc0-4aa1-937c-9669dbbb8ae6
            Description:  Patch pre-checks for [OS, GI, ORACHKSERVER, SERVER]
                 Status:  SUCCESS
                Created:  December 8, 2024 3:38:03 PM CET
                 Result:  All pre-checks succeeded

Node Name       
---------------
node1

Pre-Check                      Status   Comments                              
------------------------------ -------- -------------------------------------- 
__OS__ 
Validate supported versions     Success   Validated minimum supported versions. 
Validate patching tag           Success   Validated patching tag: 19.26.0.0.0.  
Is patch location available     Success   Patch location is available.          
Verify OS patch                 Success   Verified OS patch                     
Validate command execution      Success   Validated command execution           

__GI__ 
Validate GI metadata            Success   Successfully validated GI metadata    
Validate supported GI versions  Success   Validated minimum supported versions. 
Validate available space        Success   Validated free space under /u01       
Is clusterware running          Success   Clusterware is running                
Validate patching tag           Success   Validated patching tag: 19.26.0.0.0.  
Is system provisioned           Success   Verified system is provisioned        
Validate BM versions            Success   Validated BM server components        
                                          versions                              
Validate kernel log level       Success   Successfully validated the OS log     
                                          level                                 
Validate minimum agent version  Success   GI patching enabled in current        
                                          DCSAGENT version                      
Validate Central Inventory      Success   oraInventory validation passed        
Validate patching locks         Success   Validated patching locks              
Validate clones location exist  Success   Validated clones location             
Evaluate GI patching            Success   Successfully validated GI patching    
Validate command execution      Success   Validated command execution           

__ORACHK__ 
Running orachk                  Success   Successfully ran Orachk               
Validate command execution      Success   Validated command execution           

__SERVER__ 
Validate local patching         Success   Successfully validated server local   
                                          patching                              
Validate command execution      Success   Validated command execution           

Node Name       
---------------
node2

Pre-Check                      Status   Comments                              
------------------------------ -------- -------------------------------------- 
__OS__ 
Validate supported versions     Success   Validated minimum supported versions. 
Validate patching tag           Success   Validated patching tag: 19.26.0.0.0.  
Is patch location available     Success   Patch location is available.          
Verify OS patch                 Success   Verified OS patch                     
Validate command execution      Success   Validated command execution           

__GI__ 
Validate GI metadata            Success   Successfully validated GI metadata    
Validate supported GI versions  Success   Validated minimum supported versions. 
Validate available space        Success   Validated free space under /u01       
Is clusterware running          Success   Clusterware is running                
Validate patching tag           Success   Validated patching tag: 19.26.0.0.0.  
Is system provisioned           Success   Verified system is provisioned        
Validate BM versions            Success   Validated BM server components        
                                          versions                              
Validate kernel log level       Success   Successfully validated the OS log     
                                          level                                 
Validate minimum agent version  Success   GI patching enabled in current        
                                          DCSAGENT version                      
Validate Central Inventory      Success   oraInventory validation passed        
Validate patching locks         Success   Validated patching locks              
Validate clones location exist  Success   Validated clones location             
Evaluate GI patching            Success   Successfully validated GI patching    
Validate command execution      Success   Validated command execution           

__ORACHK__ 
Running orachk                  Success   Successfully ran Orachk               
Validate command execution      Success   Validated command execution           

__SERVER__ 
Validate local patching         Success   Successfully validated server local   
                                          patching                              
Validate command execution      Success   Validated command execution

    Use the command odacli describe-prepatchreport to view details of the pre-patch report. Fix the warnings and errors mentioned in the report and proceed with the server patching.

  8. Apply the server update. Note that you can use the --local option with the odacli update-server command to update the local node.
    [root@dbsystem1 opt]# /opt/oracle/dcs/bin/odacli update-server -v version

    For example, for 19.26: 

    [root@dbsystem1 opt]# /opt/oracle/dcs/bin/odacli update-server -v 19.26.0.0.0

    You can use the -f option to override precheck failures and complete the server patching.

  9. Confirm that the server update is successful:
    [root@dbsystem1 opt]# /opt/oracle/dcs/bin/odacli describe-job -i job_ID
  10. To patch existing Oracle Database Homes to release 19.26:
    1. On the bare metal system, run the command odacli describe-dbsystem-image to check that the repository is updated with the required Oracle Database clone files. If the database clone file is not displayed in the command output, then run the command odacli update-repository on the bare metal system to update the repository with the database clone files:
      [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-repository -f /tmp/DB_software_file
      [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-repository -f /tmp/odacli-dcs-19.26.0.0.0-date-DB-19.26.0.0.zip
    2. Run the patching pre-checks and review the prepatch report. You must run the odacli create-prepatchreport command before you patch your Oracle Database homes; otherwise, the odacli update-dbhome command fails with the error message prompting you to run the patching pre-checks.
      [root@dbsystem1 opt]# /opt/oracle/dcs/bin/odacli create-prepatchreport --dbhome --dbhomeid DB_Home_ID -v release_number
[root@dbsystem1 opt]# odacli describe-prepatchreport -i Job_ID
      [root@dbsystem1 opt]# /opt/oracle/dcs/bin/odacli create-prepatchreport --dbhome --dbhomeid 7c67c5b4-f585-4ba9-865f-c719c63c0a6e -v 19.26.0.0.0
[root@dbsystem1 opt]# odacli describe-prepatchreport -i 39ef1eeb-70d3-47ad-b3f5-48960ca0607b
      Alternatively, you can use the odacli update-database to update the databases in your deployment:
      [root@dbsystem1 opt]# odacli create-prepatchreport --database --database-id database_ID --to-home dest_dbhome_ID 
[root@dbsystem1 opt]# odacli update-database --id database_ID --to-home dest_dbhome_ID
    3. If there are no errors, then update the database home to the latest release. You need not use the -f option with the odacli update-dbhome command. Note that you can use the --local option with the odacli update-dbhome command to update the local node. You can also use the --node option to specify the node containing the database to update.
      [root@dbsystem1 opt]# /opt/oracle/dcs/bin/odacli update-dbhome --id DB_Home_ID -v release_number

      For example, for 19.26: 

      [root@dbsystem1 opt]# /opt/oracle/dcs/bin/odacli update-dbhome --id 7c67c5b4-f585-4ba9-865f-c719c63c0a6e -v 19.26.0.0.0
  11. Confirm that the patch jobs are successful:
    [root@dbsystem1 opt]# /opt/oracle/dcs/bin/odacli list-jobs

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 admin, DCS components, and DCS agent using CLI commands.

Updating the Patch Repository Using the Browser User Interface

  1. 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.

  2. Log into the Browser User Interface.

    https://Node0–host-ip-address:7093/mgmt/index.html

  3. Click Repository Manager.

  4. 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.

  5. Click Activity to monitor the progress. When the job completes successfully, the Patch Repository is updated.

Updating the DCS Admin, DCS Components, and DCS Agent After Updating the Repository and Before Patching

Before patching your appliance using the Browser User Interface, you must update the DCS admin, DCS agent, and DCS components manually through CLI commands.

Follow these steps:

  1. In the BUI, click Appliance and then click Infrastructure Patching on the lefthand pane.
  2. Using ODACLI commands, update the DCS admin, DCS components, and DCS agent:
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-dcsadmin  -v 19.26.0.0.0
[root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-dcscomponents -v 19.26.0.0.0
[root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-dcsagent -v 19.26.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 the odacli update-dcscomponents command.

Running Patching Prechecks and Patching Server, and Storage Using the Browser User Interface

  1. Do not have any jobs running or pending during the update window.

  2. In the BUI, click the Appliance tab, and then click Infrastructure Patching on the lefthand pane.

  3. In the SERVER section, view the Component Details. If you just updated the Patch Repository, click Refresh.

    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.

  4. Click Precheck to run patching prechecks. You must run the patching prechecks before updating the server and other components. Click View Pre-check Reports to view the patching prechecks report. If there are no errors in the report, then click Apply Patch to begin the job to patch the server components. For high-availability systems, when updating the server on the bare metal system, you can select the Node to Update. You can choose the node that you want to update or you can choose to update both nodes.

    When the job finishes, go to the next step. Click View Jobs for the job status.

  5. In the STORAGE section, click Refresh to refresh the Component Details. Click Precheck to run patching prechecks. You must run the patching prechecks before updating the storage components. Click View Pre-check Reports to view the patching prechecks report. If there are no errors in the report, then click Apply Patch to begin the job to patch the storage components. Click View Jobs for the job status.

    For high-availability environment, you can select the Rolling check box to perform rolling patching of storage components.

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

Patching Oracle Database Appliance DB 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

  1. 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.

  2. Log into the Browser User Interface within the bare metal system, with the oda-admin user name and password. 

    https://Node0–host-ip-address:7093/mgmt/index.html

  3. Click the Appliance tab, and then click Infrastructure Patching on the lefthand pane.

  4. In the Update Repository tab, on 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.

  5. Click Activity to monitor the progress. When the job completes successfully, the Patch Repository is updated.

Updating the DCS Admin, DCS Components, and DCS Agent After Updating the Repository and Before Patching

Before patching your DB system using the Browser User Interface, you must update the DCS admin, DCS agent, and DCS components manually, through CLI commands.

Follow these steps:

  1. In the BUI, click Appliance and then click Infrastructure Patching on the lefthand pane.
  2. Using ODACLI, update the DCS admin, DCS components, and DCS agent:
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-dcsadmin  -v 19.26.0.0.0
[root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-dcscomponents -v 19.26.0.0.0
[root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-dcsagent -v 19.26.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 the odacli update-dcscomponents command.

Running Patching Prechecks and Patching Server and Storage Components Using the Browser User Interface

  1. Do not have any jobs running or pending during the update window.

  2. Log into the Browser User Interface within the DB system with the oda-admin user name and password. 

    https://Node0–host-ip-address:7093/mgmt/index.html

  3. Click the Appliance tab, and then click Infrastructure Patching on the lefthand pane.

  4. In the SERVER section, view the Component Details. If you just updated the Patch Repository, click Refresh.

    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.

  5. Click Precheck to run patching prechecks. You must run the patching prechecks before updating the server and other components. Click View Pre-check Reports to view the patching prechecks report. If there are no errors in the report, then click Apply Patch to begin the job to patch the server components. For high-availability systems, when updating the server on the bare metal system, you can select the Node to Update. You can choose the node that you want to update or you can choose to update both nodes.

    When the job finishes, go to the next step. Click View Jobs for the job status.

  6. In the STORAGE section, click Refresh to refresh the Component Details. Click Precheck to run patching prechecks. You must run the patching prechecks before updating the storage components. Click View Pre-check Reports to view the patching prechecks report. If there are no errors in the report, then click Apply Patch to begin the job to patch the storage components. Click View Jobs for the job status.

    For high-availability environment, you can select the Rolling check box to perform rolling patching of storage components.

  7. Click Activity to monitor the progress, and verify that the job completes successfully.

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.

To create new databases of a specific release version, you must update the Oracle Database Appliance repository with the Oracle Database clone files for a release. Follow these steps to update the repository with Oracle Database clone files for the latest release.
  1. Download the Oracle Database clone software file for a release, for example, p30403662_1926000_Linux-x86-64.zip, and extract the Oracle Database clone software:
    For example, download the Oracle Database clone software patch for 19.26:
    unzip /tmp/p30403662_1926000_Linux-x86-64.zip
odacli-dcs-19.26.0.0.0-date-DB-19.26.0.0.zip
  2. Copy all the software files from the external client to Oracle Database Appliance. For High-Availability deployments, copy the software files to only one node. The software files are copied to the other node during the patching process. Use the scp or sftp protocol to copy the bundle.
    Example using scp command:
    # scp software_file root@oda_host:/tmp
    Example using sftp command:
    # sftp root@oda_host
    Enter the root password, and copy the files.
    put software_file
  3. Update the repository with latest release database software:
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-repository -f /tmp/odacli-dcs-db-clone-file.zip/

    For example, for 19.26: 

    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-repository -f /tmp/odacli-dcs-19.26.0.0.0-date-DB-19.26.0.0.zip
    Follow the same steps to update the repository with the database clone software for other supported database versions.
  4. Confirm that the repository update is successful:
    [root@oda1 opt]# /opt/oracle/dcs/bin/odacli list-jobs
[root@oda1 opt]# /opt/oracle/dcs/bin/odacli describe-job -i job_ID
  5. Delete the software zip files from the temporary location on the appliance to save space:
    [root@oda1 opt]# rm software_file
rm: remove regular file software_file? y

Parent topic: Patching Oracle Database Appliance

Patching Databases Using ODACLI Commands or the BUI

Use ODACLI commands or the Browser User Interface to patch databases to the latest release in your deployment.

Before patching the database home, upload the Oracle Database clone files for the database version, to the repository. See Updating Oracle Database Appliance Repository with Database Clone Files Using the CLI for the procedure to update the repository with the latest Oracle Database clone files.

Important:

You must run the odacli create-prepatchreport command before you patch the Oracle databases; otherwise, the odacli update-database command fails with an error message prompting you to run the patching pre-checks.

Patching Databases on Oracle Database Appliance using ODACLI Commands

Run the following command to patch a database using the CLI:

odacli update-database [-a] [-dp] [-f] [-i db_id] [-imp] [-l] [-n db_name] [-ni node] [-r] [-to db_home_id] [-j] [-h]

For more information about the options for the update-database command, see the chapter Oracle Database Appliance Command-Line Interface.

Patching Databases on Oracle Database Appliance using BUI

  1. Log into the Browser User Interface with the oda-admin user name and password.
    https://Node0–host-ip-address:7093/mgmt/index.html
  2. Navigate to the Database tab.
  3. Select the database you want to patch.
  4. Click Update.
  5. If you select Apply Data Patch, then the Data Patch for the specified database is applied and you cannot select any other options.
  6. On a high-availability system, you can also select the node in the Select Node to Update list.
  7. Select Ignore Missing Patches to ignore missing patches.
  8. Select Force Run to force the operation to run.
  9. Select the destination database home.
  10. In the Patching Options
    • Abort: To abort previously unfinished or failed patching operation.
    • Revert: To revert previously unfinished or failed patching operation.
    • None: To patch the database.
  11. Click Update.
  12. If you have not run the pre-checks earlier, then an error is displayed when you submit the job to update the database.
  13. In the Database page, select the Database and then click Precheck to run pre-checks for patching the database.
    Click Activity for job status.
  14. In the Database page, for the database to be patched, click Actions and select View Pre-patch reports to view the pre-check report. Fix any errors, and then select Action as Apply to patch the database.
  15. Verify that the patching job completes successfully.

Parent topic: Patching Oracle Database Appliance

Patching Existing Database Homes Using ODACLI or the BUI

Use ODACLI or BUI to patch database homes in your deployment to the latest release.

Before patching the database, upload the Oracle Database clone files for the database version, to the repository. See Updating Oracle Database Appliance Repository with Database Clone Files Using the CLI for the procedure to update the repository with the latest Oracle Database clone files.

Patching Database Homes on Oracle Database Appliance using ODACLI Commands

Run the following command to patch a database home using the CLI:

odacli update-dbhome -i dbhome_id -v version [-f] [-imp] [-p] [-l] [-u node_number] [-j] [-h]

For more information about the options for the update-dbhome command, see the chapter Oracle Database Appliance Command-Line Interface.

Patching Database Homes on Oracle Database Appliance using BUI

  1. Log into the Browser User Interface with the oda-admin user name and password.
    https://Node0–host-ip-address:7093/mgmt/index.html
  2. Navigate to the Database Home tab.
  3. Select the database home you want to patch.
  4. Select the Patch Version for the database home.
  5. To patch multiple database homes, select each database home to be patched and the patch version for each database home.
  6. Select the Node to Update. You can choose the node that you want to update or you can choose to update all nodes.
  7. Click Patch. Select Precheck to run pre-checks before patching the database.
    Click Activity for job status.
  8. On the Patch page, for the database to be patched, click Actions and select View Pre-patch reports to view the pre-check report. Fix any errors, and then select Action as Apply to patch the database.
  9. Select Ignore Precheck Failures to ignore failures reported in the prechecks reported. It is recommended that you fix errors reported in the precheck results.
  10. Select Ignore Missing Patches to ignore missing patches.
  11. Verify that the patching job completes successfully.

Related Topics

Parent topic: Patching Oracle Database Appliance

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.

A non-provisioned Oracle Database Appliance system does not have Oracle Grid Infrastructure or Oracle Database installed or running on it. You can upgrade Oracle ILOM and storage firmware on an unprovisioned system without running the odacli create-appliance command by reimaging the system using the bare metal ISO image of Oracle Database release 19.22 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.
Follow these steps to update the firmware:
  1. Reimage the Oracle Database Appliance using the bare metal ISO image for Oracle Database Appliance release 19.22 or later.
  2. Update the repository with the server patch for the Oracle Database Appliance release you want to patch to, for example 19.22 or later.
  3. For running odacli update-server on Oracle Database Appliance imaged with ISO of release 19.22:
    odacli update-server -v 19.22.0.0.0 -sko -f

    For Oracle Database Appliance release 19.22, 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.

  4. For running odacli update-server on Oracle Database Appliance imaged with ISO of release 19.11 or later, follow these steps:
    1. 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.

    2. Update the server:
      odacli update-server -v 19.11.0.0.0 -f

      For Oracle Database Appliance release 19.11 or later, you can use the -f option to override precheck failures and complete the server patching.

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.

You can download and install the latest Oracle Ksplice updates (uptrack-updates) with either the local ULN repository or ULN channel.
Follow these steps to install Oracle KSplice:
  1. Register your server with Unbreakable Linux Network (ULN). By default, you are registered for the Oracle Linux Latest channel for your operating system and hardware.
  2. Log in to Unbreakable Linux Network:
  3. Ensure that you have access to the Internet on the server where you want to use Ksplice. For example, if you are using a proxy server, then set the proxy server and port values in the shell with commands similar to the following:
    # export http_proxy=http://proxy.company.com:port
# export https_proxy=http://proxy.company.com:port
  4. Register the server:
    # uln_register
  5. Set up the local repository as described in the Oracle Ksplice user documentation. This enables you to download the latest Ksplice update packages at regular intervals without requiring a direct connection to the Oracle Uptrack server or to ULN.
  6. To update a system to a specific effective kernel version, install the uptrack-updates package for the current kernel.
    yum -y install uptrack-updates-'uname -r'
    You can also download the uptrack-updates RPM from the Ksplice channel and install the RPM manually. For example:
    # rpm -Uvh uptrack-updates-4.14.35-1902.11.3.1.el7uek.x86_64-20200325-0.noarch.rpm

See Also:

Oracle Linux Ksplice User's Guide for information about configuring Oracle Ksplice at:

https://docs.oracle.com/en/operating-systems/oracle-linux/

Parent topic: Applying Additional Patches and Updates on Bare Metal Systems

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.

You can apply Oracle Database Release Update (RU) patches manually using OPatch. Refer to the relevant section in this topic to run the OPatch for your database version.

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 baremetal and DB system deployments using this procedure.

Using OPatchauto to Manually Patch Oracle Database Release 12c and Later

  1. Confirm that the dcs-agent and other components are updated to the latest release.
    # odacli describe-component
# odacli list-dbhomes
  2. Update OPatch to the latest version, if available:
    1. Download the latest OPatch version from My Oracle Support.
    2. Copy the files to the local host and extract them to the ORACLE_HOME/OPatch directory.
    3. 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
  3. Download the latest database patches from My Oracle Support and copy the files to the local host.
    scp patchfilename root@hostname:directory
  4. Unzip patches to an empty directory, for example, /tmp/patchesDir as oracle 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
  5. For Oracle Database Appliance High-Availability deployments, set up SSH Keys for secure connection.
  6. Analyze the patches.
    $ORACLE_HOME/OPatch/opatchauto apply directory_with_patches_extracted -analyze -oh $ORALCE_HOME -log /tmp/opatchAutoAnalyzePatch.log
  7. As root user, apply the patches.
    $ORACLE_HOME/OPatch/opatchauto apply directory_to_extract_patches -oh $ORACLE_HOME -inplace
  8. When patching is completed on both nodes, run utlrp.sql and catcon.pl scripts to recompile invalid objects in the database.
  9. Update the registry to ensure that system component values are registered.
    # odacli update-registry -n dbhome -f

Parent topic: Applying Additional Patches and Updates on Bare Metal Systems

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

Follow these steps to clean up the patch repository:
  1. In the Browser User Interface, click Patch Manager.
  2. Click the Cleanup Repository tab, and then click Refresh to list the available patches in the repository.
  3. 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.
  4. Click Cleanup Clone Files to clean up clone files for selected components from the repository at /opt/oracle/oak/pkgrepos/orapkgs/clones/.
  5. Click Cleanup Repository to submit the cleanup repository job.
  6. 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

You can upgrade database homes of the following releases:
  • Oracle Database 12.2 to 19c
  • Oracle Database 12.1 to 19c

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.

  1. Log into the Browser User Interface with the oda-admin user name and password.
    https://Node0–host-ip-address:7093/mgmt/index.html
  2. Click the Database tab, and then select a database, click Actions, and then click Upgrade.
  3. 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.

Parent topic: Patching Oracle Database Appliance

Setting Dynamic Default Parameters

You can set dynamic default parameters using the BUI.

Setting Dynamic Default Parameters Using the Browser User Interface

Follow these steps:
  1. From the Appliance page, click Parameter Repository.
  2. The Parameter Repository page lists all the parameters in the repository. Currently, parameters of type RDBMS are supported.
  3. Select Update Parameter to create a new configuration property.
  4. In the Update Parameter page, specify the Parameter Name and Value, and provide an optional Description. Specify whether you want to create the parameter for the Bare Metal or DB System. You can also specify the whether the parameter applies to All DB Systems or you can select the DB system for which you want to create the parameter.
  5. Click OK.
  6. Confirm the action to submit the job. Monitor the job progress and check that it completes successfully.
  7. To update a parameter, select the Update option from the Actions menu.
  8. You can edit the Value, Description, and select whether the parameter applies to Bare Metal or DB System. You can also select the DB system for which you want to update the parameter or choose to apply the parameter to All DB Systems.
  9. Click Update.
  10. To delete a parameter, select the Delete option from the Actions menu. You can delete the parameter from the Bare Metal or DB System. You can also select the DB system for which you want to delete the parameter or choose to delete the parameter from All DB Systems.
  11. Click Delete.

Parent topic: Patching Oracle Database Appliance