Oracle Data Relationship Management
Release 11.1.2.3.000 Patch Set Update (PSU): 11.1.2.3.700
Readme
Apply this patch to use Internet Explorer release 11 in standards mode. After you apply this patch, you can no longer use Internet Explorer Enterprise Mode.
This Readme file describes the defects fixed in this patch and the requirements and instructions for applying this patch.
Caution: Oracle urges you 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 service interruptions, loss of data, or both.
If this patch will replace an existing 11.1.2.3.50x installation, related components such as Hyperion Foundation Services are not affected. However, upgrading from a release prior to 11.1.2.3.500 will require an upgrade of Foundation Services to 11.1.2.3.700.
This is the eleventh patch on the 11.1.2.3.000 release and is cumulative of all previous patches.
You can apply this patch to the following Data Relationship Management releases:
Release Upgrade Path From |
To |
Release 11.1.2.x |
Release 11.1.2.3.700 |
Release 11.1.1.4.x |
Release 11.1.2.3.700 |
Release 11.1.1.0.x to 11.1.1.2.x |
Release 11.1.2.3.700 |
An environment that includes multiple releases, which can include an environment with one instance of Shared Services or an environment with two instances of Shared Services |
See “Upgrading from an Environment with Multiple Releases” in the "Upgrading EPM System Products" chapter in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide. |
If you are starting from an earlier release, Oracle recommends that you upgrade to the highest level release that directly supports upgrade from your starting release.
Use the user account that has Local administrator rights and was set up for installation and configuration. This user must be an administrator and should be the same for all EPM System products installed on the machine. This Windows user requires the following local policies to be assigned:
· Act as part of the operating system
· Bypass traverse checking
· Log on as a batch job
· Log on as a service
To ensure proper performance, it is strongly recommended that Windows pagefile size on the DRM server be at least 1.5 times system memory with growth allowed up to 2.0 times system memory. When system memory is large (e.g. 64 GB and higher) the pagefile can be between 1.0 and 1.5 times system memory. Pagefile sizes smaller than this can lead to serious performance and functional issues.
Applies to all supported platforms.
Applies to all supported languages.
The following are the noteworthy known issues of this patch.
Description |
|
•21095350 |
When using IE11, create user task gets hung when click on property category tab. |
•20898876 |
When using IE11 and creating a workflow model, the hierarchy group property filter cannot be cleared. |
•19206763 |
Recent versions of McAfee On-access Virus Scanner can cause a problem by making the DRM web application believe that files have been updated and that the web application must be restarted. As a result of this, users of the web client can often have their sessions closed prematurely. The workaround to prevent this involves updating the Windows registry and adding the following DWORD: HKLM\Software\Microsoft\ASP.NET\FCNMode Set the value of FCNMode to 1 and then restart IIS. |
•18353358 |
The following inconsistency can be observed when filtering on Transaction History. When the user specifies either a node, a hierarchy and node, or a version, hierarchy and node and does NOT specify the "Include Children" option, the query uses node name so the result will include transactions for any instances of a node with the given name even if the Node ID is different. However, if the "Include Children" option is selected, then the query uses the specific Node ID and the result will not include other node instances with the same name. |
•18154631 |
The DRM installer will attempt to download and install .NET 4.0 if it is not already present. However, if the installer cannot access the internet, it will continue to wait. |
•18097151 |
In DRM Console, the page for Scheduled Tasks is only available for English language. |
•18055588 |
If database password contains the @ character, then the Apply Updates operation on a repository will get error: DRM-11035: The connection string format is incorrect. |
•18051924 |
When hierarchy is set to View By certain non-English characters and the hierarchy is downloaded to PDF/RTF/XLS, the downloaded files do not display the non-English characters correctly. |
•18051299 |
When browser language is set to French, and action script is run that generates the warning message "Script has completed processing but some rows have failures," the message contains a character displayed incorrectly. |
•18042609 |
In some cases when using Internet Explorer, an Import instance tab cannot be closed after the import is run. Must stop and restart browser to resolve. |
•17883800 |
When loading a file via the Migration Utility, the File Checksum will display "Not Found; file may have been modified!" even when the file has not been modified. |
•16828903 |
After installing and starting DRM,
opening web client gets |
•16769872 |
After starting DRM service and accessing web client, get error: "There are currently no applications
available for login. In IIS, may need to change the DRM_POOL application pool to use the Local System account or local admin account instead of the Network Service account. |
•16339614 |
In certain environments using an Oracle repository, performance for operations such as saving versions can be degraded over previous releases. This appears to be limited to very specific configurations. |
•13889243 |
Core child list and descendant list properties only return the first 100 entries. |
•13789734 |
Node type property search displays “Specified node not found” error for an existing node. |
•13376145 |
Workflow Development Kit (WDK) requires Data Manager role access instead of just Workflow role access. |
•11905795 |
Error occurs when attempting to process a query from a Java application through Web Services. This issue happens in the drm-api-adapter when it attempts to serialize the objects as SOAP to feed to the Java web service. To work around this issue, edit the drm-apiadapter.exe.config file, under the <system.serviceModel> section. Under <behaviors>, <endpointBehaviors> add a new behavior: <behavior name="httpBehavior"> <dataContractSerializer maxItemsInObjectGraph="2147483647"/> </behavior> Apply this new httpBehavior to all the http endpoints, located under <services>, <service name="Oracle.Drm.APIAdapter" ...> by adding the behaviorConfiguration="httpBehavior" attribute. For example: <endpoint address = "Automator" name="IAutomatorMgr" binding="basicHttpBinding" contract = "Oracle.Drm.Interfaces.IAutomator" bindingNamespace="http://www.oracle.com/drm/"/> will become: <endpoint address = "Automator" name="IAutomatorMgr" binding="basicHttpBinding" behaviorConfiguration="httpBehavior" bindingConfiguration="basicHttpConfiguration" contract = "Oracle.Drm.Interfaces.IAutomator" bindingNamespace="http://www.oracle.com/drm/"/> This attribute must be inserted on all of the endpoint elements. |
•11668780 |
After upgrade, no way to view version type for Translog export with As-Of version |
•10648984 |
Console gets "Database does not exist" error when database name contains @ symbol |
•10648889 |
Console gets "Operation failed" error when database name contains dot operator |
•10647639 |
After upgrade, Admin password not reset to value entered during configuration |
To apply this patch:
1. Perform a backup on the databases for any existing Data Relationship Management applications.
2. Save a backup copy of the drm-config.xml file found in the .\DataRelationshipManagement\server\config directory.
3. Uninstall the existing 11.1.2.3 release:
a. Stop the Data Relationship Management service.
b. Verify all processes are shut down.
c. Run the installer from that release and choose the Remove option.
4. Run the new setup.exe to install this patch.
5. If a multiple-machine configuration is being used, repeat the uninstall and install steps above for each machine.
6. In the Configuration Console on the application controller machine, select Application, then Apply Updates for all existing applications.
7. Make sure to save any configuration changes made in the Data Relationship Management Console.
8. Start the Data Relationship Management service.
Optional: Redeploy the Data Relationship Management Web service application (oracle-epm-drm-webservices.ear) to Oracle Weblogic. The oracle-epm-drm-webservices.ear file is located in the %EPM_ORACLE_HOME%\products\DataRelationshipManagement\api directory.
This step is only required if applying this patch to an 11.1.2.3.000 installation where the Web service application has been previously deployed. See the “Redeploying a Web Services Application” section in the Oracle® Fusion Middleware Security and Administrator's Guide for Web Services for instructions to redeploy using Oracle Enterprise Manager.
To roll back this patch:
1. For each machine where Data Relationship Management is installed, run setup.exe and choose the Remove option.
2. Restore the databases for any existing Oracle® Data Relationship Management applications from the backup files created during step 1 of Applying This Patch.
3. Restore the saved backup of the drm-config.xml file to the .\DataRelationshipManagement\server\config directory.
4. If the oracle-epm-drm-webservices.ear package from this patch was deployed on Oracle Weblogic, the oracle-epm-drm-webservices application deployment should be undeployed.
5. Reinstall the previous release.
See the “Undeploying a Web Services Application” section in the Oracle® Fusion Middleware Security and Administrator's Guide for Web Services for instructions to undeploy using Oracle Enterprise Manager.
Copyright © 2015, Oracle and / or its affiliates. All rights reserved. http://www.oracle.com