Oracle® Hyperion Enterprise Performance Management Architect, Fusion Edition

Release 11.1.2.1.000 Patch Set Update (PSU): 11.1.2.1.601

Readme

[Skip Navigation Links]

About This Patch. 1

Patch Type. 1

Supported Paths to This Patch. 1

Prerequisites. 2

Supported Platforms. 3

Supported Languages. 3

Defects Fixed in This Patch. 3

Defects Fixed in 11.1.2.1.600. 8

Defects Fixed in 11.1.2.1.104. 8

Configuring an Interface Data Source to an Oracle RAC Database. 11

Defects Fixed in 11.1.2.1.103. 12

Defects Fixed in 11.1.2.1.102. 12

Defects Fixed in 11.1.2.1.101. 12

Known Issues in This Patch. 12

Applying This Patch. 13

Rolling Back This Patch. 14

Troubleshooting FAQs. 15

 

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 replaces files in the existing installation and is a stand-alone patch.

Supported Paths to This Patch

You can apply this patch to the following releases:

·         Oracle® Hyperion Enterprise Performance Management Architect (Performance Management Architect), Fusion Edition 11.1.2.1.000

·         Oracle® Hyperion Enterprise Performance Management Architect (Performance Management Architect), Fusion Edition 11.1.2.1.101

·         Oracle® Hyperion Enterprise Performance Management Architect (Performance Management Architect), Fusion Edition 11.1.2.1.102

·         Oracle® Hyperion Enterprise Performance Management Architect (Performance Management Architect), Fusion Edition 11.1.2.1.103

·         Oracle® Hyperion Enterprise Performance Management Architect (Performance Management Architect), Fusion Edition 11.1.2.1.104

·         Oracle® Hyperion Enterprise Performance Management Architect (Performance Management Architect), Fusion Edition 11.1.2.1.600

Prerequisites

Required Oracle® Hyperion Financial Management (Financial Management), Fusion Edition Patch (If 'Cell Text Label' feature is needed either from Enterprise Performance Management Architect enabled or classic Financial Management applications.)

You must apply the Oracle® Hyperion Financial Management (Financial Management), Fusion Edition 11.1.2.1.101 patch 11689544.

Required Oracle® Hyperion Enterprise Performance Management Workspace, Fusion Edition Patch

You must apply the Oracle® Hyperion Enterprise Performance Management Workspace, Fusion Edition 11.1.2.1.600 patch 14119724.

Required Oracle® Hyperion Shared Services, Fusion Edition Patch

You must apply the Oracle® Hyperion Shared Services, Fusion Edition 11.1.2.1.600 patch 14142678.

Required Microsoft Patch

Microsoft has identified a security issue that could allow a hacker to compromise your Windows-based system. You MUST install the Microsoft VC 2005 SP1 ATL redistributable pack before applying this patch.

The updated VC 2005 redistributable is available here for both x86 (32-bit) and x64 (64-bit):

http://www.microsoft.com/downloads/details.aspx?familyid=766A6AF7-EC73-40FF-B072-9112BAB119C2&displaylang=en

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

UNIX/Linux:
Use the account that was used to install EPM System products and has Read, Write, and Execute permissions on $MIDDLEWARE_HOME.  Do not use the
root user. If you installed other Oracle products, the user who installed EPM System products must be in the same group as the user who installed the other Oracle products.

Supported Platforms

This patch set update supports all platforms supported by the 11.1.2.1.000 release.

Supported Languages

This patch set update supports all languages supported by the 11.1.2.1.000 release.

Top of Document

Defects Fixed in This Patch

·         16786734 -- Navigating to member formula in grid editor and double clicking a cell containing a formula causes the member formula window to open with error; Server was unable to process request.

·         16786590 -- Financial Management dimensions that are made as shared dimensions and deployed to other EPM applications (i.e. Hyperion Planning or Essbase or Hyperion Profitability and Cost Management) shall have dimension type property missing.

