Oracle Data Relationship Management

Release 11.1.2.4.000 Patch Set Update (PSU): 11.1.2.4.340

Readme

About this Patch. 1

Patch Type. 2

Supported Paths to this Patch. 2

Prerequisites. 2

New User Privileges for Oracle Repository. 2

Required User Rights. 3

Memory Configuration. 3

Enterprise Performance Management Architect Patch. 3

Supported Platforms. 3

Supported Languages. 3

New Features in this Patch. 4

Common User Provisioning. 4

Integration with Financial Data Quality Management 4

Hyperlinks in Workflow Instructions. 4

Enhanced Find for Implicit Shared Nodes. 4

Exclude Shared Nodes for Unique Property Validations. 4

Defects Fixed in this Patch. 4

Defects Fixed in Patch 11.1.2.4.330. 6

Defects Fixed in Patch 11.1.2.4.321. 8

Defects Fixed in Patch 11.1.2.4.320. 8

Defects Fixed in Patch 11.1.2.4.311. 10

Defects Fixed in Patch 11.1.2.4.310. 10

Defects Fixed in Patch 11.1.2.4.302. 12

Defects Fixed in Patch 11.1.2.4.301. 12

Known Issues in this Patch. 14

Applying this Patch for Data Relationship Management 16

Applying this Patch for Data Relationship Management Analytics. 16

Rolling Back this Patch for Data Relationship Management 17

Rolling Back this Patch for Data Relationship Management Analytics. 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.

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.4.x installation, related components such as Hyperion Foundation Services are not affected.  However, upgrading from a release prior to 11.1.2.4.x will require an upgrade of Foundation Services to 11.1.2.4.

This is the eighth patch on the 11.1.2.4.000 release.

Supported Paths to this Patch

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

Release 11.1.1.4.x

Release 11.1.2.4.340

Release 11.1.1.0.x to 11.1.1.2.x

Release 11.1.2.4.340

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.

For supported upgrade paths for Foundation Services and other EPM System Products, see Oracle Enterprise Performance Management System Readme.

 

Prerequisites

New User Privileges for Oracle Repository

When upgrading from a Data Relationship Management release prior to 11.1.2.4.330, additional database privileges are required to use release 11.1.2.4.340 with an Oracle repository.  Before running the Apply Updates process on the repository, the existing schema owner must be granted two additional privileges:
GRANT CREATE TYPE, CREATE SEQUENCE TO <user>;

This step is not required when upgrading from 11.1.2.4.330 or when creating a new Oracle repository since these privileges will be automatically applied to the new user.  This step is also not required when using a SQL Server repository.

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

The Oracle Data Relationship Management installer should be "Run As Administrator" in order to execute properly.

Memory Configuration

To ensure proper performance, it is strongly recommended that Windows pagefile size on the DRM server be at least 1.1 times system memory with growth allowed up to 1.5 times system memory.  When system memory is large (e.g. 64 GB and higher) the pagefile can be maintained at 1.1 times system memory.  Pagefile sizes smaller than this can lead to serious performance and functional issues.

Enterprise Performance Management Architect Patch

In order to successfully integrate Data Relationship Management and Enterprise Performance Management Architect, the following patch must be applied:  Oracle Enterprise Performance Management Architect, Fusion Edition Release 11.1.2.4.000 Patch Set Exception (PSE) 22078964.

Supported Platforms

Applies to all supported platforms.  When using Data Relationship Management Analytics with Oracle Database 11.2.x, the minimum patch level required is 11.2.0.4.

Supported Languages

This patch can be applied to all languages supported in release 11.1.2.4.320 of Oracle Data Relationship Management. For the Oracle Enterprise Performance Management System Supported Platform Matrix, go to: http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html.


 

New Features in this Patch

Common User Provisioning

Data Relationship Management supports the provisioning of users and groups in external user directories such as LDAP and Microsoft Active Directory using Hyperion Shared Services. Users and groups defined in these directories can be provisioned with user roles to Data Relationship Management applications registered with Shared Services.  Provisioned user groups in Shared Services can be mapped to node access groups and property categories to automatically manage user membership.  Common user provisioning is optionally available for Data Relationship Management applications using Shared Services for external user authentication.

