Applying patch:21068539 "OJVM PATCH SET UPDATE 220.127.116.11.4" via Enterprise Manager patch plan fails at "Deploy Patch" stage
Last updated on APRIL 21, 2017
Applies to:Enterprise Manager for Oracle Database - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Applying patch:21068539 "OJVM PATCH SET UPDATE 22.214.171.124.4" to an 126.96.36.199 database using Enterprise Manager patch plan, fails at the "Deploy Patch Phase". This issue does not happen when applying OJVM PSU to 188.8.131.52 Database version.
This is fixed in the October OJVM PSU onwards. This means that <Patch:21555791> "ORACLE JAVAVM COMPONENT 184.108.40.206.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 220.127.116.11.8 (INCLUDES CPUOCT2015) OR
Patch 21352646: DATABASE SECURITY PATCH UPDATE 18.104.22.168.0 (CPUOCT2015) OR
Database patch for Exadata 22.214.171.124.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:
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