Oracle Hyperion Profitability and Cost Management

Release 11.1.2.4.000 Patch Set Update (PSU): 11.1.2.4.127 (27732412)

Readme

About This Patch. 2

Patch Type. 2

Supported Paths to This Patch. 2

Prerequisites. 2

Required Patches. 2

Required User Rights. 3

Supported Platforms. 3

Supported Languages. 3

New Features in Previous Patches included in this Cumulative Patch. 3

REST API Version V1 is released; Version 11.1.2.4.000 is deprecated. 3

Life Cycle Management (LCM) Export/Import Includes Dimensions. 4

Templates Export/Import 4

Financial Close Management Integration for Management Ledger Profitability Applications. 5

Dimension Load Through Profitability Application Console. 5

Profitability Application Console UI Enhancements. 5

Essbase Data Load. 5

Automated Database Upgrade. 5

Management Ledger Rule Data Validation Report 6

Capture Essbase Debug Scripts. 6

Save Job Library Messages. 6

Dimension Files for the Management Ledger Sample Model 6

Defects Fixed in this patch. 6

Defects Fixed in patch 11.1.2.4.126. 7

Defects Fixed in Patch 11.1.2.4.125. 7

Defects Fixed in Patch 11.1.2.4.124. 8

Defects Fixed in Patch 11.1.2.4.123. 8

Defects Fixed in Patch 11.1.2.4.122. 9

Defects Fixed in Patch 11.1.2.4.121. 10

Defects Fixed in Patch 11.1.2.4.120. 10

Defects Fixed in Patch 11.1.2.4.110. 12

Defects Fixed in Patch 11.1.2.4.101. 13

Defects Fixed in Patch 11.1.2.4.100. 13

Known Issues in This Patch. 14

Applying This Patch. 17

Optional – Performing Manual Database Updates (only when there are errors in the automatic update). 19

Rolling Back This Patch. 20

Troubleshooting FAQs. 22

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

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

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

I applied the patch successfully but I don’t see the changes from the patch in the product. What should I do?. 23

Tips and Troubleshooting. 23

Controlling the Allocation Rounding Precision for Management Ledger Calculations. 23

Creating a Separate Log File for Persistence Messages. 24

Protected Management Ledger System Dimensions. 24

Management Ledger Business Dimensions - Shared Members. 24

Dimension Member Naming. 25

ODBC Driver Recommendation. 25

Solving Issues with Profitability and Cost Management Connection Type. 25

Modifying Default WebLogic Timeout Settings for Lifecycle Management 27

About This Patch

This Readme file describes the 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 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 is a patch set update (PSU).  It requires a full installation of Profitability and Cost Management Services for Release 11.1.2.4.000.

Supported Paths to This Patch

You can only apply this patch to release 11.1.2.4.000, or any 11.1.2.4.1xx PSU release.

Prerequisites

Required Patches

Oracle Hyperion Shared Services 11.1.2.4.002, 11.1.2.4.005, or 11.1.2.4.006

Oracle Hyperion Essbase server 11.1.2.4.014, 11.1.2.4.018, 11.1.2.4.019, 11.1.2.4.021, or 11.1.2.4.022.  Note that for Essbase server, versions 11.1.2.4.015, 11.1.2.4.016, and 11.1.2.4.017 are not supported.

Oracle Hyperion Analytic Provider Services 11.1.2.4.014, 11.1.2.4.018, 11.1.2.4.020, or 11.1.2.4.022.  Note that for the Analytic Provider Services, versions 11.1.2.4.015, 11.1.2.4.016, and 11.1.2.4.017 are not supported.

Oracle Essbase Administration Services 11.1.2.4.014, 11.1.2.4.016, 11.1.2.4.020, or 11.1.2.4.022.

Get the patches on My Oracle Support.  Be sure to upgrade all components included in each patch.

Match the versions as nearly as possible across all components. For example, if you install the 11.1.2.4.021 Essbase server patch, you should also install the 11.1.2.4.020 Analytic Provider Services patch, and the 11.1.2.4.020 Essbase Administration Services patches.

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

Applies to all platforms supported for the base release.

Supported Languages

This release supports the same languages as the base release, however some new messages may not have been translated and will display in English only.

New Features in Previous Patches included in this Cumulative Patch

Previous patches which are included in this patch introduced the following new features and enhancements in Oracle Hyperion Profitability and Cost Management. For detailed information on these features, see the Oracle Hyperion Profitability and Cost Management Administrator's Guide, the Oracle Hyperion Profitability and Cost Management User's Guide, and the Oracle Hyperion Profitability and Cost Management REST API Developer's Guide at http://docs.oracle.com/cd/E57185_01/nav/financialpm.htm (see section Oracle Hyperion Profitability and Cost Management 11.1.2.4.120).

REST API Version V1 is released; Version 11.1.2.4.000 is deprecated

Starting with this release, Profitability and Cost Management REST API version 11.1.2.4.000 is replaced by version V1.  Version 11.1.2.4.000 is disabled by default.  Oracle strongly recommends that you migrate to version V1.  If you need more time to migrate, contact Oracle Support for how to temporarily enable REST API version 11.1.2.4.000.

The Profitability and Cost Management REST Web Services API version V1 differs from version 11.1.2.4.000 in the following ways:

o    The Request Payload object has been changed to JSON format.

o    For all GET type resources, the Request Payload object is passed as a query parameter.

o    For other resources, the Request Payload object is passed as separate object outside the URI (Uniform Resource Identifier).