Integration with Financial Data Quality Management

A packaged integration with Oracle Hyperion Financial Data Quality Management, Enterprise Edition is available to use Data Relationship Management to manage dimension member mappings between ERP source systems and EPM target applications supported by FDMEE.  Refer to the Data Relationship Management EPM Integration Guide for more information on setup and usage of this integration.

Hyperlinks in Workflow Instructions

Workflow model descriptions and workflow task instructions permit the use of custom hyperlinks to related web resources to guide users participating in a Data Relationship Governance request.  Governance users can view these links on the Request page of the Web Client and navigate to the target web resources as directed.

Enhanced Find for Implicit Shared Nodes

The Find feature available on the Browse Hierarchy page of the Web Client provides an option to include Implicit Shared Nodes as part of the find results.  This option may be used to find all instances of a node in a hierarchy using shared nodes.

Exclude Shared Nodes for Unique Property Validations

Shared nodes may be excluded from validations using the unique property validation classes UniqueProp, VersionUniqueProp, and VersionUnique2Prop. A configurable option is available for validations using those classes.

 

Defects Fixed in this Patch

Defect Number

Defect Fixed

•16050672

Saving validation gives warning message and then saves opposite.

•20555192

Invalid property type {0} when add members as sibling with derived sort order.

•21208809

Performance impacts on exports due to user security.

•21810750

Performance impacts on action scripts that trigger javascript validations.

•21918004

When installing individual components instead of doing a Complete install, the documentation files only get included with the Application Server component.

•22241380

Performance impacts when browsing large, flat hierarchy.

•22370818

Enriching user unable to see properties submitted until after approval.

•22518434

Performance impacts on node selector dialog when calculating node type.

•22526723

Implicitly shared leaf nodes not showing in hierarchy.

•22540494

In some environments, when attempting to connect to an Oracle database, the DRM Console will close with an unhandled exception.

•22547806

Workflow submit fails when real-time Move validation enabled on hierarchy.

•22576102

Export run via batch client does not handle version parameter with correct precedence.

•22609094

In some cases, the inclusion of a derived Boolean property for informational purposes in a Data Governance Request task may present a error indicating the property cannot be updated when the request is submitted.

•22658208

List property allows update with empty value via action script.

•22706145

Javascript formula unable to return value for Core.SharedMap_MDM

•22743357

When searching for a node not in current view, the found node should be scrolled into view.

•22782594

Selection does not stay on the same node when moving between hierarchies.

•22813597

List properties in workflow task not displaying correctly in IE11.

•22813726

Some text in workflow not translated to French.

•22835524

Property selection issue when adding new validation to a workflow task.

•22893822

Creating external lookup property gets object reference error.

•22910781

Node selector not presenting nodes for move to which user should have access.

 

The following defects are fixed in this patch for Data Relationship Management Analytics.

Defect Number

Defect Fixed

•22189920

Workflow requests that get auto-committed will not be reflected in the Analytics module.

•22583344

Analytics module not currently run as a managed service.

•22649770

On login page for Analytics, hitting <Enter> key after typing invalid credentials will display an error page with "Internal Server Error"

•22665638

Using certain regional settings, new nodes in a newly added version may not be reflected in the Growth dashboard.

•22666625

Uninstall process for Analytics module should be more fully documented.

•22916833

User with Data Manger role should be able to see all versions in Change dashboard without being granted node access.

 

Defects Fixed in Patch 11.1.2.4.330

Defect Number

Defect Fixed

•19459973

Leaf node may temporarily disappear after being moved under another limb node.

•20619595, 20638448

EPMA Export always exports the value of #root for the parent name for the Top Node of a hierarchy, even when that value has been overridden.

•21608251

When user has Access Manager role, formula function NodeAccessGroups() returns all node access groups in system instead of just those that apply.

•21674316, 21786868

