Readme

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 of Data Relationship Management. This patch can be installed on a new machine or replace an existing Data Relationship Management installation.

If this patch will replace an existing 11.1.2.1.x installation, related components such as Hyperion Foundation Services and the Data Relationship Management Web Service are not affected.

This is the fourth PSU on the 11.1.2.1.00 release and is cumulative of releases 11.1.2.1.101, 11.1.2.1.102 and 11.1.2.1.103.

Supported Paths to this Patch

You can upgrade to this patch from the following releases:

Release Upgrade Path From	To
11.1.2.1.x	11.1.2.1.104
11.1.2.0.x	11.1.2.1.104
11.1.1.2.x	11.1.2.1.104
9.3.x	11.1.2.1.104
9.2.x	11.1.2.1.104
A release earlier than Release 9.2.x	If you are upgrading from a release earlier than 9.2.x, you must first upgrade to a supported release and then upgrade to release 11.1.2.1.104. 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 Release 9.2.x, Oracle recommends the following upgrade path: 9.2.0 to 9.2.1 to 11.1.2.1.104.

· If you are starting from Release 9.3.x, Oracle recommends the following upgrade path: 9.3.0 to 9.3.1 to 9.3.3 to 11.1.2.1.104.

· If you are starting from Release 11.1.1.x, Oracle recommends the following upgrade path: 11.1.1.0 or 11.1.1.1 or 11.1.1.2 to 11.1.1.4 to 11.1.2.1.104.

· 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 is an administrator and is the same for all EPM System products. Assign local policies if required by the product. Such assignments typically are: “Act as part of the operating system, Bypass traverse checking, Log on as a batch job, Log on as a service.”

Supported Platforms

Applies to all supported platforms.

Supported Languages

This patch applies to English only.

Top of Document

Defects Fixed in this Patch

Defect Number	Defect Fixed
• 13366122	Property values of type Date, if entered in a time zone that honors Daylight Savings Time (DST), can display incorrectly (off by 1 day) when rendered later when DST begins or ends. Similarly, property values of type DateTime can later display incorrectly (off by 1 hour) when DST begins or ends.
• 12913357	Date and Time data type properties should be static values. In previous releases, properties of type Date and type Time were subject to being adjusted based on current time zone and Daylight Savings Time. However, in some cases, the user may have a need for static values that are not subject to adjustment. Thus, these two property data types will now be static values such that whatever value is entered will remain unchanged. If a relative data type is desired, then the Datetime data type should be used. During the upgrade process to this release, all existing properties of data type Date or Time will become static values. Properties of type Date, which previously contained a date and (hidden) time component, will have the time component removed and the date value will be rounded to the nearest day. For example, a Date property with an existing value of 12/24/2011 (11:00:00 PM) will become 12/25/2011. A Date property with an existing value of 12/24/2011 (1:00:00 AM) will become 12/24/2011.
• 13525575	During upgrade of DRM repository, performance could be significantly impacted when indexes exist.
• 13526660	Copying a DRM repository from release 11.1.2 via the Repository Wizard will cause the repository to be re-initialized with the default data.
• 13538712	Export run via web services API confuses the include file name with the output file name.

Top of Document

Defects Fixed in Patch 11.1.2.1.103

