Oracle® Hyperion Profitability and Cost Management, Fusion Edition

Release 11.1.2.1 Patch Set Update (PSU): 11.1.2.1.606 Readme

[Skip Navigation Links]

About this Patch. 2

Patch Type. 2

Supported Paths to this Patch. 2

Prerequisites. 2

Other Required Patches

Required User Rights. 2

Supported Platforms. 3

Supported Languages. 3

Defects Fixed in this Patch. 3

Defects Fixed in Patch 11.1.2.1.605

Defects Fixed in Patch 11.1.2.1.604

Defects Fixed in Patch 11.1.2.1.603

Defects Fixed in Patch 11.1.2.1.602

Defects Fixed in Patch 11.1.2.1.601

Defects Fixed in Patch 11.1.2.1.600. 4

Defects Fixed in Patch 11.1.2.1.103. 4

Defects Fixed in Patch 11.1.2.1.102. 4

Defects Fixed in Patch 11.1.2.1.101. 4

Defects Fixed in Patch 11.1.2.1.100. 4

Known Issues. 9

Applying this Patch. 11

Patch Post-Installation Instructions. 12

Rolling Back this Patch. 14

Changes to Web Services in Release 11.1.2.1.101. 14

Changes to Web Services in Release 11.1.2.1.100. 15

Troubleshooting FAQs. 16

Tips and Troubleshooting. 17

Sample Model 17

Dimension Member Naming

Entering Filters. 17

Setting the Hierarchy Type Property. 17

Solving Issues with Profitability and Cost Management Connection Type. 18

Changing the Connection Type to Embedded Mode. 18

Setting the JVMOption for Embedded Connection Type. 18

Setting for High Rate of Network Connections for Windows. 19

Increasing Local Port Range for Linux. 19

Modifying Default WebLogic Timeout Settings for Lifecycle Management 20

Creating Import Staging Tables. 21

Documentation Updates. 21

Accessing EPM System Product Documentation. 21

Copying and Pasting Code Snippets from PDFs. 21

Accessibility Considerations. 21

 

About this Patch

This Readme file describes the defects fixed in this patch and the requirements and instructions for applying this patch.

The purpose of this patch is to provide important bug fixes.

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 interruption of service and/or loss of data. Before installing or applying this patch:

Verify that your system configuration (product version, patch level, and platform) exactly matches what is specified in the Readme.

Patch Type

This Opatch Patch Set Update (PSU) must be installed on a full installation of Profitability and Cost Management Services Release 11.1.2.1.00.

This patch is a cumulative patch, and includes the following releases:

         Release 11.1.2.1.100

         Release 11.1.2.1.101

         Release 11.1.2.1.102

         Release 11.1.2.1.103

         Release 11.1.2.1.600

         Release 11.1.2.1.601

         Release 11.1.2.1.602

         Release 11.1.2.1.603

         Release 11.1.2.1.604

         Release 11.1.2.1.605

Supported Paths to this Patch

You can apply this patch to releases 11.1.2.1.00, 11.1.2.1.100, 11.1.2.1.101, 11.1.2.1.102, 11.1.2.1.103, 11.1.2.1.600, 11.1.2.1.601, 11.1.2.1.602, 11.1.2.1.603, 11.1.2.1.604 and 11.1.2.1.605.

Prerequisites

Other Required Patches

This Profitability and Cost Management patch requires these other EPM System patches:

         Shared Services patch 14142678

          EPM Workspace patch 14119724 

Both the Shared Services and EPM Workspace patches must be applied on any machines where Foundation Services is installed. This Profitability and Cost Management patch must be applied on any machines where Profitability and Cost Management is installed. There is no required order for these patches. Apply all three patches in any order and then redeploy all Web applications.

Required User Rights

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.

Supported Platforms

This release supports the same platforms as the base release.

Supported Languages

Information about supported languages for EPM System products is available in a spreadsheet format on the Translation Support tab in the Oracle Hyperion Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on OTN (listed in the Oracle Business Intelligence product area):

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

Defects Fixed in this Patch

Defect Number

Description

16524200

The genealogy calc retrieves direct allocation Essbase data from the reporting cube, calculates genealogy links and writes them back to the Essbase reporting cube.  In some cases the Essbase data retrieved from the reporting cube was interpreted in the wrong way causing genealogy calculations to be unbalanced.

• 16510792