o    The Response object is now exposed as a JSON object and includes more details.

o    Exception and error messages are streamlined according to Oracle standards.

o    The URI has changed for DP Reporting Views Generation, Run DP Calculation and Run SP Multi POV Calculation.

Please refer to the REST client program for examples on using new REST API version.

This cumulative release contains also includes the following REST enhancements released in previous patch set updates:

o    The Prepare Detailed Views for Reporting (DP) resource is enhanced to create all DP reporting tables and views for one application in a single call, instead of requiring a separate call for each dimension.

o    The Essbase Data Load resource supports the new Essbase Data Load feature in the Manage Calculation screen.

o    The following resources support the new flat file dimension load feature for Management Ledger applications: Create File based HPCM Application, Enable File based Application, Update File based Application using a Flat File.

For more information, see the Oracle Hyperion Profitability and Cost Management REST API Developer's Guide.

Life Cycle Management (LCM) Export/Import Includes Dimensions

LCM Export for Profitability and Cost Management applications now allows you to export your application's dimension metadata along with the other model artifacts, into a single LCM export file.  An LCM export file that includes dimension metadata can be imported into a new, empty application that has been pre-created in the Profitability Applications console.  There is one known issue with this new feature; see the Known Issue note for bug 23512869 for details.

Please note that the target application you create in Profitability Applications console will be created with a "Native" application source type.  If the source application was initially created in EPM Architect and you want to keep the target application as "EPMA" source type also, you should use EPMA LCMs to migrate the dimensions.

Likewise, if your source application has "Master Cube" source type and you want your target application to also have "Master Cube" source type, you should copy your dimension master cube to the target environment and use the Master Cube approach to create the target application.

Templates Export/Import

For Management Ledger applications, from the Profitability Applications Console you can export the entire Profitability and Cost Management application, including application metadata, dimension metadata, program artifacts and input data all in a single operation, to a single application "template" zip file.  This feature is useful for backing up applications or for migrating them to another environment.

Export Template is available from the Actions menu after selecting a Management Ledger application.

Import Template is always available from the Actions menu.  The import process always involves defining and creating a new application into which the template is imported.

When the Include Input Data checkbox is checked in the Export Template dialog, the input data for all selected POVs will be included in the export.

On the Import Template dialog, if input data is present in the template file being imported, the Import Input Data checkbox will be enabled and input data for all selected POVs will be imported.  The cube is always automatically deployed, whether or not the input data is imported.

Financial Close Management Integration for Management Ledger Profitability Applications

Tasks for Profitability and Cost Management Ledger applications now can be incorporated into Oracle Hyperion Financial Close Management schedules and templates. Users of Financial Close Management can create Profitability and Cost Management workflows or include Profitability and Cost Management tasks in workflows with other Oracle Hyperion Enterprise Performance Management System (EPM) and non-EPM products to create an end-to-end workflow management solution for all EPM solutions. Users of Financial Close Management can find tasks assigned to them within a Financial Close Management schedule, access appropriate Profitability and Cost Management screens directly from the scheduler, perform the necessary tasks, and update their scheduled tasks with a status change.

See related files in <EPM_HOME>\products\Profitability\samples\Integration\FCM. For more information, see the Oracle Hyperion Financial Close Management User’s Guide.

Dimension Load Through Profitability Application Console

The Profitability Application Console (Navigate => Administer => Profitability Applications from the Workspace menu), now supports dimension load using flat files for Management Ledger applications. The Console allows users to create shell applications, load dimensions, and validate and enable applications for use with Profitability and Cost Management. 

For examples of the required file format, see the dimension text files in the new BksML12_Dimension_Files.zip file included with the BksML12 sample model. 

For file format details, see the Preparing Flat Files for Importing Dimensions into Management Ledger Profitability Applications section of the Oracle Hyperion Profitability and Cost Management Administrator's Guide.

Profitability Application Console UI Enhancements

The Profitability Application Console has a simplified user interface and Job Library.

Essbase Data Load

Users can choose one or more data files to load data into a Management Ledger calculation cube after it has been deployed. This feature uses the same data file formats supported by Essbase Administration Services (EAS) Console and optional data load rules.

Note that the BksML12_All_Data.txt file that is included with the BksML12 sample application can be loaded using this feature (and it does not require a load rule file).

Automated Database Upgrade

Upgrade SQL scripts for Profitability and Cost Management patches now run automatically as needed when restarting the Profitability service after applying a patch that requires a database upgrade. A manual rollback script is also included. See the Applying this Patch and Rolling Back this Patch sections for details.

Management Ledger Rule Data Validation Report

This new system report for Management Ledger applications assists users in validating the data present for the key elements in a calculation rule. For the selected rule, it shows all of the dimension intersections for the source and for the driver, along with the source or driver input value that is used to calculate the rule, for each intersection.

Capture Essbase Debug Scripts

This tool is useful for diagnosing when allocations do not match expectations. 

Management Ledger application users can check a new box in the Manage Calculation screen to request that the Essbase commands issued to calculate each rule be written to files on the server, one file per rule. This provides quick access to Management Ledger calculation instructions for troubleshooting calculation issues.

Scripts are generated in the $ARBORPATH/app/<application name>/<database name> directory, on the computer where the configured Essbase server is running, for example:

C:\Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\app\BksML12C\BksML12C

Administrators can also view the scripts on the Essbase console.  For more details, see the Calculating Management Ledger Models section of the Oracle Hyperion Profitability and Cost Management User's Guide.

Save Job Library Messages

