My Oracle Support Banner

Applying patch:21068539 "OJVM PATCH SET UPDATE 11.2.0.4.4" via Enterprise Manager patch plan fails at "Deploy Patch" stage (Doc ID 2060744.1)

Last updated on APRIL 21, 2017

Applies to:

Enterprise Manager for Oracle Database - Version 12.1.0.1.0 and later
Information in this document applies to any platform.

Symptoms

Applying patch:21068539 "OJVM PATCH SET UPDATE 11.2.0.4.4" to an 11.2.0.4 database using Enterprise Manager patch plan, fails at the "Deploy Patch Phase". This issue does not happen when applying OJVM PSU to 12.1.0.2 Database version.

New Update:

This is fixed in the October OJVM PSU onwards.  This means that <Patch:21555791>  "ORACLE JAVAVM COMPONENT 11.2.0.4.5 DATABASE PSU (OCT2015)" contains the fix.

IMPORTANT INFORMATION

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 11.2.0.4.8 (INCLUDES CPUOCT2015) OR
Patch 21352646: DATABASE SECURITY PATCH UPDATE 11.2.0.4.0 (CPUOCT2015) OR
Database patch for Exadata 11.2.0.4.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:

Issue: Patches ,21352635,21555791 need to execute SQL/PL SQL files in the upgrade mode, whereas other patches need to execute these files in the normal mode. This combination is not supported in the same patching session.

Solution:
In a single patching session, select only those patches which have the same SQL/PL SQL execution mode.

This means that it's necessary to first apply one of the pre-requisite patches in a separate patch plan, and after this has been done, then apply <Patch:21555791> using a new patch plan.

Please also note that additionally there is a combo patch which delivers <Patch:21555791> and the pre-requisite patch <Patch:21352635> together.  This combo patch is known as <Patch:21744343> "COMBO OF OJVM COMPONENT 11.2.0.4.5 DB PSU + DB SPU 11.2.0.4.0.8 (OCT2015)".  This patch also exhibits the same problems as described in this note.  This has been raised as <Bug:22242816> "Failure in applying Oct 2015 Combo Patch 21744343 to SIDB using 12c EM".    For customers who need to use the combo patch, either of the workarounds described in this note should be used.

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"

For example:

 

##################################################################################### 
##   Executing SQL scripts on databases running from ORACLE HOME : /refresh/64bit/app/oracle/product/11204       
##################################################################################### 

Mon Sep 28 14:07:41 2015 - Status of database [/refresh/64bit/app/oracle/product/11204  (OH), V11204 (SID)] is up!

Mon Sep 28 14:07:41 2015 - Checking Database Objects Status before applying the default sql on database[/refresh/64bit/app/oracle/product/11204 (OH), V11204 (SID)]

SQL*Plus: Release 11.2.0.4.0 Production on Mon Sep 28 14:07:41 2015

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

SQL> SQL> Connected.
SQL> SQL> 
V
-------------------------------------------
VAL87024

In addition the PA_APPLY_SQL<timestamp>.log located in:

$ORACLE_HOME<of database being patched>/EMStagedPatches

shows the following:

SQL> DECLARE
2 openmigrate sys.v$instance.STATUS%TYPE;
3 BEGIN
4 select status into openmigrate from v$instance;
5 IF openmigrate != 'OPEN MIGRATE' then
6 dbms_output.put_line('Ensure database is opened in UPGRADE to apply this patch');
7 dbms_output.new_line;
8 RAISE_APPLICATION_ERROR(-20001,'database not open for UPGRADE');
9 END IF;
10 END;
11 /
Ensure database is opened in UPGRADE to apply this patch
DECLARE
*
ERROR at line 1:
ORA-20001: database not open for UPGRADE
ORA-06512: at line 8 

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.