The Model Validation report for Missing Driver Assignments failed for stages having more than 100,000 assignment sources to analyze.  With this patch, the Model Validation report runs successfully for stages with over 100,000 assignment sources.

Defects Fixed in Patch 11.1.2.1.605

Defect Number

Description

• 16631799

In the case of data load errors during a re-deploy of the reporting cube, this unexpected exception may be thrown while reporting those data errors to the hpcm.log file:

java.lang.ArrayIndexOutOfBoundsExceptionjava.lang. ArrayIndexOutOfBoundsException

That error is fixed in this patch.

• 16522625

Profitability and Cost Management calculation scripts for are now generated with the directive “SET MSG NONE;”. This reduces the output to the Essbase log and improves calculation performance.

14379803

Transfer Data was ending with Done/Success status even for cases where the data was not successfully transferred.  In this patch, the job correctly ends in Done/Failed status whenever a fatal error prevents the data from being transferred.

Defects Fixed in Patch 11.1.2.1.604

Defect Number

Description

• 16311693

Genealogy calculation performance is enhanced by reducing the number of calls to Essbase during execution.

• 16232722

The Missing Driver Assignments report in Model Validation is corrected to show correct results.  In certain cases, it was reporting missing driver assignments that were not actually missing, making it difficult to identify the ones that actually were missing.

Defects Fixed in Patch 11.1.2.1.603

Defect Number

Description

• 14663950

Errors were encountered while generating calc scripts when driver selections were imported more than once from Profitability and Cost Management staging tables. This patch ensures that duplicate dimension member groups are not created when driver selections and driver exceptions are imported from staging tables.

Defects Fixed in Patch 11.1.2.1.602

Defect Number

Description

• 14757589

When multiple Staging Import Configurations are executed in parallel importing data into the same application, if there are dimension member groups shared among these different staging schemas on the source or destination side, it is possible for duplicate dimension member groups to be created in the HPCM database. This patch ensures that all import configurations are run sequentially, even when they are submitted to run in parallel, to avoid this problem.

• 14543886

When redeploying a calculation cube using the 'Update database' option along with 'Archive data and reload after deploy', if the exported data size is more than 2GB, two or more export files are created, but only the first one is reloaded back causing incomplete data.  This patch fixes that problem, allowing all data to be reloaded for larger data sizes.

Defects Fixed in Patch 11.1.2.1.601

Defect Number

Description

• 14461903

Using staging import, errors were encountered when artifacts for Driver Selections, Explicit Assignments and Assignment Rule Selections were imported using a single Import Configuration for the same Stage involving common Source and Destination dimension member groups. With this patch, this error is resolved, and records are processed successfully.

• 14611099

Previously, the order in which the dimensions were deployed to Essbase did not correspond to the order in which the dimensions appeared in the Stages UI screen. With this patch, the dimensions will be deployed to Essbase in the same order they appear in the Stages UI screen.

Defects Fixed in Patch 11.1.2.1.600

Defect Number

Description

• 14193624

This bug fixes various UI problems in the POV Manager screen that are specific to Internet Explorer version 9.

• 14364457

Using staging import, Explicit Assignments were being imported successfully even when non-level 0 dimension members were specified in the source and destination dimensions. With this patch, both source and destination dimension members are validated for the level 0 chcek and non-level 0 members are rejected.

• 14310241

Using staging import, Drivers were being imported successfully even with duplicated measures in its definition. With this patch, usage of duplicated measures is checked in Driver definitions, and those with duplicated measures are rejected.

Defects Fixed in Patch 11.1.2.1.103

Defect Number

Description

14309957

Using staging import, Driver Selection Exceptions were being imported successfully even when non-level 0 dimension members were specified in the source dimensions. With this patch, source dimension members are validated for the level 0 check and non-level 0 source members are rejected.

• 14309946

A null pointer exception error was generated in the Assignment Rule Management dialog upon refresh of the list of applied assignment rules after an assignment rule was added to or deleted from the list.

14307982

Previously, if a POV dimension member had Shared Member references defined in an application, and if that POV dimension member was used to define data to be loaded in the staging table, an ERROR_POV_GROUP_NOT_FOUND error was raised during the staging import of Assignment Rule Selections and Driver Selections data. With this patch, the Primary POV dimension member definition is considered and processing of the import continues.

14295204