The Profitability Application Console and Management Ledger Job Libraries now have a Save button in the message pop-ups so users can save the messages to a file. This is useful for multiple errors in Essbase Data Load and for Validation and Impact Analysis messages.

Dimension Files for the Management Ledger Sample Model

Dimension flat files are now packaged with sample application BksML12 so users can create the Management Ledger sample model using the File Import method. The HPCM Sample Models Readme.docx file is updated with instructions. For the location of these files, see Chapter 2 of the Oracle Hyperion Profitability and Cost Management User’s Guide.

Defects Fixed in this patch

Defect Number

Defect Fixed

• 27585917

For Management Ledger applications, the Manage Rules page is more responsive now, even for large applications with many rule sets and rules.

• 27190508

The CheckTaskStatusJob REST API was sometimes wrongly reporting Success; that is corrected in this patch.

 

Defects Fixed in patch 11.1.2.4.126

Defect Number

Defect Fixed

• 26678547

The optional MEMBER SOLVE ORDER property is now fully supported for dimension members in Management Ledger applications. It is useful for ensuring that member formula operands are computed before they are needed for computing the formula. The new property can be added using the Update Dimensions job and then redeploying the Essbase cube. The value is specified as an integer.

• 25581755, 26982074

In clustered environments, the Job Library UI for Standard  and Detailed applications was not always in sync with the correct state of a job. It will now always show the correct status of a running or completed job.

• 26329234, 27118188

In clustered environments, when SSL is enabled for shared services and an LWA is defined, HPCM was generating the SSL URL based on the host from the first Shared Services Web Application registry entry.  It now correctly uses the hostname for the Shared Services LWA registry entry.

• 25490351, 27155272

The hierarchy type for the Rule dimension in file-based Management Ledger applications is changed to 'Stored' to improve reporting performance. This change is applicable for new Management Ledger applications created by the New Application dialog or the Import Template dialog within the Profitability Applications console. 

To apply the change to an existing application, you can export it using Export Template and then import it into a new application name.

 

Defects Fixed in Patch 11.1.2.4.125

Defect Number

Defect Fixed

• 25581755, 26644720

In clustered environments, it was possible for the status of a job as displayed in the Job Library to be out of sync with the actual current status of the job.  That problem was corrected earlier for Management Ledger applications and is corrected in this patch for Standard and Detailed applications as well.

• 26431816

While editing or creating a query in the Manage Queries screen for a Management Ledger application, searching for a member could result in a Java.lang.NullPointerException error. That error is corrected in this patch.

• 26538669

The REST sample client section for the Run ML Calculations (runLedgerCalculationJob) REST API was not recognizing the subsetStart and subsetEnd parameters so it was not possible to run a subset of rule sets when using the REST sample client to invoke this API.  The sample client is corrected in this patch.

• 26764975, 26812905

For Management Ledger applications, a number of Java threads could remain open after execution of a rule set with the Parallel Execution calculation option and could remain open until the profitability service was restarted, eventually exceeding the Java threads limit.  That problem is corrected in this patch.

 

Defects Fixed in Patch 11.1.2.4.124

Defect Number

Defect Fixed

• 25581755, 25713969, 25824151, 26136906

Various issues related to job status updates in the Job Library have been corrected in this patch.

• 25944683, 25943219, 25929891, 25426198, 25950607

Various improvements for the handling of dimension attribute members and attribute associations as used in attribute filters within Management Ledger applications are included in this patch.

• 25616870, 25661406

Some changes to the Template Export feature for Management Ledger applications are made in this patch to better enable migration of those applications to Profitability and Cost Management Cloud.

 

Defects Fixed in Patch 11.1.2.4.123

Defect Number

Defect Fixed

• 24653959

Submitted jobs could take up to a minute to display with correct status in the Job Library.  With this patch, submitted jobs display immediately in the Job Library and their statuses are updated promptly.

• 25070783

For Management Ledger applications, dimension cache loading is enhanced in this patch to load more efficiently.  For applications with large dimensions, this results in much shorter wait times for accessing dimension members after updating dimensions.

• 25219342

For Management Ledger applications with large dimensions, Smart View queries could take too long to validate and save, causing the screen to hang or time out.  That problem is resolved in this patch.

• 25263275

For Management Ledger applications, member formulas with new line characters cannot be supported.  They cannot be properly imported by Template Import or LCM Import.

Template Export and LCM Export are enhanced in this patch to remove any new line characters within member formulas so they will be able to re-import cleanly without errors.

• 25340413

For Management Ledger applications with attribute dimensions, the attribute associations were not being imported on the base dimensions when Dimensions were selected for LCM import.

With this patch, LCM export is changed to export the attribute dimensions first so they will import before the base dimensions.

If you have encountered this problem, re-export your application after applying this patch, then the attribute associations will import correctly.

If the source application is no longer available for re-exporting, the workaround is to re-import the base dimensions after the initial full import. 

 

Defects Fixed in Patch 11.1.2.4.122

Defect Number

Defect Fixed

• 23472378

Enhancement: The Program Documentation system report for Management Ledger applications has a new option to suppress generation of the XML definition of each rule.  This is helps reduce the size of the report for models with many rules.

• 23710421

A validation added to staging import logic in a recent patch could sometimes cause staging imports for Standard applications to fail.  That validation is removed in this patch.

See the Known Issues note for bug 21571294 in this document for an explanation of the case that the validation was originally created to catch.

• 24546200