Generation Export incorrectly handles implicit shared node found in ancestor list.

•21690564, 22143793

Export based on hierarchy group should use the hierarchy sort order defined.

•21697854

Adding a new list value to a list property from the property grid does not save the new value correctly.

•21848371

Version restored from file could have conflict with existing hierarchy ID.

•21915924

Approving user is not able to view a request after the submitting user has been deleted from the system.

•21961278

When using Internet Explorer, exporting to an existing file that is currently locked will download invalid data.

•22011949

In workflow task, node selector dialog may not populate correctly based on node access group filtering.

•22065377

When inserting node via workflow task, some property values from new hierarchy not displayed correctly.

•22120150

Submitting user of a workflow task incorrectly receives notifications for subsequent stages that should only go to Assignees.

•22122789

Apply Updates process taking too long for new content introduced in 11.1.2.4.320.

•22126839

When downloading a hierarchy page into a spreadsheet, blank lines are inserted for branches not fully expanded.

•22160188

Timeout error received when deleting a validation due to dependency checking process.

•22226260

Workflow request not fully validating parent~node format.

•22234176, 21953276

When large value encountered during bulk insert operation, system can remain in single insert mode causing version save operation to take significantly longer.

•22241395

Migration extract file shows object access group as System instead of Standard.

•22262177, 22514388

Saving version restored from file gets ORA-02291: integrity constraint violated - parent key not found.

•22264989

Migration difference file incorrectly lists object access group as System.

•22307027

Data Creator role should not allow creating As-Of versions.

•22331158

Export does not include values for derived, overridable hierarchy level properties.

•22497054

Workflow request gets error after multiple inserts:  "node does not exist in hierarchy"

•22520386, 22546811

Node selector dialog not displaying nodes correctly on page 2.

•22526723

Implicit shared nodes not displayed correctly when descendants of implicit shared nodes.

•22590522

Batch client export uses the version variable saved with the export profile instead of the version specified in the batch client parameter.

•22609268

Repository upgrade not allowed when user-defined artifacts have been added to the repository.

Defects Fixed in Patch 11.1.2.4.321

Defect Number

Defect Fixed

•22114822

Lineage version property was being incorrectly set on Baseline versions.  This could cause error when deleting a version: "DRM-12037: Cannot update properties for a baseline or As-Of version."

•22176473

Repository upgrade process was initializing some node statistics and could take a long time in some environments.  Since these values are not yet utilized in the current release, this part of the upgrade process was removed for now.

•22198882

When creating user names, the comma and period characters are not allowed.  These characters should be allowed in order to match the behavior of previous releases.

Defects Fixed in Patch 11.1.2.4.320

Defect Number

Defect Fixed

•16478033

ENABLE USER TO SELECT DOMAIN FOR ADDING A NEW DOMAIN NODE

•16499579

CHANGES TO COLUMN/PROPERTY SELECTION NOT REFLECTED IN QUERY RESULTS

•16528292

AUDIT NOT LOGGING CORRECTLY WHEN MOVING A NODE

•17476381

UNABLE TO SELECT MULTIPLE EXPORTS TO ASSIGN TO A BOOK

•17487528

COMPARE QUERY RESULTS - IN TREE VIEW, PREVIOUS VERSION DETAILS ARE DISPLAYED

•18017867, 20127325

WORKLIST IDS DO NOT SORT CORRECTLY WHEN THERE IS MORE THAN ONE PAGE OF IDS

•18112008

LEAF NODE REQUESTS REFER TO THE PARENT NODE NAME AND NOT THE ID IN WORKFLOW

•19780378

HIERARCHIES FROM FINALIZED VERSIONS CAN BE DELETED BY ACTION SCRIPT

•19906665

REMOVE DUPLICATES FEATURE NOT WORKING CORRECTLY IN SOME CASES

•19925239

USER SESSIONS ARE STAYING OPEN

•20026950

"COULD NOT READ INT16" ERROR WHEN RESTORING A VERSION 

•20332563

