Oracle Hyperion Financial Reporting
[NOTE TO WRITERS: Go to the File or Document properties and change the title. The correct entry for Author and Company are provided in the template.]
Release 11.1.2.2.000 Patch Set Update (PSU): 11.1.2.2.505
Readme
Defects Fixed in this Patch (20639760)
Defects Fixed in Patch 11.1.2.2.504 (20068553)
Defects Fixed in Patch 11.1.2.2.502 (19606449)
Defects Fixed in Patch 11.1.2.2.501 (19128780)
Defects Fixed in Patch 11.1.2.2.500 (18659116)
Defects Fixed in Patch 11.1.2.2.315 (18631422)
Defects Fixed in Patch 11.1.2.2.314 (18412401)
Defects Fixed in Patch 11.1.2.2.313 (17671920)
Defects Fixed in Patch 11.1.2.2.311 (17213446)
Defects Fixed in Patch 11.1.2.2.305 (16484903)
Defects Fixed in Patch 11.1.2.2.303 (16088101)
Defects Fixed in Patch 11.1.2.2.302 (14625370)
Defects Fixed in Patch 11.1.2.2.300 (13997553)
Why do I get the following patch conflict error message when running OPatch?
Why do I get the OUI-67078 warning message when applying OPatch?
How can I find out which releases and patches of EPM System products are installed in a deployment?
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.
This is a patch set update (PSU).
[NOTE TO WRITERS: Add a sentence stating whether the patch Requires a full installation or a partial replacement. if its a partial replacement, The boilerplate for this statement is: This patch replaces files in the existing installation and does not require a full installation.]
[note to writers: State whether this is a cumulative or standalone Patch. If its cumulative, list the previous Patch IDs (XXXXXXXX) that are included. To find previous patch IDs, either Ask your team or look for the patch id in uninstall section of previous Readme. If Standalone, state that this patch does not include previous patches.]
You can apply this patch to the following releases:
11.1.2.2.000
11.1.2.2.300
11.1.2.2.302
11.1.2.2.303
11.1.2.2.303 PSE 16480166
11.1.2.2.303 PSE 16686640
11.1.2.2.303 PSE 16744729
11.1.2.2.305
11.1.2.2.305 PSE 17183996
11.1.2.2.311
11.1.2.2.311 PSE 17923078
11.1.2.2.313
11.1.2.2.314
11.1.2.2.315
11.1.2.2.500 PSU 18659116
11.1.2.2.501 PSU 19128780
11.1.2.2.502 PSU 19606449
11.1.2.2.504 PSU 20068553
[NOTE TO WRITERS: list the base Release(s) from which you can apply this patch and Include any prerequisite patches. TO refer to service fixes or service packs using the old nomenclature, use the fully qualified service fix/service pack version number along with the patch id, for example, 11.1.2.0.07 (12345678).]
[NOTE TO WRITERS: THis required MICROSOFT PATCH INFORMATION should be included in the following product readmes (FM, EPMA, HSF, FDM, Planning, Production Reporting, EAS) unless the patch is issued only on unix or linux platforms. Other products can delete this section.]
Microsoft has identified a security issue that could compromise Windows-based systems. Before installing this patch, verify that the Visual C++ 2005 Redistributable Package installed on the computer is current. You may search and download the latest Visual C++ 2005 Redistributable Package from:
http://www.microsoft.com/en-us/download/default.aspx
[NOTE TO WRITERS: Does this patch REQUIRE any other PATCHES FOR THE SAME PRODUCT Or for any other products? iF SO, LIST THEM HERE. If NOT, DELETE this section.
This Oracle Hyperion Financial Reporting, Fusion Edition, Release 11.1.2.2.000 patch requires these other EPM System patches:
Oracle Hyperion Shared Services patch 14020629
Oracle Hyperion Reporting and Analysis for Workspace patch 13936087
Oracle Hyperion Reporting and Analysis for Interactive Reporting patch 14200932
Both the Oracle Hyperion Shared Services, and Oracle Hyperion Reporting and Analysis for Workspace, patches must be applied on any machine(s) where Foundation Services is installed. The Oracle Hyperion Reporting and Analysis for Interactive Reporting patch must be applied on any machine(s) where the Oracle Hyperion Reporting and Analysis for Interactive Reporting is installed. This Oracle Hyperion Financial Reporting, Fusion Edition, Release 11.1.2.2.303 patch must be applied on any machine(s) where Oracle Hyperion Financial Reporting, Fusion Edition, Release 11.1.2.2.000 or Oracle Hyperion Financial Reporting, Fusion Edition, Release 11.1.2.2.300 is installed. There is no required order for these patches. Apply all four patches in any order and then redeploy all Web applications.
[NOTE TO WRITERS: Delete the windows and unix sections as appropriate based on what platforms the patch is for.]
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:
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.
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.
[NOTE TO WRITERS: dOES tHIS patch conflict with ANY OTHER PATCHES FOR the same product or ANY OTHER PRODUCT? If so, list them. IF NOt, Delete THIS Section.]
This patch is applicable for all platforms supported by Oracle Hyperion Financial Reporting, Fusion Edition, Release 11.1.2.2.000.
This patch is applicable for all languages supported by Oracle Hyperion Financial Reporting, Fusion Edition, Release 11.1.2.2.000.
[NOTE TO WRITERS: present this list in a table format.
[NOTE TO WRITERS: do not copy descriptions from bug db. they need to be rewritten to be meaningful from the customer point of view.]
[NOTE TO WRITERS: Verify that the Defects Fixed list in the Readme includes: (1) All customer-reported defects regardless of severity; (2) All Sev 1, 2, and 3 defects whether customer reported or not; (3) Sev 4 at discretion of team.
NOTE: For Sev 3, non-customer-reported defects: The objective is to let customers know what areas of the product were touched in the patch, so they know what areas to test. Use your discretion for Sev 3 defects that are clearly internal and would not be in an area that customers would need to test.
Security vulnerabilities are not typically included. The guideline is: If a security bug is reported by a customer and if the issue is fixed across the EPM suite, then we can include that bug in the readme. Otherwise - if the problem is fixed in one product but still exists in other products - we cant include them in the readme.]
The text in the first column of the table must start
with a bullet in order for the import into the Defects Fixed Finder tool to
work correctly. Like so:
|
Defect Number |
Defect Fixed |
|
20272050 |
Some reports may spill over to the next page for PDF output. |
|
20353816 |
Substitution variables cannot be selected as the default member in Financial Reporting Studio. |
|
20487730 |
A Financial Reporting book that uses a PDF for a cover page cannot be displayed in a browser. |
|
20659406 |
When using Firefox, the member selection window does not refresh properly if closed using the 'X' in the upper right corner of the window. |
[NOTE TO WRITERS: present this list in a table format.
[NOTE TO WRITERS: do not copy descriptions from bug db. they need to be rewritten to be meaningful from the customer point of view.]
[NOTE TO WRITERS: Verify that the Defects Fixed list in the Readme includes: (1) All customer-reported defects regardless of severity; (2) All Sev 1, 2, and 3 defects whether customer reported or not; (3) Sev 4 at discretion of team.
NOTE: For Sev 3, non-customer-reported defects: The objective is to let customers know what areas of the product were touched in the patch, so they know what areas to test. Use your discretion for Sev 3 defects that are clearly internal and would not be in an area that customers would need to test.
Security vulnerabilities are not typically included. The guideline is: If a security bug is reported by a customer and if the issue is fixed across the EPM suite, then we can include that bug in the readme. Otherwise - if the problem is fixed in one product but still exists in other products - we cant include them in the readme.]
The text in the first column of the table must start
with a bullet in order for the import into the Defects Fixed Finder tool to
work correctly. Like so:
|
Defect Number |
Defect Fixed |
|
19428142 |
Command Line Scheduling fails if the password contains special characters. |
|
19516449 |
Reports using formulas with grid columns that are keywords have an error. For example, Sum(IE:IF). |
|
19619992 |
When grids have 'Page break before' enabled and the POV has no data the grid size increases to create extra pages. |
|
19640733 |
Lines are suppressed in PDF output after upgrading. |
|
19708228 |
For PDF output when a grid extends to a next page the indentation is incorrect. |
|
19957406 |
Batch scheduling fails if the password contains special characters. |
|
19958126 |
Unable to add or remove Email IDs for Batch Scheduling. |
|
19971393 |
When a larger book is requested as HTML Preview or PDF Preview the 'Processing - Please Wait...' screen disappears too long before the results are displayed. |
|
20020580 |
Grid property 'Add bottom border in all pages' fails if the row after the last row in a page is hidden. |
|
20042254 |
Grids with 'centered' horizontal position are only centered on the first page in PDF output. |
|
20081678 |
Sometimes database connections are lost when multiple users are creating datasources at the same time. |
|
20100221 |
Incorrect rounding sometimes occurs for decimal places set to zero.. |
[NOTE TO WRITERS: present this list in a table format.
[NOTE TO WRITERS: do not copy descriptions from bug db. they need to be rewritten to be meaningful from the customer point of view.]
[NOTE TO WRITERS: Verify that the Defects Fixed list in the Readme includes: (1) All customer-reported defects regardless of severity; (2) All Sev 1, 2, and 3 defects whether customer reported or not; (3) Sev 4 at discretion of team.
NOTE: For Sev 3, non-customer-reported defects: The objective is to let customers know what areas of the product were touched in the patch, so they know what areas to test. Use your discretion for Sev 3 defects that are clearly internal and would not be in an area that customers would need to test.
Security vulnerabilities are not typically included. The guideline is: If a security bug is reported by a customer and if the issue is fixed across the EPM suite, then we can include that bug in the readme. Otherwise - if the problem is fixed in one product but still exists in other products - we cant include them in the readme.]
The text in the first column of the table must start
with a bullet in order for the import into the Defects Fixed Finder tool to
work correctly. Like so:
|
Defect Number |
Defect Fixed |
|
18916715 |
The 'Processing, please wait' icon and message disappear after several seconds when a book is processing reports which leads users to assume the process has hung. |
|
19056412 |
Report grids that expand over multiple pages now have the ability to provide a closing bottom line by selecting the new 'Add bottom border in all pages' checkbox for the grid in Financial Reporting Studio. |
|
19223299 |
Legends on line charts are not shown and the size and position of the charts cannot be controlled after applying patch 11.1.2.2.315. |
|
19237325 |
The 'processing' page does not appear consistently for large books. |
|
19243514 |
A grid cell with black background will disappear when exported to a PDF. |
|
19278539 |
The 'MemberProperty' function does not work if there is any other property in the same cell. |
|
19316408 |
PDF bookmarks in 11.1.2.2 do not have GoTo capability. |
|
19326793 |
A PDF report that worked in patch 302 has not worked in later patches. |
|
19353338 |
Using the Round( ) function for formatting does not work as expected. |
|
19471378 |
If a report has two grids and the first grid expands over multiple pages, the second grid will appear between the first two pages of the first grid. |
|
19485462 |
If a book that contains Microsoft Word documents is edited so that it displays 'custom text' for these documents, the page number will be wrong when printed to a PDF. |
|
19628553 |
XBRL functionality has been removed from Financial Reporting Studio starting with this patch, 11.1.2.2.502. Please visit the 'Oracle Hyperion Financial Reporting XBRL Functionality Statement of Direction (Doc ID 1508685.1)', CTRL+click_this_link, for details. |
[NOTE TO WRITERS: present this list in a table format.
[NOTE TO WRITERS: do not copy descriptions from bug db. they need to be rewritten to be meaningful from the customer point of view.]
[NOTE TO WRITERS: Verify that the Defects Fixed list in the Readme includes: (1) All customer-reported defects regardless of severity; (2) All Sev 1, 2, and 3 defects whether customer reported or not; (3) Sev 4 at discretion of team.
NOTE: For Sev 3, non-customer-reported defects: The objective is to let customers know what areas of the product were touched in the patch, so they know what areas to test. Use your discretion for Sev 3 defects that are clearly internal and would not be in an area that customers would need to test.
Security vulnerabilities are not typically included. The guideline is: If a security bug is reported by a customer and if the issue is fixed across the EPM suite, then we can include that bug in the readme. Otherwise - if the problem is fixed in one product but still exists in other products - we cant include them in the readme.]
The text in the first column of the table must start
with a bullet in order for the import into the Defects Fixed Finder tool to
work correctly. Like so:
|
Defect Number |
Defect Fixed |
|
18515677 |
A Financial Reporting report has Duplicate Command error after upgrading to 11.1.2.2. |
|
18813075 |
A Financial Reporting report containing a separator image between grids displays incorrectly in PDF and HTML preview after upgrading to 11.1.2.2. |
|
18896490 |
A Financial Reporting report prints to PDF with increased header size and gaps between grid rows. |
|
18918475 |
A Financial Reporting report does not spread header text correctly in merged cells. |
|
18919043 |
'Fix Height' incorrectly wraps the text for a Planning datasource after upgrading to 11.1.2.2. |
|
19015266 |
In Financial Reporting Studio clicking on the modify icon to enter a member name for a dimension causes a 'Subscript out of range error.' |
[NOTE TO WRITERS: present this list in a table format.
[NOTE TO WRITERS: do not copy descriptions from bug db. they need to be rewritten to be meaningful from the customer point of view.]
[NOTE TO WRITERS: Verify that the Defects Fixed list in the Readme includes: (1) Only customer reported s1 and s2 defects should be documented (2) For defects found during and corrected in the release regardless of severity they should NOT be included in the readme. (3) Only defects found internally that require specific customer testing should be documented. (4) Use discretion for S3 (internal or customer found) - err to not including them as opposed to including them.
Security vulnerabilities are not typically included. The guideline is: If a security bug is reported by a customer and if the issue is fixed across the EPM suite, then we can include that bug in the readme. Otherwise - if the problem is fixed in one product but still exists in other products - we cant include them in the readme.]
The text in the first column of the table must start with a bullet in order for the import into the Defects Fixed Finder tool to work correctly. Like so:
|
Defect Fixed |
|
|
17474319 |
The Financial Reporting report page margins are narrower in reports displayed in PDF Preview. |
|
18397374 |
The substitution variable name is not displaying correctly when used in the User POV or in a grid in a Financial Reporting report. |
|
18467193 |
A Financial Reporting report with a chart containing an Essbase alias attribute that contains an apostrophe does not display the chart. |
|
18519845 |
The grid positioning and formatting of Financial Reporting reports is not consistent in PDF Preview. |
|
18519890 |
When a Financial Reporting report is imported some column widths are adjusted that result in format changes in PDF Preview. |
|
18536030 |
A Financial Reporting report containing multiple grids with multiple database connections does not complete successfully in PDF Preview. |
|
18560765 |
When running Financial Reporting Studio on a Windows 7 64-bit client machine and you insert a grid or open member selection and then click ALT-Tab to switch applications, the client machine will become unresponsive. |
|
18606453 |
'Internet Explorer cannot display the page' error received when running a Financial Reporting book in PDF after applying patch 11.1.2.2.313. |
|
18633554 |
HTTP 500 error received when running a Financial Reporting report as a PDF after applying patch 11.1.2.2.313. |
|
18652474 |
Financial Reporting reports that use a second sorting criteria have the last two columns reversed. |
[NOTE TO WRITERS: present this list in a table format.
[NOTE TO WRITERS: do not copy descriptions from bug db. they need to be rewritten to be meaningful from the customer point of view.]
[NOTE TO WRITERS: Verify that the Defects Fixed list in the Readme includes: (1) All customer-reported defects regardless of severity; (2) All Sev 1, 2, and 3 defects whether customer reported or not; (3) Sev 4 at discretion of team.
NOTE: For Sev 3, non-customer-reported defects: The objective is to let customers know what areas of the product were touched in the patch, so they know what areas to test. Use your discretion for Sev 3 defects that are clearly internal and would not be in an area that customers would need to test.
Security vulnerabilities are not typically included. The guideline is: If a security bug is reported by a customer and if the issue is fixed across the EPM suite, then we can include that bug in the readme. Otherwise - if the problem is fixed in one product but still exists in other products - we cant include them in the readme.]
The text in the first column of the table must start
with a bullet in order for the import into the Defects Fixed Finder tool to
work correctly. Like so:
|
Defect Number |
Defect Fixed |
|
18608720 |
'Fix Height' not working for rows with merged columns in reports |
|
18631388 |
A Financial Reporting report containing multiple grids with multiple database connections does not complete successfully in PDF Preview |
|
18631408 |
The Financial Reporting report page margins are narrower in reports displayed in PDF Preview |
|
18631434 |
A Financial Reporting report with a chart containing an Essbase alias attribute that contains an apostrophe does not display the chart |
|
18631448 |
Using 'Page Break Before' with Position None/Relative has incorrect positioning |
|
18631465 |
New 'Adjust Column width to Fit' setting is randomly applied to imported reports from older versions |
|
18631493 |
When running Financial Reporting Studio on a Windows 7 64-bit client machine and you insert a grid or open member selection and then click ALT-Tab to switch applications, the client machine will become unresponsive |
|
18645530 |
PDF reports fail with HTTP 500 error after installing patch 11.1.2.2.313 or 314 |
|
18652653 |
Using a second sorting criteria results in last two columns reversed |
[NOTE TO WRITERS: present this list in a table format.
[NOTE TO WRITERS: do not copy descriptions from bug db. they need to be rewritten to be meaningful from the customer point of view.]
[NOTE TO WRITERS: Verify that the Defects Fixed list in the Readme includes: (1) All customer-reported defects regardless of severity; (2) All Sev 1, 2, and 3 defects whether customer reported or not; (3) Sev 4 at discretion of team.
NOTE: For Sev 3, non-customer-reported defects: The objective is to let customers know what areas of the product were touched in the patch, so they know what areas to test. Use your discretion for Sev 3 defects that are clearly internal and would not be in an area that customers would need to test.
Security vulnerabilities are not typically included. The guideline is: If a security bug is reported by a customer and if the issue is fixed across the EPM suite, then we can include that bug in the readme. Otherwise - if the problem is fixed in one product but still exists in other products - we cant include them in the readme.]
The text in the first column of the table must start
with a bullet in order for the import into the Defects Fixed Finder tool to
work correctly. Like so:
|
Defect Number |
Defect Fixed |
|
18416099 |
The paper size always defaults back to Letter in the Financial Reporting Book Editor when the book is saved. |
|
18397188 |
When scheduling a Financial Reporting batch with a report containing attribute dimension defined in the grid, the snapshot output returns incorrect values. |
|
18396096 |
In a Financial Reporting Book containing external content Microsoft Word .docx documents, the page numbers are not printed on the Microsoft Word .docx documents in Complete Book in PDF.
Note: The Microsoft Word document included in the Financial Reporting Book must be a .docx document, and a page number must be defined in the footer of the .docx document. |
|
18391558 |
When scheduling a Financial Reporting batch with a report containing attribute dimension defined in the grid, the snapshot output returns incorrect values. |
|
18389759 |
When editing an imported Financial Reporting report in Smart View receive an http 500 error message. |
|
18361177 |
Financial Reporting reports that include a period character in the report name cannot be launched from a related content link. |
|
18297623 |
A Financial Reporting report that is exported as 'fully formatted' will lose the number formatting when refreshed in Smart View. |
|
Defect Number |
Defect Fixed |
|
17303151 |
When running a batch that contains a Financial Reporting report with a grid with multiple database connections, the batch fails with an 'Error: An error was encountered when processing your request. Please check the web server logs for additional details when previewing POV in the batch.' |
|
17474319 |
The page margins are narrower than the previous releases in PDF output. |
|
17495169 |
The Respond to Prompt values is restored to the default values when refreshing the report in Workspace. |
|
17546156 |
The following error is displayed during start up for high availability configuration: EPMSystem:FinancialReporting1 is non-clusterable, and you have tried to bind more than once from two or more servers. Such objects can only be deployed from one server. |
|
17549397 |
Setting the 'Row - Page Break' property setting to 'Top' causes grid alignment issues for grids that span multiple pages in PDF Preview. |
|
17647698 |
The conditional formatting is not honored in Financial Reporting reports that contain supporting details and conditional formatting applied to the same cells. |
|
17720356 |
The row heights in a grid do not work correctly with planning cell text values in PDF Preview. |
|
17754883 |
Unable to format Russian characters with bold or italic fonts. |
|
17758599 |
When the 'Freeze Grid Headers' setting for columns is set to 'On', it is not honored in HTML Preview when using Internet Explorer 9 browser. |
|
17873569 |
The batch scheduler auto cleanup parameters are not working for batch jobs. |
|
17883761 |
The setting to hide the grid in a report in Financial Reporting Studio is not being honored in HTML Preview or PDF Preview. |
|
17937562 |
When importing a Financial Reporting report via Smart View into Microsoft Excel, the rows are shifted down on the first page. |
|
17967318 |
The scrollbars for the grid are barely visible in Financial Reporting Studio in Windows 7 if 'Visual Styles' is set. |
|
18113347 |
Planning user are able to view members in the respond to prompt dialog box when running a report that they have not been granted permission to view in Planning. |
|
18111912 |
When running a Financial Reporting Batch to generate the Budget Book HTML output, the index.html and the related files are not grouped together in the same folder. |
|
18153547 |
A user with Edit Permission of 'No Access' to a related content report can still see the related content report. |
|
18163591 |
A Planning user can see members in the User POV member selection dialog box in Financial Reporting Studio that they have not been granted permission to view in Planning. |
|
18199784 |
If the last folder name is the last portion of its parent folder, importing a report to this folder will import it to a different folder. |
|
18262955 |
The setting to hide the grid in a report in Financial Reporting Studio is not being honored in HTML Preview. |
|
18283492 |
Column headers are not displayed correctly when merged in certain report designs in HTML Preview. |
|
Defect Number |
Defect Fixed |
|
16018600 |
Appearance of reports is altered when exporting to Microsoft Excel. |
|
16600723 |
Financial Reporting reports that contain merged prompts may not refresh correctly in Smart View. |
|
16820390 |
In Financial Reporting, if the data values contain more than 14 digits and the option 'Adjust Column Width to Fit' is set, then the data values in the report may be truncated in HTML Preview. |
|
16863828 |
The Book Editor cannot display the full report name if the report name is too long. |
|
16902756 |
When using OAM authentication, a datasource error is displayed when inserting a Function Grid in a Microsoft Word or Microsoft Excel document. |
|
16915183 |
Exporting to Microsoft PowerPoint or Microsoft Word fails if the default preference is set to PDF Preview. |
|
16923088 |
If a text object has shading set to black, PDF Preview cannot show black as the background, but it will show a white background. |
|
16933844 |
A batch that contains a book with a Microsoft Word document that includes FRExecute statements cause the Financial Reporting server to stop responding after running the batch job the 2nd or 3rd time. |
|
16936233 |
After applying the 11.1.2.2.303 PSU, charts do not display in some Financial Reporting reports. |
|
16939194 |
In a Financial Reporting report, setting SuppressRepeat on a row fails if the previous row is a formula row. |
|
17086642 |
After applying the 11.1.2.2.305 PSU, displaying a report in PDF Preview generates an error. |
|
17206255 |
After applying the 11.1.2.2.305 PSU, a hidden grid is displayed in HTML Preview. |
|
17256635 |
Font size automatically changes in some pages in PDF output. |
|
17307957 |
When exporting a Financial Reporting report as query-ready from Workspace, text and formula rows are displayed in the exported grid, resulting in errors when refreshing via Smart View. |
|
17322747 |
The Financial Reporting server may become unresponsive when executing reports using the Essbase JAPI driver and retrieving attributes for a large number of members. |
|
17342471 |
After applying the 11.1.2.2.305 PSU, certain reports and books failed in PDF Preview. |
|
17345620 |
When scheduling a batch using the bursting option, the text functions BatchPovMember() and BatchPovAlias() do not return the correct values. |
|
17383760 |
After applying the 11.1.2.2.305 PSU, certain reports generate an extra page in PDF Preview. |
|
17443601 |
In Financial Reporting Studio, the title bar does not display the new report name after saving the report using 'Save As'. |
|
17464361 |
On a Windows 7 64 bit client machine, when you open Member Selection in Financial Reporting Studio, and then perform an Alt-Tab to switch to another application will result in Financial Reporting Studio to become in an unresponsive state. |
|
17479708 |
When a page break is used, the grid runs into the second page in PDF output. |
|
17529659 |
Connection leaks when executing certain non-Essbase books. |
|
Defect Number |
Defect Fixed |
|
14617332 |
When a row and column template is used in a Financial Reporting report, the row formulas always take precedence over column formulas. |
|
15874457 |
When opening an expanded member in Financial Reporting reports, the report top-level member is displayed instead of the expanded member, requiring users to scroll down to their former position in the report. |
|
15957851 |
After upgrading from Financial Reporting, Release 11.1.2.1 to Financial Reporting, Release 11.1.2.2, and the alignment is not bidirectional compliant when running Financial Reporting reports in PDF Preview. |
|
15966972 |
Certain PDF reports feature overlap among grids in the report body in PDF Preview. |
|
15999541 |
The Table of Content in a book which contains a report containing a FRExecute document should be the same for HTML Preview and PDF Preview. |
|
16191268 |
When using Internet Explorer 9, horizontal and vertical bars are displayed in EPM Workspace after displaying the prompt dialog. |
|
16209827 |
Sometimes custom headings and colors specified for merged columns are not displayed in multi-column Financial Reporting reports that contain two or more dimensions in one or more columns. |
|
16217736 |
When the paper size is set to A3 in the book editor property setup of a Financial Reporting Book, the Complete Book in PDF prints in paper size A4. |
|
16247974 |
Additional row gets added when refreshing the Microsoft Excel sheet exported from Workspace. |
|
16284677 |
When viewing a Hyperion Financial Report in PDF format, the underlined column headers do not show the underline when the header contains two or more lines. |
|
16304293 |
Depending on the grid alignment defined in the report, grid alignment may be incorrect in PDF files for reports migrated from Financial Reporting, Release 11.1.1.x. |
|
16312930 |
Bursting batch job cannot be finished if email option is selected and bursting more than 30 members. |
|
16362069 |
In a Financial Reporting Studio, when a row or column formula is selected the row formulas always take precedence over the column formulas and other options are disabled. |
|
16403507 |
PDF output format is changed in 11.1.2.2.302 PSU. |
|
16423654 |
When a report has multiple grids, their positions are maintained in HTML preview. |
|
16431373 |
User gets HTTP 401 error when multiple users are doing the member selection at the same time from Workspace. |
|
16438989 |
User gets HTTP 401 error when multiple users are doing the member selection at the same time from Workspace. |
|
16478056 |
User gets HTTP 401 error when multiple users are doing the member selection at the same time from Workspace. |
|
16486198 |
Grid properties panel is truncated in Financial Reporting Studio if the system locale is Hebrew. |
|
16492280 |
When exporting a Financial Reporting report to Smart View using 'Export Query Ready' option, then user gets an 'XML Load Error' message. |
|
16515686 |
ORA-00060 Deadlock error in server_messages_repositoryservices.log during batch bursting execution. |
|
16537102 |
Table of Contents always shows as 'Portrait' orientation in Complete Book in PDF even if the orientation was set as 'Landscape' orientation in book editor. |
|
16537618 |
When the header is locked in grids, user can get script error when importing reports into Smart View. |
|
16547181 |
When a user tried to open an attachment generated by batch bursting output with more than 30 members, Microsoft Outlook will become unresponsive and have to be shutdown. |
|
16581922 |
You cannot save a snapshot report to a folder created in Financial Reporting Studio. |
|
16674816 |
ManageUserPov utility throws ClassNotFoundException when doing export operation. |
|
16686350 |
When the paper size is set to A3 in the book editor property setup of a Financial Reporting Book, the Complete Book in PDF prints in paper size A4. |
|
16709123 |
When exporting a Financial Reporting report to Microsoft Excel or importing to Smart View, the number formatting is not correct. |
|
16709398 |
Multiple-line text row in a grid displays across multiple cells in HTML Preview. |
|
16725391 |
When the paper size is set to A4 in the book editor property setup of a Financial Reporting Book, the Complete Book in PDF prints in paper size Letter. |
|
16732011 |
In a Financial Reporting report that contains multiple grids, in the bottom grid in a multi-grid report, where the bottom two grids have positioning of left and relative, overlaps with grid above in PDF Preview. |
|
16744260 |
When exporting a Financial Reporting report to Microsoft Excel, the cells that contain text with embedded numbers lose their content. |
|
16788897 |
In a Financial Reporting report, the spaces between grid columns are not honored or displayed in PDF output. |
|
16826505 |
In a Financial Reporting report using a Planning Details database connection, the cell text is sometimes suppressed in PDF Preview. |
|
16837386 |
When using Internet Explorer 9, horizontal and vertical bars are displayed in EPM Workspace after displaying in the member selection, User POV, and prompt dialog. |
|
16862076 |
In Financial Reporting Studio, when selecting PDF Preview of a Financial Reporting report PDF file is being generated on C drive. |
|
16864472 |
Unable to do any Workspace related operations after opening Financial Reporting report in PDF Preview when using FireFox browser. |
|
16867510 |
In a Financial Reporting report, if the text object inside the report contains 'TAB' character, then PDF Preview of the report will display blank in the report viewer. |
|
16869478 |
When using Internet Explorer 9, horizontal and vertical bars are displayed in EPM Workspace after displaying the prompt dialog. |
|
16872822 |
In a Financial Reporting Book that contains an external Microsoft Word document with a FRExecute function, the grid in the Microsoft Word document is not displayed correctly in Complete Book in PDF. |
|
Defect Number |
Defect Fixed |
|
15941485 |
When scheduling a batch for bursting, the data retrieved is based on the User POV for all the bursting members instead of using the Batch POV. |
|
15953656 |
In a Financial Reporting report, a chart will not be displayed if the report contains an Essbase attribute with an apostrophe character in the alias name. |
|
15957851 |
PDF preview doesn't work property after upgrading from 11.1.2.1 to 11.1.2.2 for some reports. |
|
15999541 |
When a document or HTML file with FRExecute function is included in the book, the table of content displayed in HTML and PDF are not same. |
|
16014317 |
When using Internet Explorer 9, in the Respond to Prompts window, the check box adjacent to the 'Edit Member Names' option is large. |
|
16022132 |
In Financial Reporting report, table will not display any entity with "<" or ">" sign in name. |
|
16034388 |
When clicking on expansions arrow, expanded rows are blank. |
|
16038465 |
In a Financial Reporting report containing expansions, when clicking on the expansion arrow the expanded rows are empty. |
|
16099976 |
When Financial Reporting report is run inside SSO TAM, the TAM cannot interpret the error returned and displays error 401--Unauthorized. |
|
16101869 |
If a Financial Reporting report has more than one grid, then PDF Preview is not working for some reports. |
|
16175079 |
In Financial Reporting report, PDF Preview is not working after applying 11.1.2.2.302 patch set update. |
|
16191356 |
In Financial Reporting report, the "Indent Each Generation" is not working in PDF Preview after applying 11.1.2.2.302 PSU. |
|
16223075 |
PDF preview failed for some reports after applying 11.1.2.2.302 PSU |
|
16245501 |
Incorrect menu under Tools menu shown up after applying 11.1.2.2.302 PSU |
|
16250404 |
When exporting to excel as fully formatted format, negative number was formatted as text instead of number. |
|
Defect Number |
Defect Fixed |
|
6578543 |
Ability to add a cover page before the table of contents in a book when run as a 'Complete Book in PDF'. |
|
6586193 |
Ability to position the table of contents after a cover page in a book when run as a 'Complete Book in PDF'. |
|
13794304 |
When using Internet Explorer 9, horizontal and vertical bars are displayed in EPM Workspace after displaying the prompt dialog. |
|
14279634 |
Financial Reporting Studio install does not provide support for Norwegian language. |
|
14404191 |
In a Financial Reporting Book, provide the ability to insert a title page before the table of contents in a Complete Book in PDF. |
|
14461604 |
When refreshing a Financial Reporting report in Smart View, an error is displayed: ' Invalid grid. Either rows or columns have zero members. Please check suppression options and try your action again.' |
|
14461654 |
Custom headers are exported when exporting a Financial Reporting report in query ready mode. |
|
14509083 |
If a Financial Reporting Book contains a PDF document with bulleted items in the PDF document, the text in the entire PDF document is not displayed correctly when the Book is run as a Complete Book in PDF. |
|
14521217 |
In Financial Reporting Studio, if you select Web Preview and then try to change the Point of View, the error 'An error has occurred in the script on this page...Object does not support this action.' Is displayed. |
|
14534952 |
When a Financial Reporting Book is executed and returns no results, the information message "Book contains no results" is not displayed correctly in Japanese. |
|
14538700 |
If a Financial Reporting Book's static HTML table of contents page which contains multiple Book POV members, and the parent node in the table of contents that has any child nodes, then the parent node should be header text and not a dynamic link. |
|
14587607 |
When exporting a Financial Reporting report as a fully formatted report, all negative numbers in the report are formatted as text. |
|
14617332 |
When a row and column template is used in a Financial Reporting report, the row formulas always take precedence over column formulas. |
|
14617512 |
In a Financial Reporting report, the custom headings are not retained in the rows below the row and column template. |
|
14649908 |
After upgrading from 9.3.3 to 11.1.2.2, the headers are truncated when viewing the Financial Reporting reports in PDF Preview. |
|
14657357 |
When a conditional suppression condition is applied to a row in a Financial Reporting report, the data is being suppressed even though data appears in a column. |
|
14672851 |
In EPM Workspace, the Point of View is not being refreshed correctly when switching between two Financial Reporting reports. |
|
14680066 |
When a Financial Reporting report is exported as fully formatted report to Microsoft Excel, the pages are not sorted correctly in Microsoft Excel. |
|
14749940 |
A Financial Reporting Book's static HTML table of contents page with multiple Book POV members, the parent node in the table of contents has any child nodes, and then the parent node should be header text and not a dynamic link. |
|
14782151 |
In a Financial Reporting Book, the table of contents should display the same for HTML Preview and PDF Preview of the Book. |
|
14782163 |
In a Financial Reporting report, if a member label is formatted to indent 'x' characters, and the member label is too large to fit in the column, then the second row of the wrapped member label should also indent 'x' characters. |
|
14782201 |
In a Financial Reporting Book, add the ability to create a cover page before the table of contents. |
|
14798359 |
In Financial Reporting Studio, when selecting PDF Preview of a Financial Reporting report, a PDF file is being generated on C drive. |
|
14800532 |
Search performance in Financial Reporting member selection when searching for 0 level members. |
|
14827827 |
In a Financial Reporting Book, when changing the paper size setting to A3, the setting is not retained when saving the Financial Reporting Book. |
|
14842752 |
Column headers are not being displayed in Financial Reporting reports in HTML and PDF when the member names are enclosed in <>. |
|
15839312 |
In a Financial Reporting report a '1' is being displayed in the top left corner of all grids in a report. |
|
15880698 |
Unable to create a database connection to a Hyperion Financial Management datasource in Financial Reporting Studio. |
|
15891872 |
When a Financial Reporting report is exported to Microsoft Excel, a quote mark is added to the values with decimals resulting in the values being treated as text in Microsoft Excel. |
|
15898962 |
A Financial Reporting report when viewed in PDF Preview is displaying an extra line at the bottom of the grid. |
|
15929042 |
When a Financial Reporting report is exported to Microsoft Excel as a fully formatted report, a quote mark is added to the values, resulting in the values being treated as text in Microsoft Excel. |
|
15936862 |
In Financial Reporting Studio, add a row level property for a grid to add trailing dots after the member label that extend the width of the row header. |
|
15972015 |
In a Financial Reporting report, when you select Format, Alignment, Indent Increase For Each Generation By, the formatting changes are not applied to the report. |
|
16034517 |
When a Financial Reporting report is exported to Microsoft Excel as a fully formatted report, a quote mark is added to the values, resulting in the values being treated as text in Microsoft Excel. |
|
16038456 |
In Financial Reporting report the text displayed in text boxes are truncated when report is run in PDF Preview. |
|
Defect Number |
Defect Fixed |
|
11828123 |
Member selection does not respond when the primary Essbase database server in an Essbase cluster goes down. |
|
11828181 |
A Financial Reporting report fails to display correctly when expansions are selected the primary Essbase database server in an Essbase cluster goes down. |
|
11830863 |
Financial Reporting Batch fails to complete successfully when the primary Essbase database server in an Essbase cluster goes down while the batch is running. |
|
11830884 |
Financial Reporting Book fails to complete successfully when the primary Essbase database server in an Essbase cluster goes down while the book is running. |
|
13599053 |
Date and Time are not localized in a scheduled batchs detail information. |
|
13631641 |
The annotations summary is not being printed correctly in PDF reports. |
|
13643760 |
The Respond to Prompt menu launches Preview User POV if Preview User POV is on. |
|
13704460 |
An error is displayed if a Financial Reporting report is added by the use of a Function Grid to a Microsoft Word document when the merge area contains hidden fields. |
|
13724730 |
After providing different annotation permissions to a user, not all permissions are registered. |
|
13772854 |
You are unable to create a new annotation using the right-click menu on FF10 browser on MAC OS. |
|
13789080 |
Unable to type in member name in the Advanced Member Selection dialogs. |
|
13801312 |
A new version of a Financial Reporting Book or Batch created using 'Save As' is owned by the administrator user and not by the current user performing the 'Save As' operation. |
|
13812997 |
In the 'Database Connection' dialog, the 'OK' button is not displaying correctly in internet Explorer 9 when the browser language is set to Italian. |
|
13821755 |
An error is displayed if a Financial Reporting report is added by the use of a Function Grid to a Microsoft Word document when the merge area contains hidden fields. |
|
13845029 |
The 'OK' and 'Cancel' buttons were not fully displayed on the 'Select Database Connection' dialog. |
|
13854838 |
When viewing a Financial Reporting Book in HTML, and selecting to view an HTML document containing and FRExecute function, the charts and images are not displayed. |
|
13875012 |
In Internet Explorer, you are unable to create a new annotation on a text object by right-clicking. |
|
13898962 |
Related content does not work under Financial Reporting for member names with the ampersand, & character. |
|
13919896 |
Financial Reporting does not export textual data correctly when exporting a report that uses Planning Details database connection. |
|
13929626 |
The Batch POV is not retained when viewing or editing batch properties. |
|
13932388 |
When scheduling a batch, the Preview list in the bursting options is unable to get more than 191 elements. |
|
13939806 |
Unable to copy members from a .csv file when bursting a batch, if the .csv file contains more than 200 lines. |
|
13942174 |
Member names that contain brackets do not display correctly in Financial Reporting reports. |
|
13951640 |
You cannot run reports on duplicated Essbase members from HPCM with a MDX query. |
|
13955653 |
When importing a Financial Reporting report into Smart View, the worksheet tab displays the report description instead of the report name. |
|
13991006 |
A HARSnapin error occurs when opening migrated Financial Reporting reports in Financial Reporting Studio. |
|
14001680 |
In PDF Preview, after changing a member on the User POV, the Preview User Point of View dialog is displayed again. |
|
14010509 |
The User POV for multiple data sources does not reset. |
|
14019598 |
You are unable to run books that use the AND condition. |
|
14035620 |
Number formatting is not honored in PDF preview from Financial Reporting Studio. |
|
14058120 |
Annotations for book member selection are not returned. |
|
14059426 |
In annotation dialogs and tool tips, the apostrophe character is not displayed correctly. |
|
14059826 |
When browser language is set to French, the Batch Scheduler dialog displays several truncated strings. |
|
14064027 |
A warning message displays even when a valid member is selected under Financial Reporting POV. |
|
14076596 |
Financial Reporting OPatch will not be applied correctly on a server that only has Oracle Disclosure Management installed. |
|
14145197 |
Running a batch using bursting options finishes successfully but disappears from the Batch Scheduler. |
|
14169253 |
In PDF preview, the text member values of the lower grid overlaps the values of the upper grid. |
|
14175011 |
Decimal points are shifted while scheduling a Financial Reporting book as PDF. |
|
14192964 |
Exporting a Financial Reporting report in query ready mode, the percentage values are not displayed correctly when the report is opened in Smart View. |
|
14198643 |
Running a batch using bursting options, the text in body of e-mail displays repeated occurrences of the text 'Generated Snapshot Links'. |
|
14201212 |
After upgrading from Release 9.3.3 to Release 11.1.2.2, the report header font changed from Times New Roman to Arial the PDF output. |
|
14207990 |
A grid containing multiple connections with the same data source type does not work. |
|
14210958 |
When exporting Financial Reporting report to Microsoft Excel 2010, the column headers are displaying with <br> as part of the name. |
|
14222267 |
If a Financial Reporting book includes an unreachable report, a garbled message appears. |
|
14242296 |
Exporting to fully formatted does not render alphanumeric data. |
|
14249751 |
When scheduling a batch that that includes a Financial Reporting Book which contains a Microsoft Word document, selecting the batch output to MHTML will result in an error. |
|
14249866 |
In a Financial Reporting report that contains a cell with conditional formatting and related content links, when the related content server is changed in Workspace, the conditional formatting settings are modified. |
|
14256461 |
A Financial Reporting report exported to Smart View does not display in a single page when print layout is selected in Microsoft Word. |
|
14286785 |
Financial Reporting snapshot report output is not being generated successfully when running a batch using the command line scheduler utility. |
|
14313697 |
If your browser is Internet Explorer 9, then in the Financial Reporting Batch Editor the 'Bursted' option is disabled. |
|
14360273 |
The xdo.cfg file is not being read properly on UNIX OS causing PDF generation to fail. |
|
14402489 |
In the Workspace Explorer the modified date is changed when running a Financial Reporting report. |
|
14456798 |
The Financial Reporting report header font changes after upgrading to 11.1.2.2.00. |
After applying the patch, the user may need to edit the xdo.cfg file (under <EPM_ORACLE_HOME>\products\financialreporting\lib) by commenting out the following line if it is still there and there is no c:\temp directory on the Financial Reporting Server machine:
<property name="system-temp-dir">c:\temp</property>
Also, the following issues are the noteworthy known issues of this patch.
|
Defect Number |
Defect Summary |
|
11073144 |
Export of Microsoft PowerPoint 2010 is not working or supported as .mhtml format.
Workaround: Rename workspace exported .ppt file to .mhtml. Open this file in PowerPoint 97-2003 and save as .ppt. |
|
11875160 |
Stopping Financial Reporting report is not stopping Essbase query from executing. |
|
18317062 |
When the 'Freeze Grid Headers' setting for columns is set to 'On', it is not honored in HTML Preview when using Firefox browser. |
|
18433829 |
Exporting a Financial Reporting report to Microsoft PowerPoint 2010 or later is not supported in 11.1.2.2.x. but it is supported in 11.1.2.3.500. Same issue as 11073144, above. Workaround: Export the Financial Reporting report to Microsoft Word 2010 or Microsoft Excel 2010 or later. |
|
18671582 |
In Batch Scheduler, output as a static HTML web site may fail on Windows environments that implement Kerberos SSO. |
The section includes important information about applying this patch for Oracle Hyperion Financial Reporting, Fusion Edition.
[NOTE TO WRITERS: Make sure that instructions for applying the PATCH indicate specifically which components are being patched and which machines in a distributed installation should be patched. for example, on the machine hosting the shared services web application, ]
[NOTE TO WRITERS: For web applications, make sure you provide instructions for all supported application servers.]
To apply this patch:
1. Shut down all services and servlet instances related to the Oracle Hyperion EPM Release 11.1.2.2.00 installation.
2. Uninstall the Financial Reporting Studio by going to Control Panel, Add or Remove Programs, and then uninstall Financial Reporting Studio.
3. On the Financial Reporting server machines; Download and unzip the downloaded patch file, <PATCH FILE NAME>.zip, to the <EPM_ORACLE_HOME>/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).
NOTE: <PATCH FILE NAME>.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.
4. On the Financial Reporting server machines, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.
5. To apply the patch, enter the following command on one line:
Windows:
opatch.bat apply <EPM_ORACLE_HOME>/OPatch/<PATCH DIRECTORY> -oh <EPM_ORACLE_HOME>
-jdk <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 DIRECTORY> -oh <EPM_ORACLE_HOME> -jdk <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.
6. Delete the Financial Reporting precompiled jsp files located at: <ORACLE_HOME>\Middleware\user_projects\domains\EPMSystem\precompiled\hr
7. Restart Oracleฎ Hyperion EPM services and servlets.
8. All users should now clear cached files from their browsers.
For WebSphere deployments, you must use EPM System Configurator to redeploy the Web application.
9. On the Financial Reporting Studio machines; Uninstall the Financial Reporting Studio by going to Control Panel, Add or Remove Programs, and then uninstall Financial Reporting Studio.
10. Connect to the EPM Workspace machine that was patched in Step 3. Download the Financial Reporting Studio installer from the EPM Workspace menu: From the Tools menu, select Install and then select Financial Reporting Studio and then launch the installer. Follow the installation guide to install the Financial Reporting Studio to the location you want.
11. All users should now clear cached files from their browsers.
To roll back a patch:
1. Shut down all services and servlet instances related to the Oracle Hyperion EPM Release 11.1.2.2.00 installation.
2. Uninstall the Financial Reporting Studio by going to Control Panel, Add or Remove Programs, and then uninstall Financial Reporting Studio.
3. On the Financial Reporting server machines; 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 <PATCH ID> -oh <EPM_ORACLE_HOME> -jdk <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> -jdk <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. Delete the Financial Reporting precompiled jsp files located at: <ORACLE_HOME>\Middleware\user_projects\domains\EPMSystem\precompiled\hr
6. Restart Oracleฎ Hyperion EPM services and servlets.
7. All users should now clear cached files from their browsers.
8. On the Financial Reporting client machines; Uninstall the Financial Reporting Studio by going to Control Panel, Add or Remove Programs, and then uninstall Financial Reporting Studio.
9. Connect to the EPM Workspace machine that was rolled back in step 3. Download the Financial Reporting Studio installer from the EPM Workspace menu: From the Tools menu, select Install and then select Financial Reporting Studio and then launch the installer.
10. All users should now clear cached files from their browsers.
[NOTE TO WRITERS: IF THIS PATCH INCLUDES CHANGES TO A JAVASCRIPT FILE, YOU NEED TO INCLUDE THE STEP ABOVE AS A FINAL STEP. IF IT DOESNT, DELETE THIS STEP.]
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.
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:
[NOTE TO WRITERS: very important! the jdk version in the apply command is different for 11.1.2.0, 11.1.2.1, and 11.1.2.2. change the jdk160_xx directory as follows:
11.1.2.2: jdk160_29
11.1.2.1: jdk160_21
11.1.2.0: jdk160_11
The example here is for 11.1.2.2.
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
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
Copyright ฉ 2015, Oracle and / or its affiliates. All rights reserved. http://www.oracle.com