Release 11.1.2.1.000 Patch Set (PS): 11.1.2.2.000
Readme
Who should apply this patch: This PS contains defect fixes and changes that are specific to the Oracle Exalytics In-Memory machine. You should install this PS only in the following circumstances:
· You are installing Essbase on the Exalytics In-Memory Machine, or
· There is an urgent need for a defect fix that is included in this PS
Customers considering this PS for a platform other than the Exalytics In-Memory Machine should carefully review the list of fixed defects. If there is not a truly urgent need for a defect fix included in this PS, Oracle recommends customers install the upcoming Enterprise Performance Management (EPM) 11.1.2.2.000 release, which will contain an update, instead of this patch set. To check the availability of the EPM 11.1.2.2.000 release prior to installing this PS, visit the Oracle Software Delivery Cloud (https://edelivery.oracle.com).
Oracle highly recommends that you do extensive testing before making this patch available in a general production environment.
Caution: Once applied, you cannot roll back this patch or any other Essbase 11.1.2.2.000 component patch.
Patch Type
This PS replaces files in the existing installation and does not require a full installation. This PS is a cumulative patch including all items previously released in Provider Services Release 11.1.2.1.102.
You can apply this patch to the following releases:
· Provider Services Release 11.1.2.1
· Provider Services Release 11.1.2.1.102
Other Required Patches
Patch 12732564 for EPM System Installer
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.
Applies to all supported platforms.
Applies to all supported languages.
Essbase Web Services
Web services are self-contained, modular applications that one can describe, publish, locate, and invoke over a network. Web services allow access to regular applications using a Web browser. Web services use XML to code and decode data, and SOAP (Simple Object Access Protocol) to transport it.
Essbase Web Services will expose Essbase user and administrative functionality in a services-oriented (SOA) environment via Provider Services, and allow Essbase to be easily integrated with both Oracle and third-party applications.
Defects Fixed in this Patch
Use the Defects Fixed Finder tool to review the list of defects fixed prior to release 11.1.2.2.000. This tool is available here:
https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1292603.1
Defect Number |
Defect Fixed |
• 12913916 |
In the Smart View Member Selection window, searching for members with aliases that are stored in a non-default alias table does not work. The members are not found, and no error is displayed. |
• 12896745 |
If a cube created in Essbase Studio is
deployed to Essbase and opened using Smart View, when the Studio service is
running and an ad-hoc drill-down is initiated, the following error message
may occur: Dimension signature
mismatch in |
• 13406653 |
In Smart View, when executing an Essbase Studio drill-through report on duplicate members, the error message “Cannot perform cube view operation.null” may occur. |
• 13112801 |
Open JAPI connections to Essbase may unexpectedly be terminated with the following error message: "Cannot set active application/cube. Essbase Error(1051021): You have been logged out due to inactivity or explicitly by the administrator.” |
• 13078240 |
The file <APS_HOME>\lib\essconfiguration.jar is no longer needed, and has been removed. |
• 12931820 |
Executing an MDX query may result in the following error message: Cannot perform cube view operation. Calling IEssOpMdxQuery.setQuery with needCellStatus = true may prevent this error. |
• 12913916 |
In the Smart View Member Selection window, searching for members with aliases that are stored in a non-default alias table may not work. The members are not found, and no error is displayed. |
• 12788139 |
When retrieving a qualified member name for an alias name containing “++,” an incorrect member name is returned. |
• 11694142 |
The JAPI client may not properly handle an unexpected socket closure from Essbase. |
• 12781645, 12656037 |
The JAPI client may fail to recognize the status of an Essbase data load. |
The following are the noteworthy known issues for this patch:
Essbase Web Services are by default not enabled for logging messages
The Essbase Web Services component of Provider Services is not enabled for ODL logging by default. To enable logging for Web Services, perform the following procedure:
1. Open the file logging.xml, located by default in <MIDDLEWARE_HOME>\user_projects\domains\EPMSystem\config\fmwconfig\servers\<APS_SERVER_INSTANCE>, where <APS_SERVER_INSTANCE> is the name of the Provider Services instance in WebLogic.
2. Under the <log_handlers> element, insert the following:
<log_handler name='essbase-ws-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/essbasews.log' />
<property name='maxFileSize' value='10485760'/>
<property name='maxLogSize' value='104857600'/>
</log_handler>
3. Under the <loggers> element, insert the following:
<logger name='oracle.EPMOHEWS' level='WARNING:1' useParentHandlers='false'>
<handler name='essbase-ws-handler'/>
</logger>
4. Save the file and restart Provider Services.
NOTE: level can be modified to any valid logging level.
The section includes important information about applying this patch for Provider Services.
When installing this release, replace <PATCH ID> in these instructions with the patch id 11892451.
Caution: Once applied, you cannot roll back this patch or any other Essbase 11.1.2.2.000 component patch.
To apply this patch:
1. Ensure that EPM System and Provider Services are updated to Release 11.1.2.1 or later.
2. Stop all services.
3. Back up Provider Services. For example, for a typical
Provider Services installation, back up the following directories:
<EPM_ORACLE_HOME>/products/Essbase/aps/AppServer/InstallableApps/Common/aps.ear
<EPM_ORACLE_HOME>/common/EssbaseJavaAPI/11.1.2.0/lib/ess_es_server.jar
<EPM_ORACLE_HOME>/common/EssbaseJavaAPI/11.1.2.0/lib/ess_japi.jar
<EPM_ORACLE_HOME>/products/Essbase/aps/lib/aps_upgrade.jar
<EPM_ORACLE_HOME>/upgrades/aps/upgradeApplication_ps1.bat
<EPM_ORACLE_HOME>/upgrades/aps/upgradeApplication_ps1.sh
4. Apply patch 12732564 for the EPM System Installer by executing steps 6-8 below and replacing <PATCH_ID> with 12732564.
5. Apply the patch for Provider Services Release 11.1.2.2.000, patch ID 11892451, by executing steps 6-8 below and replacing <PATCH_ID> with 11892451.
6. 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.
7. On the machine hosting Provider Services, launch command prompt and change the directory to <EPM_ORACLE_HOME>/OPatch.
8. To apply the patch, enter the following command on one
line:
Windows:
opatch.bat apply
<EPM_ORACLE_HOME>\OPatch\<patch_no> -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/<patch_no> -oh <EPM_ORACLE_HOME>
-jre <MIDDLEWARE_HOME>/jdk160_21 -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.
9. Edit $domain_home/init-info/domain-info.xml and downgrade the version of "Oracle EPM APS" template to "11.1.2.0"
For Example modify this entry –
<extention-template-ref name="Oracle EPM APS" version="11.1.2.1" location="C:\Oracle\Middleware\EPMSystem11R1\common\templates\applications\epm_aps_11.1.2.1.jar"/>
to
<extention-template-ref name="Oracle EPM APS"
version="11.1.2.0"
location="C:\Oracle\Middleware\EPMSystem11R1\common\templates\applications\epm_aps_11.1.2.1.jar"/>
10. Undeploy the existing Provider Services deployment using the Weblogic admin console.
11. Deploy Provider Services using the EPM System Configurator.
12. Perform the edit in step 9, above, again.
13. Check that Provider Services and Foundation are up and running.
You cannot roll back this or any other
Essbase 11.1.2.2.000 component patch.
Troubleshooting FAQs
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.
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.
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.
Copyright
© 2012, Oracle and/or its affiliates. All rights reserved.
http://www.oracle.com