Oracle® Hyperion Financial Management, Fusion Edition
Release 11.1.2.1.000 Patch Set Update (PSU): 11.1.2.1.602
Readme
This Readme file describes the defects fixed in this patch and the requirements and instructions for installing 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 the issue described in the Readme matches the issue that you are encountering. Review the Bug Number referenced in the Readme for additional information.
· Verify that your system configuration (product version, patch level, and platform) exactly matches what is specified in the Readme.
This Patch Set Update replaces files in the existing installation and is a cumulative patch.
You can apply this patch to the following releases:
Financial Management Release 11.1.2.1.000
Financial Management Release 11.1.2.1.101
Financial Management Release 11.1.2.1.102
Financial Management Release 11.1.2.1.103
Financial Management Release 11.1.2.1.104
Financial Management Release 11.1.2.1.600
Financial Management Release 11.1.2.1.601
Prerequisites
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:
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.”
Oracle Database Requirements
· If you use Oracle Database Client 10.2.x or 11.1.x for Financial Management, you must set the StmtCacheSize registry setting for Oracle OLE DB to 10 on all Financial Management application servers. This is due to a memory issue in Oracle Provider for OLE DB. The registry setting path is: Hkey_Local_Machine\Software\Oracle\Key_Homename\Oledb. Note that the 11.2.x Oracle Database Client should not be changed.
To resolve the high memory usage, enable Statement Caching. The configured value must not be zero. The recommended value is between and 1 and 10.
1. Edit the following registry value: Hkey_Local_Machine\Software\Oracle\Key_Homename\Oledb Value Name: StmtCacheSize Value (decimal): 1 where Key_Homename refers to the appropriate Oracle Home.
2. Stop and restart the HFM application processes.
In addition, if you are using System 11 on a 64-bit operating system with a 10g database, the Oracle OLE provider on all Financial Management servers must be at least 10.2.0.4.21+.
If you are using 32-bit with 10g, the Oracle OLE provider version MUST be at or greater than the database server version. If you are running 32-bit or 64-bit and using 11.1.0.6 or 11.1.0.7 OLE Provider, you must upgrade to Oracle Database Client 11.1.0.7.33+.
This patch applies to all supported platforms.
This patch is supported for English only.
· This release features logging capability for the Task
Automation module. You can enable logging using this registry setting:
HKLM\SOFTWARE\Hyperion
Solutions\Hyperion Financial Management\Web\HsvActionsLogLevel
(DWORD)
Accepted
values are:
0 - None
1 - Error
2 - Warning
3 - Debug
4 - Trace
Level
None: No logging
Level Error: Anything that occurs in an exception
Level Warning: Any warning messages, such as unexpected input parameters
Level Debug: Logs the input parameters for task automation and key
methods
Level Trace: Logs enter and exit methods in every method and class
Messages
are logged to: EOI\diagnostics\logs\hfm\hfmtaskflows-diag-<PID>.log
The logging level is read from the registry setting periodically every minute.
The logging level determines which messages are logged.
The message format includes timestamp, level, thread ID and message.
Note: The identity that is running the IIS application pool process must have full access to the log file directory. Example: EOI\diagnostics\logs\hfm\
· This release features Enhanced Cell Text capability which enables you to enter multiple cell text entries and create cell text labels. For details, see the Oracle Hyperion Financial Management Enhanced Cell Text Addendum, which is posted on the Oracle Technical Network.
This feature is also supported by Oracle Hyperion Performance Management Architect, Oracle Hyperion Financial Reporting, and Oracle Hyperion Smart View for Office. See these Readmes:
· Oracle Hyperion Performance Management Architect Readme 11.1.2.1.102 (11780153)
· Oracle Hyperion Financial Reporting Readme 11.1.2.1.101 (11732644)
· Oracle Hyperion Smart View for Office Readme 11.1.2.1.101 (12398953)
·
17951242
– Extended analytics extracts hang application.
·
17707842
– During EPMA deploy web server name is displayed in application server
dropdown.
·
17641634
– In WDEF the + icon does not display the intercompany entities.
·
17375403
– When running ICP report receive erroneous message “You do not have access
rights to the data.”
·
16921279
– Unable to see POV members in WDEF opened from smart view.
·
16883780
– Review level does not work correctly in manage ownership if SupportSubmissionPhaseForAccounts is enabled.
·
16690190
– When documents are removed the records is the BINARYFILES table are not
removed from the database.
·
16390111
– When executing EA extract to file using task flow the resulting file is not
copied to the specified location.
·
16021248
– Using HS.CalculateExchangeRate in rules generates
error "Invalid Item ID."
·
14590534
– Unable to export task audit data.
·
14101719
– In WDEF you cannot reuse the same member list in multiple AddMember
functions.
·
13794569
– When you generate an intercompany report in xls
there are extra spaces in subtotal/totals.
Email Alerts
You must re-register the new “mailer.dll” by performing the following steps:
1. Perform an IISRESET.
2. Register the mailer using the command:
Regasm /codebase “%Oracle_Home%\EPMSystem11R1\products\FinancialManagement\Web server\mailer.dll”
Note: You must include the double quotes in the command, otherwise it will not register properly.
Also, you will need to use regasm from v2.0. of .Net Framework. If you are using 64-bit, use the regasm from the 64-bit framework (Framework64).
Metadata/Data Exports
You will need to set the AspResponseBufferLimit by performing the following steps.
By default, the value for the ASPBufferLimit property in IIS 6 and for the bufferLimit property in IIS 7 is 4,194,304 bytes (4 MB).
The recommendation is to set the value to 1073741824 (1 GB).
To increase the buffering limit in IIS 6, follow these steps:
1. Click Start, click Run, type cmd, and then click OK.
2. Type the following command, and then press ENTER:
cd /d %systemdrive%\inetpub\adminscripts
3. Type the following command, and then press ENTER:
cscript.exe adsutil.vbs SET w3svc/aspbufferinglimit LimitSize
Note: LimitSize represents the buffering limit size in bytes. For example, the number 1073741824 sets the buffering limit size to 1 GB.
To increase the buffering limit in IIS 7, follow these steps:
1. Click Start, click Run, type inetmgr, and then click OK.
2. In the left hand panel, expand the computer name by clicking the plus sign next to it.
3. Expand the “Sites”.
4. Expand “Default Web Site”
5. Select the HFM web site in the expanded list.
6. In the middle panel “Features View”, in the IIS section, double click the ASP icon.
7. Expand “Limits Properties”.
8. Change “Response Buffering Limit” to 1073741824.
9. In the right hand panel, select “Apply”.
10. Restart IIS.
System Reports
If you are experiencing issues generating system reports in PDF format, add the following Registry Variables on the HFM application server:
Under [HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\Hyperion Financial Management\Server\SystemReports]
add the following DWORD values (these examples are using decimal values and only positive values are allowed)
"jvmMaxHeapSize"="768"
"jvmMinHeapSize"="16"
You may need to adjust these values up or down depending on your specific environment.
Clearing Cell Text
Cell text can be cleared through rules by using the HS.SetCellTextWithLabel function and entering a null string (“”).
For example, HS.SetCellTextWithLabel(<POVExpression>,<CellTextLabel>, “”)
This will clear the cell text contents of the specified label for the specified POV.
However, if no other cell text labels for the same POV contain cell text, the Boolean return value (True/False) for the function HS.ContainsCellText will not be updated until all users log off. The HS.ContainsCellText function which is not label-specific might therefore return a True value when in fact no cell text exists.
To verify whether cell text does in fact
exist in one or more of the cell text labels, it will be necessary under these
circumstances to check each label individually using the function HS.ContainsCellTextWithLabel(<POVExpression>,<CellTextLabel>) or HS.GetCellTextWithLabel(<POVExpression>,<CellTextLabel>).
LCM Web Service
In order for HFM Migrations to run successfully, the user running the LCM Web Service must have R/W access to the “%EPM_ORACLE_INSTANCE%\products\FinancialManagement\Web\FileTransferData” directory.
Additional Known Issues
·
12655012
– When invalid dimension members are assigned to a variable and use the same
variable for validation, the rules file does not validate properly.
·
12616998
– Searching for members does not work correctly when using a member list as a
filter.
·
12565880
– When you click in a data grid, errors may occur in Internet Explorer 8.
·
14005018
– Loading data with cell text takes much longer than loading data without cell
text.
·
14085078
– Loading cell text takes a long time.
·
14163818
– If the HFM ODL log is too large, you may need to manually truncate it.
·
14001376
– In Process Journals, when viewing the list of posted journals, the Date Posted
column is displayed in the wrong format if the IE browser language is set as
Russian.
·
13954904
– When you schedule a taskflow, the End Time minutes
value option is not saved correctly.
·
13416097
– Emails sent from Process Control do not contain all of the documented
details.
·
13078129
– Results of periodic translation rules differ based on the order of input.
·
14194479
– Timestamp is modified when WDEF with celltext is
opened.
·
14336993
– POV details are not passed to linked forms in smartview.
·
11685157
– Temp files are not cleared from the HFM Server Working Folder after loading
data using FDM.
·
13740796
– Unable to open .mht format from custom documents.
·
13778676
– In smartview receive “Unknown error in HFMProvider. Data at
the root level is invalid. line1, position1.”
·
14209871
– Idle sessions are not being cleared.
·
14342894
– Extended analytics does not extract data for dynamic accounts.
·
14532449
– Cannot load ICT using Russian text encoding.
·
14734967
– Smartview throws error "checking form syntax -
unable to run calculate" for WDEF.
·
15870144
– Error creating a journal report that contains journals with working status.
·
15936108
– Force calculate doesn't work for new account member added after metadata load
·
16198546
– Data blocked with NOINPUT rule is deleted when loading normal input data.
·
16269791
– Need ability for separate HFM clusters to point to different datasources.
·
17811923
– Users with restricted access can load data.
·
13592575
– In Journals the ‘Filter by Entity’ option does not work with more than one
entity.
The section includes important information about applying this patch for EPM System Installer.
Note: This patch should be applied to all machines that have the Financial Management Client/ADM driver installed. This patch should be applied to ALL HFM application servers and ALL HFM Web servers.
To apply this patch:
1. Stop Financial Management. Ensure that all HFM processes are not running, including HsxServer.exe, HsvDataSource.exe, odl_rotatelogs.exe and CASecurity.exe. If you are running IIS, stop and re-start it.
2. Download
and unzip the downloaded patch file, <PATCH
FILE NAME>.zip, to the <EPM_ORACLE_HOME>\OPatch directory (by default, Oracle/Middleware\EPMSystem11R1\OPatch).
Note: <PATCH FILE NAME>.zip is
the name that My Oracle Support assigns to this patch. When you download the
file, a message indicates what the filename is.
3. From a command line, change the directory to <EPM_ORACLE_HOME>\OPatch.
4. Enter the following command to apply the patch:
opatch.bat apply
<EPM_ORACLE_HOME>\OPatch\18252538 -oh
<EPM_ORACLE_HOME> -jre
<MIDDLEWARE_HOME>\jdk160_21
where <MIDDLEWARE_HOME> is Oracle\Middleware by default.
5. Restart Foundation Services.
6. All users should now clear cached files from their browsers.
To roll back a patch:
1. Stop Financial Management. Ensure that all HFM processes are not running, including HsxServer.exe, HsvDataSource.exe, odl_rotatelogs.exe and CASecurity.exe. If you are running IIS, stop and re-start it.
2. From a command line, change the directory to <EPM_ORACLE_HOME>\OPatch (by default, Oracle/Middleware/EPMSystem11R1\OPatch).
3. Enter
the following command:
opatch.bat rollback –id 18252538 -oh
<EPM_ORACLE_HOME> -jre
<MIDDLEWARE_HOME>\jdk160_21
where <MIDDLEWARE_HOME>
is Oracle\Middleware by default.
4. All users should now clear cached files from their browsers.
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:
opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>\jdk160_21
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 use the new patch (this action might be appropriate if the previous patch was not critical) or (2) request a “merged patch” consisting of the new patch and the patch that it conflicts with. To request a merged patch, contact your Oracle Support representative.
This warning means that the patch being applied is a superset of a patch already on the deployment and the existing patch will be rolled back. The following snippet shows the context of this warning.
The following warnings
have occurred during OPatch execution:
1) OUI-67078:Interim patch 12345678 is a superset of the patch(es) [77777777] in OH C:\Hyperion
-----------------------------------------------------------------------------------
OPatch Session completed with warnings.
Copyright © 2014, Oracle and/or its
affiliates. All rights reserved.
http://www.oracle.com