Release 11.1.2.3.000 Patch Set Update (PSU): 11.1.2.3.820
Readme
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.
This is a patch set update (PSU). This patch replaces files in the existing installation and does not require a full installation.
You can apply this patch to the following releases:
11.1.2.3.500 (17891352) or later.
• Install Oracle’s Hyperion® Shared Services Release 11.1.2.3.500.
• Install Oracle® Hyperion Smart View, Fusion Edition release 11.1.2.5.200 or later.
The user applying the patch should be the user who was set up to install and configure EPM System products. Required user privileges or rights:
Use the user account that has Local administrator rights and was set up for installation and configuration. This user is an administrator and is the same for all EPM System products. Assign local policies if required by the product. Such assignments typically are: “Act as part of the operating system, Bypass traverse checking, Log on as a batch job, Log on as a service.”
Use the account that was used to install EPM System products and has Read, Write, and Execute permissions on $MIDDLEWARE_HOME. If you installed other Oracle products, the user who installed EPM System products must be in the same group as the user who installed the other Oracle products. OPatches are not intended to be applied using a root user.
Applies to all supported platforms. Office 2003 is not supported.
This patch supports English only.
A method of autotagging a template of a business reporting workbook is provided that includes receiving the template of the business reporting workbook; receiving user specified selection of portions of the template, wherein the portions are associated with at least two dimensions of the business reporting workbook; creating a modification of the template by associating a type of tag with the portions; and generating an eXtensible Business Reporting Language (XBRL) version of the business reporting workbook based on the modification of the template.
|
Issue |
|
|
• 24299279 |
FAILURE TO CREATE A ZIP FILE Workaround: set taxonomy_cache_poll = 0 in the mappingtool.properties on the server. |
|
• 24298062 |
001/822100 - DUPLICATE MAPPINGS REPORTED. NEED TO SPECIFY DIM NAMES IN TAG FOR DIMs IN CELL AU AND BA WORKAROUND: ADD DIM NAMES "ifrs:MiningAssetsMember" TO CELLS AU6; AX6; "ifrs:MiningPropertyMember" AU7; "ifrs:OilAndGasAssetsMember" BA6 ; REMOVE DIM TAGS FOR THE DEFAULT DIMENSIONS H5, BP5; H8, J8, K8, M8 etc. |
|
• 23858378 |
001/ 871100 - 11 DIMENSIONAL MAPPING ERRORS. NEED TO ADD DIM NAMES ifrs:SegmentsMember TO RELEVANT DIMENSION CELLS |
|
• 23858316 |
001/827570 - 10 DUPLICATES. WORKAROUND – ADD
CONCEPT NAME |
|
• 23755658 |
001/822390-8 VALIDATION REPORT DOES NOT LIST PROPER NUMBER OF ANALYZED MAPPINGS. WORKAROUND: If
user notices missing mappings on a whole column on a dimension |
|
• 23754062 |
260/825500 - XBRL PREFIX MUST BE RESPECTED WHEN USING CONCEPTNAME IN TAGGING |
|
• 23750217 |
260/832410 - INVALID DIMENSIONAL MAPPINGS REPORTED IN ARELLE. WORKAROUND: 1. Remove all DIM tags for the default dimensions – cells D39, V39; D41, T41, V41, AL41; D43, E43, F43, G43 etc. 2. Apply name attribute "ifrs:ExplorationAndEvaluationAssetsMember" to Z42 cell |
|
• 23746664 |
WHEN PUBLISHING ALL NETWORKS FOR 260 CLIENT USES OVER 11GB OF MEMORY. WORKAROUND: If you
try to publish with a non-network worksheet having very large number of cells
together with existing xml |
|
• 23744508 |
PUBLISHING FAILS IF "PUBLISH EMPTY CELLS" CHECK BOX NOT CHECKED. |
|
• 23725119 |
001/823180 – A LOT OF REJECTED AND DUPLICATE MAPPINGS Publishing returns 324 rejected and 815 duplicate mappings. WORKAROUND: 1. Apply dim name attribute for $G$72 and $CG$72 2. Apply dim name attribute on CJ$72 3. Apply dim name attribute on $BO$73 |
|
• 23719311 |
001/822390-8 - INVALID DUPLICATE MAPPINGS $D$8, $E$8, $F$8 WORKAROUND: On the worksheet the taxonomy labels are
the following: To work around this issue need to specify Concept name in both conflicting or duplicate names. |
|
• 23665480 |
014/834120 – ERRORS IN ARELLE VALIDATION REPORT. It would appear
that a mapping like $G$16 and $G$21 requires a dimension mapping, but there
is not a header in the containing sheet table |
|
• 23597931 |
MAPPING VALUES ARE NOT EXTRACTED ON DOCLET REFRESH With Document
attached few columns(I,J,K and U,V,W) are hidden and with which the cell
level mapping had issue. |
|
• 23570442 |
001/822390-22 - SOME DATAPOINTS REPORTED AS DIMENSIONALLY INVALID IN ARELLE There are few workarounds that had to be applied: 1. Tagged dimension names in some tables (A98; A132-A137) to avoid dimensionally invalid errors 2. Concept names applied to concept cells, as algorithm by parent|child label generated duplicates 3. Untagged totals rows 8, 23, 51, etc.
|
|
• 23564894 |
001/822390-21 - SOME DATAPOINTS ARE REPORTED AS DUPLICATES There are few
workarounds that had to be applied: |
|
• 23535389 |
NETWORK 014_818000 HAS ERRORS. WORKAROUND: The cells E thru N for row 16 must be merged. After merging these cells, the corresponding data cells will be mapped with the correct dimensions. Validating the published XBRL will produce no primary item dimensional errors |
|
• 23316079 |
NETWORK 861000 - DATA VALUES ARE NOT PUBLISHED IF DIMENSION NAME IS MISSING IN EXCEL WORKSHEET Workaround: The sheet is missing some labels and needs |
|
• 23307389 |
ALLOW VALUES FOR DATE FIELDS ENTERED AS A DATE. Currently values for date fields have to be entered as text (prepended with '), for instance: '2015-01-12 |
|
• 23253952 |
TAXONOMY REFERENCE FIELD IS EMPTY Workaround: |
Server hosting Disclosure Management – 16GB of Total Ram
Disclosure Management Application – set max to minimum of 8GB
Client requires a 64 bit machine with minimum of 8GB of Ram:
64bit version of Office and SmartView
This section includes important information about applying this patch for Oracle Hyperion Disclosure Management.
Before you begin the installation of the patch, back up your existing Disclosure Management database and associated files in case you need to restore your current installation.
Note: Typically the Disclosure Management installers are served out from the: Oracle\Middleware\EpmSystem11R1\common\epmstatic directory on the Web Server. If the Web server is on a different server than the Disclosure Management server, ensure the Disclosure Management installers are also available on the Web server.
To apply this patch:
1. On the server hosting the Disclosure Management Service, shut down all services and servlet instances related to the Oracle® Hyperion EPM Release 11.1.2.3.500 installation. To avoid possible confusion, you may want to consider renaming the folders of previously applied patches in the opatch directory by adding _old to the folder name.
2. Download and unzip the downloaded patch file, 23099997.zip, to the <EPM_ORACLE_HOME>/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).
NOTE: 23099997.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.
3. On all machines that have Oracle® Hyperion Disclosure Management server installed, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.
4. To apply the patch, enter the following command on one line:
Windows:
opatch.bat apply <EPM_ORACLE_HOME>\OPatch\<PATCH DIRECTORY> -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/<PATCH DIRECTORY> -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_35 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc
NOTE: The default for <EPM_ORACLE_HOME> is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.
5. The additional manual step of running database sql script needs to be performed. The script is located at:
<PATCH_DIRECTORY>\files\database\<dbtype>\update_qmr_report.sql.
6. Manually update all the Disclosure Management client-side systems as following:
· Copy the Disclosure Management add-in folder content (1 MSI) from the install image to
<ServerDrive>/Oracle/Middleware/EPMSystem11R1/common/epmstatic/disclosure_mgm/svext
· On every machine where Oracle HTTP Server is installed, if you are using the embedded proxy servlet, copy the Disclosure Management add-in folder content to all machines in the system. You must then restart Oracle HTTP Server.
· Install Disclosure Management add-in DiscManSetup.msi.
· Install HVX add-in DiscManHVX.msi.
· Restart Microsoft Word or Excel. This will cause the Disclosure Management installer to run. Follow the installer's prompts.
· From the Disclosure Management About dialog box, ensure that the client version is updated to 11.1.2.3.820.
7. All users should clear cached files from their browsers and temp directory.
8. After completing the OPatch procedure, you can delete the WebLogic temp directory if applicable and restart all the services and servlet instances which were previously shut down (in step 1 above).
9. If this patch is applied on PS3 PSU500 – the additional manual step of running database sql scripts needs to be performed. The scripts are located at <PATCH_DIRECTORY>\files\database\<dbtype>\create_qmr.sql and <PATCH_DIRECTORY>\files\database\<dbtype>\update_qmr_report.sql. If the patch is applied on PSU PSU790 or later, this step should be skipped.
10. All users should clear cached files from their browsers.
To roll back a patch:
1. On the server hosting the Disclosure Management Service , shut down all services and servlet instances related to the Oracle® Hyperion EPM Release 11.1.2.3.820 installation.
2. From a command line, change the directory to <EPM_ORACLE_HOME>/OPatch (by default, Oracle/Middleware/EPMSystem11R1/OPatch).
3. To roll back the patch, enter the following command on one line:
Windows:
opatch.bat rollback -id 23099997 -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 23099997 -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.
4. If this patch is applied on PS3 or PS3 PSU500 and step 8 in section "Applying this Patch" was executed – the additional manual step of running database sql scripts needs to be performed. The scripts are located at <PATCH_DIRECTORY>\files\database\<dbtype>\drop_qmr.sql and <PATCH_DIRECTORY>\files\database\<dbtype>\rollback_qmr_report.sql
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 am getting error loading a taxonomy. It seems the application is unable to download taxonomy over HTTPS . Is there a workaround?
You can add the following entries to the Disclosure Management server JVM options (usually located under HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\DisclosureManagement0\ HyS9Disclosure_epmsystem1):
-DUseSunHttpHandler=true
-Dssl.SocketFactory.provider=sun.security.ssl.SSLSocketFactoryImpl
-Dssl.ServerSocketFactory.provider=sun.security.ssl.SSLSocketFactoryImpl
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
I am having trouble connecting via SSL, what is the most likely problem?
The most like likely scenario is that the certificate is self-signed and the root certificate is not installed. When trying to connect and prompted for the warning, click the “View Certificate” button and make sure to install the root certificate.
Most likely the server has no access to the internet and the HTTP Cache needs to be populated. Unzip the http.zip archive file located within Opatch into the following directory:
<MIDDLEWARE_HOME>\user_projects\epmsystem1\DisclosureManagement\discman1\XbrlFiles\resources\System\cache.
Some other things to consider:
Make sure that the entry point specified in the mappingtool.properties file is valid or existing.
Make sure that the target namespace matches the entry in qmr.properties and the entry point in mappingtool.properties
Make sure that the supported taxonomy version entry in qmr.properties file matches the active taxonomy version.
I currently have Arelle version 2015-08-30. The new version was recently posted on arelle.org . Can I download and use that version? Which one should I use?
We encourage users to download and use the latest version of Arelle. Be aware, that validation plugins are separated now and have to be loaded prior to the first use.
One way to do it is to start ArelleGui.exe, click on ”Help” -> ”Manage plug-ins”, in the Plug-in manager click on ”Select” and choose the appropriate plugin from the list. For the HVX users that would be ”eba” plugin that incorporates both EBA and EIOPA validation rules. For the users reporting to the SEC, that would be ”efm” plugin. You can also load EdgarRenderer plugin that implements U.S. SEC Edgar Renderer.
The other way is to open command-line window, navigate to the directory where Arelle is installed and issue the command:
arelleCmdLine ––plugins=”+</path/to/arelle>/plugin/validate/<plugin name>” , where </path/to/arelle/> is path to Arelle folder and <plugin name> is the name of validation plugin.
For example:
arelleCmdLine ––plugins=”+c:\arelle_2016-03-08\plugin\validate\efm”
Option of loading taxonomy manager is not working in Disclosure Management on Multi Node Environment. Is there a workaround?
Due to configuration files existing in the file system, it is recommended that Disclosure Management be running on a single node only.
If using multiple nodes is still required by the client, please follow the following procedures when registering taxonomy, FDM files or uploading a new mapping file:
a. Bring down all DM nodes except one.
b. Register the taxonomy, or FDM files, or mapping file.
c. Copy the following files from the node that is up to all the other nodes:
§ <MW_HOME>\user_projects\epmsystem1\DisclosureManagement\discman1\config\mappingtool.properties
§ <MW_HOME>\user_projects\epmsystem1\DisclosureManagement\discman1\config\qmr_mappings.xml
§ All the files and folders from <MW_HOME>\user_projects\epmsystem1\DisclosureManagement\discman1\XbrlFiles except resources
d. Make sure that the following files are exactly the same across nodes specifically the proxy settings
§ <MW_HOME>\user_projects\epmsystem1\DisclosureManagement\discman1\lib\xbrlData.properties
e. Bring back all the DM nodes.
Copyright © 2015, Oracle and / or its affiliates. All rights reserved. http://www.oracle.com