·         16786531 -- EPM Architect does not validate and prevent deployment of Hyperion Planning and Financial Management applications, if shared member is preceding the primary member.

·         16757769 -- Data Synchronization fail as Essbase(ASO) puts negative numbers within brackets that are not recognized as valid by Financial Management.

·         16753968 -- Hyperion Planning Deployment may fail due to database connection time out. Workaround: Below steps may help.

1. Stop EPM Architect Dimension Server

2. Navigate to the " BPMA_Server_Config.xml" file (<Middleware Home>\EPMSystem11R1\products\Foundation\BPMA\AppServer\DimensionServer\ServerEngine\bin)

3. Take the backup of the BPMA_Server_Config.xml

4. Edit the logging configuration section of your BPMA_Server_Config.xml file so that debug-level messages will be logged to the Windows Event Viewer by changing the logging level from INFO to DEBUG see below.

<log4net debug="false">

    <!-- Define some output appenders -->

      <appender name="ConsoleAppender"

type="log4net.Appender.ConsoleAppender,log4net" >

      <param name="Threshold" value="DEBUG" />

        <layout type="log4net.Layout.PatternLayout,log4net">

        <param name="ConversionPattern" value="%d %m%n" />

      </layout>

    </appender>

      <appender name="EventLogAppender"

type="log4net.Appender.EventLogAppender,log4net" >

      <param name="ApplicationName" value="AWB_DimServer" />

      <param name="LogName" value="Application" />

      <param name="Threshold" value="DEBUG" />

        <layout type="log4net.Layout.PatternLayout,log4net">

        <param name="ConversionPattern" value="[%t] %-5p %m" />

      </layout>

    </appender>

      <appender name="DebugOutAppender"

type="log4net.Appender.OutputDebugStringAppender,log4net" >

      <param name="Threshold" value="DEBUG" />

        <layout type="log4net.Layout.PatternLayout,log4net">

        <param name="ConversionPattern" value="%X{processid} Thread ID: [%t];

%-5p %m" />

      </layout>

    </appender>

       <appender name="ODLAppender"

type="Hyperion.DimensionServer.ODLAppender,odl_appender_2">

      <param name="Threshold" value="DEBUG" />

    </appender>

      <!-- Setup the root category, add the appenders and set the default priority -->

    <root>

      <priority value="DEBUG" />

      <appender-ref ref="ConsoleAppender" />

    <appender-ref ref="EventLogAppender" />

      <appender-ref ref="DebugOutAppender" />

      <appender-ref ref="ODLAppender" />

    </root>

5. Now add the following XML tags under </Data_Access_Layer> section of the BPMA_Server_Config.xml

<ConnectionPooling>

        <PoolingEnabled>true</PoolingEnabled>

        <!--Connection Lifetime is the maximum life time (in seconds) of the connection.  Setting this to 0 disables it.-->

        <ConnectionLifetime>0</ConnectionLifetime>

        <!--MaximumPoolSize is the maximum number of connections in the pool.-->

        <MaximumPoolSize>100</MaximumPoolSize>

        <!--MinimumPoolSize is the minimum number of connections in the pool.-->

        <MinimumPoolSize>1</MinimumPoolSize>

        <!--Controls the enlistment behavior and capabilities of a connection in context of COM+ transactions or System.Transactions. This setting must be either "dynamic" or "true".-->

        <Enlist>true</Enlist>

          <!--The following 5 settings are specific to Oracle database  Connection Timeout is the maximum time (in seconds) to wait for a free connection from the pool.-->

        <ConnectionTimeout>15</ConnectionTimeout>

        <!--HA Events enables ODP.NET connection pool to proactively remove connections from the pool when an Oracle RAC service, service member, database, or node goes down.  Works with RAC, Data Guard, or a single database instance.-->

        <HAEvents>false</HAEvents>

        <!--Load Balancing enables ODP.NET connection pool to balance work requests across Oracle RAC instances based on the load balancing advisory and service goal.-->

        <LoadBalancing>false</LoadBalancing>

        <!--PoolSizeDecrement (Decr Pool Size) is the number of connections that are closed when an excessive number of established connections are unused.-->

        <PoolSizeDecrement>5</PoolSizeDecrement>

        <!--PoolSizeIncrement (Incr Pool Size) is the number of new connections to be created when all connections in the pool are in use.-->

        <PoolSizeIncrement>1</PoolSizeIncrement>

        <!--Validate Connection validates connections coming from the pool.-->

        <ValidateConnection>false</ValidateConnection>

        <!--The following 4 settings are specific to MS SQL Server-->

        <ConnectionReset>true</ConnectionReset>

        <LoadBalanceTimeout>0</LoadBalanceTimeout>

        <!--The following setting can be used to add any custom setting not covered by anything else.-->

        <CustomSetting></CustomSetting>

      </ConnectionPooling>

