Oracle® Hyperion Data Relationship Management



Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Authors: EPM Information Development Team

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:


Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Table of Contents:


New Features

Installation Information

Supported Platforms

Supported Languages

Supported Paths to this Release

Defects Fixed in this Release

Known Issues

Documentation Updates

Accessibility Considerations


This document includes important, late-breaking information about this release of Oracle Hyperion Data Relationship Management. Review this Readme thoroughly before installing Data Relationship Management.

Special Note

The documentation for Data Relationship Management can be leveraged for use as the documentation for the following products:

  • Hyperion Data Relationship Steward

  • Hyperion Data Relationship Management for Customer Hub

  • Hyperion Data Relationship Management for Hyperion Enterprise Planning Suite

  • Hyperion Data Relationship Management for Hyperion Financial Close Suite

  • Hyperion Data Relationship Management Read Only Access

New Features

See the Oracle Hyperion Data Relationship Management New Features. For new features relating to installation, architecture, and deployment changes in this release, see "New Features" in the Oracle Enterprise Performance Management System Installation and Configuration Readme.

Installation Information

Late-breaking information about installation of Oracle Enterprise Performance Management System products is provided in the Oracle Enterprise Performance Management System Installation and Configuration Readme. Review this information thoroughly before installing EPM System products.

Supported Platforms

Information about system requirements and supported platforms for EPM System products is available in a spreadsheet format in the Oracle Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on the Oracle Technology Network (OTN):

Supported Languages

Information about supported languages for EPM System products is available in a spreadsheet format on the Translation Support tab in the Oracle Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on OTN:

Supported Paths to this Release

You can upgrade to EPM System Release from the following releases:

Note: For instructions to upgrade, see the Oracle Hyperion Data Relationship Management Installation Guide, “Upgrade a Data Relationship Management Installation” and the Oracle Enterprise Performance Management System Installation and Configuration Guide, "Upgrading EPM System Products."

Table 1. Table

Release Upgrade Path FromTo


11.1.1 – patch to or

9.3 – patch to 9.3.3

9.2 – patch to 9.2.1

A release earlier than Release 9.2

If you are upgrading from a release earlier than 9.2, you must first upgrade to a supported release and then upgrade to release For upgrade procedures for the earlier release, see the product installation guides for the interim release that you are upgrading to.

An environment that includes multiple releases, which can include an environment with one instance of Oracle Hyperion Shared Services or an environment with two instances of Oracle Hyperion Shared Services

See "Upgrading from an Environment with Multiple Releases" in the "Upgrading EPM System Products" chapter in the Oracle Enterprise Performance Management System Installation and Configuration Guide.

Defects Fixed in this Release

If you are coming from Release or, use the Defects Fixed Finder tool to review the list of defects fixed between those releases and Release This tool is available here:

  • 13650994 -- Extended European characters cause book exports to truncate

  • 13628440 -- The Create As-Of Version dialog prevents entering time in 24-hour format

  • 13614628 -- An error occurs if curly brackets ({}) or a pipe (|) special character are used in a failure message for a real-time validation

  • 13608491 -- Property query operators Contains and Not Contains are not working properly

  • 13596849 -- Batch Client parameters are case sensitive when using Oracle RDBMS as the repository

  • 13587039 -- ConcatWithDelimiter formula function limiting delimiter to a single byte

  • 13545190 -- Property category user access disappears after editing assigned properties

  • 13491776 -- Format formula function not working properly

  • 13447587 -- Date and DateTime values created during Daylight Savings Time (DST) are off by one day

  • 13428953 -- Database table RM_SESSION_INFO entries not displayed for running sessions

  • 13418416, 13376289 -- In Generation Export, only one column of ancestor section is exported

  • 13387765 -- When the "Combine Export Output" option is selected while running books, the export drops characters

  • 13376222 -- In Generation Export, the "Use Inverted Level" option does not work properly

  • 13375965 -- During repository upgrade, receive error "String was not recognized as a valid datetime"

  • 13250858 -- DRM Migration Utility cannot extract all metadata objects at one time

  • 13088403 -- Action Script actions are case sensitive

  • 13087951 -- In the Batch Client, the file specified in the PreFile name parameter is not found

  • 13082071 -- The use of a combined book file still creates individual export files

  • 13033951 -- List Values tab is greyed out when defining a ListGroup property type

  • 13025571 -- DRM stops responding when ReplaceStr formula function is used to replace same character or number

  • 12903376, 12903199 -- Difference Exports displays error "Value cannot be null" from Batch Client.

  • 12884172, 12863039 -- Validation is not working properly

  • 12795820 -- After searching, the Go button opens the hierarchy but does not jump to the relevant node

  • 12770014 -- In the Configuration Console, on the Running Processes tab for an application, clicking the Memory Usage column does not sort the column

  • 12426210 -- When a new user is created, the dot character (.) is ignored by the user interface

  • 12408742 -- Import converts long hyphen (em dash) to incorrect characters.

  • 12339931 -- Cannot download import error report with Internet Explorer if SSL is used

  • 11927731 -- DRM List functions in the property formula do not honor the node sort order

  • 9958018 -- Unable to save a data property when regional settings differ between client and server

  • 8459100 -- Request ability to migrate data from one version on one machine to another.