In HPCM 11.1.2.1.102, the PIVOT clause was introduced in staging import programs as part of a performance enhancement.  However, the PIVOT clause is only available in Oracle 11g.  This patch enables backward compatibility to the 10g database version.

14255588

In HPCM 11.1.2.1.102, whenever the driver name provided in the staging table for that import record was not available in the database for that application, the exception column was populated with EXCEPTION_WITH_NULL_MESSAGE.  With this patch, the message posted in the "exception" column of the staging table will be ERROR_DRIVER_NOT_FOUND.

14254652

In earlier releases, the Manifest file in profitability.ear did not include information about release and build number of the Profitability and Cost Management build.  That information is now included.

14224885

To reduce the execution time for importing explicit assignments from staging tables, this patch adds logic to gather statistics for necessary Profitability and Cost Management tables as part of Application deployment from Performance Management Architect, and also in the Assignment Import process. This results in considerable performance gains. 

14218203

In Model Validation, when the dimension members and groups to be included in the validation query exceeded 1000, a business logic exception was raised. This problem was specific to the Oracle database.  With this patch, an unlimited number of members can be included in the validation query without error.

Defects Fixed in Patch 11.1.2.1.102

Defect Number

Description

• 14049857

The Import Configurations list under the Import Staging tables cannot be sorted by clicking the header.

• 14042712

Assignments are not displayed in Show Alias mode if there are no Alias associations.

• 14036086

When using External Automation with Profitability and Cost Management, the getTaskStatusByProcessName returns incorrect
values. For example, the
getTaskStatusByProcessName returns the result "Failure" when the process is still running.

• 14013539

When you run an import of assignments from the Staging tables into an application, duplicate rows are created and errors are generated as a result.

• 14007398

When multiple Import Configurations importing data from different Staging schemas into different Profitability and Cost Management applications are executed in parallel, errors were generated in the Staging table’s EXCEPTION column even for valid staging data.

• 13946345

The generation of calc scripts is slow for a larger model.

• 13946209

The import of assignment rule and driver selections from Staging tables is slow when loading large amounts of data.  

• 13719789

Errors are generated when trying to redeploy Unicode Essbase cubes. 

Defects Fixed in Patch 11.1.2.1.101

Defect Number

Description

• 13784593

Unexpected error in business logic because more than one result was returned for a single result query.

• 13783798

When importing driver definitions through staging tables, some drivers were not successfully imported.

• 13703757

A new Web Services method, processGenealogyPathsWithOutASOCubeClear, has been added to run Genealogy execution paths without clearing the ASO cube for the selected POV.

See “Changes to Web Services in Release 11.1.2.1.101” in this document. Also see the Web Services sample client in the <EPM_ORACLE_HOME>\products\Profitability\samples folder.

• 13703735

A new Web Services method, clearASOCube, has been added to clear the ASO cube for a selected POV and Layer combination.

See “Changes to Web Services in Release 11.1.2.1.101” in this document. Also see the Web Services sample client in the <EPM_ORACLE_HOME>\products\Profitability\samples folder.

• 13703625

You cannot import drivers that have a priority that is >100 using staging tables, although they can be successfully created through the UI.

• 13649681

Performance is very slow when performing the POV Manager Copy.

• 13644794

Trace allocation does not work for calculation of databases.

The BSO database is not supported for Trace Allocation because it requires a manual default calculation to be run on the Calculation database.

To work around this issue, use the ASO option for tracing after data has been transferred to the ASO database.

The BSO option will be disabled in a future release.

• 13613423

A new Web Services method has been added to clear POV Data.

This new operation is equivalent to the operation performed in the UI (Manage Model, then POV Manager, and then Delete).

See “Changes to Web Services in Release 11.1.2.1.101” in this document. Also see the Web Services sample client in the <EPM_ORACLE_HOME>\products\Profitability\samples folder.

• 13610902

Lifecycle Management does not work for Profitability and Cost Management when in Compact deployment mode.

• 13609679

EPM Architect cloning does not work if the system locale is not supported.

• 13609614

Calculation script generation produces only one script, but multiple scripts are expected.

• 13609559

There is very slow performance when importing assignment rules for Profitability and Cost Management models.

• 13589416

When using the “copyPOVData” command in the Web Services Sample Client, POV names are not displayed.

See “Changes to Web Services in Release 11.1.2.1.101” in this document.

• 13589346