ACTION SCRIPT DOES NOT ESCAPE PAIR OF DOUBLE QUOTES

•20359741

SELECT NODE DIALOG DOESN'T DISPLAY WELL BELOW 16TH LEVEL

•20655175

API CALL: CREATEBOOK/UPDATEBOOK DOESNT ADD THE BOOKITEM

•20765610

TOP NODE CAN BE CREATED THAT IS NOT UPPERCASE (SYSTEM PREFERENCES ISSUE)

•20828266

DEFAULT PROPERTY CATEGORY NOT INITIALIZED IN DB FOR NEW USERS

•21035822

CREATE AS OF VERSION SHOWS INCORRECT TIMESTAMP WHEN EXECUTED COMPARISON EXPORT

•21049850

HAVE PROPERTY CATEGORIES RETAINED WHEN ROLES ARE ASSIGNED OR UNASSIGNED

•21123666

VIEW NODE PROPERTIES ICON FROM THE VERSION BROWSE/SEARCH IS GRAYED OUT

•21186733

CHOOSING STAY ON PAGE WITH UNSAVED PROPERTY CHANGES NOT WORKING PROPERLY

•21203005

HIERARCHY GROUPS DON'T STAY COLLAPSED

•21234341

ERROR SAVING RESTORED VERSION

•21239104

OBJECT REFERENCE ERROR INSERTING SHARED NODES WHEN UPNAME SYS PREF TO TRUE

•21288621, 21288654

ISSUES WITH FIREFOX 38.X SUPPORT

•21321591

QUERY WITH CONTAINS NOT FUNCTIONING PROPERLY (Previously, the query operator "Contains" functioned as a string match for the specified string.  Now this operator will look for the specified string as a member in a list property.)

•21322574

ALLOW REMOVAL OF DESCRIPTION FROM WORKFLOW TASKS

•21349624

GENERATION EXPORT WITH EXCLUSION FILTER DOES NOT SAVE 

•21365909

UNABLE TO TELL SYSTEM VERSES STANDARD OBJECTS IN SHORTCUTS

•21377199

OBJECTACCESS=SYSTEM DOES NOT WORK AS PART OF GENERAL SECTION IN MDM_CONNECT

•21385233

VERSION FILE WILL NOT IMPORT ERROR: AN ITEM WITH THE SAME KEY HAS ALREADY BEEN LOADED

•21423398

ENHANCEMENT TO TYPE TO SELECT FROM LIST

•21495054, 21785508

JAVASCRIPT PROPERTIES SHOWING CALCULATION INACCURACIES DURING CONCURRENT BATCH OPERATIONS

•21525113

ORPHAN TAB SHOWS NO ORPHANS, BUT 250+ ARE KNOWN TO EXIST

•21613653

UPLOAD FILE / HIERARCHY RESTRICTION DOES NOT WORK SIMULTANEOUSLY

•21635891

DRM TASK MANAGER ERRORS EVERY 3 MINUTES

•21667465

UNABLE TO SAVE VERSION

•19931714

LIST TAB STAYS ON LOADING IN PROPERTY DEFINITION

•21288474

VARIOUS TRANSACTION HISTORY ISSUES

•20788128

IMPORT FIELD WITH UNMATCHING QUOTES CAN CAUSE INCORRECT ROW PARSING

•21113925

KICKED BACK TO WORKLIST PAGE WHEN TRYING TO ADD AN ITEM ON IE11

•21793777

DRM SERVICE WILL NOT START PROPERLY WITHOUT AT LEAST ONE ENABLED APPLICATION

•21748200

PROP.ORIGIN REPORTING INCORRECTLY

Defects Fixed in Patch 11.1.2.4.311

Defect Number

Defect Fixed

•21147577

When adding certain roles (Interactive User, Data Creator, Data Manager, Application Administrator) to a user via API and then trying to retrieve the user details via GetUser(), an exception is returned.

•21251134

When loading a version into memory from the database, some of the relationships may not load properly causing nodes to be loaded as orphans instead of hierarchy nodes.  Version back-ups to file and Version copies made when this condition exists will restore with orphan nodes.  New version back-ups/copies should be made and confirmed.

 

