Oracle Hyperion Provider Services

 

Release 11.1.2.2.100 Patch Set Update (PSU): 11.1.2.2.106

Readme

About this Patch. 1

Patch Type. 1

Supported Paths to this Patch. 2

Prerequisites. 2

Required User Rights. 2

Supported Platforms. 2

Supported Languages. 2

Defects Fixed in this Patch. 3

Known Issues in this Patch. 3

Applying this Patch. 3

Rolling Back this Patch. 4

Troubleshooting FAQs. 4

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

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

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

I applied the patch successfully but I don’t see the changes from the patch in the product. What should I do?. 5

About this Patch

This Readme file describes the defects fixed in this patch and the requirements and instructions for applying this patch.

Note: This patch is cumulative and includes defects fixed in earlier patches.

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 is a patch set update (PSU). This patch replaces files in the existing installation and does not require a full installation.

Supported Paths to this Patch

You can apply this patch to the following releases:

11.1.2.2.100

11.1.2.2.101

11.1.2.2.102

11.1.2.2.103

11.1.2.2.104

11.1.2.2.105

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

UNIX/Linux:

Use the account that was used to install EPM System products and has Read, Write, and Execute permissions on $MIDDLEWARE_HOME. 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. OPatches are not intended to be applied using a root user.

Supported Platforms

Applies to all supported platforms.

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

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Supported Languages

Applies to all supported languages.

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

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Defects Fixed in this Patch

Note: This patch is cumulative and includes defects fixed in earlier patches.

Defect Number

Defect Fixed

·   18091317

When Smart View Client VBAPI is used to query members performance is slow in some cases.

·   17505154

When the retrieval sheet has empty rows between members and zooming in on the member above, the empty row inserts additional empty rows between the retrieved child members.

 

Known Issues in this Patch

This patch does not contain any known issues.

Applying this Patch

The section includes important information about applying this patch for Provider Services. The <PATCH ID> is 18148649.

To apply this patch:

1.    Stop Provider Services.

2.    Download and unzip the downloaded patch file, <PATCH ID>_<PLATFORM ID>.zip, to the <EPM_ORACLE_HOME>/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

NOTE: <PATCH ID>_<PLATFORM ID>.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.

3.    On the machine hosting Provider Services, launch command prompt and change the directory to <EPM_ORACLE_HOME>/OPatch.

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

Windows:
opatch.bat apply <EPM_ORACLE_HOME>/OPatch/<PATCH ID> -oh <EPM_ORACLE_HOME>
-jre <MIDDLEWARE_HOME>/jdk160_29


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/<PATCH ID> -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_29 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

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

5.    Check that the Central Inventory exists and contains the expected set of components by entering the following command:

Windows: opatch.bat lsinventory -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_29

Unix/Linux: ./opatch lsinventory -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_29

If this command does not return the expected set of components, the /inventory directory wasn't created properly under <HYPERION_HOME> during the installation. In this case, follow the steps in “Resolving Central Inventory Issues” below before proceeding with these steps.

6.    You are prompted to enter an email address and optional password. If you ignore this prompt by selecting the Enter key, the following message is displayed: “You haven’t provided an e-mail address for notification of security issues. Do you wish to remain uninformed of security issues ([Y]es, [N]o)” enter “Y” and the installer continues to the end of the installation.  If you enter an email address and a password, the password must be from your Metalink account. If the password is invalid the installation will yield an error and stop.  If you do not know your Metalink password, leave the password blank and the installation will continue.

7.    Re-start Provider Services.

Rolling Back this Patch

To roll back a patch:

To roll back the patch, enter the following command on one line:

Windows:
opatch.bat rollback -id <PATCH ID> -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_29

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 <PATCH ID> -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME> /jdk160_29 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

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

Troubleshooting FAQs

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

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_29

UNIX/Linux:

./opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_29 –invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

I applied the patch successfully but I don’t see the changes from the patch in the product. What should I do?

When patching an .EAR file for an application, you may need to delete the cached files in the following folders in order to see the changes provided with the patch:

<MIDDLEWARE_HOME>/user_projects/domains/<DOMAIN_NAME>/servers/
<MANAGED_SERVER_NAME/tmp/

<MIDDLEWARE_HOME>/user_projects/domains/<DOMAIN_NAME>/servers/
<MANAGED_SERVER_NAME/cache