2 Patching and Upgrade

This chapter describes issues related to the Infrastructure 12.1.2 upgrade.

The following topics are covered in this chapter:

2.1 Issues Pertaining to Product Upgrade

This section contains the following topics:

2.1.1 Upgrade Assistant Script Execution Triggers Error Message on Solaris X64 Platforms

When launching the Upgrade Assistant from a Solaris X64 platform command line, the following error can appear:

./ua: [[: not found

You can ignore this message. The Upgrade Assistant will continue to launch in GUI mode despite this error.

2.1.2 Log Button Does Not Display Logs

The Log button in the Upgrade Assistant wizard does not display the logs.

Use a text editor outside the Upgrade Assistant to view the logs.

2.1.3 Error Message Displayed on Terminal Screen While upgrading OHS 12.1.2 on Solaris.X64

The following error message is displayed on the terminal screen during Fusion Middleware Upgrade Assistant 12.1.2 ua script execution :

./ua: [[: not found
./ua: [[: not found

Ignore this error message.

2.1.4 JRF Domains Do Not Support JRockit in 12.1.2

In Oracle Fusion Middleware 12.1.2. JRockit is supported only for WebLogic Server client-side applications. JRockit is no longer supported for use with WebLogic Server JRF domains

2.2 Issues Pertaining to Product Patching

This section contains the following topics:

2.2.1 Error with Library Regeneration During OPatch

The following message is displayed when library regeneration fails during OPatch:

Patching component oracle.wls.core.app.server, 12.1.2.0.0... 

There is an error with library regeneration, please refer to the log file for details. OPatch will continue applying the patch..... 

OPatch failed with error code 115

Due to this error, the patch is not applied to all affected libraries. This leads to an inconsistent state of the environment.

Run OPatch rollback to restore the pre-patch environment.

For more information about how to roll back a patch, see "Using OPatch to Patch Oracle Fusion Middleware" in Patching with OPatch.

2.2.2 OPatch Does Not Restore Regenerated Libraries Even After User Quits the Patching Process

When OPatch postscript fails, users choose not to proceed the patching process, and quit. After quitting the patching process, OPatch does not restore regenerated libraries correctly.

Check the OPatch log to determine whether the library regeneration has occurred. If the library regeneration has occurred, then apply the patch again. When the OPatch post script fails again, choose y to proceed with the patching process. OPatch will not rollback the patch automatically this time. User needs to roll back OPatch manually to restore the pre-patch environment.

For more information about how to roll back a patch, see "Using OPatch to Patch Oracle Fusion Middleware" in Patching with OPatch.