Defect Number	Defect Fixed
• 12983129	After upgrading, this error displays when user tries to open a hierarchy or clicks exports: “Error processing Export [ADI_TransAudit_InOut]:Enum Description "Bulk Copy Process Run" not found.”
• 12904031	The function ArrayIndex() is not returning the expected results.
• 12901660, 12886566	When downloading the results file this error is displayed: “This operation requires IIS integrated pipeline mode”.
• 12878882	For export, the “Include Inactive Nodes” option does not return the expected results.
• 12878199	Request history displays this error: DRM-11008: Column “C_Comment” Not Found.
• 12874691	For upgrade, this error displays when analyzing property references: Invalid Column Name “C_Class” with 11.1.2.0 Database.
• 12864573	Special characters are shown in the tool tip when trying to add a duplicate node.
• 12863039	Validations are not working properly.
• 12859514	For upgrade, this error displays when opening any hierarchy in an upgraded application: “Bulk copy process run not found”.
• 12858232	An object reference error is displayed when creating a new export.
• 12844937	In console, error displays when you click Add to create a new application.
• 12825936	Transaction history audit columns do not show node description.
• 12825904	When adding a node, the MaxDescr system preference is not enforced.
• 12825885	When adding a node, validations are not performed on the description property.
• 12825869	Various defects related to description property when adding a node.
• 12815567	For upgrade, records copied shows row count for all records when version is selected.
• 12806522	After upgrade, user is unable to log in due to error with validation of “HierContainCC”.
• 12806234	DRM export is unable to add a blank line to header; the blank line removed when saving.
• 12802928	When creating a validation, this error is displayed "The server returned an error processing the action: GetValidationTemplates. Error message: Requested value 'HierContain' was not found."
• 12802435	Upgrade includes tables added by customer on source versions.
• 12801637	AsOf versions do not have the correct node descriptions.
• 12800759	When running an import via a batch script, an object reference error is displayed in the log.
• 12760586	When running an import via a batch script, if a version already exists an incorrect error message is displayed in the log.
• 12757555	When a script with multiple UpdateVersionPropValue or RemoveVersionPropValue actions is run, the script hangs and times out.
• 12736610	Query filters do not correctly process parentheses.
• 12698282	Creating a validation; error in Eden database.
• 12684444	In import, hierarchies cannot be entered for a column.
• 12683887	A global derived property with a local property reference is not enforced as in previous releases.
• 12680626	Some global derived property definition classes that have local property definitions for parameters are not reported in the Invalid Property References section of the Repository Analysis.
• 12680246	Upgrade stops if database has a derived formula property definition that contains special characters.
• 12679361	For upgrade, clicking Test Connection does not detect that a 11.1.2.1.101 database needs to be updated.
• 12666768	Import using multiple ignore columns is unable to correctly remove columns.
• 12666351	For upgrade, the import delimiter value “Tab” is upgraded as “Other”.
• 12666321	Ignore column is not assigned to import sections after upgrade.
• 12655963	Import version with duplicate nodes returns errors related to global properties.
• 12653145	An invalid reference to a fully qualified property name results in an error.
• 12653017	After fixing validation issues, marked hierarchies do not refresh. After manually refreshing the affected hierarchy, all batch validation results are cleared for all hierarchies.
• 12647696	Export to Oracle database with DRM Float type causes errors and truncation.
• 12641977	This error is displayed when running Version export where two or more hierarchies have at least one node in common: “Node list already contains node”.
• 12638196	Functions that take a list parameter display an error when a [comma] is used as the list delimiter.
• 12633417	Global find results disappear after user selects GoTo a node.
• 12628668	An error is displayed when user selects Database Table as target device and when running export to a table.
• 12627660	List items do not get saved to the database.
• 12622548	Running request history with any request ID value gives ORA-01036 error.
• 12618832	Derived properties without formulas result in errors.
• 12613534	Hierarchy XML export is not correctly formatted.
• 12613204	User gets the following error when running Hierarchy XML exports with any of the export specific columns selected: "DRM-23081: Export was unable to run due to the following error: The given key was not present in the dictionary."
• 12595916	The And() function evaluates the first two arguments only.
• 12591635	An object reference error is displayed when an import with invalid node name characters is run.
• 12586377	When attempting to blend a hierarchy from one version to another where the hierarchy does not exist, the blender returns an IncompleteSystemError status and provides no other information.
• 12583485	Delete version transaction is not logged in audit when version is saved.
• 12581941	Marked nodes do not get refreshed when running a query with different criteria.
• 12581908	From Query results, the GoTo operation does not work for a related node.
• 12566187	An error occurs if an explicit shared node is selected in a hierarchy where the primary node does not exist.
• 12563802	Select validation dialog does not display namespace.
• 12563706	Tags for special characters used in functions are case sensitive.
• 12563409	Various formula functions do not save with property.
• 12563240	Blender options do not default to the correct values.
• 12555858	Oracle upgrade script fails.
• 12555022	In request history, transaction records are not created for committed request items.
• 12544618	Various issues with Audit request filter controls.
• 12543986	Deleted node displays on the Relationships tab causing a “Node does not exist” error.
• 12543977	An object reference error is displayed when refreshing the hierarchy tree after changing a node name.
• 12543963	Properties selected for FindByProperties are listed twice in Find By menus.
• 12538876	Incorrect formula evaluation error for bad formula when using node.
• 12538096	GetGlobalNodesPropCategories error is displayed in global query results for deleted node.
• 12534227	Clicking on “Put As” displays “Must specify valid information for parsing in the string” error.
• 12432585	When trying to upgrade an 11.1.2.1.101 target database from a 9.3.3 source, this error is displayed “Input string was not in a correct format” for RM_Access_Group_Definition.
• 12426042	In Compare, a “PageIndex” error is displayed after changing number of items per page.
• 12415929	In Oracle GL, AccountTypeRequired batch validation does not work.
• 12415611	When changing Inherited parameter on OracleGL namespace an error is displayed.
• 12339134	A user with the Data Creator role can run standard objects with selected properties having no permissions set.
• 11906649	Node access group and Validation values are not imported when the “Skip Default Values” option for derived properties is set.
• 10385538	A fixed width object reference error is displayed in import results.
• 9960354	Upgrading to Oracle 11GR2 displays this error: “Insufficient memory to continue”.