The Profitability and Cost Management Web Services method "getTaskStatusByProcessName" returns the status of the tasks created by the process name (such as New, Done or Active). It does not return a Success or Failure for the process itself.

See “Changes to Web Services in Release 11.1.2.1.101” in this document.

• 13589315

When using the “getPovs” command in the Profitability and Cost Management Web Services Sample Client, the list of POVs is not consistent in format with other Web Services commands.

See “Changes to Web Services in Release 11.1.2.1.101” in this document.

• 13542330

When a customer performs an Essbase database deployment using the "Update Database" option, the task ends with an error on the ' ImpCalcDatawRules' step.

In addition, an Essbase rule file (*.rul) for Unicode applications is incorrectly generated using the "English_UnitedStates.Latin1@Binary" encoding.

Defects Fixed in Patch 11.1.2.1.100

Defect Number

Description

• 12867632

When invoking a request using the Web Services sample client, the following parameters no longer have to be passed to complete the processGenealogyExecutionPaths function:

·         execute_in_chain

·         overwrite_existing_flag

The only parameters that are required for the processGenealogyExecutionPaths function are listed below:

·         application_name

·         pov_dimension_member_names

·         layer_name

·         paths

The Web Services sample client is available in the <EPM_ORACLE_HOME>\products\Profitability\samples folder.

See “Changes to Web Services in Release 11.1.2.1.100” in this document.

• 12867593

Import Staging Web Service method does not generate CES task IDs.

See “Changes to Web Services in Release 11.1.2.1.100” in this document.

• 12848718

The deployment of a Profitability and Cost Management application was taking an extremely long time to complete. An index is required to facilitate faster deployment of applications from EPM Architect.  

• 12848709

When importing Assignment Rule selections, the staging load is very slow.

• 12848691

The Copy POV operation takes an extremely long time to complete.

• 12826069

The LCM import of stages fails when the Dimension name contains a space, for example, “Cost Center.”

There are two workarounds to this issue:

1.    Do not use spaces in dimension names.

2.    Create any stage that have a space in the name manually, and import the remaining stages using Lifecycle Management. For the manual stages, select the check box beside the object so it can still be selected for import.

• 12825846

Performance improvements have been implemented for the import of assignments from staging tables.

• 12652376

On Linux servers only, a problem occurs with Essbase when you try the "update" functionality when deploying the calculation cube in Profitability and Cost Management.

• 12623574

For some specific models, or areas within those models, trace allocation performance is very slow, and eventually causes the Essbase server to become unresponsive. An Internal Server error is generated in Profitability and Cost Management.

• 11879099

Genealogy calculations run for a very long time on models that have a large number of intrastage assignments.

Known Issues

Defect Number

Known Issues

13930150

Currently, the Oracle Hyperion Profitability and Cost Management Administrator’s Guide states that, in order to perform an Essbase deployment, the Power User must be granted the following rights:

         Create and maintain elements within the model, such as stages, drivers, POVs, driver associations, assignments and application preferences.

         Perform POV Copy, calculation validation, data entry and trace allocations.

         Deploy to Essbase and generate calculation scripts

         Import and export data.


In addition to the above rights, the Profitability and Cost Management Power User ALSO requires the Essbase access right, such as Create application and Application Manager in order to input data into Essbase.

11742793

In instances where the name of a new Profitability and Cost Management application contains foreign characters, which may result in longer names, you may not be able deploy the application in EPM Architect.

To work around this issue, create the application using a shorter version of the application name, or enter the name in English.

11737519

After completing a maintenance upgrade from an existing Release 11.1.2.0 application to Release 11.1.2.1, Essbase deployment tasks from the Manage Database task area fails.

To work around this issue, you must re-register the application in Performance Management Architect:

1.    From the EPM Workspace main menu, select Navigate, then Administer, and then Application Library.

2.    Right-click the application, and select Reregister.

3.    Select the options for your application and then click Reregister.

After the application is re-registered, deploy to Essbase.

 

10278828

If you enter unexpected or restricted words or characters in the Driver Editor, the validation error message is not explicit.

10008989

If the sum of the lengths of the prefix and the dimension name exceeds 80 characters, deployment to Essbase will fail.

The concatenation of dimension and prefix names must not exceed 80 characters.

10007895

When upgrading from Release 11.1.1.3.x to Release 11.1.2.1, the upgrade may fail if the EPM_ORACLE_INSTANCE variable is not set.