The UI component for adding attribute dimension members into a rule filter definition for Management Ledger applications did not support larger attribute dimensions. This patch improves the UI response time and adds a search capability for selecting members from larger attribute dimensions.

• 24653300

When clicking a link from a balancing report to invoke Smart View, the error message:

"Cannot perform cube view operation.null"

was displayed. That error is resolved in this patch.

• 24653352

A performance enhancement for Management Ledger applications introduced in a recent patch could cause all of the available JVM memory to be filled. That enhancement is modified in this patch to limit the amount of JVM memory used while still retaining the original performance improvement.

 

Defects Fixed in Patch 11.1.2.4.121

Defect Number

Defect Fixed

• 22926699

For applications with large dimensions and many attribute associations, redeploying from EPM Architect (EPMA) to Profitability and Cost Management (PCM) could take very long, causing the process to appear to be hung. This patch includes a performance improvement that allows EPMA to PCM redeployments to finish successfully in a reasonable time.

• 23026706

When deploying PCM outline to Essbase using the Update method, some delete, rename, and reparent operations were not performed correctly; that problem is corrected in this patch.

• 23192037

The hpm_ws_rest_client could fail with an error when used with the -help argument; that is corrected in this patch.

• 23230034,

23330661

Dimension hierarchies for attribute dimensions could be incorrectly deployed to Essbase; this patch ensures that attribute dimension hierarchies are properly deployed.

• 23214501, 23214772

When calculating a large Management Ledger model using concurrent calculation, the calculation could fail with an 
ORA-00001: unique constraint violation error; that problem is addressed in this patch.

• 23324094

On rare occasions due to unexpected system failure, it is possible for Profitability and Cost Management jobs to be stuck in New, Submitted, or Running status in the Job Library even after the job has terminated. Since these are active statuses, the job entries for these jobs cannot be deleted from the UI.  With this patch, each time the Profitability service is restarted, it will change terminated jobs that have remained in these statuses to Failure status, to reflect their true status and allow them to be deleted from the Job Library UI.

When restarting the Profitability service you should also restart Essbase to ensure that any jobs that were stuck in these statuses are not still running in Essbase.

 

Defects Fixed in Patch 11.1.2.4.120

Defect Number

Defect Fixed

• 21474371

This performance enhancement considerably reduces the time it takes to run Duplicate Application from the Profitability Applications console for very large models.

• 21524550, 21967193

Profitability and Cost Management jobs that execute multi-stage CES taskflows could get stuck after the first stage when running with a non-English browser setting.  That issue is fixed in the Shared Services 11.1.2.4.002 patch, which is required for this patch.

• 22097978

In Manage Rules for Management Ledger applications, the Search function in the member selector could appear to not return anything when searching a very large dimension.  The Search function performance is improved in this patch.

• 22159519

This performance enhancement reduces the time it takes to deploy large applications with attributes from EPM Architect to Profitability and Cost Management when attributes are used heavily in large dimensions.

• 22293477

For Standard Profitability applications migrated to 11.1.2.4 from earlier releases, a new application preference was not given a default value by the migration, causing failure when trying to run the new Genealogy Statistics and Execution Statistics system reports. This patch completes the migration by setting a default value for the new application preference if it does not have a value.

• 22591224

This enhancement makes it easier to import the BksML12 model by importing the entire application including dimensions, model artifacts and input data using the Import Template feature in the Profitability Applications console.  See the HPCM Sample Models Readme.docx file in the <EPM_HOME>\products\Profitability \samples directory for more details.

• 22668706

Oracle RDB issue only during upgrade:  For Profitability and Cost Management (PCM) instances using an Oracle database, the 11.1.2.4.000 release had a dependency on the Oracle XML DB option being installed with the RDBMS server instance. If you installed or upgraded to PCM 11.1.2.4.000 without having installed the XML DB option, one of the new database tables and one new database view required for Management Ledger applications would fail to be created during the 11.1.2.4.000 database schema configuration step.  The Configurator would appear to have run successfully, but you would see this error in the configtool.log file:

ora-44425: xml db needs to be installed for creating an xmltype table or column

and 5 related occurrences of:

ora-00942: table or view does not exist.

If you see those errors you can ignore them after successfully applying this patch.

This patch removes the dependency on the XML DB option, and applying this patch automatically creates the failed table and view if they are found to be missing.

• 22706048

This performance enhancement reduces the time it takes to redeploy large Management Ledger dimension models to Essbase when selecting the Update Database - Preserve Data option.

• 22757251

The Update Dimensions feature in the Profitability Applications console was not allowing update of user-defined dimension members under UserDefinedDriverMeasures in the Measures dimension for Master Cube source Standard applications. This patch enables the Measures system dimension for selection in Update Dimensions so the user-defined members of that dimension can be updated.

 

Defects Fixed in Patch 11.1.2.4.110

Defect Number

Defect Fixed

• 20696042

This enhancement enables a significant performance improvement for Detailed calculations with multi-source calculation rules that use the Same-as-Source (SAS) option in their destination assignment rules.

Detailed multi-source calculation rules with SAS can benefit from this enhancement when all of the destination stage dimension columns reside directly on the stage table (not on a look-up table) and when its destination assignment rules do not use any dimension filters.

• 21511360

Detailed calculation jobs could end in status "Success" even when no data was processed due to no matching data found.  This problem most typically occurred when the wrong Data POV was specified at runtime and no data existed in the source and/or destination tables for that POV.  It could also occur when there was no data in the source and/or destination tables matching the intersections defined by the source and destination assignment rules for all the rules in the entire model.