5. Increase the  ConnectionTimeout to some higher value say for example 60.

6. Now start the Dimension Server.

7. Go to event viewer, there should be an event which includes the entire connection string as per the changes that we did in step 4.

8. Also make sure that the connection pool settings disappear if you remove the <ConnectionPooling> section from the BPMA_Server_Config.xml file and

9. Restart EPM Architect Dimension Server.

·         16698995 -- Dimension member attributes are not synchronizing between Application Library and Shared Library.

·         16692426 -- Validation that prevents same name for dimension or member for Alias dimension or its member should be removed for Hyperion Planning.

·         16295165 -- Excluded shared members are getting migrated through Life Cycle Management in EPM Architect.

·         16273421 -- Hyperion Profitability and Cost Management local dimension changed to shared dimension after deployment causes it to be removed from Dimension Library.

·         16072404 -- Hyperion Planning generic dimension member has ‘TwoPassCalc’ property missing in EPM Architect.

·         16061342 -- If Essbase(ASO) generic dimension Data Storage is ‘LabelOnly’, Hierarchy Type is ‘Stored’ and its children Consolidation is ‘~’; EPM Architect should treat it as valid instead of validation Error: Consolidation must be set to '+' in stored hierarchies.

·         15940439 -- Modify a property of deployed Essbase application and run validate application, EPM Architect still reports application as ‘in sync with deployment’.

·          15889266 -- Create Hyperion Workforce Planning application with local dimension, Synchronize Entity dimension with Shared Library, share Entity dimension; an error occurs: An exception occurred while merging a local dimension into an existing shared dimension (in replace mode). 

·         15889216 -- Member rename option displays member name, description, and alias, where it is expected to display only member name.

·         15889204 -- Over-ride and set ‘Period Type’ property of parent members (months) to ‘Base Time Period’, Exclude child members (weeks), Validation fails expecting 'Summary Time Period' for Month members.

·         15889145 -- Though transformation operator is set to none; Data synchronizer is converting number as string to double and storing in target application causing Hyperion Financial Report displaying double instead of text.

Note: In the external source file; dimension names, member names and data must be enclosed within quotes and quotes should be as selected in the data synchronization definition.

·         15889113 -- Dimension Library search does not work when non-English is set as primary language in browser.

·         15884818 -- Share Hyperion Planning local dimensions and use them for Financial Management application deployment; dimension name in metadata XML file and their internal properties in database such as ‘MappedType’ would be missing.

·         15883794 -- Deploy an application by excluding a parent member, then move child member from the excluded parent member to another parent and redeploy; redeployment aborts.

·         15882274 -- Rename and add an alias to a member without alias, deployment of application of this member fails with validation error: The given key was not present in the dictionary.

·          15864956 -- Migrated dimension members from EPM Architect using Lifecycle Management are not maintaining sort order as in the source.

·         14810332 -- Migrated Hyperion Planning member formulae from EPM Architect using Lifecycle Management are getting their double quotes striped leading to member formula error during deployment.

