Development Restricted
Release 11.1.2.4.000 Patch Set
Update (PSU): 11.1.2.4.257
Readme
This Readme file describes the defects fixed in this patch as well as the requirements and instructions for applying this patch to the Oracle® Hyperion Disclosure Management software.
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 Oracle® Hyperion Disclosure Management software installation 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 adds new files or 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.4.000; 11.1.2.4.100; 11.1.2.4.200; 11.1.2.4.225; 11.1.2.4.250; 11.1.2.4.253; 11.1.2.4.254; 11.1.2.4.255.
• Install Oracle’s Hyperion® Shared Services Release 11.1.2.4.000.
• Install Oracle® Hyperion Smart View, Fusion Edition release 11.1.2.5.216 or later.
The user applying this patch should be the same user who was configured 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 access 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 and 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 the following languages: English only.
|
Defect Fixed |
|
|
26844209 |
REFRESHING DOCLETS IN MASTER DOCUMENT GENERATES EXTRA ROWS/COLUMNS IN MASTER DOC |
|
27076577 |
VARIABLE VALUES ARE
CHANGING WHILE EXPORT AND IMPORT THE HDM REPORT |
|
26525497 |
DUPLICATE COLUMN
RENDERING FROM EXCEL DOCLET TO THE WORD REPORT |
|
26773199 |
ERROR "DOCLET
IS MISSING FROM ITS LOCATION...." WHEN REFRESHING |
This section includes important information about applying this patch for Oracle Hyperion Disclosure Management.
Before you begin the installation of this patch, back up your existing Oracle® Hyperion Disclosure Management database and associated files in case you need to restore your current installation.
Note: Typically the Disclosure Management installers are available in the following directory on the Web Server: <ServerDrive>/Oracle\Middleware\EpmSystem11R1\common\epmstatic. If the Web server is on a different server than the Oracle® Hyperion Disclosure Management server, ensure the Oracle® Hyperion Disclosure Management installers are also available on the Web server.
To apply this patch:
1. On the server hosting the Oracle® Hyperion Disclosure Management Service, shut down all services and servlet instances related to the Oracle® Hyperion EPM Release 11.1.2.4.000, 11.1.2.4.100, 11.1.2.4.200, 11.1.2.4.225, 11.1.2.4.250,11.1.2.4.253, 11.1.2.4.254, 11.1.2.4.255 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, 27111243.zip, to the <EPM_ORACLE_HOME>/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).
NOTE: 27111243.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 several database sql scripts needs to be performed only if upgrading from PS4 or PS4 PSU100. The scripts are located at <PATCH_DIRECTORY>\files\database\<dbtype>\ create_qmr.sql and 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 Oracle® Hyperion Disclosure Management add-in DiscManSetup.msi.
· Restart Microsoft Word or Excel. This will cause the Oracle® Hyperion Disclosure Management installer to run. Follow the installer's prompts.
· From the Oracle® Hyperion Disclosure Management About dialog box, ensure that the client version is updated to 11.1.2.4.257.
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. All users should clear cached files from their browsers.
To roll back a patch:
1. On the server hosting the Oracle® Hyperion Disclosure Management Service , shut down all services and servlet instances related to the Oracle® Hyperion EPM Release 11.1.2.4.257 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 27111243 -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 27111243 -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. The additional manual step of running two database sql scripts needs to be performed if rolling back to PS4 or PS4 PSU100. The scripts are located at <PATCH_DIRECTORY>\files\database\<dbtype>\ rollback_qmr_report.sql and drop_qmr.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 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.
Option of loading taxonomy manager
is not working in Oracle® Hyperion Disclosure Management
on Multi Node Environment. Is there a workaround?
Due to configuration files existing in the file system,
it is recommended that Oracle® Hyperion Disclosure Management
be running on a single node only.
If
using multiple nodes is still required by the client, please follow the
following procedureswhen registering taxonomy, FDM
files or uploading a new mapping file:
a. Bring down all
DM nodes except one.
b. Register the
taxonomy, upload mapping file, register FDM data files
as required.
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. We are having trouble trying to add Excel doclet to the Master Document, what is the possible workaround?
In the registry key of the client machine: HKEY_CURRENT_USER\Software\Oracle\Disclosure Management, create a string key called ”UseClipboard”. Then set this to ”True”.
Copyright ©
2016, Oracle and / or its affiliates.
All rights reserved. http://www.oracle.com