Oracle Hyperion Data Relationship Management

 

Release 11.1.2.2.000 Patch Set Update (PSU): 11.1.2.2.311

Readme

About this Patch. 1

Patch Type. 2

Supported Paths to this Patch. 2

Prerequisites. 3

Required User Rights. 3

Supported Platforms. 3

Supported Languages. 3

Defects Fixed in this Patch. 3

Defects Fixed in Patch 11.1.2.2.310. 4

Defects Fixed in Patch 11.1.2.2.309. 4

Defects Fixed in Patch 11.1.2.2.308. 5

Defects Fixed in Patch 11.1.2.2.307. 6

Defects Fixed in Patch 11.1.2.2.306. 7

Defects Fixed in Patch 11.1.2.2.305. 7

Defects Fixed in Patch 11.1.2.2.304. 8

Defects Fixed in Patch 11.1.2.2.303. 9

Defects Fixed in Patch 11.1.2.2.302. 9

Defects Fixed in Patch 11.1.2.2.301. 10

Defects Fixed in Patch 11.1.2.2.300. 12

Known Issues in this Patch. 15

Applying this Patch. 17

Rolling Back this Patch. 17

About this Patch

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.

FIPS Algorithm Policy

When enabling FIPS Algorithm Policy on the DRM Web Servers where ASP.NET 2.0 is used, the application-level Web.config file for DRM client applications must be edited to enable the correct encryption algorithm for view state data.  This step must be performed each time a new patch is installed.

1.    In a text editor, open the application-level Web.config file.

2.    Locate the <system.web> section.

3.    Add the following line to the <system.web> section:

4.    <machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>

5.    Save the Web.config file.

6.    Restart the Microsoft Internet Information Services (IIS) service.  This can be done by running the following command at a command prompt:  iisreset

See Microsoft Knowledge Base article 911722 for additional background on selecting application view state data encryption algorithms with FIPSAlgorithmPolicy set to Enabled.

Patch Type

This Patch Set Update (PSU) requires a full installation. This patch can be installed on a new machine or replace an existing installation.

If this patch will replace an existing 11.1.2.2 installation, related components such as Hyperion Foundation Services are not affected.

This is the twelfth patch on the 11.1.2.2.00 release and is cumulative of all previous patches. 

Supported Paths to this Patch

You can apply this patch to the following releases:

Release Upgrade Path From

To

11.1.2.x

11.1.2.2.311

11.1.1 – patch to 11.1.1.2 or 11.1.1.4

11.1.2.2.311

9.3 – patch to 9.3.3

11.1.2.2.311

9.2 – patch to 9.2.1

11.1.2.2.311

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 11.1.2.2.311. 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 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.

Notes:    

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.

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:

Windows:

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

Supported Platforms

Applies to all supported platforms.

Supported Languages

Applies to all supported languages.

Defects Fixed in this Patch

Defect Number

Defect Fixed

•18253333

When creating a Hierarchy export and selecting the Tabbed Output option, each row of output should be indented by a number of Tabs based on the level of the node to be consistent with the behaviour in releases prior to 11.1.2.

•18646601, 20054859

Running a script created from Node Model gets error: "Object reference not set to an instance of an object"

•18886868

Certain export types are not applying the Node Selection setting correctly (All Nodes, Limb Nodes Only, Leaf Nodes Only)

•18998289

Restoring a version backup file that contains shared nodes gets error:  "Nullable object must have a value."

•19589756, 19670722

External user account is sometimes unable to login. Probable cause is certain API calls that do not cleanup their sessions.

•19866862

When a node is moved to a new parent, Loss transactions are logged for each hierarchy where the node exists.  However, Loss transactions should only be logged for each hierarchy where the node has the same parent as the original hierarchy.

•19987158

Operation "Clear All Below" is getting incorrectly logged in transaction history as "Remove Duplicates"

•20081340

Web applications should be compiled in Release mode.

•20129119

Description column for Hierarchy Groups not populated on the Browse page.

Defects Fixed in Patch 11.1.2.2.310

Defect Number

Defect Fixed

•17859864

When FIPS Algorithm Policy is enabled on the DRM web server, attempting to run a migration utility extract will get error:  DRM-29005: error exporting objects to memory

•17883779, 17891759, 17897100

When running a Generation Export using fixed width output, the pad character and justification specified for each column were not being correctly applied.

Defects Fixed in Patch 11.1.2.2.309

Defect Number

Defect Fixed

•16487591

Anonymous user can change user properties which affect other users using same anonymous profile.

•16930498