Defects Fixed in Patch 11.1.2.4.310

Defect Number

Defect Fixed

•14606340

Dependency checking not functional for java script objects.

•17408364

Not able to override the model filter at the workflow task level.

•17910872

Parent node selection on workflow task is not in alphanumerical order.

•18056283

Validation scripts sometimes cannot be saved.

•18454097

Install wizard not installing IIS virtual directories in 11.1.2.3.500.

•18634416

Need better performance on node selector pop-ups.

•18637380

Float default value not saved to repository with decimal separator in non EN-US.

•18856166

Slow performance browsing large hierarchies in workflow client.

•19501118

Property dependencies not showing accurately in DRM or migration client.

•19570351

When a request is rejected after lines added, submitting user is unable to copy.

•19931727

Need ability to have mouse over on property show qualified property name and label. 

•20305345

Parameter "Ancestor Sequence #" not working properly in Generation Export.

•20326714

Generation Export producing different results in 11.1.2.3.304. 

•20347578

Workflow has 2 items,  Add plus Insert.  Commit stage can change node name on both.

•20563463

Workflow task name (not label) displayed on bulk upload form.

•20638160

List property allows Null value via action script.

•20655175

CreateBook/UpdateBook API call does not add the BookItem.

•20671302

Hierarchy tree browse does not resize content based on content length.

•20701671

RemoveProp action should not apply to Description property.

•20732255

Export book not in conformance with new structure fails to throw error.

•20883082

More than 2 back-to-back splits results in only 2 requests.

•20898220

DRM NET JNI Bridge initializing and immediately reaching java max heap size.

•20916928

DRM-61045 error when registering DRM in the Console.

•21044462

Properties are copying over between request items in the same request.

•21051440

Changes to Property Definition table are not effective until service restart.

•21078280

Inclusion of required global node property in workflow task disables a string field.

 

Defects Fixed in Patch 11.1.2.4.302

Defect Number

Defect Fixed

•20686185

When creating an import using an external connection to a database, the tables are available to map but not the views.

•20689463

The temporary folder for ASP.NET files used by the web client was created in a different directory (C:\ade\alm-git) in the 11.1.2.4.301 release.  After installing the 11.1.2.4.302 release, the files will now reside in the correct location and the C:\ade\alm-git directory can be deleted.

•20700140, 20722658

Process used to support external user authentication (drm-netjnibridge-host.exe) does not start properly in Windows 2012 environment.

•20724530

Creating an external connection to a database view on MSSQL gets error when saving.

•20751745

Importing values with unexpected quotes can cause lines to be processed incorrectly with no warning message.

 

Defects Fixed in Patch 11.1.2.4.301

Defect Number

Defect Fixed

•20257241

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

•20305952

Action script messages display some French language characters incorrectly.

•20365524

Script that adds and deletes the same node can get object reference error.

•20394117

As-Of version with the same date offset cannot be created after the original version was deleted and recreated.

•20412802

Running Generation Export with Hierarchy Group selection gets error:  "DRM-23067: Export is not runnable."

•20416861, 20570176

When a request is pushed back to the Submit stage, it is not assigned to any Node Access Group.

•20447178

When deleting and adding node types via the API, get error "DRM-12150: A Node Type with the name xxx already exists"

•20448761

Need new web service call that will return glyph name based on glyph id.

•20466646

When copying a version, properties such as Status, Owner and Copy Time may not be correctly populated.

•20466820

User name field is not populated for an attachment until the request is saved.

•20466966

Hierarchy Group constraint on workflow task property is not correctly limiting the available hierarchies for selection.

•20474599

Workflow metadata cannot be deleted while a version delete is pending.

•20507239

Node access rights not properly enforced for editing custom properties.

•20507304, 20538644, 20554885

Node access rights not properly applied to node in alternate hierarchy.

•20508420

Blending selected hierarchies into version where they do not exist gets error:  "DRM-21026: Invalid target Hierarchy specified"