These cases are detected now, allowing the job to terminate in status "Success with Warnings" and warning messages are posted to hpcm.log.

• 21519072

A new view called HPM_EXPD_POV_TEMP_OBJECT is added to help analyze Detailed calculations.  It lists POV-specific system-generated tables by POV.

• 21661597

In a recent release, scripts for creating the sample tables used with the BksDP30 Detailed sample model were added for Microsoft SQL Server.  However, that script created the sample tables without any decimal places for the measure columns, resulting in rounding/truncation when importing the data, and causing rounding errors in the calculations.  In this patch, the measure columns for the sample model tables are defined as NUMERIC(18,6) to minimize the rounding errors.

• 21669292

For Detailed applications, the Smart View links in the Stage Balancing screen were broken, using the wrong metadata to look for which Essbase application to open in Smart View.  That problem is corrected in this patch.

• 21699015, 21813422

A recent release included integration capability between EPM Financial Close Management (FCM) and Profitability and Cost Management (HPCM).  In that initial integration, the HPCM Manage Queries screen was not able to open when invoked as an FCM task, and the Manage Database screen had some trouble when selecting a data file to load, when the screen was invoked as an FCM task.  Those problems are corrected in this patch.

• 21806197

Management Ledger calculation rules have been enhanced to record member selections in a way that avoids calculation rules becoming invalid after referenced dimension members have been "reparented".  Rules are automatically updated to the new format when the Profitability service is first started after applying this patch.  Rules from previous-version Life Cycle Management (LCM) files are also converted as they are imported.

 

Defects Fixed in Patch 11.1.2.4.101

Defect Number

Defect Fixed

• 21540026

For Profitability and Cost Management Standard applications, in multi-user situations or after a single user having an application open for some period of time, non-fatal unexpected errors could occur in various screens.  Those errors are now suppressed.

 

Defects Fixed in Patch 11.1.2.4.100

Defect Number

Defect Fixed

• 13249770, 13249579

For Detailed Profitability calculations, this patch includes two enhancements to optimize the performance of the Clear Calculated Values operation.  Applications with large destination stage tables that include several destination measure columns should see a significant reduction in the time required for clearing calculated results.

• 20268185

Management Ledger calculation rules and Smart View queries for Management Ledger and Standard applications could not be saved or loaded in Profitability and Cost Management instances that use an Oracle 12c database.  This patch includes full support for these operations with Oracle 12c.

• 20524624

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.

With this patch only rows for source intersections with data are inserted into the rule expansion table.  This should give some performance gain for multi-source calculation rules.

• 20868503

This patch contains performance enhancements for Standard applications Genealogy Calculations, including one specific enhancement for models that use dimensions with dynamic hierarchies.

• 20997176

The prepareDetailedViewsForReporting Web Services API was not functioning properly.  It now creates the Detailed reporting tables and views as intended.

• 21051724

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.

• 21314519

For Profitability instances using Microsoft 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, larger assignment rule definitions are now supported for all supported databases.

 

Known Issues in This Patch

Defect Number

Issue

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

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

• 20215848

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

• 20219396

Reporting cube deployment fails when a generic dimension is associated with a dynamic hierarchy type.  An ASO cube cannot have attribute dimensions associated with dynamic generic dimensions. This issue occurs with Standard and Management Ledger application types.

• 20293473

The HPM_EXP_CALC_SCRIPT view does not select all rows from HPM_CALC_SCRIPT. It omits rows that were created by the processMultiPOVCalcScript web service API.

• 20352749, 21922011

Profitability jobs involving Essbase, like cube deployment, calculations for Standard and Management Ledger applications, etc. may fail due to timeout when using the "APS" Essbase Connection Type.  Oracle recommends using the "Embedded" Essbase Connection Type whenever possible.  If you must use APS mode, you will need to increase the default WebLogic timeout settings.

• 20354742

Smart View queries in Standard and Management Ledger applications fail with validation errors when they reference dimension members containing '&' characters in the member name.

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.

• 20421528

For Management Ledger applications using the "APS" Essbase connection type, the Cells Updated statistic is missing from the Execution Statistics system report.  Oracle strongly recommends you use the "Embedded" Essbase connection type.

• 20550180

In an Enterprise Performance Management (EPM) compact deployment installation, persistence messages from HPCM and from other EPM products that use EclipseLink technology are being redirected to the hpcm.log file. 

See the section Creating a Separate Log File for Persistence Messages near the end of this document for instructions in editing the logging.xml file to redirect these messages to a separate log file.

• 21029692

For Microsoft SQL Server based Profitability instances, database upgrade errors can occur when running the EPM System Configurator during the maintenance upgrade to 11.1.2.4.000. 

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 or 11.1.2.2.500 to 11.1.2.4.000.  They do not occur when upgrading from 11.1.2.1.xxx or 11.1.2.2.000 or 11.1.2.3.XXX or for new installations of 11.1.2.4.000.  They do not occur for Profitability instances using Oracle databases.

The automatic database upgrade included in this patch will correct any previous database upgrade seeded data errors due to this bug.

If your system is SQL Server based and you encountered SQL errors in the Configurator log files (configtool*.log) when upgrading from 11.1.2.2.3xx or 11.1.2.2.500 to 11.1.2.4.000, follow the additional instructions in the final step of the Applying this Patch section of this document to apply the fix.

• 21137858

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.

• 21510459