Some URLs not being properly constructed based on values configured for Web Farm Hostname and Port Number.

•16998532

The DRM implementation of cryptographic service providers should be updated to be aligned with Federal Information Processing Standards (FIPS-140) to allow FIPSAlgorithmPolicy to be set to Enabled. 

When enabling FIPS Algorithm Policy on the DRM Web Servers where ASP.NET 2.0 is used, the application-level Web.config file for DRM client applications must be edited as follows to enable the correct encryption algorithm for view state data.

 

1. In a text editor, open the application-level Web.config file.

2. Locate the <system.web> section.

3. Add the following line to the <system.web> section:

<machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>

4. Save the Web.config file.

5. Restart the Microsoft Internet Information Services (IIS) service. To do this, run the following command at a command prompt:  iisreset

 

See Microsoft Knowledge Base article 911722 for additional background on selecting application view state data encryption algorithms with FIPSAlgorithmPolicy set to Enabled.

•17334496

For node names containing caret (^) where shared node maintenance is enabled, properties incorrectly display as read-only.

•17419732

Formula function Pos() returns 1 instead of 0 when search string is empty.

•17695360

When Shared Node Delimiter is the same as the Domain delimiter, an error could occur.

•17799706

For property values longer than 32K, values could be truncated after importing and saving the version with Oracle database.

Defects Fixed in Patch 11.1.2.2.308

Defect Number

Defect Fixed

•14642098

Access assigned via global node access group is lost after restarting application.

•14705731

Downloading hierarchy compare results using Internet Explorer and SSL gets error.

•15961441, 16822231

Saving version that was restored from file gets error due to shared nodes.

•16343391

GlobalPropLocalSecurity system preference not functioning correctly.

•16445885

Timestamps for As-Of version incorrect when client and server in different timezones.

•16455769

Action script file not loaded correctly when line contains a lone double quote.

•16478368

Node name containing caret character does not display correctly when also using shared nodes.

•16835420

Repository upgrade process not correctly handling legacy properties using Inverted Level deriver.

•16843405

When exporting to database table that contains a space in the table name, can get error: DRM-23081: Export was unable to run.

•16874690

For legacy request data upgraded to 11.1.2.0 and then later release, property names are missing from request items.

•16925323

EPMA export missing some of the properties that should be included.

•16954840

When exporting to database table, empty string values are getting exported as NULL in SQL Server although earlier releases exported them as empty string.

•16964073

Change made to prevent null reference when trying to close invalid session.

•16991845

When the arguments for function NodePropValue() were a node in current version but not in current hierarchy and a version level property, the function was not returning the value of the version level property.

Defects Fixed in Patch 11.1.2.2.307

Defect Number

Defect Fixed

•15893400

When importing data to EPMA from DRM via the API, a custom inclusion filter was not being applied and thus all nodes were being imported.

•16524331

Running multiple, concurrent exports via batch client can sometimes receive error: The inactivity timeout of (00:01:00) has been exceeded.

•15850818, 16537507, 16537516

Operations such as loading, saving, copying or blending on large versions can make DRM appear unresponsive.

•16621349

When running a Difference Export and checking for property differences, any additional columns selected were not getting included in the output for this section.

•16733767

Exporting to SQL Server table could get error if column names contained lower case characters.

•16774646

Stored procedure USP_WFCLAIMREQUEST is not used but can cause compilation error when running DRM database scripts manually.

Defects Fixed in Patch 11.1.2.2.306

Defect Number

Defect Fixed

•16342958

DRM service may be unresponsive when loading very large versions.

•16396429

When running simultaneous batch client processes, some may not complete successfully.

•16426874, 16487848

Exporting large data set to database table using Fast Appends option can get error: DRM-23081:…OracleParameter object is
already contained in a collection

•16431917

Excess memory usage when running large action scripts.

•16439551

Large export job can get error: The inactivity timeout of (00:01:00) has been exceeded

•16446624

Version loaded via batch client operation does not automatically get loaded for web client.

•16498815

When exporting to database table, the column lengths can now be specified.  However, this required manually updating some existing exports that used non-string fields.  Otherwise, would get error DRM-23081:…Length cannot be less than zero.

•16538145

Formula function Equals() is not case-sensitive.  Although other comparisons in the system are case insensitive, the Equals() function should be case-sensitive.

Defects Fixed in Patch 11.1.2.2.305

Defect Number

Defect Fixed

•14466917

XML export tags should not include namespace label.

Previous format:

<Property name="Name [Core]">A1111</Property>

New format:

<Property name="Name">A1111</Property>

•14710607, 16291407, 16099092