•20533476

Hierarchy constraints for node data type properties are not persisting correctly.

•20563793

Importing a hierarchy containing a duplicate limb node which has duplicate descendants gets error: "An element with the same key but a different value already exists"

•20570738

When one of the items in a request fails a real-time validation, the remaining items in the request are still being committed instead of all being rolled back.

•20577231

Request activity for the Unclaim action should show no user.

•20602901

Synchronize not available in context menu for Compare results.

•20609598

Inserting node as sibling gets object reference error.


 

Known Issues in this Patch

The following are the noteworthy known issues of this patch for Data Relationship Management.

Defect Number

Description

•23076347

External Node Access Groups are available when editing Internal user.

•23056836

FDMEE integration using non-ASCII characters (FDMEE bug 23051532)

When using non-ASCII characters for a target app and location name, the DRM import or export profile does not automatically happen. A workaround is to manually execute the import/export in DRM.

Precondition:
1.DRM has been configured for the integration.
2.Have created non-ASCII location and execute it.even though the status is fail,the data have been loaded into tables.
Steps for the workaround:
1.Login DRM, go to Import,open the FDMEE Import,click Edit Parameters,and edit the value of LOADID to the Process ID of the Metadata Load.
2.Click Run to execute the import process manually and check the result status.
3.When ready to export, open the export profile, choose the Version to export.
4.Click Edit Parameters, edit the value of the LOCNAME to the location name and run it.
5.Check the exported values in DB table TDATAMAP_STG.

•21464822

Email notification for workflow request is displayed in English when server locale and browser settings set to non-English.

•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
error:  "HTTP Error 500.19 Internal Server Error"
To resolve this, ensure that web site drm-web-client is using Application Pool "ASP.NET v4.0 drm_pool" and not some other application pool.

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

•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

•10648889

Console gets "Operation failed" error when database name contains dot operator

•10647639

After upgrade, Admin password not reset to value entered during configuration

 

The following are the noteworthy known issues of this patch for Data Relationship Management Analytics.

Defect Number

Description

•22266880

On Windows 2012 using Internet Explorer with language settings either Simplified Chinese (zh_CN) or Traditional Chinese (zh_TW), the Analytics pages display in English.  Need to apply Web Logic Server patch ARU17935230 to resolve this.

 

Applying this Patch for Data Relationship Management

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

To apply this patch release:

1.    Perform a backup on the databases for any existing Data Relationship Management applications. Database backups should be performed when Data Relationship Management service is stopped.

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.4 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 release.

5.    If a multiple-machine configuration is being used, repeat the uninstall and install steps above for each machine.

6.    When using an Oracle repository, run the following statement for the current schema owner for each application to be updated:

GRANT CREATE TYPE, CREATE SEQUENCE TO <user>;

7.    In the Configuration Console on the application controller machine, select Application, then Apply Updates for all existing applications.

8.    Make sure to save any configuration changes made in the Data Relationship Management Console.

9.    Start the Data Relationship Management service.

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

Applying this Patch for Data Relationship Management Analytics

To install the Data Relationship Management Analytics module, refer to the Oracle Data Relationship Management Installation Guide for instructions.  To upgrade the Data Relationship Management Analytics module from a previous release:

1.    Stop the WLS Admin Server.

2.    Stop the Oracle DRM Managed Server.

3.    Run script upgrade.cmd (Windows) or upgrade.sh (Linux)

4.    Enter requested information for EPM Domain.

5.    Start the WLS Admin Server.

6.    Start the Oracle DRM Managed Server.

 

Rolling Back this Patch for Data Relationship Management

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.

Rolling Back this Patch for Data Relationship Management Analytics

To uninstall the Data Relationship Management Analytics module:

1.    Ensure that the WLS Admin Server is running.

2.    Stop the Oracle DRM Managed Server.

3.    Run script uninstallAll.cmd (Windows) or uninstallAll.sh (Linux)

For additional information, see the “Deploying Applications” section in the Oracle® Fusion Middleware Administrator's Guide.