To work around this issue, ensure that the EPM_ORACLE_INSTANCE variable is set before running the upgrade_reregister_ps1.bat (sh) script.

For instructions, see the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.

9562829

On the Driver Data tab of the Data Entry screen, when you double-click a non-0-level member that had not been previously selected, a busy indicator is displayed and the selected non-0 level member is not expanded correctly.

To work around this issue, click on the row to select it first, and then double-click to expand the selection.

9309229

Attribute Dimension Member associations for the Measures dimension are not deployed   to Profitability and Cost Management.

This feature is not currently supported.

9289136

Occasionally, the first time you create a new import configuration after an installation, when the import configuration is opened, the data source details are missing and the configuration cannot be edited or run.

To work around this issue, restart the services, and then open the import configuration.

8449860

If global drivers have been loaded into a model, when you select “Clear All” for all stages after running the calculation scripts, the global driver measures are not deleted. When the stages are cleared, the global data is not cleared because they do not have stage specifications.

8208784

For MSSQL Server, when creating the Import Staging Tables configuration, the application does not respond, and the screen is disabled during loading.

To work around this issue, ensure the credentials for both MSSQL Server and the database type are correct, and retry the operation.

7394379

When starting a taskflow, the following error message may be displayed:

“oracle.classloader.util.AnnotatedNoClassDefFoundError”


To work around this issue, from the Task Areas, select Jobs Status, then Search Process, and stop the current job. Select Jobs Status, then Manage Task Flow to restart the task.

7228966

When a Profitability and Cost Management application is deployed to Essbase, the stage dimensions are created in Essbase with the dimension name prefixed with the defined stage prefix. If the resulting dimension name is the same as any existing member name or dimension name in the application, the Essbase cube deployment will fail.

To work around this issue, when creating definitions in the model, ensure that the resulting Essbase dimension names are unique in the final outline.

7192173

Filtering on Aliases in the user interface is not supported in this release.

When you filter on names in assignment rules, matching is performed on both names and aliases.

7113198, 7113162

If you are using Firefox 2.0 as your browser, the cursor is not displayed in a number of locations on the screen, such as edit fields, name, description, and so on. This issue is fixed by using Firefox 3.0.

6979777

It is possible to incorrectly import negative, empty, and duplicated order driver records using the import from the HPM_STG_DRIVER.
 

 

Applying this Patch

The section includes important information about applying this patch for Oracle Hyperion Profitability and Cost Management.

To apply this patch:

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.    Download and unzip the downloaded patch file, P16823586_11121606_<platform>.zip, to the %EPM_ORACLE_HOME%\OPatch directory (by default, C:\Oracle\Middleware\EPMSystem11R1\OPatch).

Note:  P16823586_11121606_<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:

Windows:
opatch.bat apply %EPM_ORACLE_HOME%\OPatch\HPCM_11_1_2_1_606_16823586 -oh %EPM_ORACLE_HOME% -jre %MIDDLEWARE_HOME%\jdk160_21

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_1_606_16823586 -oh $EPM_ORACLE_HOME -jre $MIDDLEWARE_HOME/jdk160_21 -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.

6.    Finalize the configuration, as described in “Patch Post-Installation Instructions.”

7.    Clear cached files from your browsers.

Patch Post-Installation Instructions

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).

2.    Start the EPM System Configurator. For instructions on using the EPM System Configurator, see the following guides:

o    Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.

o    Oracle Hyperion Enterprise Performance Management System Installation Start Here

3.    Under Profitability and Cost Management, select Deploy to Application Server only, and then click Next.

CAUTION: DO NOT select Configure Database, as this option will totally clear the database, and ALL existing applications will be lost. For additional information, refer to the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.

4.    Complete the remaining steps for the EPM System Configurator, as outlined in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.

5.    Run the appropriate database update script for your database type and release:

Release

Database Type

Database Patch Files

From Release 11.1.2.1.00

MSSQL Server

Apply the following database update patch scripts using MSSQL Server Management Studio:

 

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.100.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.101.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.102.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.103.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.600.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.602.sql

 

From Release 11.1.2.1.00

Oracle

Apply the following database update patch scripts:

 

         Use sqlplus to run the following file like: sqlplus <hpcm_db_schema>/<password> @create_11.1.2.1.100.sql

o    %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.100.sql

         Use SQL Developer to run the following files --

o    %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.101.sql

o    %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.102.sql

o    %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.103.sql