When exporting to database table, the column size should be displayed, editable and used to determine field width when exporting.

•14840824

DRM configured with Single Sign On is not allowing login.

•16028824, 16057259

Export does not use option to remove duplicates based on key when target is database table.

•16080967

Action script performance issue when using certain validations and node access groups.

•16086084

During repository copy, large formula strings could be truncated in target.

•16210722

Export to database table gets error when some columns not mapped and columns are defined not nullable. (Previously, any columns in the target table that were not mapped to a property in the export would be populated with an empty string.  With this fix, the unmapped columns will now be populated with NULL.)

•16241464

Export does not use option to pivot on column when target is database table.

•16242067

XML export handling of version and hierarchy level properties.  The following changes have been made.

1. Version/Hierarchy level properties are now listed just once at the Version/Hierarchy level instead of being repeated.

2. File header changed from:

<MDMMetadata xmlns="http://www.w3.org/2001/XMLSchema-instance">

<Versions xmlns="">

to:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<MDMMetadata>
<Versions>

 

•16270719

Export to database table does not Clear Based on Version ID.

•16297708

External connection may not retrieve all tables to which user has access.

•16319761

Unexpected error during version save can leave the version marked as Connected but not yet saved.

•16388633

Function NodeAccessGroups() now returns global access groups before local access groups.

Defects Fixed in Patch 11.1.2.2.304

Defect Number

Defect Fixed

•14155292

Running large action script via batch can fail with error:  "The maximum retry count has been exceeded."

•14360313

Running action script can cause high CPU usage on DRM engines and adversely affect other processes.  This patch includes some initial performance enhancements.

•15898259

Exporting to Oracle database table can get intermittent error: "DRM-23081: Export was unable to run due to the following error: Connection request timed out."

•15992704

Certain step in the repository upgrade process for release 11.1.2.0 is redundant with step done in later release.  This step is being removed to improve upgrade performance.

•16000203

Applying updates to a 11.1.2.0 repository can get error: "No contexts of type Update exist in the current scope."

 

 

Defects Fixed in Patch 11.1.2.2.303

Defect Number

Defect Fixed

•14345835

Formula function IsAlpha() evaluates empty string as False whereas in previous release it returned True.

•14595328

Entering invalid password for Oracle repository in the console can cause the user to be incorrectly locked out.

•14629417, 14752548

Book containing export with validations can report incorrect failures from the validations.

•14685539

During Oracle bulk copy operations, error messages may display incorrectly as "Index (zero based) must be greater than or equal to zero and less than the size of the argument list" instead of showing the actual error.

•14698495

When adding a node while scrolled down on a large hierarchy, the focus will shift back to the top of the page instead of staying on the currently selected node. Only affects IE browser.

•14706701, 14740431

In the Repository Wizard when using the option to Generate SQL Scripts, clicking the Back button on the Repository Creation Script page can generate error:  ORA-12560: TNS:protocol adapter error

•14706892

In the Repository Wizard when using the option to Generate SQL Scripts and entering lowercase tablespace names, can get error: ORA-12560: TNS:protocol adapter error

•14713070

When upgrading to Oracle repository and datafiles are not allowed to autoextend, the error is not properly reported.

•14713286

Upgrade script for 11.1.2.1 may attempt to rollback after already committed if error is encountered

•14756128

Loading versions can cause DRM to become unresponsive

•14775183, 14775196

Transaction audit not working correctly when node and hierarchy specified without version

•14775576, 14786549

Upgrade fails with error: "Input string was not in a correct format"

•14803932

Upgrade can get error "Table or view does not exist" if specified user does not have DBA rights.

Defects Fixed in Patch 11.1.2.2.302

Defect Number

Defect Fixed

•14389535

Transaction Log export via batch client uses Default Current Version instead of version specified in batch client file.

•14484549

Upgrading a database where a table name exists in more than one schema can get error "key already exists" error

•14493988

Migration client gets unhandled exception error when browser set to Norwegian Language options.

•14499310

In certain cases it is valid for global properties to reference local properties and some of these cases were being incorrectly reported as invalid.

•14503336, 14524599

FormattedDate() formula function issues with format "mm" for minutes and AM/PM for times in 12 o'clock hour.

•14520930

Node glyphs not displayed for shared nodes when node types are enabled.

•14521318

Upgrading a database where tables in the repository are partitioned can cause an error in the analysis phase.

•14526313

Functions AncestorProp() and AscNodeProp() can get object reference error when nested inside other functions.

•14527410

Generation export exclusion filter should only exclude ancestors and not bottom nodes.

