Oracle Hyperion Profitability and Cost Management
Release 11.1.2.3.701 Patch Set Update (PSU): 21473370
Readme
New Features in this Cumulative Patch
Web Service to support multi-POV calculations for Standard Profitability applications
Defects Fixed in Patch 11.1.2.3.700
Defects Fixed in Patch 11.1.2.3.506
Defects Fixed in Patch 11.1.2.3.505
Defects Fixed in Patch 11.1.2.3.504
Defects Fixed in Patch 11.1.2.3.503
Defects Fixed in Patch 11.1.2.3.502
Defects Fixed in Patch 11.1.2.3.501
Patch Post-Installation Instructions
Why do I get the following patch conflict error message when running OPatch?
Why do I get the OUI-67078 warning message when applying OPatch?
How can I find out which releases and patches of EPM System products are installed in a deployment?
Solving Issues with Profitability and Cost Management Connection Type
[NOTE TO WRITERS: Go to the File or Document properties and change the “title.” The correct entry for “Author” and “Company” are provided in the template.]
Apply this patch to use Internet Explorer Release 11 in standard mode. After you apply this patch, you can no longer use Enterprise mode. You must apply the 11.1.2.3.700 PSUs for all EPM System products in your deployment. For details, see the "Prerequisites" section.
This Readme file describes the new features, performance enhancements, and defects fixed in this patch and the requirements and instructions for applying this patch.
Caution: You are urged 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.
This patch set update (PSU) requires a full installation of Profitability and Cost Management Services for Release 11.1.2.3.000.
It also requires installation of the Oracle Enterprise Performance Management System 11.1.2.3.500 Patch Set Update 17529887.
[NOTE TO WRITERS: Add a sentence stating whether the patch Requires a full installation or a partial replacement. if it’s a partial replacement, The boilerplate for this statement is: “This patch replaces files in the existing installation and does not require a full installation.”]
[note to writers: State whether this is a cumulative or standalone Patch. If it’s cumulative, list the previous Patch IDs (XXXXXXXX) that are included. To find previous patch IDs, either Ask your team or look for the patch id in uninstall section of previous Readme. If Standalone, state that this patch does not include previous patches.]
You can apply this patch to the following releases:
11.1.2.3.5XX, 11.1.2.3.700.
[NOTE TO WRITERS: list the base Release(s) from which you can apply this patch and Include any prerequisite patches. TO refer to service fixes or service packs using the old nomenclature, use the fully qualified service fix/service pack version number along with the patch id, for example, 11.1.2.0.07 (12345678).]
1.
Ensure that Oracle Enterprise Performance Management System 11.1.2.3.500
Patch Set Update 17529887 has been applied.
All patches must be applied on any machines where Foundation Services is
installed. After all patches are deployed, you must redeploy the web
applications.
2. If you have not already applied the Profitability and Cost Management 11.1.2.3.700 patch, review the Readme file for that patch to be familiar with its content and requirements. If you are using Internet Explorer 11 or FireFox 31, Oracle strongly recommends that you apply that patch first along with all its pre-requisite patches and corresponding patches for other products you have installed.
3. The following patches are required for all Profitability and Cost Management 11.1.2.3.7xx releases; apply them if you have not already done so.
o If you are using WebLogic Application Server, apply WebLogic Server Patch 17437110 for Release 10.3.6 to use Simplified Chinese and Traditional Chinese language settings when using Internet Explorer 10 and Internet Explorer 11 on Windows 8 and Windows 8.1. For instructions on applying the patch, see Oracle Smart Update: Applying Patches to Oracle WebLogic Server.
o Apply Oracle Hyperion Shared Services 11.1.2.3.700 PSU - 20675028. Apply the patch to all computers in the deployment.
o Apply Oracle Hyperion Enterprise Performance Management Workspace 11.1.2.3.700 PSU - 20612400. Apply to all computers with Foundation Services deployed.
o Check My Oracle Support for the latest Essbase portfolio products (Essbase, Essbase Administration Services, Hyperion Provider Services, and Essbase Studio) patches with release version greater than 11.1.2.3.500. If found, download and apply. Be sure to upgrade all components included in the Essbase patch (server, client, runtime client, API, and JAPI).
[NOTE TO WRITERS: Delete the windows and unix sections as appropriate based on what platforms the patch is for.]
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:
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.”
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.
[NOTE TO WRITERS: State whether this patch IS being released on all platforms OR list the supported platforms.
If being released on all platforms, say “Applies to all supported platforms.”
If being released on one specific platform, list that platform (with no introductory text).
If being released on more than one specific platform, put the platforms in a bulleted list (with no introductory text). For example:
This release supports the same platforms as the base release.
This way of listing supported platforms is required for consistency in the Defects Fixed Finder.]
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.
Note that some new messages may not have been translated and will display in English only.
[NOTE TO WRITERS: State whether this patch IS being released on all languages OR list the supported languages. If ENGLISH ONLY, State "This patch supports English only."]
This is a cumulative patch. A previous patch, 11.1.2.3.502, which is included in this patch, introduced a new Web Service to support multi-POV calculations for Standard Profitability applications in serial and concurrent modes.
Use this operation to initiate the process and run calculation scripts for a selected Standard Profitability application for a selected range of POVs. The following actions relate to the check boxes on the Manage Calculation tab of the application:
· Clear Calculated
· Generate
· Calculate
|
The operations will be performed for all the stages in the application. Calculation scripts generated are distinct from the ones generated for a single POV from UI or Single Calc web service. Generated calculation scripts will cover all members between starting POV group (startPovGrp) and ending POV group (endPovGrp). Only one dimension can change between the starting and ending group. Users may have to issue more than one invocation if it is not possible to express all POVs using a single expression of the starting (startPovGrp) and ending Grp (endPovGrp). |
· String applicationName: Name of the Standard Profitability and Cost Management application for which calculation scripts should be generated and executed, depending on the options selected.
· MultiPOVCalcScriptOptionsDTO options: Selection details for processing calculation scripts.
|
startPovGrp |
Starting POV information for which calculation script generation and execution should be performed. See Table 2, POVMemberGroupDTO. |
povDimensionMember1=2012 povDimensionMember2=March povDimensionMember3=Actual povState=Draft |
|
endPovGrp |
Ending POV information for which calculation script generation and execution should be performed. See Table 2, POVMemberGroupDTO. |
povDimensionMember1=2012 povDimensionMember2=June povDimensionMember3=Actual povState=Draft |
|
layerName |
Layer name for which calculation scripts should be generated and executed. Valid values: COST REVENUE |
COST |
|
clearCalculatedData |
Boolean flag specifying whether clear calculated data for all stages is desired |
TRUE |
|
saveScripts |
Boolean flag specifying whether the generated calculation scripts should be saved |
FALSE |
@return String: CES Task ID generated for this operation.
|
Note: |
Use the getTaskflowStatusByProcessName operation to get the status of this CES taskflow name (as it is displayed on the Taskflow Status Summary). |
The processMultiPOVCalcScripts method takes in a range of POVs to do the calculation for all stages in the application. It clears all the calculated data (if clearCalculatedData flag is set to TRUE) and then generates and executes the calculation scripts for the POV range specified. The saveScripts flag determines whether the generated scripts are saved at the end of execution.
When the method is run the next time, the generated scripts will be cleared if they exist.
Starting with patch 11.1.2.3.503, which is included in this patch, there is a new dependency for the Detailed Profitability calculation engine on the dimension hierarchy reporting tables that were previously optional. These tables are deployed from the Calculate => Manage Database menu, Reporting Tables and Views tab. You must re-deploy these tables each time after you have re-deployed the Detailed application from Enterprise Performance Management Architect (EPMA). This enhancement and new dependency are only for Profitability and Cost Management instances using an Oracle database.
|
Defect Number |
Defect Fixed |
|
• 19882443 |
This patch includes a major performance enhancement for Detailed applications. Now in many cases, calculation rules defined with assignment rules that use the dimension "same as source" feature can now be executed with far fewer execution steps, resulting in drastically reduced runtimes for large applications with a high percentage of same-as-source rules. Specifically, this enhancement applies to multi-source calculation rules that use ratio-based drivers, and where all of the same-as-source dimensions in the destination assignment rule(s) for the calculation rule are registered directly on the destination stage table, not on a lookup table. |
|
• 21182028 |
This patch includes a performance enhancement for the Clear Calculated Values calculation option for Detailed applications that clears results columns in a single pass. This can lead to a significant reduction in runtimes for destination stage tables with millions of rows and many destination measure columns. |
|
• 21482424 |
The Clear Calculated Values option for Detailed applications has been generating error messages related to dropping temporary tables and views that don't exist. This situation has been addressed so that these extraneous messages will no longer appear in the hpcm.log file. |
|
• 21482481 |
This patch includes a new database view called HPM_EXPD_POV_TEMP_OBJECT. It is useful for understanding the POV-specific tables and views that are generated during calculation of Detailed models. This new view identifies which system-generated tables and views belong to which POV, for debugging or verifying calculation results. |
|
• 21482513 |
It was possible for a Detailed calculation job to end in Success status when no calculations were performed. This typically happens when there is no data in the source stage table that matches the Data POV supplied at runtime. It can also happen when none of the source or destination assignment rules match any sources or destinations in the stage tables. In this patch, these conditions are now detected so that the job can be completed in status "Success with Warnings". |
|
Defect Number |
Defect Fixed |
|
• 20805563 |
This patch adds compliance for Internet Explorer 11 and Mozilla Firefox 31. |
|
• 20983470 |
The prepareDetailedViewsForReporting Web Services API was not functioning properly. It now creates the Detailed reporting tables and views as intended. |
|
• 21051712 |
Missing columns in a unique index were preventing Staging Import for Detailed applications from importing Driver Exceptions and Assignment Rule Selections when the source stage had more than three dimensions. Now Staging Import can import these model artefacts for models containing up to five source stage dimensions. |
|
• 21149791 |
This patch contains another performance enhancement for Standard applications Genealogy Calculation for models that use dimensions with dynamic hierarchies. It improves performance by reducing the number of connects to Essbase that are made when dynamic hierarchies are involved. |
|
• 21311146 |
For Profitability instances using MS SQL Server database, assignment rules in Standard and Detailed applications could not be saved when their XML definition exceeded 4000 characters; in some cases this might occur after adding around 20 or more Level 0 dimension members to the rule. With this patch, very large assignment rule definitions are now supported for all supported databases. |
|
Defect Number |
Defect Fixed |
|
• 20829770 |
For Standard applications with dynamic dimensions, genealogy calculation was using too many connections to Essbase to get dimension information, causing the genealogy calculation to run long. This patch optimizes the Essbase connections to make genealogy calculation run faster. |
|
Defect Number |
Defect Fixed |
|
• 16345518 |
During calculation of Detailed
applications, the system-generated calculation rule expansion
table is populated with all of the potential source intersections for the model. Storing all
of the potential sources led to performance and storage issues. |
|
• 20786873 |
For Standard applications with dynamic dimensions, genealogy can produce wrong results in the stages containing those dimensions. This is due to a recent performance optimization. In this patch, the performance optimization is only applied for stored dimensions so that genealogy calculation will produce correct results for stages containing dynamic dimensions. |
|
Defect Number |
Defect Fixed |
|
• 20175018, 20114621 |
Standard application calc script file names must be unique for each application. Due to the 8-character file name limit for Essbase files and the naming convention used to encode meaning into the file names, rare occurrences of name collisions were possible, causing the calculation to fail. With this patch an alternate naming convention is used to guarantee file name uniqueness. The new naming convention uses the same script type prefix character as before, followed by an '_' character and a six-digit number that is unique across all applications within the Profitability instance, for example "a_003946". All new generated calc scripts and regenerated calc scripts will be created using the new convention. If you have any customizations that rely on the old naming convention, you should make the necessary changes. If you have any custom scripts that conflict with the new convention, you should rename them or save them to a different location. To identify file names with the application, POV, and stage to which they belong, a new database view called HPM_EXP_CALC_SCRIPT is created with this patch. |
|
• 20215848, 19680163 |
For Standard applications with large numbers of explicit assignments, it was possible for the Model Validation for Assignment Rule Validations to time out and fail with an error. This patch resolves the timeout problem - however there are some caveats: 1) The validation may still take several minutes to run, sometimes up to 30 minutes or more. There is no hourglass or feedback for the user to know the validation is still running. You have to stay on the page - you cannot navigate away. 2) Depending on the number of explicit assignments/assignment rules to validate, you may reach the Workspace timeout before the validation is finished. In this situation you need to click on the Workspace timeout pop-up so that your Workspace session continues. 3) Depending on the browser you use you may experience client (browser) timeout issues. For Internet Explorer it should continue until it completes (given that the above instructions were followed). But for FireFox you may need to configure the browser timeout settings so that you do not receive errors such as "bad gateway". |
|
• 20231772 |
Starting with the 11.1.2.3.503 patch, for Profitability instances using an Oracle database, the dimension hierarchy reporting tables for Detailed applications were generated incorrectly, with '~' characters in the non-Level0 member names. These wrong dimension member names led to wrong calculation results for calculation rules that referenced non-Level0 members. That problem is resolved in this patch. |
|
Defect Number |
Defect Fixed |
|
• 19634779 |
Concurrent executions of Genealogy calculation in Standard Profitability applications could take a long time to execute and were generating Essbase buffer errors. This fix enhances the performance of the Genealogy calculation by serializing the buffer storing part of the calculation. |
|
• 19882373, 18892120 |
Detailed Profitability applications with large dimensions could take a long time to calculate. Any Detailed application within a Profitability and Cost Management instance which has a large cumulative total number of dimension members (across all the applications in the instance) could also suffer from poor performance. For Profitability and Cost Management instances using an Oracle database, this performance enhancement offers faster calculation for some of these types of applications. Detailed applications that may benefit from this enhancement are those where all columns mapped to EPMA dimensions for the destination reside directly upon the destination stage table, not in a joined lookup table. Calculation rules within such applications can benefit from this performance enhancement when their destination assignment rules do not include a name filter, a UDA filter, or an attribute filter. NOTE: For Profitability and Cost Management instances using an Oracle database, this enhancement creates a new dependency for the Detailed Profitability calculation engine on the dimension hierarchy reporting tables that were previously optional. These tables are deployed from the Calculate => Manage Database menu, Reporting Tables and Views tab. You must re-deploy these tables each time after you have re-deployed the Detailed Profitability application from Enterprise Performance Management Architect (EPMA). |
|
• 20021283, 19649427 |
During Genealogy calculation for Standard
Profitability applications, errors could occur
when the Essbase cell count exceeded
2^32 values. |
|
Defect Number |
Defect Fixed |
|
• 18476743, 18303973 |
Dimension metadata updates like renaming, reparenting, or adding dimension members were not being properly updated in the deployed Essbase outline. This was occurring for both Detailed and Standard application types. |
|
• 18711778 |
For Standard Profitability applications having commas in member names, Data entry values could disappear after deployment to Essbase. |
|
• 18847875, 18519990 |
Certain Detailed Profitability applications having very large dimensions could take an unusually long time to complete. Indexes are added in this patch to bring the runtimes down for these applications. |
|
• 18538894, 18537306 |
Copied Profitability taskflows in CES Workflow Editor failed to run. |
|
• 19197542, 19002277 |
In certain specific circumstances it is possible to get a unique constraint violation when importing assignments for Standard Profitability applications. This error can occur in 2 possible situations: 1) When there are driver selections created for a stage used as a "destination" assignments stage where that stage is not also used as a "source" assignment stage and that stage has > 1 dimension. 2) Driver selections are imported for a stage that is used as a source stage but that source stage has a single dimension. The above 2 use cases will cause a "unique constraint" error to occur on either the HPM_DRV_DIMGRP table or HPM_BLK_EDT_IMP_PIVOT table during the Staging import and thus fail the import. This issue is addressed in this patch. |
|
• 19446409, 18497751 |
For Standard Profitability applications, the Data Entry screen for entering driver data only properly supported up to two decimal places; values with greater than three decimal places got rounded to two places. 0 and values that rounded to 0 disappeared and it was unclear whether or not they were saved. With this patch, the Data Entry screen supports values up to 7 decimal places. |
|
Defect Number |
Defect Fixed |
|
• 18634068 |
In the case where EPM is not configured in SSL but SSL offloading is enabled for external clients to connect to, launching the Smart View client from HPCM was failing. That problem is resolved in this patch by always using the right URL for launching the Smart View client under these settings. |
|
• 18764889 |
For Profitability and Cost Management Standard Profitability applications, when the Concurrent Calculation option was selected in Model Level Preference, the calculation engine successfully generated the Essbase calc scripts, but it failed to execute them due to failure to connect to Essbase. This patch corrects the Essbase connection errors in order to execute the calculations successfully. |
[NOTE TO WRITERS: This section is required. If the patch doesn’t have any known issues, INCLUDE THIS SENTENCE.]
The following issues are the noteworthy known issues of this patch.
|
Defect Number |
Known Issues |
|
• 21321291 |
For Detailed applications, calculation may fail if member names contain the '*' character. NOTE: Oracle strongly recommends avoiding the use of special characters within dimension member names. The '_' (underscore) and ' ' (space) characters are supported in member names. Other special characters may not work in all cases and their use is discouraged. |
|
• 20268185 |
On Profitability and Cost Management instances using an Oracle 12c database will have problems saving and loading larger Smart View Query definitions for the Standard application type. There is a known issue that affects saving and loading queries over 4000 characters. Note: If you have created any Smart View queries in Oracle 11g whose XML definition is larger than 4000 characters, and you then upgrade the database to Oracle 12c you will not be able to open, run, or delete any Smart View query definitions due to this limitation. |
|
• 19205232 |
For SQL Server based Profitability instances, database upgrade errors can occur when running the EPM System Configurator during the upgrade process. The errors prevent many important rows of seeded data from being inserted into the Profitability product database, and they cause any Detailed Profitability Object Calculation definitions to be deleted rather than being converted into Calculation Rules. The errors only occur when upgrading from 11.2.2.3xx to 11.1.2.3.000. They do not occur when upgrading from 11.1.2.1.xxx or 11.1.2.2.000 or for fresh installations of 11.1.2.3.000. They do not occur for Profitability instances using Oracle databases. If your system is SQL Server based and you encountered errors in the Configurator log files when upgrading from 11.1.2.2.3xx to 11.1.2.3.000, follow the additional instructions in the Patch Post Installation Instructions section of this document to apply the fix. |
|
• 18966716 |
When using the Web Services API processCalcScripts to run a Standard model, note that for the clearAllStageList or clearCalculatedStageList parameters, you must list at least one stage. If you would prefer to clear no stages, add the last stage to the list, since it typically has no data at the time this operation is run. |
|
• 18803053 |
When there are no dimension member aliases defined for any member in any dimension in any application in the entire Profitability instance, Driver Selections/Exceptions and Assignments/Assignment Rule Selections screens are not able to display their data -- the screen flickers and then the content disappears. The workaround is to create at least one member alias for at least one dimension in at least one application in the Profitability instance. |
[NOTE TO WRITERS: Per Legal: This sentence must be included IF THERE ARE KNOWN ISSUES.]
[NOTE TO WRITERS: If the patch is cumulative, check with your product team about whether to include any known issues from the earlier patches.]
The section includes important information about applying this patch for Oracle Hyperion Profitability and Cost Management.
[NOTE TO WRITERS: Make sure that instructions for applying the PATCH indicate specifically which components are being patched and which machines in a distributed installation should be patched. for example, “on the machine hosting the shared services web application, …”]
[NOTE TO WRITERS: For web applications, make sure you provide instructions for all supported application servers.]
To apply this patch:
1. Perform a full system backup, including EPM Architect and the Profitability and Cost Management databases. You will need this if you have to roll back the patch after completing the steps in the Patch Post-Installation Instructions section.
2. Shut down the Profitability service (Hyperion Profitability - Web Application).
3. Download and unzip the downloaded patch file, P21473370_11123701_<platform>.zip, to the %EPM_ORACLE_HOME%/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).
NOTE: P21473370_11123701_<platform>.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.
4. From a command line on each machine on which Profitability and Cost Management is installed, change the directory to %EPM_ORACLE_HOME%/OPatch.
5. To apply the patch, enter the following command on one line:
[NOTE TO WRITERS: very important! the jdk version in the apply command is different for 11.1.2.0, 11.1.2.1, and 11.1.2.2. change the jdk160_xx directory as follows:
11.1.2.2: jdk160_29
11.1.2.1: jdk160_21
11.1.2.0: jdk160_11
The example here is for 11.1.2.2.
Windows:
opatch.bat apply %EPM_ORACLE_HOME%\OPatch\HPCM_11_1_2_3_701_21473370 -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 HPCM_11_1_2_3_701_21473370 -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.
NOTE: Applying any Profitability and Cost Management Patch Set Update (PSU) resets the current security policy defined for the Profitability Web Service within Oracle Web Services Manager (OWSM). If web services are used, it is important to perform the web services security policy setup steps now. For instructions on setting up Web Services security policies please refer to the Oracle® Hyperion Profitability and Cost Management External Automation Processes Guide.
After installing the patch, you must finalize the post-patch configuration, as described in the following procedure.
To finalize the post-patch configuration:
1. Shut down the Profitability service (Hyperion Profitability – Web Application).
Run the appropriate database update patch script for your database type and release. Run the script from the Profitability and Cost Management product database/schema/user. Capture the SQL script log output and save it. If there are any errors, report them to Oracle Support.
These scripts are cumulative to ensure that all database updates from previous 11.1.2.3 patches are properly applied.
|
Release |
Database Type |
Database Patch Files |
|
From Release 11.1.2.3.500 or later |
MS SQL Server |
Run the following database update script using MS SQL Server Management Studio against the Profitability and Cost Management product database:
· %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.3.701.sql
Note: If your Profitability instance was affected by
the 11.1.2.2.3xx to 11.1.2.3.000 upgrade errors |
|
From Release 11.1.2.3.500 or later |
Oracle |
Run the following database update script in the Profitability and Cost Management product schema/user using Oracle SQL Developer:
· %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.3.701.sql |
2.
For WebLogic deployments, you must clear
the WebLogic cache.
For WebSphere deployments, you must use EPM System Configurator to
redeploy the Web application.
3. Start the Profitability service.
4. All users should now clear cached files from their browsers.
5. Invoke Profitability and Cost Management, open an application, and check in the System Information tab under Model Summary to verify that the Schema Version is 1.30.
6. Re-register each of your Profitability and Cost Management applications using Application Library.
7. For each Detailed application, you must re-deploy the Reporting Tables and Views.
8.
Important extra step for some Profitability instances using MS SQL
Server (see bug# 19205232 from the Known Issues section):
If all of the following criteria are applicable to your Profitability instance,
then you must use Life Cycle Management (LCM) to import 11.1.2.2 Object
Calculation definitions that were wrongly deleted during the upgrade and
convert them into 11.1.2.3 Calculation Rule definitions:
o you are upgrading from release 11.1.2.3.500 or 11.1.2.3.501 and have not already performed this step
o your Profitability instance uses MS SQL Server
o you recently upgraded from 11.1.2.2.3xx to 11.1.2.3.000
o you have Detailed Profitability applications that were created in 11.1.2.2
o those Detailed Profitability applications contain Object Calculation definitions
For each Profitability application in your instance, use LCM to import and convert your 11.1.2.2 Object Calculation definitions from your pre-upgrade LCM export files into your 11.1.2.3 Detailed Profitability applications as Calculation Rules.
[NOTE TO WRITERS: If your product is a web application, you need to add this step after the step where the patch is applied:
This step is not required for WebLogic.]
[NOTE TO WRITERS: IF THIS PATCH INCLUDES CHANGES TO A JAVASCRIPT FILE, YOU NEED TO INCLUDE THE STEP ABOVE AS A FINAL STEP. IF IT DOESN’T, DELETE THIS STEP.]
1. Perform a full system backup, including EPM Architect and the Profitability and Cost Management databases.
2. Shut down the Profitability service (Hyperion Profitability – Web Application).
3. From a command line, change the directory to %EPM_ORACLE_HOME%\OPatch. By default, the path is C:\Oracle\Middleware\EPMSystem11R1\OPatch.
[NOTE TO WRITERS: very important! the jdk version in the apply command is different for 11.1.2.0, 11.1.2.1, and 11.1.2.2. change the jdk160_xx directory as follows:
11.1.2.2: jdk160_29
11.1.2.1: jdk160_21
11.1.2.0: jdk160_11
The example here is for 11.1.2.2.
4. To roll back the patch, enter the following command on one line:
Windows:
opatch.bat rollback -id 21473370 -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 21473370 -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. If you have already run the database update scripts from step 2 of the Patch Post-Installation Instructions section, you should restore your Profitability and Cost Management product database schema from the backup you took in step 1 of the Applying this Patch section.
6.
For WebLogic deployments, you must clear the
WebLogic cache.
For WebSphere deployments, you must use EPM System Configurator to
redeploy the Web application.Start the Profitability service.
7. Start the Profitability service.
8. All users should now clear cached files from their browsers.
9. Re-register each of your Profitability and Cost Management applications using Application Library.
10. For each Detailed application, you must re-deploy the Reporting Tables and Views.
[NOTE TO WRITERS: IF THIS PATCH INCLUDES CHANGES TO A JAVASCRIPT FILE, YOU NEED TO INCLUDE THE STEP ABOVE AS A FINAL STEP. IF IT DOESN’T, DELETE THIS STEP.]
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.
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:
[NOTE TO WRITERS: very important! the jdk version in the apply command is different for 11.1.2.0, 11.1.2.1, and 11.1.2.2. change the jdk160_xx directory as follows:
11.1.2.2: jdk160_29
11.1.2.1: jdk160_21
11.1.2.0: jdk160_11
The example here is for 11.1.2.2.
Windows:
opatch.bat lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_29
UNIX/Linux:
./opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_29 –invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc
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
It is advised to not use any of the system dimension member names for member names in any of the other dimensions or hierarchies. For example, DirectAllocation or GenealogyAllocation are system members in the AllocationType dimension and these names should not be used in any other dimensions in the model.
Detailed Profitability applications require a user-configured ODBC data source called PROFITABILITY_DS in order to transfer data into the three Essbase reporting cubes that are now available for Detailed Profitability applications. See the Creating the ODBC Data Source to Enable Data Transfers section of the Oracle Hyperion Profitability and Cost Management Administrator's Guide for more information.
Oracle recommends using the DataWire ODBC driver from the Oracle Data Access client for configuring this data source.
By default, Profitability and Cost Management uses "Embedded mode" to connect to Essbase. If you are using APS, the APS mode uses many TCP ports while deploying the Essbase cubes. This situation may cause a network error which is displayed in the Profitability and Cost Management log file.
If you receive a network error when using the APS Connection Type, switch the Connection Type to embedded mode, and redeploy the cube.
To set the Connection Type to Embedded mode:
1. In Profitability and Cost Management, from Task Areas, select Manage Model, and then Model Summary.
2. On the Model Summary screen, select the Model Level Preference tab.
3. Under Essbase Connection Information, select "embedded" from the Connection Type drop-down list.
4. Click the Save icon.
If you are experiencing difficulties using the "embedded" Connection Type mode in Profitability and Cost Management to connect to Essbase (especially in distributed configurations), you must set the environment variable ESS_ES_HOME as a JVMOption for Profitability and Cost Management to point to any local folder which contains two empty folders called bin and data.
· If APS is installed on the system, set ESS_ES_HOME to the same value as the APS_HOME environment variable. (APS_HOME should have the required folder structure.)
· If APS is not installed, set ESS_ES_HOME to any folder which contains empty bin and data folders.
Note: No changes are required if you are using the "APS" Connection Type mode.
To set the JVMOption for the Embedded Connection Type:
1. Stop the Profitability and Cost Management server.
2. Edit the Windows registry for HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\Profitability0\HyS9HyS9PftWeb.
3. Add a JVMOptionX (where X is the next integer, based on the existing number of JVMOptions). For example, if the current JVMOptionCount is set to decimal 17, then add JVMOption18.
4. Set the string value for the new JVMOptionX to -DESS_ES_HOME=<folder-name>, where folder name is the name of the folder that contains the empty bin and data folders.
5. Increment the JVMOptionCount to the next integer. For example, if JVMOption18 is added, then set JVMOptionCount to decimal 18.
6. Start the Profitability and Cost Management server.
To improve the ability of the Windows operating system to deal with a high rate of network connections:
1. From the Windows Registry, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters.
2. Add or modify the following registry entries:
o TcpTimedWaitDelay - Set this to a low value (for example, 30) for the sockets to be released quickly. This DWORD value ranges between 30-300.
o MaxUserPort - Set this to a high value (for example, 33000) to increase the total number of sockets that can be connected to the port. This is a DWORD value.
CAUTION: Before modifying these parameters, refer to the Microsoft Windows operating system documentation for more details.
3. Reboot the system for the changes to take effect.
CAUTION: Oracle recommends that only a system administrator who is very familiar with the system should make this change. The system administrator should consider all the effects on the Operating System before making this change.
To improve the ability of the Linux server to deal with a high number of outgoing network connections, increase the local port range.
1. From a Linux shell, enter the following command to find the current range:
$ sysctl net.ipv4.ip_local_port_range
Sample Output:
net.ipv4.ip_local_port_range = 32768 61000
2. Set the new local range using one of the following commands:
# echo 1024 65535 > /proc/sys/net/ipv4/ip_local_port_range
OR
$ sudo sysctl -w net.ipv4.ip_local_port_range="1024 64000"
Note: The available parameters are listed under /proc/sys/. This option is only useful for high bandwidth, busy Linux servers or large scale grid servers.
3. To permanently modify /proc filesystem (the local port range), edit the /etc/sysctl.conf file to append the following:
# increase system IP port
limits
net.ipv4.ip_local_port_range = 1024 65535
If you are using Lifecycle Management to import large models, the import may take longer to process than the time specified in the default timeout settings on the Oracle WebLogic Server (defect 7166332).
To work around this issue, you must reset the default timeout settings as described in the following procedure.
To modify the default timeout for WebLogic Server:
1. Navigate to %Middleware_HOME%\user_projects\epmsystem1\httpConfig\ohs\config\OHS\ohs_component\mod_wl_ohs.conf.
2. In the configuration file, locate the section LocationMatch/profitability:
<LocationMatch
/profitability>
SetHandler weblogic-handler
PathTrim /
KeepAliveEnabled ON
KeepAliveSecs 20
WLIOTimeoutSecs 3000
Idempotent OFF
WeblogicCluster servername:6756
</LocationMatch>
11. Add the following lines within the LocationMatch/profitability section:
WLIOTimeoutSecs 3000
Idempotent OFF
12. Navigate to:
%Middleware_HOME%\user_projects\epmsystem1\httpConfig\ohs\config\OHS\ohs_component\htppd.conf.
5. Set Timeout to 3000, as shown in the following text:
# Timeout: The number of
seconds before receives and sends time out.
Timeout 3000
Note: The server timeout shown above is a suggested limit, and may be modified to suit the specific timeout settings provided in the documentation for your application server.
Copyright © 2015, Oracle and / or its affiliates. All rights reserved. http://www.oracle.com