For Management Ledger applications, when importing a dimension file, if you define an Alias table in the header you must define Alias values for all of
the members in the dimension. The alias value does not necessarily have to be different from the original member name, but you do need to specify a value for each alias table on each member row in the file.

• 21571294

Staging Imports for Standard applications cannot work properly if two Stages have identical dimensions but in a different order.  For example:

Stage 1:  Product, Customer, Entity
Stage 2:  Customer, Entity, Product

When two stages have the same dimensionality the order must be identical also.

• 21912553

When Profitability and Cost Management is scaled within a clustered environment, each module within the Profitability enterprise application must be targeted to all of the servers within the Profitability cluster.

• 22497510

For Management Ledger applications, in certain cases where the Essbase allocation must allocate to level 0 members of a specified parent member it is unable to do so. Instead of allocating to the set of level 0 children it only allocates to the first child in the hierarchy. To work around this issue, in the rule you must select all the level 0 members individually.

• 23512869

LCM Export includes a Metadata folder which contains two artifacts: ApplicationData and Dimensions.  Only the Dimensions artifact is supported for this release.  You can select the ApplicationData for export but application metadata is not actually exported.

To import, you must pre-create the application in the Profitability Applications console, then you can import into it. When importing, you can select the Dimensions artifact; do not select the ApplicationData artifact.

• 24927444

Selecting Suppress Missing in a query definition returns the error "Cannot perform cube view operation.null".  If you deselect that option, the query runs and you can see data along with missing data rows.

• 25110657

EPM Architect performs a validation for Profitability and Cost Management applications that prevents different attribute dimensions from having their members associated at different levels of the same base dimension. 

If your model has multiple attribute dimensions that each need to be associated at different levels of the same base dimension, you must create a PCM application with  Deploy Origin Type "Native" or "Master Cube" in order to avoid the more restrictive EPMA validation. Please see the Profitability and Cost Management Administrator's Guide for more details on these alternate approaches for creating PCM applications.

(Note that all members of the same attribute dimension must still be associated at the same level of the base dimension.)

 

Applying This Patch

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

If you have Management Ledger applications, you should back them up using Life Cycle Management (LCM) in Shared Services.

2.    This patch must automatically re-register your Profitability and Cost Management applications, which will delete native non-Admin user provisioning.  Use Life cycle Management  (LCM) in the Shared Services console to export the Native Directory under Foundation, usually located at Foundation => Shared Services => Native Directory, so you can restore it in step 11. 

1)  From the Shared Services console, open the Application Groups folder.
2)  Open the Foundation sub-folder and select Shared Services. 
3)  Export the Native Directory artifact and all content under it. 

You will need the resulting LCM export file in step 11 to restore the user provisioning.

3.    Shut down the Profitability service (Hyperion Profitability - Java Web Application).

4.    Download and unzip the downloaded patch file, P27732412_111240_Generic.zip, to the <EPM_ORACLE_HOME>/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

5.    On each machine on which Profitability and Cost Management is installed, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.

6.    To apply the patch, enter the following command on one line:

Windows:

opatch.bat apply <EPM_ORACLE_HOME>/OPatch/HPCM_11_1_2_4_127_27732412 -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_4_127_27732412 -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_35 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

NOTE: The default for <EPM_ORACLE_HOME> is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

7.    For WebLogic deployments, you must clear the WebLogic cache.

For WebSphere deployments, you must use EPM System Configurator to redeploy the Web application.

8.    All users should now clear cached files from their browsers.

9.    Start the Profitability service (Hyperion Profitability - Java Web Application). Note that this step now automatically performs any required database updates after applying a new patch - there is no need to run a manual SQL script.

10. 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 11124.131. 

If instead you get a Schema Version Mismatch error, report this to Oracle Support.  You can also search the hpcm.log file for SQL errors following the first recent occurrence of the string '11124.131'.  If you find an error that you can resolve, the database upgrade can be performed manually after resolving the error, to complete the installation (see the Performing Manual Database Updates section below).

11. From the Shared Services console, import the LCM file you created in step 2, to restore the native user provisioning.

12. For each Detailed application, you must re-deploy the Reporting Tables and Views.