•14533681

Creating database export connection via OLEDB can get "key already exists" error.

•14546712

Columns may be set as read-only when retrieving table via OLEDB.

•14558259

Export using Bottom Level property to repeat nodes gets error.

•14562870, 13035575

Batch client export with no /outfile parameter overwrites previous output path.

Defects Fixed in Patch 11.1.2.2.301

Defect Number

Defect Fixed

• 10202399

Using IE7, Find and Orphans tabs appear on top of dialog boxes

• 11930385

Unable to set node property after triggering validation message

• 12399803

Export fixed width pad character not included in results

• 12407805

API AnnulNode method not working correctly

• 12835031

Imported shared nodes not populated with local property values

• 12953026

Error logging in to client after database connection lost: DRM-28017 or DRM-61025

• 12954278 

Extended Boolean values all get migrated as False

• 13706662

Export to database table fails if target contains identity column

• 13714592

Shared node gets copied to different version as a shared node instead of regular node

• 13721031

Adding property to blender can get error: specified cast is not valid

• 13725628

Import can be copied with duplicate name

• 13775285

Show All properties filter not working correctly

• 13873381

Slow performance when loading script file

• 13878259

Transaction History node find from pick list not allowing selection

• 13929458

Repository wizard analysis reporting false invalids

• 14003463

RangeList property control not working as expected in client

• 14008410

Validations at Move/Remove/Merge level not firing in real-time

• 14022493

User login at API adapter affects locked accounts

• 14037312

API AddUser method missing Exclude From Lockout parameter

• 14043172

Unable to execute the API user lockout method

• 14055418

Merge node information not logged in transaction history

• 14066141

Performance issue with transaction reports after upgrade

• 14086214

Viewing related shared nodes gets error: Item with the same key already exists

• 14087555

API GetQueryNames gets null exception error

• 14091669

API GetQuery always returns UserDefined param as False

• 14113787

Generation export not handling Quoted Strings correctly

• 14113805

Book containing more than 64 exports gets error

• 14128268

Node approval not working correctly

• 14148094

Formula with additional Concat() function gets error

• 14155292

Large action script via batch client gets error: Maximum retry count exceeded

• 14158170

Unable to add domain node via API AddNode

• 14158480

Editing external connection for database gets error

• 14159363

Generation export not handling exclusion filter

• 14181088

Request engine not locking version during validation and roll back

• 14182390

Legacy node props data with spaces in list not handled correctly during upgrade

• 14192984

Export description column is too wide

• 14222210

Export pivot property on column not working correctly

• 14222298

External connection for database with large number of tables gets error

• 14222396

During blend, hierarchy property is copied although not selected

• 14233438

Stranded baseline version prevents non-Data Manager users from client login

• 14239095

Import saved with non-standard version variable gets error

• 14239743

Shared nodes not populated with Primary Node Descendants list

• 14261877

Request processing slow at API

• 14293140

Blend returned error after running action script

• 14301608

API export using include file not working correctly

• 14303954

Version column D_LEGACY_COPY_TIMESTAMP not populated

• 14304001

UI issue adding nodes to AscNodes property

• 14305900

10 concurrent node search attempts can halt server

• 14306075

Editing Lookup values on property grid gets permission error

• 14311957

Script checkbox does not enable after substituting version

• 14312139

Script gets "index out of range" error after changing column order

• 14342302

Removing version from version variable gets error

• 14344074

Intermittent error when accessing client login page

• 14360407

DRM opening too many database connections

• 14372456

Heavy load on Request API and long-running import can cause server to halt

 

Defects Fixed in Patch 11.1.2.2.300

Defect Number

Defect Fixed

• 12703155

Performance issues regarding dependency checking

• 13031853

During version backup, no warning occurs if metadata is skipped during restore

• 13081582

When export book is saved with a combined filename, cannot change the file name and save the book

• 13526005

Property list cannot be sorted

• 13554056

Slow performance by database analysis space usage query

• 13647164

Inherited validation is not assigned in grid for descendants of domain node

• 13652082

Property definition of the Associated Group data type does not have domain control

• 13718193

In Compare, put nodes “Use these settings as default” option is not working

• 13733024

In Administer, unable to remove or type over the default name for a new node access group

• 13733165

Errors in event log when unloading an unsaved version

• 13733921

Object reference error when using domain validations with domain and non-domain nodes

• 13733963

Export validations are not saved/copied with the EPMA export type

• 13734142

“Property container was null or not found” error after deleting a node

• 13737369

Internal and mixed mode authentication fail in non-English environment

