Last updated on APRIL 21, 2017
Applies to:Enterprise Manager for Oracle Database - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Applying patch:21068539 "OJVM PATCH SET UPDATE 18.104.22.168.4" to an 22.214.171.124 database using Enterprise Manager patch plan, fails at the "Deploy Patch Phase". This issue does not happen when applying OJVM PSU to 126.96.36.199 Database version.
This is fixed in the October OJVM PSU onwards. This means that <Patch:21555791> "ORACLE JAVAVM COMPONENT 188.8.131.52.5 DATABASE PSU (OCT2015)" contains the fix.
At the time of writing this bug is only fixed in <Patch:21555791>. This patch has the following pre-requisites:
Patch 21352635: DATABASE PATCH SET UPDATE 184.108.40.206.8 (INCLUDES CPUOCT2015) OR
Patch 21352646: DATABASE SECURITY PATCH UPDATE 220.127.116.11.0 (CPUOCT2015) OR
Database patch for Exadata 18.104.22.168.12 (Oct2014)
Please note that it is not possible to use the same patch plan to apply <Patch:21555791> and one of the pre-requisite patches. If this is attempted, the following warning will be shown:
The following steps will reproduce the problem:
1) Ensure that the Oct2014 or later CPU is applied on the database (this is a pre-requisite for the patch)
2) Apply <patch:21068539> using Enterprise Manager patch plan
3) The patch will fail at "For all hosts:Deploy Patch Phase"
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms