Updating Oracle Exadata Database Node

Update Oracle Exadata database servers to a higher Oracle Exadata software version.

Note:

You must download the latest version of the Patch Manager before starting the patch operation. Refer to my Oracle Support note 888828.1 to download the latest version of the Patch Manager software: https://support.oracle.com/rs?type=doc&id=888828.1.

1. Create an Oracle Exadata Database node image.

   The following command imports an Oracle Exadata image to the Oracle FPP Server as an image. In the example, image specifies the name of the Oracle Exadata image that you want to add, imagetype specifies EXAPATCHSOFTWARE for Oracle Exadata software, version specifies the version of the Oracle Exadata software, and path specifies the absolute path location of the Oracle Exadata software home that you want to import.

   rhpctl import image -image image_name -imagetype EXAPATCHSOFTWARE 
   -version software_version -path absolute_path

   When you import an Oracle Exadata software home with this command, the version parameter must be the exact version of the Oracle Exadata software required by the patchmgr on the database node, for example 23.4.0.0.0.221111.1. The path parameter should contain Oracle Exadata update zip files.

2. Deploy the Oracle Exadata Database node image to the client cluster.

   Note:

   You need to deploy the image only when running the patch operation from an Oracle FPP Client. This step is not required when running the patch operation from the Oracle FPP Server.

   The following command deploys an Oracle Exadata image to a client cluster. In the example, image specifies the name of the Oracle Exadata image that you want to deploy, client specifies the name of the cluster to which you want to deploy the image, and path specifies the absolute path location for deploying the Oracle Exadata software home on the rhpclient-less target or client side.

   rhpctl deploy image -image image_name 
   -client client_cluster_name -path image_file_path

   The targetnode parameter is required if the node hosting the home is not a Oracle Fleet Patching and Provisioning Client. If the rhpclient-less target or client option is not specified, then the Oracle Exadata image is deployed to the Oracle Fleet Patching and Provisioning Server.

3. Evaluate the current configuration and perform pre-upgrade checks.

   The following command evaluates the current configuration and performs pre-upgrade checks. In the example, image specifies the name of the Oracle Exadata image that you want to use for update, iso_repo specifies the image in the ISO repository, and client specifies the name of the cluster in which you want to update database nodes.

   Note:

   The Oracle Exadata database node image ZIP does not include the patchmgr binary. When you import the image, ensure that patchmgr (dbnodeupdate.zip) is in the directory specified by the -path option. The -path directory must contain both the database node image ZIP (ISO ZIP) and dbnodeupdate.zip. If dbnodeupdate.zip is not available, place patchmgr in a fixed location on the target system and specify that location with the -patchmgrloc option.

   rhpctl update exadata -dbnodes comma_separates_list_of_nodes -image image_name -iso_repo iso_image_name 
   -client client_cluster_name -patchmgrargs "patch_manager_arguments" -liveupdate full -eval

   • If you do not specify the list of nodes for -dbnodes, then Oracle FPP automatically discovers all active database nodes in the cluster.
   • If the client option is not specified when issuing the command, then database node update is performed on the Oracle Fleet Patching and Provisioning Server.
   • The -liveupdate option is a new feature available for Oracle Exadata 24.1 and later releases.
4. Create a backup of the current configuration.

   rhpctl update exadata -dbnodes {comma_separates_list_of_nodes | [-batches "comma_separated_list_of_batches]} -image image_name 
   -iso_repo iso_image_name -client client_cluster_name -patchmgrargs "patch_manager_arguments" -backup

5. Update Oracle Exadata Database node with the new image.

   rhpctl update exadata -dbnodes {comma_separates_list_of_nodes | [-batches "comma_separated_list_of_batches"]} -image image_name 
   -iso_repo iso_image_name -client client_cluster_name -patchmgrargs "patch_manager_arguments" -liveupdate full

6. Query the Oracle Exadata client to check the client configuration and Exadata live update information:

   rhpctl query client -client client1 -exadata
   
   Audit ID: 90
   Site: client1
   Rapid Home Provisioning Client Version: 23.0.0.0.0
   Rapid Home Provisioning Client Full Version: 23.6.0.0.0
   Enabled: true
   Host from which RHPC last registered: client1vm01.example.com
   Port number last registered by RHPC: 8896
   ...
   ...
   Image status: success
   Exadata software version: 23.1.7.0.0.231012
   Exadata Live Update Type: full
   Exadata Live Update Version: 23.1.90.0.0.240226 (Live Update applied. Reboot at any time to finalize outstanding items.)
   Node type: GUEST
   ...
   ...