Known Issues

The following are the noteworthy known issues of this release:

  • 13895089 -- RangeList formula function is not working as expected.

  • 13889243 -- Core child list and descendant list properties only return the first 100 entries.

  • 13878259 -- Transaction history node find from list does not allow selection of highlighted node.

  • 13872956 -- Incomplete system error when blending both structure and properties separately.

  • 13861712 -- Real-time validations are unexpectedly executing when users perform validate assigned action.

  • 13849993 -- PropertyContainer was null or not found. Error when deleting a node with the hierarchy open.

  • 13830783 -- Invalid characters display between sections in combined Book output when using Unicode character encodings.

  • 13822426 -- Property formula referencing a global node with NodePropValue() function gets error.

  • 13804937 -- Function ReplaceStr() has issues with blank parameters and [openparen] and [closeparen].

  • 13804927 -- Database size copy issue.

  • 13800528 -- Blender is not copying some shared nodes.

  • 13791026 -- Export error received when include file contains duplicates.

  • 13789734 -- Node type property search displays “Specified node not found” error for an existing node.

  • 13781092 -- Data and log file required space estimate during upgrade are not consistent with final file sizes.

  • 13775285 -- Show all properties filter is not working.

  • 13743515 -- Generation export adds blank column to the end of the report.

  • 13737369 -- Authentication settings fail in non-English environment. Workaround: In Data Relationship Management Console, open Help menu, select Language, and then change language to English(US). Save the configuration and start the application.

  • 13683850 -- Performance issue with transaction reports after upgrade.

  • 13620567 -- Cannot connect using CSS external authentication; session times out.

  • 135825366, 13805190 -- Glyph refresh issues.

  • 13526005 -- Property list cannot be sorted.

  • 13496860 -- Export was unable to run due to the following error: incorrect syntax

  • 13477297 -- Upgrading existing database is five times larger than current database.

  • 13376145 -- Workflow user role and node access group are not working as expected.

  • 13081582 -- Saving an export book with a combined filename is not working properly.

  • 13035575 -- When you use the Batch Client to perform multiple exports and do not specify OutFile in the configuration file, the client uses the default filename from the first export for every export, with the result being that the file is overwritten multiple times.

  • 13000537 -- When running the console, server status icon shows Stop and Started repeatedly. When the console is restarted while the servers are running, the list of running processes and Windows Event Log do not load.

  • 12954278 -- Boolean values are migrated as false regardless of original value.

  • 12953026 -- Error received when logging into Data Relationship Management Web client after database connection is lost.

  • 12835031 -- In hierarchy import, shared nodes do not populate with the local properties.

  • 12825883 -- Getting “Commit outside of transaction” error.

  • 12708863 -- When Windows locale is set to German or French and a comma is used as the delimiter for imports or action scripts, an error may occur. Note that an error does not occur when using other delimiters.

  • 12658032 -- Equals formula function does not evaluate properly.

  • 12407805 -- AnnulNode() call is not working through API.

  • 11930385 -- Unable to set node property after triggering validation message.

  • 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-api-adapter.exe.config file, under the <system.serviceModel> section.

    Under <behaviors>, <endpointBehaviors> add a new behavior:

    <behavior name="httpBehavior">

    <dataContractSerializer maxItemsInObjectGraph="2147483647"/>


    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" bindingConfiguration="basicHttpConfiguration"

    contract = "Oracle.Drm.Interfaces.IAutomator"


    will become:

    <endpoint address = "Automator" name="IAutomatorMgr"

    binding="basicHttpBinding" behaviorConfiguration="httpBehavior"

    bindingConfiguration="basicHttpConfiguration" contract = "Oracle.Drm.Interfaces.IAutomator"


    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

  • 10202399 -- In Internet Explorer 7, when creating a new version or hierarchy, the tabs for selecting hierarchy, find nodes, and orphans remain on top of the box to add the version or hierarchy.

  • 10055031 -- Find nodes does not jump to the correct node if it is a shared node.