·         14793140 -- Lifecycle Management export contains undesired hidden period dimension members that are causing validation failures during deployment or re-deployment after Lifecycle Management import.

·         14787625 -- Compare engine detects changes in static hidden properties at application and dimension level, which is incorrect and causes false validation failures that prevents application re-deployment.

·         14398952 -- In the import file; if a User Defined Attribute values for primary and shared members are different; both the values should be merged and updated to primary and shared members.

·         16784372 -- When synchronizing between shared and application libraries, User Defined Attribute values that are blank or null in the source are not replacing the target values.

·         14371975 -- Upon migration from EPM Architect using Lifecycle Management; additional User Defined Attribute values in the destination should get deleted.

·         13966275 -- Lifecycle Management import of Shared Library dimension may fail with: Error "Couldn't determine the column delimiter for the ads file being imported"

·         12591248 -- ‘Holding Company’ property of Financial Management application’s Entity dimension should be restricted from having set to same entity (self referencing) or the first entity with ‘Holding Company’ property set to the second and the second entity with ‘Holding Company’ property set to the first (circular referencing).

·           9149761 -- Essbase member rename in EPM Architect creates a new member in the target application on deployment, rather than a rename of an existing member.

·         8984354 – ‘Measures’ and ‘AllocationType’ dimensions lose system members when used in Essbase application.

Defects Fixed in 11.1.2.1.600

·         13683141 -- The member order in Financial Management may differ from the member order in the Shared Library of Enterprise Performance Management Architect.

·         14224653 -- Enterprise Performance Management Architect 11.1.2.1.600 is to be made to support Internet Explorer 9 in compatibility view mode.

·         14236227 -- The Run Integrations role is not sufficient to run data synchronizations.

·         14284395, 13950687, 13331147, 13732777, 14481726 -- After application deployment in EPMA, “(500)internal server error" occurs.

·         14302350 -- In Batch client, Execute deploy and Execute Redeploy commands fail with the error, Invalid data source, Either the data source does not exist or the application has not been deployed to the data source.

·         14302450 -- File generator fails to generate ADS files for applications that have dimension association between the Entity dimension and the Currency dimension.

·         14302475 -- Running a search in Dimension library and closing the search pane result in browser becoming unresponsive for a while.

·         14310687 -- Load multiple User Defined Attributes via interface tables fails if Value column is blank.

·         14331936 -- In Batch Client, add the ability to remove members along with their descendants.

·         14342783 –- In the Shared Library, expanding a Dimension that is not valid for all plan types, results in error.

Defects Fixed in 11.1.2.1.104

·         13567745 –- When you try to validate a Performance Management Architect Essbase block  storage application that contains a dimension with a 100k flat hierarchy, the validation may hang.

·         13699481 –- Aliases may not be deployed from Performance Management Architect to Essbase.

·         13566883 –- When you try to validate a previously deployed Performance Management Architect application after editing the Alias property of the Period dimension, the validation may fail.

·         13525416 –-  The Start year in the Scenario dimension cannot be set to “No Year” unless the End Year is also set to “No Year”.

·         13628975 –- Some deployed and in sync with deployment applications may go out of sync after you upgrade to this release. If you perform a “Compare to deployed application" task on the original and upgraded applications, the results may show no differences between the original and the upgraded applications.

·         13615572 –- You may be unable to start the Dimension Server when Performance Management Architect is configured with Oracle Real Application Clusters (RAC) using a JDBC URL. You need to add support for the RAC database as an interface data source for synchronizing data.
See “Configuring an Interface Data Source to an Oracle RAC Database.”

·         13480022 -- The contents of the Oracle database schema for Performance Management Architect may be deleted after upgrading from 9.3.3 to 11.1.2.1.

Note: If you upgrade the Performance Management Architect schema from 9.3.3 to 11.1.2.1.000 or 11.1.2.1.x before you apply this patch (that is, 11.1.2.1.104), then the database may be corrupted. To fix this:

1.    Restore the 9.3.3 database from the backup copy of the database.

2.    Apply the 11.1.2.1.104 patch to 11.1.2.1.000 or 11.1.2.1.x.

3.    Use EPM System Configurator to upgrade from 9.3.3 to 11.1.2.1.104 by selecting the “Upgrade existing database to the current release…” option.

·         13603732 –- Performance Management Architect Batch Client does not support SiteMinder Single Sign On (SSO). Following is an example of launching the Batch Client script:

set bpmaserverurl=http://sp-win-0029.us.oracle.com/hyperion-bpma-server;
set workspaceurl=http://sp-win-0029.us.oracle.com:8080/workspace/;

set SSOType='SiteMinder';
set SSOFormUsernameField='user';
set SSOFormPasswordField='password';
Set SMPath=http://sp-win-0029.us.oracle.com:8080/siteminderagent/forms/login.fcc;

set AuthenticationPreemptive='True';

login BI-en, password;

create application
properties(ApplicationName, ApplicationDescription, ApplicationType)
values('Plan1', 'Description for BC_Test', 'Planning');

quit;

Note: The SSOType value should be set as 'SiteMinder'.
The SSOFormUsernameField value should be set as 'user'.
The SMPath value varies from one setup to another, depending on how SiteMinder is configured.

·         13543165 –- You may be unable to export metadata from Performance Management Architect for a Planning application using Lifecycle Management.

·         13614897 –- After creating a Profitability and Cost Management application in Performance Management Architect, deploying the application to the Profitability and Cost Management Web-tier, creating stages in a model, and deploying the Profitability and Cost Management application to Essbase, the stage dimensions may not be visible in the Performance Management Architect application library, and there may be an error in the Profitability and Cost Management log file.

·         13507024 –- You may be unable to synchronize an Account dimension from a Planning application to an Essbase aggregate storage application using the Shared Library in Performance Management Architect.

·         13719033 –-  If you map a source member to an [ICP None] member and write it in the Mapping Table Designer as \[ICP None\], validate, and finish the mapping, when you reopen the mapping, and click Edit Mapping, the Data Synchronizer may save  \[ICP None\] incorrectly as  \\[ICP None\\].

·         13698038 –- Some applications in the Application Library may have the status "Migration Pending," and the diagnostics tool may be unable to resolve this. To resolve this, you can use the diagnostic tool to delete the applications from Performance Management Architect, unless the applications also exist in Financial Management.

·         13385907 –- You may be unable to redeploy Essbase aggregate storage and block storage applications after you migrate them to an Exalytics computer with Essbase 11.1.1.6.

·         13788967 –- Data synchronizations across different plan types within the same
application may not work. The dimensionality of the source dimensions is repeated on
the destination dimensions without respect to dimension differences.

·         13610984 –- In the Shared Library, if you create folders (for example, Parent > Child > GrandChild), move a dimension to the bottom folder (for example, the GrandChild folder), and search for any member by right-clicking on a dimension in that folder, the member displays in the "Member Find - Shared Library" property window. However, when you double-click the member, the member may not be located in that dimension.

·         13918709 –- If you try to export a dimension that contains a forward slash character (that is, a /) from the Shared Library using Lifecycle Management, the export may not be successful.

·         13683141 -- The member order in Financial Management may differ from the member order in the Shared Library of Enterprise Performance Management Architect.

·         13941638 –- You may be unable to import Performance Management Architect application settings, shared dimensions, filters, and overrides in Lifecycle Management.

·         13962729 –- If you use shared dimensions in your Essbase applications, the applications may validate more slowly in Performance Management Architect.

·         13922185 -- The Performance Management Architect dimension server may fail to start in a mixed IPv4 and IPv6 Windows environment.

·         12586704 –-  If you make a change to an alias in an Essbase application, then redeploy the application to Essbase using the Batch Client, the aliases may not display in Essbase.