13. Important extra step for some Profitability instances using Microsoft SQL Server (see bug# 21029692 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 maintenance upgrade to 11.1.2.4.000 and convert them into 11.1.2.4 Calculation Rule definitions:

o    Your Profitability instance uses Microsoft SQL Server.

o    You have Detailed Profitability applications that were created in 11.1.2.2 and those Detailed Profitability applications contain Object Calculation definitions.

o    You recently upgraded from 11.1.2.2.3xx or 11.1.2.2.500 to 11.1.2.4.000.

o    You have not already performed these steps when applying a previous patch for 11.1.2.4.

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.4 Detailed Profitability applications as Calculation Rules.

NOTE:  Applying any Profitability and Cost Management Patch Set Update (PSU) can reset the current security policy defined for the Profitability Web Service within Oracle Web Services Manager (OWSM).  If web services are used, you may need 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.

Optional – Performing Manual Database Updates (only when there are errors in the automatic update)

If step 10 in the Applying this Patch section above reveals that errors occurred during the automatic database updates performed during service startup, and you have identified and corrected the problem, you can follow these instructions to complete the required database updates manually.

1.    Shut down the Profitability service (Hyperion Profitability – Web Application).

Run the appropriate database update patch script for your database type.  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.

 Database
 Type

Database Patch Files

 MS SQL

 Server

Run the following database update script using Microsoft SQL Server Management Studio against the Profitability and Cost Management product database:

 

<EPM_ORACLE_HOME>\products\Profitability\database\Common\MSSQLServer\create_11.1.2.4.120.sql

 

Note: If your Profitability instance was affected by the 11.1.2.2.3xx to 11.1.2.4.000 upgrade errors (see bug# 21029692 in the Known Issues section), in addition to applying the database updates for this patch and previous patches, this script will also correct the seeded data errors from that upgrade.

 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.4.120.sql

 

2.    Start the Profitability service (Hyperion Profitability - Java Web Application).

3.    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 11124.131. 

4.    For each Detailed application, you must re-deploy the Reporting Tables and Views.

5.    Complete any remaining steps you have not performed in the Applying this Patch section above.

 

Rolling Back This Patch

To roll back 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 – Java Web Application).

3.    If there are any database updates to be rolled back, they should be rolled back before rolling back the Opatch because the Opatch rollback will remove the rollback SQL scripts.  You may want to save the rollback script in a directory outside of <EPM_ORACLE_HOME> before rolling back the Opatch.

To roll back the database changes made by this patch, run the appropriate scripts for your database, if any are required.

 Release

 Database
 Type

Database Patch Files

 Rolling back to
 release
 11.1.2.4.120 or
 11.1.2.4.121 or
 11.1.2.4.122 or
 11.1.2.4.123 or
 11.1.2.4.124 or
 11.1.2.4.125 or
 11.1.2.4.126

 N/A

If you applied this patch on the 11.1.2.4.120, 11.1.2.4.121, 11.1.2.4.122, 11.1.2.4.123, 11.1.2.4.124, 11.1.2.4.125, or 11.1.2.4.126 release and are rolling back to that release, there are no new database changes to roll back from this patch.

 Rolling back to
 release
 11.1.2.4.110

 MS SQL

 Server

If you applied this patch on the 11.1.2.4.110 release and are rolling back to that release, run the following database rollback script using Microsoft SQL Server Management Studio against the Profitability and Cost Management product database:

·   <EPM_ORACLE_HOME>\products\Profitability\database\Common\MSSQLServer\rollback_11.1.2.4.120.sql

 Rolling back to
 release
 11.1.2.4.110

 Oracle

If you applied this patch on the 11.1.2.4.110 release and are rolling back to that release, run the following database rollback script in the Profitability and Cost Management product schema/user using Oracle SQL Developer:

·   <EPM_ORACLE_HOME>\products\Profitability\database\Common\Oracle\rollback_11.1.2.4.120.sql

 Rolling back to
 release
 11.1.2.4.101 or

 11.1.2.4.100

 MS SQL

 Server

If you applied this patch on the 11.1.2.4.100 or 11.1.2.4.101 release and are rolling back to either of those releases, run the following database rollback scripts using Microsoft SQL Server Management Studio against the Profitability and Cost Management product database, in this order:

·   <EPM_ORACLE_HOME>\products\Profitability\database\Common\MSSQLServer\rollback_11.1.2.4.120.sql

·   <EPM_ORACLE_HOME>\products\Profitability\database\Common\MSSQLServer\rollback_11.1.2.4.110.sql

 Rolling back to
 release
 11.1.2.4.101 or

 11.1.2.4.100

 Oracle

If you applied this patch on the 11.1.2.4.100 or 11.1.2.4.101 release and are rolling back to either of those releases, run the following database rollback scripts in the Profitability and Cost Management product schema/user using Oracle SQL Developer, in this order:

·   <EPM_ORACLE_HOME>\products\Profitability\database\Common\Oracle\rollback_11.1.2.4.120.sql

·   <EPM_ORACLE_HOME>\products\Profitability\database\Common\Oracle\rollback_11.1.2.4.110.sql

 Rolling back to
 release
 11.1.2.4.000

 MS SQL

 Server

If you applied this patch on the 11.1.2.4.000 release and are rolling back to the 11.1.2.4.000 base release, run the following database rollback
scripts using Microsoft SQL Server Management Studio against the Profitability and Cost Management product database, in this order:

·   <EPM_ORACLE_HOME>\products\Profitability\database\Common\MSSQLServer\rollback_11.1.2.4.120.sql

·   <EPM_ORACLE_HOME>\products\Profitability\database\Common\MSSQLServer\rollback_11.1.2.4.110.sql

·   <EPM_ORACLE_HOME>\products\Profitability\database\Common\MSSQLServer\rollback_11.1.2.4.100.sql

 Rolling back to
 release
 11.1.2.4.000

 Oracle

If you applied this patch on the 11.1.2.4.000 release and are rolling back to the 11.1.2.4.000 base release, run the following database rollback
scripts in the Profitability and Cost Management product schema/user using Oracle SQL Developer, in this order:

·   <EPM_ORACLE_HOME>\products\Profitability\database\Common\Oracle\rollback_11.1.2.4.120.sql

·   <EPM_ORACLE_HOME>\products\Profitability\database\Common\Oracle\rollback_11.1.2.4.110.sql

·   <EPM_ORACLE_HOME>\products\Profitability\database\Common\Oracle\rollback_11.1.2.4.100.sql


Capture the log messages; if there are any errors, report them to Oracle Support. 

4.    From a command line, change the directory to <EPM_ORACLE_HOME>/OPatch (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

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

Windows:

opatch.bat rollback -id 27732412 -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 27732412 -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.

6.    For WebLogic deployments, you must clear the WebLogic cache.

For WebSphere deployments, you must use EPM System Configurator to redeploy the Web application.

7.    All users should now clear cached files from their browsers.

8.    Start the Profitability service (Hyperion Profitability – Java Web Application).

9.    Invoke Profitability and Cost Management and open an application.  If you get a Schema Version Mismatch error, report this to Oracle Support.

10. Re-register each of your Profitability and Cost Management applications using Application Library.

11. For each Detailed application, you should re-deploy the Reporting Tables and Views.

12. If you are rolling back to release 11.1.2.4.101 or prior and you have Management Ledger applications that were created prior to applying this patch, you will need to re-import them from the LCM backups you took in step 1 of the Applying this Patch section.  You only need to re-import the contents of the Model folder for each application; you do not need to re-import dimension metadata or other artifacts.

Troubleshooting FAQs

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.

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_35

UNIX/Linux:

./opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_35 –invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

I applied the patch successfully but I don’t see the changes from the patch in the product. What should I do?

When patching an .EAR file for an application, you may need to delete the cached files in the following folders in order to see the changes provided with the patch:

<MIDDLEWARE_HOME>/user_projects/domains/<DOMAIN_NAME>/servers/
<MANAGED_SERVER_NAME/tmp/

<MIDDLEWARE_HOME>/user_projects/domains/<DOMAIN_NAME>/servers/
<MANAGED_SERVER_NAME/cache

Tips and Troubleshooting

Controlling the Allocation Rounding Precision for Management Ledger Calculations

There is a hidden installation preference you can insert in the database to change the number of decimal places that allocation results are rounded to during Management Ledger calculation (the current default is 7 decimal places).

In the following SQL statements, replace <value> with an integer from -6 to 7 (keep the single quotes). 

A value of -6 rounds to the nearest million; a value of 0 rounds to the nearest whole number; a value of 7 rounds to 7 decimal places. 

During the allocation, the remainders from the rounding operations are added to the destination intersection with the largest allocated value.

For Oracle databases, execute this SQL statement in SQL Developer while connected as the Profitability product schema owner and then commit the change:

INSERT INTO HPM_INSTALLATION_PREFERENCE

      (ID,NAME,VALUE,HPM_INSTALLATION_ID,CREATED_TIMESTAMP,CREATED_USERID,MODIFIED_TIMESTAMP,MODIFIED_USERID,DISPLAY_ORDER)

VALUES (40,'MLCalculationPrecision','<value>',1,SYSDATE,'INIT',SYSDATE,'INIT',40);

 

For Microsoft SQL Server databases, execute this SQL block in SQL Server Management Studio while connected to the Profitability product database:

BEGIN

   SET IDENTITY_INSERT HPM_INSTALLATION_PREFERENCE ON

   INSERT INTO HPM_INSTALLATION_PREFERENCE  

      (ID,NAME,VALUE,HPM_INSTALLATION_ID,CREATED_TIMESTAMP,CREATED_USERID,MODIFIED_TIMESTAMP,MODIFIED_USERID,DISPLAY_ORDER)
   VALUES (40,'MLCalculationPrecision','<value>',1,getDate(),'INIT',getDate(),'INIT',40)
   SET IDENTITY_INSERT HPM_INSTALLATION_PREFERENCE OFF

END

go

Creating a Separate Log File for Persistence Messages

For Enterprise Performance Management (EPM) instances installed as compact deployment, messages from other installed EPM products are also directed to the hpcm.log file. The logging.xml file can be edited to redirect these messages to a new log file called "persistence.log".  You may find advantage in splitting the persistence messages to a separate log file even for standard deployments.  To do so, follow these steps:

1.    For compact deployments, the logging.xml file is located at <MIDDLEWARE_HOME>\user_projects\domains\EPMSystem\config\fmwconfig\servers\EPMServer0
For standard deployments, the logging.xml file is located at <MIDDLEWARE_HOME>\user_projects\domains\EPMSystem\config\fmwconfig\servers\Profitability0

2.    Edit the logging.xml file and define a new log handler within the <log_handlers> section.  Here is a suggested definition for a new handler:

<log_handler name="persist-handler" class="oracle.core.ojdl.logging.ODLHandlerFactory">
  <property name="path" value="${domain.home}/servers/${weblogic.Name}/logs/persistence.log"/>
  <property name="maxFileSize" value="20000000"/>
  <property name="maxLogSize" value="100000000"/>
  <property name="useSourceClassAndMethod" value="true"/>
</log_handler>

3.    Alter the logger for org.eclipse.persistence in the <loggers> section to point to the
new handler, as in the example below, where the handler name has been changed from "epmpcm-handler" to
"persist-handler".

<logger name="org.eclipse.persistence" level="NOTIFICATION:16" useParentHandlers="false">
  <handler name="persist-handler"/>
</logger>

Protected Management Ledger System Dimensions

The Management Ledger Rule and Balance dimensions are system dimensions that are seeded and should not be edited in any way, even if some part of the system allows it (e.g. EPM Architect Dimension Library or Update Dimensions in the Profitability Applications console).  These dimensions are reserved for system use.

Management Ledger Business Dimensions - Shared Members

In Management Ledger business dimensions, do not make shared members that reference non-level-0 base members.  Doing so will cause the copy POV and the calculation operations to fail because it creates situations where HPCM needs to write to non-level-0 members, which is not supported in Essbase for ASO cubes.

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.  This is good practice for all Profitability and Cost Management application types.

ODBC Driver Recommendation

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.

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

4.    Click the Save icon.

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:

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

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>

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

WLIOTimeoutSecs 3000
Idempotent OFF

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