1. Administering Oracle Java Cloud Service
  2. Patch an Oracle Java Cloud Service Instance
  3. Perform Patch Prechecks and Address Patching Issues

Perform Patch Prechecks and Address Patching Issues

Optional patching prechecks identify possible sources of patching failure, if any, enabling you to identify and remedy problems before attempting to patch.

Topics

Perform a Patch Precheck

Before you apply a patch on an Oracle Java Cloud Service instance, you can run a precheck to identify and fix potential issues.

The precheck operation helps detect problems such as:

  • Disk space shortage

  • Missing database connectivity

  • Servers not running

  • Storage access failure

The precheck operation does not detect whether another maintenance operation, such as a backup, restoration, or scaling operation, is in progress. These operations prevent you from applying a patch.

  1. Access your service console.
  2. Click the name of the service instance to which you want to apply a patch.
  3. Click the Administration tile.
  4. Click the Patching tab.
  5. Beside the patch that you want to precheck, click PSU Menu icon, and then select Precheck.
  6. When prompted for confirmation, click Yes.
  7. To determine whether the prechecks completed, periodically click Refresh Refresh icon.
    The Precheck summary link is displayed.

    • If prechecks pass, a green check mark icon is displayed.

    • If prechecks fail, a red exclamation mark icon is displayed.

  8. Click Precheck summary.
  9. If there are precheck failures, address the issues, and then run Precheck again.

After you fix any precheck failures, you are ready to apply the patch.

Address Patch Precheck Issues

Running prechecks prior to patching lets you know of conditions that would prevent successful patching.

By performing prechecks, you can identify problems that you can address before you try to apply a patch.

Accessing Error Messages

Error messages are shown on the Patching Precheck Results dialog displayed when you click the Patching results link on the Patching page.

Note:

The values provided in the following messages are examples. Your values and host names will differ.

Topics:

Failure Due to Manual Patching

If you have installed patches manually and then attempt to apply approved patches from the Patching page of the Oracle Java Cloud Service Console, you see messages such as the following. 

2019-07-23T11:52:26.145+00:00[SEVERE]:PATCHING-59996-[JaaS]-[1]-[FAILURE]: 
[PSM-PATCH-60000: The patches applied on the service are not matching the expected 
patches. The expected patches are ["19795066","19154304","18905788","19632480",
"19030178","22754279","19002423","21663638"] and the actual patches 
are ["19632480","26910516","19002423","19154304","19030178","18905788","19795066",
"22754279","18459080","21663638"]. When the patch is applied, the patch operation 
will move the service to patch level [12.2.1.2.190617]]

Remove the patches you applied manually, and then rerun patching prechecks or apply a patch from within the Patching page of the Oracle Java Cloud Service Console. To avoid this error in the future, apply approved patches only when they become available from the Patching page.

Disk Space Shortage

If patching would fail because of insufficient space on the block storage volume mounted on the Administration Server VM, you see the following error message.

Not enough space on vm. Dir size: 457 Free space: 350

If there is not enough space, try freeing up disk space by deleting unwanted backups, for example.

Missing Database Connectivity

If patching would fail because of missing database connectivity, you see the following error message.

Could not connect to database running at 
location. 
Please ensure that the database, VM, database instance, and 
database listener being used by the service are running. 
Currently configured: testdb.example.com:1521:orcl12c

Ensure that your database exists and is healthy. Open your Oracle Database Cloud Service Console and check the status of your database deployment.

Node Manager Is Not Running

If patching would fail because the Node Manager is not running, you see the following messages.

Nodemanager is not running on test_adminserver. 
Could not reach node manager on host: test_adminserver.

Start the Node Manager.

Connectivity Issues between Managed Servers and the Administration Server

If patching would fail because there is no SSH connectivity between the Managed Servers and the Administration Server, you see the following messages.

Connectivity issue between Managed Server 
VM test-wls-2 and Admin Server VM test-wls-1. Please contact 
Oracle Support Services to ensure connectivity 
is restored.

Contact Oracle Support Services to ensure that connectivity is restored.

Servers Not Running

If patching would fail because the Administration Server or Managed Servers are not running, you see the following messages.

Admin Server is not running on test-wls-1.
Please ensure Admin Server is running through 
Node Manager. Could not reach adminserver: test_adminserver 
on host test-wls-1 through NodeManager.

Could not reach managed server: test_server_1 on host test-wls-1
through NodeManager. Please refer to the WebLogic
documentation to start managed server through 
node manager using WLS Console or wlst.

Start servers that are not running.

Storage Access Failure

If patching would fail because the storage container cannot be accessed, you see the following message.

Unable to download patch artifact 
from the Oracle Cloud Storage.

Although you have a storage container, run a check that tells you whether you have a storage container.

The result can indicate that the container is down.