1. Administering Oracle Java Cloud Service
  2. Troubleshoot Oracle Java Cloud Service
  3. Problems with Patching and Rollback

Problems with Patching and Rollback

This section identifies some potential issues you may face after patching and rollback operations.

The following recommendations ensure that patching and rollback operations enable you to continue running your applications.

My identity key store and trust store are missing after a patching, rollback, or restoration operation

If you have identity key stores and trust stores, they can disappear after you apply a patch, roll back a patch, or restore a backup. You may have configured one of the following:

  • Custom identity key store and custom trust store

  • Custom identity key store and Java standard trust store

  • WebLogic Server identity key store and WebLogic Server trust store

Patching , rollback, and restoration operations replace the directories you may have used to keep the custom key store and trust store, so they are essentially emptied.

To protect your key store and trust store, create the key stores and trust stores by using the OPSS KeyStoreService (KSS). See Configuring the OPSS Keystore Service for Demo Identity and Trust in Administering Security for Oracle WebLogic Server.

If you don’t want to use the OPSS KeyStoreService, you can put the key store and trust store in the WebLogic domain created by Oracle Java Cloud Service.

It’s particularly important to protect your key store and trust store for JDK patching. Each JDK patch replaces the previous version.

Before you apply a WebLogic Server patch:

  • Do not put CA certificates in the existing demo keystores

  • Do not put custom key stores and trust stores in the <MW_HOME>/wlserver/lib directory

  • Do not put CA certificates anywhere on the system except in key stores

I receive a message stating that the virtual machines are unhealthy

You cannot apply a patch if the service's virtual machines are not in a healthy state.

Restore the service using a backup and try patching again.

I receive a message stating that the service is busy with another operation

You cannot apply a patch when the service is under maintenance, for example, scaling or backup.

Wait until the service is no longer under maintenance and try patching again.