• 13740383

In Import, “Index out of range” error occurs when you navigate to and from the columns tab

• 13740418

In Import, unable to deselect domain column selection value on domain options tab

• 13740483

In Migration Utility, issues with HTML report for domain attributes of imports and blenders

• 13740602

UI issues with new node dialog box when domain is assigned to a version

• 13743515

Generation export adds blank column in the end of the export

• 13780244 

In Browse, unable to create a new hierarchy with a domain top node

• 13780531

Upgrading database from 11.1.2.1 gets error “Enum description ‘Add’ not found”

• 13781082

SQL Server log file (.LDF) very larger after upgrade

• 13781092

Data/log file space requirement estimate not consistent with final file sizes

• 13781497

“Insufficient memory to continue” error when upgrading to Oracle on a Win32 computer

• 13789289

When deleting a version that has had As-Of versions created, engine errors occur

• 13791012

User with data creator role cannot change the version status property from working to submitted or from submitted to finalized even though the user is the version owner

• 13791026

When running an export, this error displays “Export was unable to run due to the following error: An item with the same key has already been added”

• 13794924

In Import, domain name qualification is not working for some node data type properties

• 13800528

Blender not copying some shared nodes

• 13804937

Blank parameters in ReplaceStr formula function cause issues

• 13815675

“Incorrect number of parameters supplied” error occurs for each API call

• 13820493

In API, setVersionVariable() method is not working

• 13821702

Import using [Ignore Column] in Hierarchy Node section gets object reference error

• 13822426

Referencing global node with NodePropValue function causes object reference error

• 13825366

Glyph refresh issues

• 13826404

When AddUser is called from the public API, if the LockoutDateTime filed is not set, the DateTime value is reported as invalid because Timezone Kind is not set and server hangs

• 13830102

Input arguments not passed correctly when drm-update-manager restarts itself after updating configuration on the first run when “Apply Updates” is used in the console.

• 13830524

ReplaceStr() formula function not correctly handling [openparen] and [closeparen]

• 13830783

In export book, invalid characters in combined output for Unicode character endcodings

• 13831070 

Error “Buffer too small” displayed during database analysis of an Oracle schema

• 13840927

In Import, when Map By Column domain name qualification method is selected, name not qualified for domain in Hierarchy Node section

• 13851125 

When creating a repository with scripts, Admin User must use a hardcoded default password

• 13861712

Real-time validation unexpectedly executing when Validate Assigned action is executed

• 13867084

In upgrade, snapshot data model specifies RM-REQUEST.C_COMMENT as a large object

• 13871437 

Upgrade of 11.1.2.0.x database fails during request updates

• 13875125 

Alias property for node gets assigned as node name by default

• 13880293

In the console menu, under Help, Application Tree Legend menu, the Japanese character is truncated

• 13887591

In the API, method to copy node across versions is not implemented

• 13897075

Hierarchy type property needs blank value for Essbase property

• 13901373

Alias property is missing for the generic hierarchy node property for Planning

• 13905103

Support for profiling formula performance

• 13905568 

HasChildWith() formula function only returns True when first child has a True value.

• 13941861

Incomplete system error when separately blending both structure and properties

• 13941874 

Hierarchy blends return an incomplete system error status

• 13972329

ReplaceStr does not work properly to replace a period

 


 


 


 


 


 

 

Known Issues in this Patch

The following issues are the noteworthy known issues of this patch.  

Defect Number

Description

• 17883800

When FIPS Algorithm Policy is enabled on the DRM web server, and a file is loaded via migration utility, the File Checksum will display "Not Found; file may have been modified!"  This message does not the affect the ability to load the file properly.

• 17777252

Field labels on Configuration Console may disappear after completing the Repository Wizard.  Restarting Console will restore the labels.  Issue has been resolved in the 11.1.2.3 release line. 

• 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.

• 13620567

Cannot connect using CSS external authentication using Support Groups option; session times out.

• 13496860

Export was unable to run targeting table in EPMA schema due to the following error: incorrect syntax

• 13376145

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

• 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.

• 12658032

Equals formula function does not evaluate properly for mismatched parentheses.

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

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

 


 

Applying this Patch

The section includes important information about applying this patch for Oracle Hyperion Data Relationship Management. Follow this procedure to replace an existing 11.1.2.2 installation. Refer to the Oracle Hyperion Data Relationship Management Installation Guide for instructions for new installations or upgrades from previous releases.

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.2 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.2.000 or 11.1.2.2.300 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.

Rolling Back this Patch

To roll back a 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® Hyperion 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.