·         13950066 –- When creating a profile using interface tables, there should be an option to suppress the creation of transaction logs, as there is when creating a profile using flat files.

·         13950177 –- When using Lifecycle Management to migrate Public Sector Planning and Budgeting artifacts, Public Sector Planning and Budgeting members' smart list associations may be overridden.

·         11704366 –- The task flow for the redeployment of a Performance Management Architect – Hyperion Profitability and Cost Management application may remain active and may not be completed.

·         14051754 -– You may be unable to deploy an application from Performance Management Architect to Hyperion Profitability and Cost Management.

·         14070343 -- When you change the case of an alias value name for a dimension member that is deployed to Planning, the validation fails, because renaming a value by changing only the case is equivalent to renaming to a value that already exists in Planning.  

·         14013229 –- After you synchronize metadata, the aggregation property of shared members may be incorrect.

·         14099528 –- Data synchronizations may terminate when you are working with Essbase applications on a Solaris platform.

·         14162435 –- The Oracle RAC database should be supported as an interface data source
 for synchronizing data.

Configuring an Interface Data Source to an Oracle RAC Database

To configure an interface data source to an Oracle RAC database:

1.    Log on to Hyperion Shared Services Console and use Lifecycle Management to export the file, InterfaceTables.instance.xml, from Performance Management Architect artifact. You can find Performance Management Architect in Application Groups --> Foundation --> Deployment Metadata --> Shared Services Registry --> Foundation Services --> EPMA.

2.    In the InterfaceTables.instance file, add the JDBC URL, with a descriptive block, to the interface data source tag as shown below:

    <instance name="DatasourceRAC">

        <list>

            <listItem type="server">adc2130465.us.oracle.com</listItem>

            <listItem type="databaseType">Oracle</listItem>

            <listItem type="databaseVerType">OracleRAC</listItem>

            <listItem type="databaseName">rac11g123.us.oracle.com</listItem>

            <listItem type="port">1521</listItem>

            <listItem type="username">EPMADS1</listItem>

            <listItem type="password">681Kq3rgXODoR3kWgfm4ww==</listItem>

    

              <listItem type="jdbcUrl">jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=on)  (ADDRESS=(PROTOCOL=TCP)(HOST=adc2130465.us.oracle.com) (PORT=1521))  (ADDRESS=(PROTOCOL=TCP)(HOST=adc2130466.us.oracle.com) (PORT=1521))  (CONNECT_DATA=(SERVICE_NAME=rac11g123.us.oracle.com) (FAILOVER_MODE = (TYPE = SELECT) (METHOD = BASIC) (RETRIES = 180) (DELAY = 5))))

</listItem>

 

        </list>

    </instance>

3.    Use Lifecycle Management to import the InterfaceTables.instance file back into the deployment metadata.

4.    Restart the Performance Management Architect Process Manager service to refresh the interface table data source information.

Note: The following JDBC URL formats cannot be imported via interface tables: jdbc:oracle:thin:@[HOST][:PORT]:SID and jdbc:oracle:thin:@//[HOST][:PORT]/SERVICE

If you update the JDBC URL syntax incorrectly in the InterfaceTables.instance.xml file, accessing  the data source while importing or synchronizing data may cause either an ORA-12154 or an ORA-12505 database error. If you receive either of these errors, check the JDBC URL syntax.

Top of Document

Defects Fixed in 11.1.2.1.103

·         12665493 -- Using a Performance Management Architect batch script, the order of the members is sorted and displayed incorrectly.

·         12661113 -– You may be unable to perform a full deployment using a Performance Management Architect batch script. To perform a deployment, follow these steps:

Execute Deploy

Parameters(ApplicationName, InstanceName, ApplicationServer, HubProject, ClearAll,CheckIntegrity, waitforcompletion, purgeTransactions, deployOption, Notes,fullDeploy)