o    %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.600.sql

o    %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.602.sql

 

From Release 11.1.2.1.100

MSSQL Server

Apply the following database update patch scripts using MSSQL Server Management Studio:

 

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.101.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.102.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.103.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.600.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.602.sql

 

From Release 11.1.2.1.100

Oracle

Apply the following database update patch scripts using SQL Developer:

 

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.101.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.102.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.103.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.600.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.602.sql

 

From Release 11.1.2.1.101

MSSQL Server

Apply the following database update patch scripts using MSSQL Server Management Studio:

 

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.102.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.103.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.600.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.602.sql

 

From Release 11.1.2.1.101

Oracle

Apply the following database update patch scripts using SQL Developer:

 

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.102.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.103.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.600.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.602.sql

 

From Release

11.1.2.1.102

MSSQL Server

Apply the following database update patch scripts using MSSQL Server Management Studio:

 

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.103.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.600.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.602.sql

 

From Release

11.1.2.1.102

Oracle

Apply the following database update patch scripts using SQL Developer:

 

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.103.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.600.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.602.sql

 

From Release

11.1.2.1.103

MSSQL Server

Apply the following database update patch script using MSSQL Server Management Studio:

 

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.600.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.602.sql

 

From Release

11.1.2.1.103

Oracle

Apply the following database update patch script using SQL Developer:

 

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.600.sql

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.602.sql

 

From Release

11.1.2.1.600 (or)

11.1.2.1.601

MSSQL Server

Apply the following database update patch script using MSSQL Server Management Studio:

 

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\MSSQLServer\create_11.1.2.1.602.sql

 

From Release

11.1.2.1.600 (or)

11.1.2.1.601

Oracle

Apply the following database update patch script using SQL Developer:

 

         %EPM_ORACLE_HOME%\products\Profitability\database\Common\Oracle\create_11.1.2.1.602.sql

 

From Release

11.1.2.1.602 (or)

11.1.2.1.603 (or)

11.1.2.1.604 (or)
11.1.2.1.605

Oracle (or)

MSSQL Server

There are no database scripts to be executed.

 

 

6.    Start the Profitability service.

7.    If you are using Web Services with Release 11.1.2.1.00, see the following sections for specific instructions:

         “Changes to Web Services in Release 11.1.2.1.100”

         “Changes to Web Services in Release 11.1.2.1.101”

 

Rolling Back this Patch

To roll back a patch:

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, C:\Oracle\Middleware\EPMSystem11R1\OPatch).

4.    To roll back the patch, enter the following command on one line:

Windows:
opatch.bat rollback -id 16823586 -oh %EPM_ORACLE_HOME% -jre %MIDDLEWARE_HOME%\jdk160_21

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 16823586 -oh $EPM_ORACLE_HOME -jre $MIDDLEWARE_HOME/jdk160_21 -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 the Profitability Service.

6.    Clear cached files from your browsers.

 

Changes to Web Services in Release 11.1.2.1.101

Changes have been made to the Profitability Web Services WSDL file, and corresponding changes were made to the sample client that is being shipped with this release. Use the latest sample client with Web Services. See the Web Services sample client in the %EPM_ORACLE_HOME%\products\Profitability\samples folder.

CAUTION: Any custom generated WebService port type client implementations must be modified accordingly.

To access the ProfitabilityService WSDL file and view parameters and details for the new or revised methods, go to http://<servername>:19000/profitability/ProfitabilityService?WSDL.

The following changes have been made in this release:

       A new Web Services method, clearPOVData, has been added to clear POV Data. This new operation is equivalent to the operation performed in the UI (Select Manage Model, then POV Manager, and then Delete).

       A new Web Services method, processGenealogyPathsWithOutASOCubeClear, has been added to run Genealogy execution paths without clearing the ASO cube for the selected POV.

       A new Web Services method, clearASOCube, to clear the ASO cube for a selected POV and Layer combination.

       When using the getPovs command in the Profitability and Cost Management Web Services Sample Client, the POV information displayed was not consistent with the format expected by other Web Service commands. This listing is now correctly displayed, and the state of the POV is included as shown in the following example listing application: Bikes72:

POV Information = 2010_January_Actual, POV State = Draft
POV Information = 2009_January_Actual, POV State = Draft

       When using the copyPOVData command in the Web Services Sample Client, POV names were not displayed in a readable format as part of the confirmation message. They are now displayed correctly. In addition, when any POV dimension member passed is invalid, an appropriate message is posted in the hpcm.log to advise that the dimension member is invalid.

       The Profitability and Cost Management Web Services method getTaskStatusByProcessName now returns a “Success” or “Failure” status of the process name, in the addition to the status of the individual tasks created by the process name (such as New, Done or Active).

Changes to Web Services in Release 11.1.2.1.100

Changes have been made to the Profitability Web Services WSDL file, and corresponding changes were made to the sample client that is being shipped with Release 11.1.2.1.100. Use the latest sample client with Web Services. Any custom generated WebService port type client implementations must be modified accordingly.

To access the ProfitabilityService WSDL file, go to http://<servername>:19000/profitability/ProfitabilityService?WSDL.

The following changes were made:

o    Comments have been added to the Profitability Web Services sample client and that is shipped with Release 11.1.2.1.100 to clarify the use of operations and parameters. To view the Web Service API Reference – ProfitabilityService, navigate to http://download.oracle.com/docs/cd/E17236_01/epm.1112/hpm_api_ref.html.

o    Effective with this release, if you created custom Web Services port type clients to invoke a request to perform the “processGenealogyExecutionPaths” function, remove the following Boolean attributes because they are no effective with this release, and may cause compile time errors if they remain:

§  execute_in_chain

§  overwrite_existing_flag

 

The only parameters that are required for the “processGenealogyExecutionPaths” function are listed below:

§  application_name

§  pov_dimension_member_names

§  layer_name

§  paths

The Web Services sample client is available in the <EPM_ORACLE_HOME>\products\Profitability\samples folder.

These changes have also been modified in the hpm_ws_client.bat/.sh sample.

Troubleshooting FAQs

How can I find out which releases and patches of EPM System products are installed in a deployment?

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_21

Note: The default for %EPM_ORACLE_HOME% is C:\Oracle\Middleware\EPMSystem11R1.
      The default for %MIDDLEWARE_HOME% is C:\Oracle\Middleware.

UNIX/Linux:

./opatch lsinventory -oh $EPM_ORACLE_HOME -jdk $MIDDLEWARE_HOME/jdk160_21

Note: The default for $EPM_ORACLE_HOME is $HOME/Oracle/Middleware/EPMSystem11R1.
      The default for $MIDDLEWARE_HOME is $HOME/Oracle/Middleware.

Why do I get the following patch conflict error message when running OPatch?

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.  


Why do I get the OUI-67078 warning message when applying OPatch?

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.

Tips and Troubleshooting

Sample Model

A sample application is available in the product installation which can be used for testing and self-led exploration of functional areas.  The sample application includes a small data set and a fully built out model that illustrates various uses of drivers, assignments, and assignment rules.

Life Cycle Management extracts and data files are provided to support importing the model metadata, allocation artifacts, and cost and driver data.

The sample application files can be found at:

 <Middleware Home>\EPMSystem11R1\products\Profitability\samples\Bikes

Dimension Member Naming

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.

Entering Filters

When entering a search value in a filter, enter the entire string if the filters are Attribute-based or UDA-based.

If you require a wildcard at the beginning of a filter, only question marks can be used, as in “?ac”.

Trailing wildcard symbols, such as asterisks (*) and question marks (?) are supported in assignment rule name and alias filters. For example, enter "B*" to filter members having names or aliases beginning with the letter "B".

Note:  You cannot use an asterisk at the beginning or within a filter for assignment rules, such as "*B" or “B*a”.

For assignment rule filters:

         Both the EQUAL and NOT EQUAL operations are currently supported to filter Names, Aliases and Attributes.

         Only the EQUAL operation is currently supported for UDAs.

         When "Name" is selected as the parameter, matching is performed on both names and aliases.

Setting the Hierarchy Type Property

The ‘Hierarchy Type’ property applies only to Aggregate Storage Databases in Essbase. (The Reporting Cube is generated by Profitability and Cost Management).

If a Dimension Hierarchy Type is set to 'Stored' in EPM Architect, all its members must have the consolidation set to "+ (addition)". The only exception is if the Dimension root member has the "Data Storage (ASO)" set to "LabelOnly," then generation 2 children of the root member which are not the first child can have the consolidation set to ‘~ (ignore)’ (for example, ‘NoMember’). Any dimension members that use a consolidation symbol other than ADDITION and IGNORE in the Stored hierarchy type (for example, - SUBTRACT) will cause error messages while generating the reporting cube.

