Hyperion Planning (MOSC)

MOSC Banner

Which (ADF) July 2017 CPU for Hyperion 11.1.2.4

edited Sep 1, 2017 11:44AM in Hyperion Planning (MOSC) 5 commentsAnswered ✓

Hello

Have been trawling through MOS to identity July 2017 CPU's relevant to our Hyperion installation, i.e. a standard deployment of Hyperion Planning 11.1.2.4.(006) with Essbase / Foundation Services / HTTP etc.

So, considering $MW_HOME/oracle_common specifically, 'opatch lsinventory' looks like this:

     Installed Top-level Products (2):

     Oracle Application Developer 11g                                     11.1.1.7.0
     Oracle AS Common Toplevel Component                         11.1.1.2.0
     There are 2 products installed in this Oracle Home.

Considering Doc ID 2261562.1 (Patch Set Update and Critical Patch Update July 2017 Availability Document) and specifically "Section 3.3.34 Oracle JDeveloper and Oracle ADF", I am minded to apply the following even though there is no specific reference to Hyperion:

      11.1.1.7.0 SPU Patch 25264940

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center