Top of Document

Defects Fixed in Patch 11.1.2.1.102

Defect Number	Description
•12398534	Export with record delimiters of LF or CRLF not upgraded correctly
•12398834	Export with field delimiter of TAB not upgraded correctly
•12569467	Export with a parameter greater than 4000 characters gets upgrade error ORA-22835
•12579088	Upgrade of long property values spanning multiple rows may not be correct
•12597040	Property Hier System Category not upgraded correctly to Hierarchy Group
•12608742 •12624067	Export with no parameters and external connection gets error on upgrade
•12608809	Upgrade of large table can get timeout error
•12608856	Upgrade of export headers/footers not handled for namespaces
•12618630	Upgrade of derived property without a formula not handled correctly
•12622428	Upgrade of property value nested within a formula not handled correctly
•12624065	Upgrade of property name that is subset of another property name not correct
•12629767 •12641733	Upgrade of property names containing certain special characters not correct
•12637418	Upgrade gets error: Cannot truncate table RM_Access_Group_Definition
•12648362	Upgrade of deriver class without parameters not handled correctly
•12660086	Import with Ignore Column parameter not upgraded correctly
•12660250	Import with TAB delimiter not upgraded correctly
•12669027	Upgrade does not populate hierarchy listing for specific import column

Top of Document

Defects Fixed in Patch 11.1.2.1.101

Defect Number	Description
•10294835	Unable to View All Properties in DRM v11.1.2
•11830915	Export definition changes do not get the new table definition
•11830995	Property query does not interpret join operator correctly
•11831034	Saving books are not logged in audit
•11836616	Global RW Derived properties show and export incorrect values after overridden
•11673955	Migration utility treats validations and node access groups as missing dependencies
•11709965	Import of large, flat hierarchy takes longer and uses more memory
•9148801	Version load hangs after application is disabled in Console and DRM restarted
•9559414	After Annul All Below, inserting limb node can get error
•10427403	Removing property value where PropEquivBool validation is assigned gets error
•10433096	Console gets error when all applications removed
•11077849	Batch client parameter /PropertyRefByLabel causes error in script operation
•11653738	Last Changed On property not updated when a property value is removed
•11675761	Able to perform remove and delete actions on an inactive node
•11677524	Some functions do not resolve property names unless fully qualified
•11707048	Shuttle control cannot select available item when only one item shown by default
•11711719	Lookup property is cleared when saving new property with lookup values
•11719442	Navigating script grid with top section collapsed can get error
• 11734550	API adaptor times out after first call to view WSDL
• 11716770	Transaction audit against large database has poor performance
• 11740778	Global inheriting property gets error after version deleted where its controlling hierarchy was assigned
• 11768542	Node access group displays fully qualified name after it has been edited

