Oracle® Hyperion Enterprise Performance
Management Architect, Fusion Edition
Release 11.1.2.3.700 Patch Set Update (PSU): 11.1.2.3.700
Readme
Apply this patch to use
Internet Explore Release 11 in Standard Mode. After you apply this patch, you
can no longer use Internet Explorer Enterprise Mode. You must apply the
11.1.2.3.700 PSU for all EPM products in your deployment. For details see the “Prerequisites”
section.
This Readme file describes the defects fixed in this patch and the requirements and instructions for applying this patch.
Caution: Oracle urges you to carefully read and understand the following requirements. Failure to comply may result in applying a patch that can cause your application to malfunction, including service interruptions, loss of data or both.
You can apply this patch to the following
releases.
1. Oracle® Hyperion Enterprise Performance Management Architect (Performance Management Architect), Fusion Edition 11.1.2.3.500. (17479840).
2. Oracle® Hyperion Enterprise Performance Management Architect (Performance Management Architect), Fusion Edition 11.1.2.3.501. (19466859).
1. Ensure this product's 11.1.2.3.50x ((17479840 or 19466859) patch is applied first.
2. Apply these required EPM System release 11.1.2.3.700 PSUs first:
· Apply Oracle Hyperion Shared Services 11.1.2.3.700 PSU – 20675028. Apply the patch to all computers in the deployment.
· Apply Oracle Hyperion Enterprise Performance Management Workspace 11.1.2.3.700 PSU – 20612400. Apply to all computers with Foundation Services deployed.
3. For the rest of the products, apply the product patch on the computer where the product is deployed. Use the table below to find EPM product 11.1.2.3.700 PSU patch numbers. If the product is not listed, then it does not have a 11.1.2.3.700 PSU, and no action is needed.
Note: For Oracle Hyperion Calculation Manager, apply the patch on all computers where Oracle Hyperion Planning, or Oracle Hyperion Financial Data Quality Management Enterprise Edition, or Oracle Essbase is deployed.
Note: If you are using IBM WebSphere Application Server, you must redeploy the EPM System web applications after applying EPM System release 11.1.2.3.700 PSUs.
Product |
11.1.2.3.700
PSU Patch Number |
Oracle Data Relationship Management |
21107706 |
Oracle Financial Reporting |
20838970 |
Oracle Hyperion Calculation Manager |
21292109 |
Oracle Hyperion Disclosure Management |
20619384 |
Oracle Hyperion Financial Close Management |
20768349 |
Oracle Hyperion Financial Data Quality Management Enterprise Edition |
20779592 |
Oracle Hyperion Financial Management |
20955781 |
Oracle Hyperion Interactive Reporting |
20768325 |
Oracle Hyperion Performance Management Architect |
20929659 |
Oracle Hyperion Planning |
20643564 |
Oracle Hyperion Profitability and Cost
Management |
20915688 |
Oracle Hyperion Reporting and Analysis
Framework |
20768325 |
Oracle Hyperion Tax Provision |
21219363 |
Oracle Hyperion Web Analysis |
20880421 |
Supported
Languages
This patch can be applied to all languages
supported in release 11.1.2.3.000 of Oracle Enterprise Performance Management
System. For the Oracle Enterprise Performance Management System Supported
Platform Matrix, go to: http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
Microsoft has identified a security issue that
could allow a hacker to compromise your Windows-based system. You MUST install
the Microsoft VC 2005
SP1 ATL redistributable pack before applying this patch.
The updated VC 2005 redistributable is
available here for both x86 (32-bit) and x64 (64-bit):
The user applying the patch should be the user who was set
up to install and configure EPM System products. Required user privileges or
rights:
Windows:
Use the user account that has Local administrator rights and was set up for
installation and configuration. This user is an administrator and is the same
for all EPM System products. Assign local policies if required by the product. Such
assignments typically are: “Act as part of the operating system, Bypass traverse
checking, Log on as a batch job, Log on as a service.”
UNIX/Linux:
Use the account that was used to install EPM System products and has Read,
Write, and Execute permissions on $MIDDLEWARE_HOME. If you installed other
Oracle products, the user who installed EPM System products must be in the same
group as the user who installed the other Oracle products. OPatches are
not intended to be applied using a root user.
For supported platforms refer the Oracle
Enterprise Performance Management System Certification Matrix.
These defects are fixed in this release.
Defect Number |
Defect Fixed |
• 21127936, 20213957 |
Add the ability to bypass the validation of the member-level DataStorage property for EssbaseASO applications. |
• 21032391, 20922373 |
It should be
possible to specify the order of custom dimensions of Financial Management
application; except for ‘Use For Currency’, From and To dimensions; which must
have order value of 1 and 2 respectively. |
• 20683486 |
In Microsoft SQL
server2008R2; Dimension Server takes long time to start after the Lifecycle
Management import of a large dimension. |
The following issues are the noteworthy known issues for this patch.
Defect Number |
Defect Description |
• 16310436 |
In Dimension Library, expand two member trees, select base member of the second tree and left click the first member tree to collapse and select it; now second tree’s base member is still not unselected and also its properties are loaded in the property grid editor. |
• 16984252 |
In Dimension library, create a Hyperion Planning member with name ‘%’ in it; ‘%’ character gets re-displayed as ü. Workaround: Rename the member to get back the ‘%’ character; further member name gets displayed correctly in Hyperion Planning after deployment. |
• 17229508 |
In 64 bit Microsoft Excel; File generator fails with error: 'Compile error in hidden module; frmFlatFileGeneration’. |
• 17765670 |
Importing the Lifecycle Management from 11.1.1.4.500 to 11.1.2.3.500 changes some of the dimension level and member level properties. The detailed information is provided in the Oracle® Hyperion Enterprise Performance Management Architect, Administrator’s Guide. Please refer to the section “Property Differences from Earlier Releases.” |
• 16863069 |
Lifecycle Management imported Essbase
applications from 11.1.1.4.500 to 11.1.2.3.500 are unable to deploy. Workaround: 1. Right click on the Essbase application
from application Library and select Edit. 2. Make sure application is displayed in
Dimension Library. 3. Right-click on the application name
and select ‘Dimension Performance Settings’. 4. Sort the order of the dimensions and
click ok. 5. Now Application deployment will be
successful. |
• 17739405 |
Lifecycle Management import fails to
process shared dimension member alias information and in creating association
between local and shared dimension, further Migration status report shows a
warning: ‘Property 'Custom1TopMember' is deprecated; therefore no dimension
association was created for it’. Workaround: 1.
Navigate to Shared Service console, 'File System' node. 2.
Select Financial Management related dimensions under 'Shared Library
Dimensions'. 3.
Also select HFM application, by navigating to 'Application Metadata' and then
expanding 'Consolidation applications'. 4. Import above selected artifacts. |
• 17963359 |
Transformation of classic to EPM
Architect Financial Management application fails for the applications with
security classes having underscore (_) in their names. |
• 16468539 |
Validation tool in 11.1.2.3.500 may report an error: “dbJDBCDriverProperty missed”. |
• 14761743 |
In Internet Explorer 9.x browser, grid editor with scroll bar shall have dislocation of rows and columns. |
• 16573845, 16554466 |
In Oracle Access Manager 11g, resources
are protected by default and they need to be unprotected to enable processing
flow and internal requests between components; there by make EPM Architect’s
functionalities work (e.g.: Import, File generator, Batch client). |
The section includes important information about applying this patch for Performance Management Architect.
To apply this patch:
1. Stop all Enterprise Performance Management Architect services.
2. Stop Oracle® Hyperion Calculation Manager (Calculation
Manager), Oracle® Essbase Studio and Oracle® Hyperion Profitability and Cost
Management (Profitability and Cost Management), if they are running on the same
computer where Performance Management Architect services are running.
3. Download and unzip the downloaded patch file, 20929659_xxx.zip to the <EPM_ORACLE_HOME>/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).
Where xxx represents Windows 32-bit,
64-bit, or UNIX:
For Windows 32-bit, the patch file name
is: 20929659_WIN32.zip.
For Windows 64-bit, the patch file name
is: 20929659_x64.zip.
For UNIX, the patch file name is: 20929659_UX.zip.
4. Back up the EPMA database repository.
Note: If you need to roll back this Patch Set Update, you need to restore from this database backup. Restoring from the backup, results in loss of all changes.
5. On the computer where the Performance Management Architect Dimension Server, Web Tier, and Data Synchronization components are located, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.
6. To
apply the patch, enter the following command on one line:
Windows:
opatch.bat apply <EPM_ORACLE_HOME>/OPatch/20929659 -oh <EPM_ORACLE_HOME>
-jdk <MIDDLEWARE_HOME>/jdk160_35
NOTE: The default for <EPM_ORACLE_HOME>
is C:/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME>
is C:/Oracle/Middleware.
UNIX/Linux:
./opatch apply <EPM_ORACLE_HOME>/OPatch/20929659 -oh <EPM_ORACLE_HOME> -jdk
<MIDDLEWARE_HOME>/jdk160_35 -invPtrLoc
<EPM_ORACLE_HOME>/oraInst.loc
NOTE: The default for <EPM_ORACLE_HOME>
is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME>
is $HOME/Oracle/Middleware.
7. Restart Enterprise Performance Management Architect services.
8. Start Oracle® Hyperion Calculation Manager (Calculation Manager), Oracle® Essbase Studio and Oracle® Hyperion Profitability and Cost Management (Profitability and Cost Management), if they were stopped in step 2.
9. Restart Foundation Services.
10.
All
users should now clear cached files from their browsers.
To roll back a patch:
1. Stop all Enterprise Performance Management Architect services.
2. Stop Oracle® Hyperion Calculation Manager (Calculation Manager), Oracle® Essbase Studio and Oracle® Hyperion Profitability and Cost Management (Profitability and Cost Management), if they are running on the same computer where Performance Management Architect services are running.
3. From a command line, change the directory to <EPM_ORACLE_HOME>/OPatch (by default, Oracle/Middleware/EPMSystem11R1/OPatch).
4.
To roll back the patch, enter the following
command on one line:
Windows:
opatch.bat rollback -id 20929659 -oh
<EPM_ORACLE_HOME> -jdk
<MIDDLEWARE_HOME>/jdk160_35
NOTE: The default for <EPM_ORACLE_HOME> is C:/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME>
is C:/Oracle/Middleware.
UNIX/Linux:
./opatch rollback –id 20929659 -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME> /jdk160_35 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc
NOTE: The default for <EPM_ORACLE_HOME> is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME>
is $HOME/Oracle/Middleware.
5.
Start
all Enterprise Performance Management Architect services.
6.
Start Oracle®
Hyperion Calculation Manager (Calculation Manager), Oracle® Essbase Studio and
Oracle® Hyperion Profitability and Cost Management (Profitability and Cost
Management), if they were stopped in step 2.
7. Restart Foundation
Services.
8.
All
users should now clear cached files from their browsers.
Troubleshooting FAQs
In EPM System Release 11.x, you can use the lsinventory command to OPatch to find the release and patches that are
installed in an Oracle Home. For example, enter the following command on one
line:
Windows:
opatch.bat lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_35
UNIX/Linux:
./opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_35
–invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc
If the patch that you apply conflicts with
a previously applied patch, you may receive the following error message when
running OPatch:
Patch(es) <PreviousPatch#>
conflict with the patch currently being installed (<NewPatch#>).
If you continue, patch(es) <PreviousPatch#> will be rolled back and the
new patch (<NewPatch#>) will be installed.
If a merge of the new
patch (<NewPatch#>) and the conflicting patch(es)
(<PreviousPatch#>) is required, contact Oracle Support Services and
request a Merged patch.
This error is returned when one patch
attempts to update a previously patched file. When this conflict happens, you
can either (1) roll back the previous patch and apply
the new patch (this action might be appropriate if the previous patch was not
critical) or (2) request a “merged patch” consisting of the new patch and the
patch that it conflicts with. To request a merged patch, contact your Oracle
Support representative.
This warning
means that the patch being applied is a superset of a patch already on the
deployment and the existing patch will be rolled back. The following snippet
shows the context of this warning.
The following warnings have occurred during OPatch execution:
1) OUI-67078:Interim patch 12345678 is a superset of the patch(es) [77777777]
in OH C:\Hyperion
-----------------------------------------------------------------------------------
OPatch Session completed with warnings.
I
applied the patch successfully but I don’t see the changes from the patch in
the product. What should I do?
When patching an
.EAR file for an application, you may need to delete the cached files in the
following folders in order to see the changes provided with the patch:
·
<MIDDLEWARE_HOME>/user_projects/domains/<DOMAIN_NAME>/servers/
<MANAGED_SERVER_NAME/tmp/
·
<MIDDLEWARE_HOME>/user_projects/domains/<DOMAIN_NAME>/servers/
<MANAGED_SERVER_NAME/cache
EPM Architect fails
due to Oracle database connection time out. What should I do?
Below steps may help
1.
Stop EPM Architect Dimension Server
2. Navigate to
the " BPMA_Server_Config.xml" file
(<Middleware
Home>\EPMSystem11R1\products\Foundation\BPMA\AppServer\DimensionServer\ServerEngine\bin)
3.
Take the backup of the BPMA_Server_Config.xml
4. Edit the
logging configuration section of your BPMA_Server_Config.xml file so that
debug-level messages will be logged to the Windows Event Viewer by changing the
logging level from INFO to DEBUG see below.
<log4net debug="false">
<!-- Define some output appenders
-->
<appender
name="ConsoleAppender"
type="log4net.Appender.ConsoleAppender,log4net"
>
<param name="Threshold" value="DEBUG"
/>
<layout
type="log4net.Layout.PatternLayout,log4net">
<param name="ConversionPattern"
value="%d %m%n" />
</layout>
</appender>
<appender
name="EventLogAppender"
type="log4net.Appender.EventLogAppender,log4net"
>
<param
name="ApplicationName" value="AWB_DimServer" />
<param name="LogName"
value="Application" />
<param
name="Threshold" value="DEBUG" />
<layout
type="log4net.Layout.PatternLayout,log4net">
<param name="ConversionPattern"
value="[%t] %-5p %m" />
</layout>
</appender>
<appender
name="DebugOutAppender"
type="log4net.Appender.OutputDebugStringAppender,log4net"
>
<param
name="Threshold" value="DEBUG" />
<layout
type="log4net.Layout.PatternLayout,log4net">
<param name="ConversionPattern"
value="%X{processid}
Thread ID: [%t];
%-5p %m" />
</layout>
</appender>
<appender
name="ODLAppender"
type="Hyperion.DimensionServer.ODLAppender,odl_appender_2">
<param
name="Threshold" value="DEBUG" />
</appender>
<!--
Setup the root category, add the appenders and set
the default priority -->
<root>
<priority
value="DEBUG" />
<appender-ref
ref="ConsoleAppender" />
<appender-ref ref="EventLogAppender"
/>
<appender-ref
ref="DebugOutAppender" />
<appender-ref
ref="ODLAppender" />
</root>
5. Now add the
following XML tags under </Data_Access_Layer>
section of the BPMA_Server_Config.xml
<ConnectionPooling>
<PoolingEnabled>true</PoolingEnabled>
<!--Connection
Lifetime is the maximum life time (in seconds) of the connection. Setting this to 0 disables it.-->
<ConnectionLifetime>0</ConnectionLifetime>
<!--MaximumPoolSize is the maximum number of connections in the
pool.-->
<MaximumPoolSize>100</MaximumPoolSize>
<!--MinimumPoolSize is the minimum number of connections in the
pool.-->
<MinimumPoolSize>1</MinimumPoolSize>
<!--Controls
the enlistment behavior and capabilities of a connection in context of COM+
transactions or System.Transactions. This setting
must be either "dynamic" or "true".-->
<Enlist>true</Enlist>
<!--The
following 5 settings are specific to Oracle database Connection Timeout is the maximum time
(in seconds) to wait for a free connection from the pool.-->
<ConnectionTimeout>15</ConnectionTimeout>
<!--HA Events
enables ODP.NET connection pool to proactively remove connections from the pool
when an Oracle RAC service, service member, database, or node goes down. Works with RAC, Data Guard, or a single
database instance.-->
<HAEvents>false</HAEvents>
<!--Load
Balancing enables ODP.NET connection pool to balance work requests across
Oracle RAC instances based on the load balancing advisory and service
goal.-->
<LoadBalancing>false</LoadBalancing>
<!--PoolSizeDecrement (Decr Pool
Size) is the number of connections that are closed when an excessive number of
established connections are unused.-->
<PoolSizeDecrement>5</PoolSizeDecrement>
<!--PoolSizeIncrement (Incr Pool
Size) is the number of new connections to be created when all connections in
the pool are in use.-->
<PoolSizeIncrement>1</PoolSizeIncrement>
<!--Validate
Connection validates connections coming from the pool.-->
<ValidateConnection>false</ValidateConnection>
<!--The
following 4 settings are specific to MS SQL Server-->
<ConnectionReset>true</ConnectionReset>
<LoadBalanceTimeout>0</LoadBalanceTimeout>
<!--The
following setting can be used to add any custom setting not covered by anything
else.-->
<CustomSetting></CustomSetting>
</ConnectionPooling>
6.
Increase the ConnectionTimeout to some higher value say for
example 60.
7.
Now start the Dimension Server.
8. Go to event
viewer, there should be an event which includes the entire connection string as
per the changes that we did in step 4.
9. Also make
sure that the connection pool settings disappear if you remove the <ConnectionPooling> section from the
BPMA_Server_Config.xml file and
10.
Restart EPM Architect Dimension Server.
Copyright © 2008, 2015, Oracle
and/or its affiliates. All rights reserved.