Values('AppName', 'Aso931', 'localhost:1423', 'Default Application Group', 'false','false', 'true', 'true', ‘AppView’, 'deploy comments sample','true');

 

fullDeploy = true: If fullDeploy flag is set to true, then a full deployment will be performed.

fullDeploy = false: If fullDeploy flag is set to false, then an incremental deployment will be performed.

Top of Document

Defects Fixed in 11.1.2.1.102

·         10402758 -- Add the new dimension type: CellTextLabel.

·         11799426 -– Default interface tables should be created for the new CellTextLabel dimensions.

·         11700577 -– The CellTextLabel dimension should not be shown when creating data synchronizations.

Top of Document

Defects Fixed in 11.1.2.1.101

·         11799602 -– Unable to update the property values during an import for shared dimensions in Performance Management Architect applications.  

Top of Document

Known Issues in This Patch

·         13606149 -- You may have a problem with mapping when you create a profile to import the ADS file for an application upgraded from version 9.3.x.

·         13147663 -- Data Synchronization cannot be launched from the Batch Client. Following is an example of launching Data Synchronization in the Batch Client:

Execute DataSynchronization
Parameters(DataSynchronizationName, DataTransformationOperator, FileName,ValidateOnly, WaitForCompletion, dataSyncLoadOptionHpMode)
Values('CVGCOMP Job Title', 'None', '
file:///C:/CvgCompLd_JobTtl.txt','false', 'true');

FileName
-If the synchronization uses an external source file for the source of the synchronization, the location of the external source file must be a URL location in which the Performance Management Architect WebTier is running. For example, the FileName should be formatted as 'file:///C:/CvgCompLd_JobTtl.txt'.

If the location of the file is on another computer (that has access to Performance Management Architect WebTier) then the URL format of the file location should be: 'file://///<server_name>:/CvgCompLd_JobTtl.txt'.

·         16959684 -- Upon Lifecycle Management Import, User Defined Attribute values that are blank or null in the source are not replacing the target values.

·         16933478 -- When synchronizing between shared and application libraries, non-array type member property values that are blank or null in the source are not replacing the target values.

·         16663135 -- Data synchronization step in Task flow continue to remain in active status if it becomes ‘Completed with Errors’; it should continue with next step instead.

·         16310436 -- In Dimension Library, expand two member trees, select base member of the second tree and left click the first member tree to collapse and select it; now second tree’s base member still not unselected and also its properties are loaded in the property grid editor.

·         15973070 -- Cloned dimensions member properties are incorrectly reported as different from that of deployed application by Compare to deployed report.

·         12768686 -- For browser preference set to Russian, In the Task flow user interface; words are unreadable in Processing Tab for the Action List and for the table with parameter name and type.

Top of Document

Applying This Patch

The section includes important information about applying this patch for Performance Management Architect.

To apply this patch:

1.    Stop all Performance Management Architect services.

2.    Stop Oracle® Hyperion Calculation Manager (Calculation Manager) and Oracle® Hyperion Profitability and Cost Management (Profitability and Cost Management), Oracle® Hyperion Essbase Studio, if they are running on the same computer where Performance Management Architect services are running.

3.    Download and unzip the downloaded patch file, 15883303_xxx.zip, to the <EPM_ORACLE_HOME>/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

Where xxx represents Windows 32-bit, 64-bit, or UNIX:

For Windows 32-bit, the patch file name is: 15883303_WINNT.zip

For Windows 64-bit, the patch file name is: 15883303_x64.zip

For UNIX, the patch file name is: 15883303_UX.zip

Note: 15883303_xxx.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.

4.    Back up the Performance Management Architect database repository.

Note: If you need to roll back this service fix, you will need to restore from this database backup. Restoring from backup will result in loss of all changes.

5.    On the computer where the Performance Management Architect Web Tier, Dimension Server, and Data Synchronization components are located, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.

6.    To apply the patch, enter the following command on one line:

Windows:
opatch.bat apply <EPM_ORACLE_HOME>\OPatch\15883303 -oh <EPM_ORACLE_HOME>
-jre <MIDDLEWARE_HOME>\jdk160_21

Note: The default for <EPM_ORACLE_HOME> is C:\Oracle\Middleware\EPMSystem11R1. The default for <MIDDLEWARE_HOME> is C:\Oracle\Middleware.

UNIX/Linux:
opatch apply <EPM_ORACLE_HOME>/OPatch/15883303 -oh <EPM_ORACLE_HOME>
-jre <MIDDLEWARE_HOME>/jdk160_21

Note: The default for <EPM_ORACLE_HOME> is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

7.    Restart all Performance Management Architect services.

8.    Restart Foundation Services.

9.    Start Calculation Manager and Profitability and Cost Management, Essbase Studio,  if you stopped these services in step 2.

10. All users should clear cached files from, and restart, their browsers.  

Top of Document

Rolling Back This Patch

To roll back a patch:

1.    Stop all Enterprise Performance Management Architect services.

2.    Stop Calculation Manager and Profitability and Cost Management, Essbase Studio, if they are running on the same computer where Performance Management Architect services are running.

3.    From a command line, change the directory to <EPM_ORACLE_HOME>/OPatch (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

4.    To roll back the patch, enter the following command on one line:
Windows:
opatch.bat rollback -id 15883303 -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>\jdk160_21

Note: The default for <
EPM_ORACLE_HOME > is C:\Oracle\Middleware\EPMSystem11R1. The default for <MIDDLEWARE_HOME> is C:\Oracle\Middleware.

UNIX/Linux:
opatch rollback -id 15883303 -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_21

Note: The default for <
EPM_ORACLE_HOME > is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

5.    Restart all Performance Management Architect services.

6.    Restart Foundation Services.

7.    Start Calculation Manager and Profitability and Cost Management, Essbase Studio, if you stopped these services in step 2.

8.    All users should clear cached files from, and restart, their browsers.

Top of Document

Troubleshooting FAQs

How can I find out which releases and patches of EPM System products are installed in a deployment?

In EPM System Release 11.x, you can use the lsinventory command to OPatch to find the release and patches that are installed in an Oracle Home. For example, enter the following command on one line:

Windows:

opatch.bat lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_21

NOTE: The default for <EPM_ORACLE_HOME> is C:/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is C:/Oracle/Middleware.

UNIX/Linux:

./opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_21

NOTE: The default for <EPM_ORACLE_HOME> is C:/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is C:/Oracle/Middleware.

Why do I get the following patch conflict error message when running OPatch?

If the patch that you apply conflicts with a previously applied patch, you may receive the following error message when running OPatch:

Patch(es) <PreviousPatch#> conflict with the patch currently being installed (<NewPatch#>).

If you continue, patch(es) <PreviousPatch#> will be rolled back and the new patch (<NewPatch#>) will be installed.

If a merge of the new patch (<NewPatch#>) and the conflicting patch(es) (<PreviousPatch#>) is required, contact Oracle Support Services and request a Merged patch.

This error is returned when one patch attempts to update a previously patched file. When this conflict happens, you can either (1) roll back the previous patch and use the new patch (this action might be appropriate if the previous patch was not critical) or (2) request a “merged patch” consisting of the new patch and the patch that it conflicts with. To request a merged patch, contact your Oracle Support representative.  

Why do I get the OUI-67078 warning message when applying OPatch?

This warning means that the patch being applied is a superset of a patch already on the deployment and the existing patch will be rolled back. The following snippet shows the context of this warning.

The following warnings have occurred during OPatch execution:
1) OUI-67078:Interim patch 12345678 is a superset of the patch(es) [77777777] in OH C:\Hyperion
-----------------------------------------------------------------------------------
OPatch Session completed with warnings.

Top of Document

 

Copyright © 2012, Oracle and/or its affiliates. All rights reserved.
http://www.oracle.com