Documentation Updates

Accessing EPM System Product Documentation

The most recent version of each EPM System product guide is available for downloading or viewing from the EPM System Documentation area of the OTN Web site ( You can also use the Oracle Enterprise Performance Management System Documentation Portal (, which also links to EPM Supported Platform Matrices, My Oracle Support, and other information resources.

Deployment-related documentation is also available from the Oracle Software Delivery Cloud Web site (

Individual product guides are available for download on the Oracle Technology Network Web site only.

Copying and Pasting Code Snippets from PDFs

When you cut and paste code snippets from a PDF file, some characters can be lost during the paste operation, making the code snippet invalid. Workaround: Cut and paste from the HTML version of the document.

User's Guide Updates

When creating a Generation export, the Oracle Hyperion Data Relationship Management User's Guide states that a Generation export can be saved to a database table. This is incorrect. A Generation export can be saved only to a text file.

Administator's Guide Updates

Setting Data Relationship Management Transaction History Logging Levels

The following information should be included in the "Working with System Preferences" chapter of the Oracle Hyperion Data Relationship Management Administrator's Guide.

You must have application administrator privileges to set Data Relationship Management Transaction History logging levels. Set the TransactionLevels system preference to specify the action types to capture in the transaction history.

To set Transaction History logging levels:

  1. In the Data Relationship Management Web client, select Administer.

  2. Under Metadata, expand the System Preferences and edit the TransactionLevels preference.

  3. In TransactionLevels, select one or more transaction level types:

    • Logged Action records basic logging information, such as users logging in and logging out.

    • Core Action records actions that change the version, hierarchy, or node information, such as Add Node, Change Property, or Move Node.

    • Result Action records actions that result from core actions. For example, if the "clear all below core" action is performed, then properties are cleared from individual nodes. Clearing properties from the individual nodes is a result action.

    • Loss Action records loss of data due to a core action. For example, when a node is deleted, the defined properties for that node are deleted, which is a loss action. Loss actions are controlled by the LossLevel system preference.


      If the Loss Action is specified, or if the AllowAsOf system preference is turned on, then Core Actions are tracked, even if not set in the TransactionLevels system preference.

  4. Set the LossLevel preference:

    • Defined – Only values that are specifically set at the node are tracked when the node is deleted.

    • All Items – Derived, default, and inherited values are tracked in the LossAction.

  5. Stop and restart the application, or restart the Data Relationship Management service.

Loading or Viewing Large Files in the Migration Utility

The following information should be included in the Migrating Oracle Hyperion Data Relationship Management Metadata chapter of the Oracle Hyperion Data Relationship Management Administrator's Guide.

When loading or viewing a large file using the Migration Utility, the following error may occur:

Unexpected Error There was an unexpected error trying to process your request: Maximum request length exceeded.

This error occurs because the default limit for uploaded files is 4 MB. To change the default limit to 20 MB, add this setting within the <system.web> element of the web.config file:

<httpRuntime maxRequestLength="20480" executionTimeout="3600" />


By default, the web.config file is located in C:\Oracle\Middleware\EPMSystem11R1\products\DataRelationshipManagement\client\migration-client.

For information on changing configuration of the Migration Utility, see “Configuring the Migration Utility” in the Oracle Hyperion Data Relationship Management Installation Guide.

Accessibility Considerations

This Readme file is accessible in HTML format.