To be able to use other consolidation type symbols (other than ADDITION and IGNORE) the hierarchy type should be set to ‘DYNAMIC.’

Note: If a dimension member has a formula, the hierarchy type must be set to ‘DYNAMIC.’

To set the Hierarchy Type:

1.    From EPM Workspace, select Navigate, then Administer, and then Dimension Library.

2.    Under the application, select some dimension (except Alias, Attribute, UDA).

3.    In the Property Grid, select the appropriate Hierarchy Type property:

o    Select Stored for any dimension whose dimension members use the following consolidation symbols:

§  + ADDITION

§  ~ IGNORE (only underneath LABEL ONLY members.)

o    Select Dynamic for any dimension whose dimension members need to use all supported consolidation symbols, or have a formula.

4.    Redeploy the application to the Profitability and Cost Management, and then Essbase.

 

Solving Issues with Profitability and Cost Management Connection Type

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.

Changing the Connection Type to Embedded Mode

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 Information, select “embedded” from the Connection Type drop-down list.

4.    Click the Save icon.

If the cube deployment fails in embedded mode, or you have to use APS mode, you can modify the Windows registry TCPIP parameters - TcpTimedWaitDelay and MaxUserPort - as recommended by the Windows Operating System documentation.

CAUTION: Before making any changes to the Windows Registry, consult the Microsoft Windows Operating System documentation for the correct settings and best practices to avoid any risk of corrupting the registry.

Setting the JVMOption for Embedded Connection Type

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.

Setting for High Rate of Network Connections for Windows

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.

 

Increasing Local Port Range for Linux

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 to your /etc/sysctl.conf file:


# increase system IP port limits
net.ipv4.ip_local_port_range = 1024 65535

 

Modifying Default WebLogic Timeout Settings for Lifecycle Management

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\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>

3.    Add the following lines within the LocationMatch/profitability section:

WLIOTimeoutSecs 3000

Idempotent OFF

4.    Navigate to Middleware\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.

Creating Import Staging Tables

In order to import model data from relational databases into Profitability and Cost Management, you must create a set of staging tables in a separate database to format the information for use in the application.

CAUTION: Do not modify the product schema for the import.

Staging database scripts are available for MSSQL Server and Oracle Database. Use the create_staging.sql script to create the import tables in the new database.

To create staging tables:

1.    Create a new Oracle or MSSQL Server database, outside of the product schema.

2.    Navigate to the location for the appropriate SQL script in the default location for your database type:

o    EPM_ORACLE_HOME/products/Profitability/database/Common/MSSQLServer

o    EPM_ORACLE_HOME/products/Profitability/database/Common/Oracle 

3.    Run the appropriate SQL script against the new database:

o    To create new staging tables, run create_staging.sql

To import data and metadata using these staging tables, see the Oracle Hyperion Profitability and Cost Management Administrator's Guide.

Documentation Updates

Accessing EPM System Product Documentation

The most recent version of each EPM System product guide is available for download from the Enterprise Performance Management System Documentation area of the OTN Web site (http://www.oracle.com/technology/documentation/epm.html). For faster access to the documentation, you can also use the Enterprise Performance Management Documentation Portal (http://www.oracle.com/us/solutions/ent-performance-bi/technical-information-147174.html) which also links to EPM Supported Platform Matrices, My Oracle Support, and other information resources.

Deployment-related documentation is also available from the Oracle E-Delivery Web site (http://edelivery.oracle.com/EPD/WelcomePage/get_form).

Individual product guides are available for download on the Oracle Technology Network Web site only.

Copying and Pasting Code Snippets from PDFs

When you cut and paste code snippets from a PDF file, some characters can be lost during the paste operation, making the code snippet invalid.
Workaround: Cut and paste from the HTML version of the document.

Accessibility Considerations

It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community. Oracle’s Hyperion Profitability and Cost Management supports accessibility features, which are described in Appendix C in the Oracle Hyperion Profitability and Cost Management User's Guide. The most up-to-date version of this guide can be found in the EPM System Documentation Library on the Oracle Technology Network (http://www.oracle.com/technology/documentation/epm.html).

In addition, this Readme file is accessible in HTML format.

 

 

Copyright © 2012, Oracle and/or its affiliates. All rights reserved.
http://www.oracle.com