Top of Document

Defects Fixed in Release 11.1.2.1

Defect Number	Defect Fixed
• 8661420	Batch client export parameters /HIER and /NABBREV not working properly.
• 8668248	Batch client command line parameter does not take precedence over config file
• 9067171	Migration utility not handling property dependencies correctly
• 9455214	Batch client not supporting multiple operation mode
• 9707476	Session expires even when user is not idle
• 9958120	Unable to save a data property when regional settings differ between server & client
• 9975486	Migration utility not populating list values in basic HTML report
• 9976815	When choosing ANSI encoding for hierarchy export, a UTF8 file is created
• 10017289	Derived property not picking up value from concatenation formula
• 10022655	Ancestor exports need to supported during upgrade
• 10038906	Processing error causes event log error if event sources does not exist
• 10062552	Error when saving more than 10 hierarchies in single export
• 10113691	Same machine listed multiple times in console when using fully qualified name
• 10151796	Online Help not working in Windows 2008
• 10154776	Formulas allowed with circular references that cause stack overflows
• 10185792	Property formula evaluates but won't save
• 10194038	After searching, the Go button does not jump to relevant node
• 10202992	User Guide does not explain object access level instructions for saving
• 10222448	Export fails when exporting to table with 100 columns due to data type
• 10260944	Online Help cannot be viewed with SSL required on IIS
• 10266507	Creating property using own name in formula results in error on saving
• 10272104	Header and Footer customization tags in hierarchy export not working properly
• 10309735	Search by Name/Description taking a long time to complete
• 10315626	Level property value has changed from earlier versions
• 10316380	Format function not working properly
• 10352417	Date type node properties save date value incorrectly when OS locale changes
• 10413244	Stuff function does not work correctly to remove some characters with null
• 10418578	Export not inserting field delimiter when first column of output is blank
• 10419199	Errors with validations for properties with differing names and labels
• 10621162	Action script reports success when insert failed due to invalid node name

Top of Document

Defects Fixed in Release 11.1.2.0

Defect Number	Defect Fixed
• 9215083	Request for ability to hide system-defined property categories
• 8304725	Web Pub – Selecting hierarchy export displays request for previous version
• 8264732	Assign MDM user to some roles to control permission on version and hierarchy
• 8232319	Ability to have username greater than 20 characters
• 6591140	Request for “Add Sibling” to position new node
• 6584544	Provide search functionality in hierarchy export top node selection
• 6541894	Request support for unicode

Top of Document

Known Issues in this Patch

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

Defect Number	Description
•11668780	After upgrade, no way to view version type for Translog export with As-Of version
•10647639	After upgrade, Admin password not reset to value entered during configuration
•11064169	After upgrade, some transaction history times not adjusted for Daylight Savings Time
•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"/> </behavior> Now 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.

Top of Document

Applying this Patch

The section includes important information about applying this patch for Data Relationship Management. Follow this procedure to replace an existing 11.1.2.1.x 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. Uninstall the existing 11.1.2.1.x 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.

2. Run the new setup.exe to install 11.1.2.1.104.

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

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

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

6. Start the Data Relationship Management service.

Top of Document

Rolling Back this Patch

To roll back a patch:

For each machine where Oracle^® Hyperion Data Relationship Management is installed, run setup.exe and choose the Remove option.

Top of Document