Explore the Patching Page

You can use the Patching page to view available patches, initiate a patching process, and roll back a patch as necessary.

Topics:

What You Can Do from the Patching Page

You can perform these tasks from the Patching page:

View a list of available patches. See View Patch Details.
Perform patching prechecks. See Perform Patch Prechecks and Address Patching Issues.
Apply a patch. See Apply a Patch.
Check the patch history.
Roll back a service to its previous patch level. See Roll Back a Patch.

What You See on the Patching Page

The following table describes the key information shown on the Patching page.

Element	Description
Oracle Java Cloud Service link	Click this link to return to the Oracle Java Cloud Service Console.
(in the page header)	Menu icon provides the following options: Open WebLogic Server Administration Console—Open the WebLogic Administration Console to administer your application environment. Open Fusion Middleware Control Console—Open Fusion Middleware Control to administer your application environment. Open Load Balancer Console—Open the console to administer the load balancer, if a local load balancer has been configured for the service instance. Note that access to the administrative consoles is disabled by default. When you create a service instance, you can enable consoles by selecting a check box on the Details page of the instance creation wizard. For an instance this is already created, you must create an access rule in order to activate the console choices. See Enabling Console Access in an Oracle Java Cloud Service. Start—Start the nodes for the Administration Server, Managed Servers, load balancer, and Managed Servers on the Coherence data tier (if provisioned). Stop—Stop the nodes for the Administration Server, Managed Servers, load balancer, and Managed Servers on the Coherence data tier (if provisioned). Restart—Stop and then immediately restart all the nodes in the service instance. Scale Out—Adds a managed server node. Define Auto Scaling Rules—Opens the Add Rule dialog box, which opens the Rules page where you can configure auto-scaling rules. Change License Type—Opens the Change License Type dialog box, which enables you to choose whether to leverage your existing on-premises (BYOL) license or use your Oracle Java Cloud Service cloud license. Add Load Balancer—Add a user-managed load balancer to this service instance. Disable/Enable Load Balancer—Depending on the selection, either blocks access to the service instance or forwards the requests it receives from clients to the Oracle WebLogic Server Managed Servers. Manage Access Rules—Create and manage rules to control access to the nodes for this service instance. Add SSH Access—Add public SSH keys to the nodes that make up this service instance. Manage Tags/Add Tags—Either remove or add tags to a service instance. Manage Tags appears if a tag already exists for the service instance. Add Tags appears if no tags exist for the service instance. Enable Backups—Enable backups for this service instance. View Activity—View all administrative activities that have been performed on your service instances. View Instance Metrics—View performance metrics for this service instance.
	Click to refresh the page. The date and time the page was last refreshed is displayed adjacent to this button.
Available Patches	Displays patches that are available. The patch number is displayed, as well as whether the patches are optional or mandatory. The release date and affected components are displayed. Information about whether a restart is required is displayed.
	Represents an available patch.
	This menu has two choices: Precheck—Performs prechecks without attempting to patch, and reports any errors found so that you can address them before you patch. Patch–Preforms prechecks, then patches the Oracle Java Cloud Service instance with the selected patch. When Oracle Coherence is enabled for a service instance: Applying a patch will do a rolling restart of the Managed Coherence Servers on the Coherence data tier. By default, the patching operation checks that the `StatusHA` state for a Coherence member is `NODE-SAFE` before shutting down the node to apply the patch. You may choose to override the default behavior by selecting the Confirm checkbox on the Patch Service dialog. If you confirm, this means you accept the possibility of data loss and agree to shut down a server even if `NODE-SAFE` cannot be reached.
	Represents a successful patching precheck operation.
	Represents a failed patching precheck operation.
	Represents a patching operation in progress.
Patch History	Displays the history of patches that have been applied to the service instance.
	Indicates a successful patching operation. Appears in the Patch History section. Click this icon to obtain more information about the patching operation.
	Displayed on a tools patch, indicates that the patch version for your existing service instance is older than the current version. You will also see a warning stating that the service is on a deprecated tools version. To address this issue, apply the latest tools patch to your service instance.
	Initiates an operation to roll back the service to its patch level prior to applying the patch.