Checking Prerequisites Before Applying a Patch

Before you apply a patch, you can check its prerequisites to make sure that it can be successfully applied by using the Oracle Database Classic Cloud Service console or, if desired, by using one of the ways listed in Other Ways to Check Prerequisites Before Applying a Patch at the end of this topic.

The prerequisites-checking operation:

• Confirms that the patch is available for download.

• Verifies that there is enough space in the /u01 directory to apply the patch.

• Compares the patch’s prerequisites to the database deployment by running opatch prereq commands.

Checking Prerequisites Before Applying a Patch by Using the Oracle Database Classic Cloud Service Console

Before You Begin

Before checking patch prerequisites, make sure the database deployment has the latest cloud tooling because some patches require a certain minimum level of cloud tooling. For more information, see Updating the Cloud Tooling on Database Classic Cloud Service.

Procedure

1. Go to the Patching page for the database deployment on which you want to check patching:

   1. Open the Oracle Database Classic Cloud Service console.

      For detailed instructions, see Accessing the Oracle Database Classic Cloud Service Console.

   2. Click the database deployment on which you want to check patching.

      The Oracle Database Classic Cloud Service Overview page is displayed.

   3. Click the Administration tile and then click the Patching tab.

      The Oracle Database Classic Cloud Service Patching page is displayed. A list of patches you can apply appears in the Available Patches section.

2. Click the action menu () that is associated with the patch whose prerequisites you want to check, and then select Precheck.

   If further input is required, specify the required details in the Patch Precheck Service window and click Precheck to continue. The Patch Precheck Service window displays in the following circumstances:

   • If you have previously checked prerequisites for the selected patch, the Patch Precheck Service window shows the results of the previous check and asks if you want to perform another set of prerequisite checks.

   The Patching page redisplays, showing a status message indicating that prerequisite checks are in progress.

3. Refresh the Patching page occasionally to update the status message.

   Note that prerequisite checking can take several minutes to complete.

4. When the prerequisite checks are completed, the Precheck results link is displayed.

   Click Precheck results to display the results of the prerequisite checks.

Other Ways to Check Prerequisites Before Applying a Patch

• For database deployments hosting single-instance databases, you can use the patch db prereq subcommand of the dbaascli utility. See Checking Patch Prerequisites by Using the dbaascli Utility.

• For database deployments hosting Oracle Real Application Clusters (RAC) databases, you can use the prechecks option of the raccli apply patch command. See Checking Patch Prerequisites by Using the raccli Utility.

Checking Patch Prerequisites by Using the dbaascli Utility

You can use the patch db prereq subcommand of the dbaascli utility to the check the prerequisites of a patch before you apply it to a database deployment hosting a single-instance database or an Oracle Data Guard configuration of single-instance databases.

Before You Begin

Before checking patch prerequisites, make sure the database deployment has the latest cloud tooling because some patches require a certain minimum level of cloud tooling. For more information, see Updating the Cloud Tooling on Database Classic Cloud Service.

Procedure

1. Connect as the opc user to the compute node.

   For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).

2. Start a root-user command shell:

   $ sudo -s
   #

3. Check the the prerequisites of a patch:

   # dbaascli patch db prereq
   

   The prerequisites report displays.

   The patch db prereq subcommand is not yet available on Oracle Cloud at Customer. Instead, for a database deployment hosting a single-instance database you must use the dbaascli dbpatchm prereq command, and for a database deployment hosting an Oracle Data Guard configuration of single-instance databases you must use the dbpatchmdg precheck_async command.

4. Exit the root-user command shell:

   # exit
   $

Checking Patch Prerequisites by Using the raccli Utility

This topic does not apply to Oracle Cloud Infrastructure or to Oracle Cloud at Customer.

You can use the prechecks option of the raccli apply patch subcommand to check the prerequisites of a patch before you apply it to a database deployment hosting an Oracle Real Application Clusters (RAC) database.

Before you begin

Before you precheck a patch, make sure the database deployment has the latest cloud tooling. For more information, see Updating the Cloud Tooling by Using the raccli Utility.

Procedure

1. Connect to the compute node as the opc user.

   For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).

2. Precheck the patch using the apply patch -prechecks subcommand for the database type you are checking:

   • Database Clustering with RAC:

     $ raccli apply patch -db -tag tag-name -prechecks
     

   • Database Clustering with RAC and Data Guard Standby:

     $ raccli apply patch -db -tag tag-name -prechecks -dg
     

   Where tag-name is the name of the patch. To find out the tag name for the latest available patch, see What's New for Oracle Database Classic Cloud Service.

3. Track the progress of the precheck job to its completion by using the raccli describe job command.