25797429- Oracle Business Intelligence Enterprise Edition Suite Bundle Patch 11.1.1.9.

170418

25797429 - Oracle Business Intelligence Enterprise

Edition Suite Bundle Patch 11.1.1.9.170418
Readme last updated: 18 April 2017

This document includes the following sections:

Section 1: Patch Information

Section 2: Important Notes to Read Before Installing the Bundle Patch

Section 3: Installation Instructions

Section 4: Post-Installation Instructions

Section 5: Deinstallation Instructions

Section 6: References

Section 7: Bugs Fixed by This Patch

Section 8: Known Issues

Section 1: Patch Information

For an introduction to Oracle BI Enterprise Edition (Oracle BI EE) Suite Bundle Patches refer to My Oracle
Support note 1591422.1 "OBIEE Suite Bundle Patches." It includes information on the bundle patch lifecycle,
availability, and version names.

Oracle BI EE Suite Bundle Patches are cumulative. That is, the content of all previous 11.1.1.9.x bundle
patches is included in the latest bundle patch.

Oracle BI EE Suite Bundle Patch 11.1.1.9.170418 includes all the bug fixes released in Oracle BI EE Suite
Bundle Patch 11.1.1.9.170117 and new bug fixes. For a detailed report of new bug fixes in Oracle BI EE
Suite Bundle Patch 11.1.1.9.170418, see Section 7: Bugs Fixed by This Patch.

To install the Oracle BI EE Suite Bundle Patch 11.1.1.9.170418 patch, Oracle BI EE 11.1.1.9.0 must be
installed in the Oracle BI Home directory. Subsequent Oracle BI EE patches can be installed on Oracle BI EE
11.1.1.9.0 or any Oracle BI EE bundle patch with a lower fifth numeral version than the one being installed.
For example, you can install 11.1.1.9.170418 on 11.1.1.9.0.

A Bundle Patch is a collection of cumulative patches for the Oracle BI EE components. The patches in a
Bundle Patch have been tested to work together. Therefore, you must apply every patch in the Bundle
Patch.

Patch 25797429 is the top-level patch and it contains all of the cumulative component patches. This provides
a single patch to download from My Oracle Support, although there are several component patches that
must be installed in the Oracle BI Home directory.

Note that some component patches might not have changed since the last Bundle Patch was installed but all
are included in the Bundle Patch. Only component patches that have NEW changes will be installed by
OPatch. For Oracle BI EE Suite Bundle Patch 11.1.1.9.170418, the following component patches are new:

Oracle Business Intelligence Presentation Services (BIPS)

Oracle BI Server (BISERVER)

Oracle BI Publisher (BIP)

Oracle BI Mobile App Designer (BIMAD)

Oracle Enterprise Performance Management Components Installed from Oracle BI Installer 11.1.1.9.0
(BIFNDNEPM)

The Oracle BI EE Suite Bundle Patch 11.1.1.9.170418 under the top-level patch 25797429 consists of the
following component patches:

The HP-UX Itanium platform is not supported for BIFNDNEPM patch in this release

Patch Abstract
25710734 Oracle Business Intelligence Publisher (BIP)
25796832 Oracle Enterprise Performance Management Components Installed from Oracle BI Installer
11.1.1.9.0 (BIFNDNEPM)
25710656 Oracle Business Intelligence Server (BISERVER)
25710602 Oracle Business Intelligence Presentation Services (BIPS) (BIFNDN)
24346370 Oracle Business Intelligence ADF Components (BIADFCOMPS)
25818798 Oracle Business Intelligence Platform Client Installers and MapViewer
21517672 Oracle Business Intelligence Third Party
25738050 Oracle BI Mobile App Designer

Section 2: Important Notes to Read Before Installing the

Bundle Patch
Take some time to review and assess various issues that may impact your installation process.

This section consists of the following topics:

"Section 2.1: For Customers Moving From 11.1.1.7.x to 11.1.1.9.170418"

"Section 2.2: Interim Patch Conflict Detection and Resolution"

"Section 2.3: For Oracle Exalytics and Oracle Fusion Applications Customers"

"Section 2.4: For Clustered Environments"

Section 2.5: Version Changes from 11.1.1.9.161018

Section 2.1: For Customers Moving From 11.1.1.7.x to

11.1.1.9.170418
If you are upgrading from 11.1.1.7.x, some additional steps are required before you install the
11.1.1.9.170418 patch.

If you are upgrading from Oracle BI EE Bundle Patch 11.1.1.7.160719, or from an earlier 11.1.1.7.x
Bundle Patch, and you have not applied any interim one-off patches, first upgrade to 11.1.1.9.0 and
apply the Oracle BI EE Suite Bundle Patch 11.1.1.9.170418. All bug fixes that were previously in your
installation are included.

If you are upgrading from Oracle BI EE Bundle Patch 11.1.1.7.160719, or from an earlier 11.1.1.7.x
Bundle Patch, and you have applied additional interim one-off patches, then contact Oracle Support
for assistance.

Section 2.2: Interim Patch Conflict Detection and Resolution

Some bug fixes in the Oracle BI EE Suite Bundle Patch 11.1.1.9.170418 might conflict with your current
installation. Run patch reports before you start to find out whether this affects you.

1. Navigate to My Oracle Support and download the Oracle BI EE Suite Bundle Patch 11.1.1.9.170418
into the Oracle BI Home directory.

Oracle BI EE Suite Bundle Patch 11.1.1.9.170418 contains the following zip file:

p25797429_111190_<platform>.zip

2. In the Oracle BI Home directory, unzip the downloaded patch zip into a subdirectory below the Oracle
BI Home directory. For example:
On UNIX: You might extract patch 25797429 into prod_mwhome/Oracle_BI1

The patch is extracted in the prod_mwhome/Oracle_BI1/25797429 directory.

On Windows: You might extract patch 25797429 into C:\prod_mwhome\Oracle_BI1

The patch is extracted in the prod_mwhome\Oracle_BI1\25797429 directory.

3. Unzip the eight component patch zip files into the 25797429 directory as follows:

For each component patch zip file, extract the files into a subdirectory under the 25797429 directory.

For example, extract the zip file p25710734_111190_Generic.zip into the

prod_mwhome/Oracle_BI1/25797429 directory.

The component patch is extracted in the prod_mwhome/Oracle_BI1/25797429/25710734 directory.

4. Change directory to the extracted patch subdirectory.

For example:

On UNIX: If you extracted patch 25710734 into prod_mwhome/Oracle_BI1/25797429

/25710734, then enter the following:
cd prod_mwhome/Oracle_BI1/25797429/25710734

On Windows: If you extracted patch 25710734 into C:\prod_mwhome\Oracle_BI1\25797429

\25710734, then enter the following:
 cd c:\prod_mwhome\Oracle_BI1\25797429\25710734

5. Check for patch conflicts by entering the following command:

opatch prereq CheckConflictAgainstOHWithDetail -ph ./

6. Review the OPatch prerequisite report to view patches that conflict with the Oracle Business
Intelligence component patch and the patches for which the Oracle Business Intelligence component
patch is a superset.
7. For each conflicting patch, review the My Oracle Support document titled "Fusion Middleware Patch
Conflict Resolution" (Doc ID 1329952.1). The document enables you to determine if a conflict
resolution patch is available, if you need to request a new conflict resolution patch, or if you can
ignore the conflict.
8. Repeat the previous steps (Step 4 to Step 7) for the next patch subdirectory until conflicts for all
components have been checked.
9. When all the interim one-off patches that you have requested are available at My Oracle Support,
proceed to install the Bundle Patch by following the steps in Section 3: Installation Instructions.

Section 2.3: For Oracle Exalytics and Oracle Fusion Applications

Customers
If you have Oracle Exalytics or Oracle Fusion Applications installed, some additional checks are required
before you install the Oracle BI EE Suite Bundle Patch 11.1.1.9.170418:

Oracle Exalytics customers must not install this Oracle Business Intelligence Bundle Patch unless it is
certified for the specific Oracle Exalytics patch or patch set update that they are applying. For more
information see Oracle Exalytics In-Memory Machine Installation and Administration Guide and the
Oracle Exalytics certification information.
For Oracle Fusion Applications customers, this Oracle Business Intelligence Bundle Patch is applied as
part of a Fusion Applications installation or upgrade. Oracle Fusion Applications customers must not
apply this Bundle Patch independently.

Section 2.4: For Clustered Environments

If you horizontally scaled out your Oracle Business Intelligence system on to multiple machines, then you
must apply the Oracle BI EE Suite Bundle Patch 11.1.1.9.170418 to all machines in the cluster.

Section 2.5: Version Changes from 11.1.1.9.161018

Starting from Oracle BI EE Suite Bundle Patch 11.1.1.9.161018 version information in BI Analytics
Administration link and BI Publisher Administration link is changed to 11.1.1.9.0 followed by Build timestamp
information.

For example: in Oracle BI EE Suite Bundle Patch 11.1.1.9.170418, BI Analytics Administration page is
showing the version as "Oracle Business Intelligence Product Version 11.1.1.9.0 (Build 170327.1029 64-bit)"

BI Publisher Administration page is showing the version as "Oracle BI Publisher 11.1.1.9.0

(build:20170318.1122)"

Note:
 Above mentioned build number is for Linux-64 platform. There will be a slight build
timestamp difference for other platforms.

Section 3: Installation Instructions

To install this bundle patch:

1. Back up the Oracle BI system, including the following:

The <Oracle BI Home>\bifoundation\server directory.
The <Oracle Instance>\bifoundation\OracleBIServerComponent
\coreapplication_obis1\repository directory.
The <Oracle BI Home>\bifoundation\jee\mapviewer.ear\web.war\WEB_INF
\conf\mapViewerConfig.xml file, if you have modified it.

Tip:

The location of the Oracle BI Home directory and the Oracle Instance directory
depend on where Oracle BI was originally installed, and on the platform. For
example:

On UNIX, the Oracle BI Home directory might be prod_mwhome/Oracle_BI1

2. Important Pre-requisite step before applying Bundle Patch : The prerequisite patch
21873359 is required for all Oracle BI Mobile App Designer patches as it prevents rollback
failure. Download patch 21873359 from My Oracle Support and apply on top of 11.1.1.9.0
before applying any bundle patch.
3. Stop the Oracle BI system (in the order shown):
a. Oracle BI system components:
On UNIX, navigate to prod_mwhome/instances/<instance>/bin and enter the following
at the command prompt:

./opmnctl stopall

On Windows, navigate to prod_mwhome\instances\<instance>\bin and enter the

following at the command prompt:
opmnctl stopall

b. WebLogic Managed Server(s):

Skip this step if you have installed the BI Domain with the Simple Install option, because the
Simple Install option does not create a WebLogic Managed Server.

On UNIX, navigate to prod_mwhome/user_projects/domains/<domain_name>/bin and

enter the following at the command prompt:
./stopManagedWebLogic.sh bi_server1

On Windows, navigate to prod_mwhome\user_projects\domains\<domain_name>\bin

 and enter the following at the command prompt:

stopManagedWebLogic.cmd bi_server1

c. WebLogic Administration Server:

On UNIX, navigate to prod_mwhome/user_projects/domains/<domain_name>/bin and
enter the following at the command prompt:

./stopWebLogic.sh

On Windows, navigate to prod_mwhome\user_projects\domains\<domain_name>\bin

and enter the following at the command prompt:

stopWebLogic.cmd

4. Clear the files that are associated with the binary cache for the Catalog Manager in Oracle Business
Intelligence as follows:
a. Go to the <Oracle BI Home>/bifoundation/web/catalogmanager/configuration/ directory (using
a file manager application or the command line). For example:
On UNIX: If the Oracle BI Home directory is prod_mwhome/Oracle_BI1, then go to the
following directory:
prod_mwhome/Oracle_BI1/bifoundation/web/catalogmanager/configuration/

On Windows: If the Oracle BI Home directory is C:\prod_mwhome\Oracle_BI1, then go

to the following directory:

C:\prod_mwhome\Oracle_BI1\bifoundation\web\catalogmanager\configuration\

b. Remove the following cache directories for Catalog Manager (if they exist):
org.eclipse.osgi
org.eclipse.equinox.app
5. If you have not already downloaded the Bundle Patch (see Step 1 in "Section 2.2: Interim Patch
Conflict Detection and Resolution"), download the Oracle BI EE Suite Bundle Patch 11.1.1.9.170418
from My Oracle Support into the Oracle BI Home directory. The Bundle Patch contains the following
zip file:

p25797429_111190_<platform>.zip

6. If you have not already extracted the patch zip file, unzip the downloaded patch zip file
25797429_111190_<platform>.zip into a subdirectory below the Oracle BI Home directory. See Step
2 in "Section 2.2: Interim Patch Conflict Detection and Resolution"
7. If you have not already extracted the component zip files, unzip the eight component patch zip files
into the 25797429 directory. See Step 3 in "Section 2.2: Interim Patch Conflict Detection and
Resolution"
8. At the command prompt, change directory to the Oracle BI Home directory using the command
appropriate for the operating system.

For example:

On UNIX: If the Oracle BI Home directory is prod_mwhome/Oracle_BI1, then enter the

following:

cd prod_mwhome/Oracle_BI1
 On Windows: If the Oracle BI Home directory is C:\prod_mwhome\Oracle_BI1, then enter the
following:
cd c:\prod_mwhome\Oracle_BI1

9. At the command prompt, set the ORACLE_HOME, PATH, and JAVA_HOME environment variables as
appropriate for the operating system.

For example:

On UNIX: If you are using a command shell derived from the C shell, then set the environment
variables by entering the following:
setenv ORACLE_HOME $PWD
setenv PATH $ORACLE_HOME/bin:$PATH
setenv JAVA_HOME $ORACLE_HOME/jdk
setenv PATH $JAVA_HOME/bin:$PATH
setenv PATH $ORACLE_HOME/OPatch:$PATH

On Windows: If the Oracle BI Home directory is C:\prod_mwhome\Oracle_BI1, then set the

environment variables by entering the following:
set ORACLE_HOME=C:\prod_mwhome\Oracle_BI1
set PATH=%ORACLE_HOME%\bin;%PATH%
set JAVA_HOME=%ORACLE_HOME%\jdk
set PATH=%JAVA_HOME%\bin;%PATH%
set PATH=%ORACLE_HOME%\OPatch;%PATH%

10. At the command prompt, install all component patches that comprise the Oracle BI EE Suite Bundle
Patch 11.1.1.9.170418.

You can apply the component patches in two ways:

If all of the Oracle BI EE components have been installed and configured in your existing Oracle
BI system, you can apply all patches together as follows:
a. Change directory to the extracted patch directory.

For example:

On UNIX: If you extracted patch 25797429 into prod_mwhome/Oracle_BI1/25797429,

then enter the following:

cd prod_mwhome/Oracle_BI1/25797429

On Windows: If you extracted patch 25797429 into C:\prod_mwhome\Oracle_BI1

\25797429, then enter the following:

cd c:\prod_mwhome\Oracle_BI1\25797429

b. Enter the following command:

opatch napply skip_duplicate

If only some of the Oracle BI EE components have been installed and configured in your existing
Oracle BI system, or you prefer to apply patches separately, apply the patches individually as
follows:
a. Change directory to the extracted patch subdirectory.
 For example:

On UNIX: If you extracted patch 25797429 into prod_mwhome/Oracle_BI1/25797429

/25710734, then enter the following:

cd prod_mwhome/Oracle_BI1/25797429/25710734

On Windows: If you extracted patch 25710734 into C:\prod_mwhome\Oracle_BI1

\25797429\25710734, then enter the following:

cd c:\prod_mwhome\Oracle_BI1\25797429\25710734

b. Apply the patch by entering the following command:

opatch apply

c. When the message "Opatch Succeeded" is displayed, repeat the previous steps for the
next patch subdirectory until all the patches have been applied.
11. Download and apply all patch conflict resolution overlay patches as determined in "Section 2.2:
Interim Patch Conflict Detection and Resolution"
12. Apply the patch by entering the following command:

opatch apply

13. Verify that the Oracle BI EE Suite Bundle Patch 11.1.1.9.170418 has been applied successfully as
follows:

Run the following command to list the patches that have been applied to the Oracle home that is
specified by the ORACLE_HOME environment variable (currently the Oracle BI Home) : opatch
lsinventory

14. Remove the jsp_servlet subdirectory associated with Oracle BI Publisher (if it exists), as follows:
a. Go to the directory containing the jsp_servlet subdirectory (using a file manager application or
the command line).

If it exists, then the jsp_servlet subdirectory is located in one of the directories below the
<Middleware Home>/<Domain Home>/servers/bi_server1/tmp/_WL_user
/bipublisher_11.1.1 directory.

For example:

On UNIX: If the Middleware Home directory is /prod_mwhome and the Domain Home
directory is /user_projects/domains/bifoundation_domain, then go to the following
directory:
/prod_mwhome/user_projects/domains/bifoundation_domain/servers/bi_server1
/tmp/_WL_user/bipublisher_11.1.1

On Windows: If the Middleware Home directory is C:\prod_mwhome and the Domain

Home directory is \user_projects\domains\bifoundation_domain, then go to the
following directory:

C:\prod_mwhome\user_projects\domains\bifoundation_domain\servers
\bi_server1\tmp\_WL_user\bipublisher_11.1.1

b. Look in each directory below <Middleware home>/<Domain home>/servers/bi_server1

 /tmp/_WL_user/bipublisher_11.1.1 , and remove any jsp_servlet subdirectory that you find.
15. Start the WebLogic Administration Server and the Managed Server(s) by performing the following
actions:
a. Starting WebLogic Administration Server:
On UNIX, navigate to prod_mwhome/user_projects/domains/<domain_name>/bin and
enter the following at the command prompt:

./startWebLogic.sh

On Windows, navigate to prod_mwhome\user_projects\domains\<domain_name>\bin

and enter the following at the command prompt:
startWebLogic.cmd

b. Starting Managed Server(s):

On UNIX, navigate to prod_mwhome/user_projects/domains/<domain_name>/bin and
enter the following at the command prompt:

./startManagedWebLogic.sh bi_server1

On Windows, navigate to prod_mwhome\user_projects\domains\<domain_name>\bin

and enter the following at the command prompt:
startManagedWebLogic.cmd bi_server1

16. When you have applied all the Oracle BI EE Suite Bundle Patch 11.1.1.9.170418 patches , start the
Oracle BI system components by performing the following actions:
On UNIX, navigate to prod_mwhome/instances/<instance>/bin and enter the following at
the command prompt:

./opmnctl startall

On Windows, navigate to prod_mwhome\instances\<instance>\bin and enter the following

at the command prompt:

opmnctl startall

17. For Oracle Business Intelligence Client Tools only: Having applied the Oracle BI EE Suite Bundle
Patch 11.1.1.9.170418, you must also update each desktop installation of the Oracle Business
Intelligence Client Tools (Oracle BI Administration Tool, Job Manager, and Catalog Manager) as
follows:
a. Deinstall the Oracle Business Intelligence Client Tools from every computer where the client
tools have been installed by following the instructions in Chapter 5 of Oracle Fusion Middleware
Installation Guide for Oracle Business Intelligence.
b. Reinstall the Oracle Business Intelligence Client Tools on every computer where the client tools
have been deinstalled by following the instructions in Chapter 5 of Oracle Fusion Middleware
Installation Guide for Oracle Business Intelligence.
18. (Optional) Minimize disk usage by:
Deleting the downloaded Oracle BI EE Suite Bundle Patch 11.1.1.9.170418 zip files.
Deleting the extracted patch directories (for example, C:\prod_mwhome\Oracle_BI1\25797429
).

19. For customers using Financial Reporting:

 You must update your local version of Financial Reporting Studio after installing the latest patch.
Follow the Oracle Enterprise Performance Management System Standard Deployment Guide to install
the Financial Reporting Studio. Ensure that you install the Financial Reporting Studio as an
administrator.

Section 4: Post-Installation Instructions

After installing the patch bundle, you must perform various tasks.

This section consists of the following topics:

"Section 4.1: Editing Settings in OracleBIJavahostComponent to Enhance Export to Microsoft Excel

Functionality"
"Section 4.2: Clearing the Cache"

Section 4.1: Editing Settings in OracleBIJavahostComponent to

Enhance Export to Microsoft Excel Functionality
Follow these steps to enhance the export to Microsoft Excel functionality.

You can use Oracle BI EE to export data from analyses, dashboards, and other Oracle BI Presentation
Catalog objects to Microsoft Excel. To further enhance this export functionality, edit
OracleBIJavaHostComponent configuration files as follows:

1. Stop the Oracle BI system (in the order shown):

a. Oracle BI system components:
On UNIX, navigate to prod_mwhome/instances/<instance>/bin and enter the following
at the command prompt:
./opmnctl stopall

On Windows, navigate to prod_mwhome\instances\<instance>\bin and enter the

following at the command prompt:

opmnctl stopall

b. WebLogic Managed Server(s):

Skip this step if you have installed the BI Domain with the Simple Install option, because the
Simple Install option does not create a WebLogic Managed Server.

On UNIX, navigate to prod_mwhome/user_projects/domains/<domain_name>/bin and

enter the following at the command prompt:

./stopManagedWebLogic.sh bi_server1

On Windows, navigate to prod_mwhome\user_projects\domains\<domain_name>\bin

and enter the following at the command prompt:
stopManagedWebLogic.cmd bi_server1
 c. WebLogic Administration Server:
On UNIX, navigate to prod_mwhome/user_projects/domains/<domain_name>/bin and
enter the following at the command prompt:
./stopWebLogic.sh

On Windows, navigate to prod_mwhome\user_projects\domains\<domain_name>\bin

and enter the following at the command prompt:

stopWebLogic.cmd

2. Navigate to the prod_mwhome/instances/instance1/config/OracleBIJavaHostComponent

/coreapplication_obijh1 folder.
3. Perform the following actions:
a. In the config.xml file, configure the XMLP tag for large data as follows:

<XMLP> <InputStreamLimitInKB>0</InputStreamLimitInKB>

<ReadRequestBeforeProcessing>false</ReadRequestBeforeProcessing></XMLP>

b. In the xdo.cfg file, add the following parameter inside the properties tag:

<property name="xlsx-keep-values-in-same-column">true</property>

4. Restart the WebLogic Administration Server and the Managed Server(s) by performing the following
actions:
a. Starting WebLogic Administration Server:
On UNIX, navigate to prod_mwhome/user_projects/domains/<domain_name>/bin and
enter the following at the command prompt:

./startWebLogic.sh

On Windows, navigate to prod_mwhome\user_projects\domains\<domain_name>\bin

and enter the following at the command prompt:
startWebLogic.cmd

b. Starting Managed Server(s):

On UNIX, navigate to prod_mwhome/user_projects/domains/<domain_name>/bin and
enter the following at the command prompt:
./startManagedWebLogic.sh bi_server1

On Windows, navigate to prod_mwhome\user_projects\domains\<domain_name>\bin

and enter the following at the command prompt:

startManagedWebLogic.cmd bi_server1

5. Restart the Oracle BI system components by performing the following actions:

On UNIX, navigate to prod_mwhome/instances/<instance>/bin and enter the following at
the command prompt:
./opmnctl startall

On Windows, navigate to prod_mwhome\instances\<instance>\bin and enter the following at

the command prompt:
 opmnctl startall

Section 4.2: Clearing the Cache

When the installation of the Bundle Patch is complete, all end users must clear their browser cache.

Section 5: Deinstallation Instructions

Follow these steps to deinstall a patch.

If you experience any problems after installing a patch, then you can deinstall each patch as follows:

1. Stop the Oracle BI system (in the order shown):

a. Oracle BI system components:
On UNIX, navigate to prod_mwhome/instances/<instance>/bin and enter the following
at the command prompt:

./opmnctl stopall

On Windows, navigate to prod_mwhome\instances\<instance>\bin and enter the

following at the command prompt:
opmnctl stopall

b. WebLogic Managed Server(s):

Skip this step if you have installed the BI Domain with the Simple Install option, because the
Simple Install option does not create a WebLogic Managed Server.

On UNIX, navigate to prod_mwhome/user_projects/domains/<domain_name>/bin and

enter the following at the command prompt:
./stopManagedWebLogic.sh bi_server1

On Windows, navigate to prod_mwhome\user_projects\domains\<domain_name>\bin

and enter the following at the command prompt:

stopManagedWebLogic.cmd bi_server1

c. WebLogic Administration Server:

On UNIX, navigate to prod_mwhome/user_projects/domains/<domain_name>/bin and
enter the following at the command prompt:
./stopWebLogic.sh

On Windows, navigate to prod_mwhome\user_projects\domains\<domain_name>\bin

and enter the following at the command prompt:
stopWebLogic.cmd

2. Set environment variables (for example, ORACLE_HOME) as described in Section 3: Installation

Instructions
3. Verify that the patch has actually been applied, by running the command opatch lsinventory as
described in Section 3: Installation Instructions.
4. At the command prompt:
a. Change directory to the extracted patch directory. For example:
On UNIX: If you extracted patch 25797429 into prod_mwhome/Oracle_BI1/25797429,
then enter the following:
cd prod_mwhome/Oracle_BI1/25797429

On Windows: If you extracted patch 25797429 into C:\prod_mwhome\Oracle_BI1

\25797429, then enter the following:
cd c:\prod_mwhome\Oracle_BI1\25797429

b. Deinstall the patch by entering the following command:

opatch rollback -id <patch number> -jre $ORACLE_HOME/jdk/jre

Note:

To deinstall multiple patches all at the same time, enter the following
command:
opatch nrollback -id <comma-separated list of patch IDs>

5. Start the Oracle BI system (in the order shown):

a. WebLogic Administration Server:
On UNIX, navigate to prod_mwhome/user_projects/domains/<domain_name>/bin and
enter the following at the command prompt:
./startWebLogic.sh

On Windows, navigate to prod_mwhome\user_projects\domains\<domain_name>\bin

and enter the following at the command prompt:
startWebLogic.cmd

b. If stopped, WebLogic Managed Server(s):

On UNIX, navigate to prod_mwhome/user_projects/domains/<domain_name>/bin and
enter the following at the command prompt:

./startManagedWebLogic.sh bi_server1

On Windows, navigate to prod_mwhome\user_projects\domains\<domain_name>\bin

and enter the following at the command prompt:

startManagedWebLogic.cmd bi_server1

c. Oracle BI system components:

On UNIX, navigate to prod_mwhome/instances/<instance>/bin and enter the following
at the command prompt:

./opmnctl startall

On Windows, navigate to prod_mwhome\instances\<instance>\bin and enter the

 following at the command prompt:

opmnctl startall

Section 6: References
No document is referenced for this patch set.

Section 7: Bugs Fixed by This Patch

Oracle BI EE Suite Bundle Patch 11.1.1.9.170418 includes all the bug fixes released in Oracle BI EE Bundle
Patch 11.1.1.9.170117 and the following new bug fixes described in the following sections:

"Section 7.1: Oracle Business Intelligence Presentation Services (BIPS)"

"Section 7.2: Oracle Business Intelligence Server (BISERVER)"
"Section 7.3: Oracle Business Intelligence Publisher (BIP)"
"Section 7.4: Oracle BI Mobile App Designer (BIMAD)"
"Section 7.5: Oracle Enterprise Performance Management Components Installed from Oracle BI
Installer 11.1.1.9.0(BIFNDNEPM)"

Section 7.1: Oracle Business Intelligence Presentation Services

(BIPS)
New bug fixes for Oracle Business Intelligence Presentation Services (BIPS) are listed here.

25307805 COMPLETE FIX/PATCH FOR 25177893

25315395 APOSTROPHE IN PRESENTATION VARIABLE IS FAILING WITH SYNTAX ERROR

25248006 DELIVERS INCORRECT JOB STATUS

24490711 RFA - AGENTS TAKING TOO LONG TO SAVE IN CATALOG

25177893 SAWSERVER CRASHES ON SELECTING MULTIPLE VALUES IN A DBL-COL PROMPT

20308183 PRIVILEGE SETTING OF ACCESS TO EXPORT DOESN'T WORK AFTER REFRESH

23522483 FILTERS AGAIST COLUMNS WHERE DATA HAS LOWER ASCII FORMATTING CHARACTERS
FAILS

22601212 AUTO-COMPLETE PROMPT NOT WORKING

22310977 REPORT EXPORT TO EXCEL NOT DISPLAYING DATA VALUES AFTER UPGRADE TO
OBI11.1.1.9.0

22269576 WRITEBACK NOT WORKING IN 11.1.1.9.5

21649378 CELL VALUE AND FORMAT OF NULL CHANGED BETWEEN 11.1.1.7 AND 11.1.1.9

20575923 QA:JS ERROR TYPEERROR: THIS.VIEWENV IS UNDEFINED IN VIEWCONTROLLER.JS

24361835 Fix for Bug 24361835

25434534 QA: REL12 : 11.1.1.9.170130: BUG 22310977 INTRODUCES DIFS IN DEV MATS

24691106 OTBI-E CLOUD CONDITIOANL FORMATTING LOST FOR "FUSE" STYLE WITH GREEN BAR
STYLING

21945490 11.1.1.9.0:DASHBOARD PRINT->PRINTABLE PDF DOES NOT RESPECT SECTION PROPERTIES

25576227 REL12: BISERVER COMPONENT FAIL TO START WITH HUGE NUMBER OF REPORTING GROUPS

24557072 BIP REPORT AS LINK THROWING "BAD REQUEST" ERROR

25583541 REL13 SMC: ORACLE.BI_TEMPLATE SET EXTRA_JAVA_PROPERTIES ONLY TO OBI GROUP

24443466 HOW TO TRANSLATE CUSTOM OTBI REPORT TO DIFFERENT LANGUAGE IN CLOUD

24590404 Fix for Bug 24590404

25375525 DATA VISUALIZATION CLOUD: UPDATE CATALOGMANAGER JAR SIGS TO WORK WITH LATEST
JRE

25209488 DASHBOARD LINK OR IMAGE OBJECTS ALLOWING USER TO CONFIGURE THIRD PARTY
WEBSITES

25499822 QA:ANALYSIS OPTIONS MISSING THE PAGE LINKS COLOUR FROM FA THEME

Section 7.2: Oracle Business Intelligence Server (BISERVER)

New bug fixes for Oracle Business Intelligence Server (BISERVER) are listed here.

25751176 MAKE USE OF THE NEW GETDIRECTBULKMEMBERS API FROM BI SECURITY SERVICE

25050624 CUSTOMIZATIONS EXTRACTED WITH EXTRACTCUSTOMIZATION FAILED TO APPLY ON REL13

RPD

25490496 QA:RGRN:REL12 BP170130 EXTRACTCUSTOMIZATION UTILITY FAILED WITH NQSERROR:

28006

25492222 REL12.1 ST15 GSI & CRM FAILED -- INVOCATION OF BI FACADE (RUNPROVPHASESTILLCONF

24897977 PATCH 22306296 IS FAILING WHILE RUNNING RPD SYNCPATCH

25438880 FIX ADF BIND VARIABLE ISSUE

25443280 COLUMN MAPPING INVALID ERROR IN CSA UTILITY

25439485 REL12.1 ST13:FUSCDRMOVM94 : IP POSTCONFIGURE FAILED ON BI HOST OBIPS1 STARTUP

25445390 COMMENT OUT 'EXTRACTCUSTOMSUBJECTAREAS_CPP' API FROM PATCHINGUTIL CLASS

25416959 CSAS DISAPPEARED IN R12 UPGRADE : EXTRACTCUSTOMIZATIONS UTILITY

25289608 RNR: UBER UTILITY GENERATES NEW RPD WITH DEFAULT PWD

25265423 BISERVERRNRPATCHER UTILITY DOES NOT GENERATE STATUS XML FILE

25241866 BISERVERAPPLYVERTICALRULES UTILITY REQUIRES A PARAM IN UBER FLOW

25097491 REL13 SMC: BISERVEREXTENDER FAILS ON RPD USING CSFKEY TO RETRIEVE

USERNAME/PWD

24950206 CSAS DISAPPEARED DURING REL11 PB PATCHING : COMMON DIMENSION EXTENDER

25409416 ERROR WHILE PUBLISHING CSA : INCORRECT REL12/13 BACKPORT 20351929

25348545 REL12.1 ST10: CDRMOVM85: IP FAILS AT POSTCONFIGURE ON BI HOST WITH BIPS STARTUP

22534841 EDIT AND EXECUTION OF AGENTS FAILING WITH ERROR 'EXEC_WHEN_MISS_FLG' IS NOT A
VA

24849554 PATCH BUG 24514480 CAUSES REGRESSIONS IN OTBI

25120916 CSM IMPORT FAILURE DUE TO RPD CORRUPTION AFTER VERTICAL RULES FILE PUBLISH

Section 7.3: Oracle Business Intelligence Publisher (BIP)

New bug fixes for Oracle Business Intelligence Publisher (BIP) are listed here.

18559885 USAGE TRACKING NOT CAPTURING USER LOGIN EVENT

22347592 CLICKING 'RETURN' ON JOBDETAILS PAGE DOESNT SHOW JOB HISTORY, SEARCHES
FOREVER.

23012546 Fix for Bug 23012546

24617870 RESPECT PERCENT WIDTH FOR TABLES SET IN WORD

24934358 TEMPORARY DIRECTORY IS NOT CLEARED IN SERVER RESTART

24949452 UBS: EAL: SLOW PERFORMANCE OF THE MANAGE SCHEDULES SCREEN

25242562 OLD CACHE IS NOT RELEASED AFTER RE-INDEXING OF METADATA

25308775 SFTPUTIL GET CANNOT HANDLE 1 CHANNEL LIMIATION

17965888 STYLE TEMPLATES DO NOT SUPPORT APPLYING A TABLE STYLE TO A TABLE WITHIN A
TABLE
21771932 IE11: REPORT HISTORY PAGE ONLY SHOWS MAX 33 ENTRIES. FF\CHROME SHOWS MORE.

22851196 HYPERLINKS DO NOT GET RID OF UNDERLINE BELOW THEM

22880136 SHOW A WARNING MESSAGE TO BIP SCHEDULER JOB SUBMITTERS DURING THE QUEUE
PERIOD

23057101 RE-ARRANGING COLUMNS IN A DATA MODEL-DATA SET IS NOT ALLOWED IN 11.1.1.9.16

24691403 REPORTITEMRUNNER OBJECT REMAINS EVEN AFTER REPORT IS TIMED OUT

24934641 XPT INTERACTIVE REPORTS CAN CAUSE OOM BY MEMORY LEAK

25139096 Fix for Bug 25139096

25669205 Fix for Bug 25669205

Section 7.4: Oracle BI Mobile App Designer (BIMAD)

New bug fixes for Oracle BI Mobile App Designer (BIMAD) are listed here.

25516062 CBFH-TEST: MAD FAILS AS FAILURE TO GET META DATA FROM THE DATA SOURCE

Section 7.5: Oracle Enterprise Performance Management

Components Installed from Oracle BI Installer 11.1.1.9.0
(BIFNDNEPM)
New bug fixes for Oracle Enterprise Performance Management (BIFNDNEPM) are listed here.

24499111 ARBORPATH/BIN/.ODBC.INI GET UPDATED WITH TRIAL LICENSE STRING ISSUE

24710282 CHROME: NO TOP-LEVEL MENUS; MISPLACED CONTEXT MENU

22721776 FR STUDIO INSTALLER SHOULD ENABLE SSE FLAG TO SUPPORT SHA2 CERTIFICATE

24681838 MDX CELL-STATUS WITH ADMIN + FILTER + CALC FAILS

24581748 FA:REL12:ROLE GUIDS ARE NOT IN SAME FOR SAME ROLE

23507931 ONE ROW REPORT MEMBER ID PROBLEMS

24317224 PS4 FUSION VERSION OF BUG 22449827

23252950 SV MBR ID:DETAIL-LEV 0 MBERS 'IN A HIER V1 OR V2' ARE NOT HOLDING CORRECT PARENT
23082316 PLANNING ATTACHMENTS DISPLAY INCORRECTLY IN HTML PREVIEW IN GRID

23562356 FR SCHEDULER_BURSTING ZIP FILE CAN'T BE OPEN AS TOP FOLDER NAME IS BLANK

23252977 SV MBR ID:DETAIL-LEV 0 MBERS 'IN A HIER V1 OR V2'-DOES NOT DRILLUP HIERARCHY

21848516 SV MEMBER ID TESTING:SCENARIO ERRORED WHEN IN POV (NOT ON ROW)

24704802 SQL QUERY/DB DETAILS NOT GETTING PUSHED INTO PROJECTS ESSBASE RULES FILES

23184655 EXPORT TO EXCEL OF REPORT WITH NO DATASOURCES GENERATES INVALID EXCEL FILE

22682356 BACKGROUND IMAGE DOES NOT DISPLAY IN FR REPORT

24416492 REL10.0:E2E:HCM:SAAS PATCHING:AGL:ESSBASESERVER1 IS DOWN

22898874 PORT REQ OF BUG 20511310 TO PS4.FUSION BRANCH

22909960 FR STUDIO WORKSPACE BATCH SCHEDULER ICANNOT BE DELETED

22583517 NOT STRESS:FA:FIN:HOT:JSP COMPILATIONS ERRORS FROM HRJSPMAP.JSPF

24760446 FR-PAGE DOES NOT REFRESH FR WINDWS-CHANGE USER POV, PREVIEW U POV, RESP TO
PRMPT

24358882 OTBI 12C:- BI_SERVER1 FAILED TO START DUE TO FIN*REPORTING DEPLOYMENT FAILED

24906271 NULLPOINTEREXCEPTION READING REPORT FROM REPOSITORY

24674849 SECURITY - EHTEAM - LOCAL PRIVILEGE ESCALATION (WEAK FILE PERMISSIONS)

24360422 MISALIGNMENT OF THE COLUMNS IN CASE OF A MULTI-GRID FRS REPORT

25092660 FR BUILD 11.1.2.4.560.0512 >> BATCHES DO NOT WORK-SUBMITS AND THEN DISAPPEARS

23853078 ADD VERSION NUMBER TO STATUS JSP

22846500 FR REPORT: CALCULATION REFERENCING A SECOND GRID GOES TO NULL

25115676 FR 11.1.2.4.560.0512>>FR DRILLTHROUGH NOT WORKING RENDERED RPT AND STUDIO

25092660 FR BUILD 11.1.2.4.560.0512 >> BATCHES DO NOT WORK-SUBMITS AND THEN DISAPPEARS

23853078 ADD VERSION NUMBER TO STATUS JSP

25097346 FA: FR BUILD 11.1.2.4.560.0512 >> FR STUDIO, LOGIN SCREEN CRASHES

22846500 FR REPORT: CALCULATION REFERENCING A SECOND GRID GOES TO NULL

25115676 FR 11.1.2.4.560.0512>>FR DRILLTHROUGH NOT WORKING RENDERED RPT AND STUDIO

25221043 FA:REL12 RUPGRADE:WORKSPACE IS NOT LAUNCHED AND KEEPS LOADING

25163083 BAD PERFORMANCE SELECTING MEMBERS IN FRS AFTER APROX 50 ROWS

25179066 FA: R12:: FR STUDIO 11.1.2.4.560.0513 CONNECT FAILS WITH 404 FILENOTFOUND (SSL)

20404518 GL ASO CUBES: ENABLE ROUNDING FEATURE FOR FORMULA COMPONENT

23269251 SV MEMBERID ER BUG 18262452 VERIFICATION-CONSOLIDATED SV USUABILITY ISSUES

24653163 MDX FORMULAS MEMORY LEAK (ESPECIALLY FOR OBIEE GENERATED "FILTER")

24735916 OBIEE REPORT IS CRASHING ESSBASE ASO APPLICATION.

25388738 GL APP CRASHES WHEN TRYING TO RUN CUSTOM CALC ALLOCATION

24907222 ENHANCE CUSTOMCALC FUNCTION TO ALLOW ROUNDING

25072213 EEIT-TEST - GATEWAY TIMEOUT - IN READ:UNABLE TO SAVE THE ESSBASE RULES MAPPING

24370558 NOT STRESS:FA:FIN:MISSINGRESOURCEEXCEPTION ON SERVER STARTUP

24388263 STRESS:FA:FIN:ADD SERVLET FILTER INIT PARAM-AVOID ATGPF CODE KILLS REST SESSIONS

25379921 R12_PREFLIGHT_NO MENU SELECTION INDICATOR DISPLAYS IN FR STUDIO MENU OPTIONS

25491866 REL11 PRECOMPILED JSPS NOT BEING DELETED AS PART OF RUPGRADE FROM REL11 TO REL12

25497220 UNABLE TO ACCESS PROPERTIES ON FR GRID DESPITE NO ERROR

24791049 EPM FAILED TO GET USERNAME PASSWORD FROM CREDSTORE CONFIGURED IN

REG.PROPERTIES

24667368 PROVIDE API FOR GETTING THE ALIASID TABLE

25510299 UPDATE ESSBASE ORACLE SIGNED JARS TO WORK WITH LATEST JRE IN BI 11.1.1.9.0

25682282 ECTB-TEST-REL12: CANNOT CONNECT TO CUBES DUE TO ESSBASE DB CONNECTION STRING

25693318 FA:REL12:[FUSION-DB_KEY] CREDENTIALS STORE ERROR WHILE ACCESSING GL CUBES

25742574 CHANGE JPS_CONFIG DEFAULT TO \\CONFIG\\FMWCONFIG\\JPS-CONFIG-JSE.XML

25474892 REL12.1 ST6 - FAP0892 GSE::FR REPORTS NOT SHOWING DATA WHILE SV REPORTS SHOWS

25065147 ERROR WHEN EXECUTING DRILL-THROUGH: ERROR IN THE STATEMENT INTERPRET. LINE =
689

25537282 SIGN THE "XSDLIB.JAR" THAT IS PART OF ESSBASESTUDIO SERVER

25651616 BACK PORT JAR SIGNING FIXES FROM 25510299, FOR BI 11.1.1.7 DELIVERY
24846912 UPDATE BI 11.1.1.7 TOMCAT EAS JAR SIGNATURES TO WORK WITH LATEST JRE UPDATES

24908060 UPDATE ESSBASE EAR 3RDPARTY JAR SIGNATURES TO WORK WITH LATEST JRE UPDATES

25218146 ESSBASE EAR - 3RD PARTY JARS REQUIRE RE-SIGNING FOR 11.1.1.9.0

Section 8: Known Issues

These sections lists known issues for this bundle patch.

This section consists of the following topics:

"Section 8.1: OPatch Issues"

"Section 8.2: readme.txt Files in the Oracle BI EE Bundle Patch"
"Section 8.3: Unzip Utility Cannot Extract Oracle BI EE Suite Bundle Patch 11.1.1.9.170418"
"Section 8.4: Upgrade WebLogic Demo Certificates for New OpenSSL Version"
"Section 8.5: For HP-UX Itanium Customers"

Section 8.1: OPatch Issues

For information about OPatch issues, navigate to My Oracle Support and review the document titled "Master
Note for OPatch" (Doc ID 293369.1).

Section 8.2: readme.txt Files in the Oracle BI EE Bundle Patch

Ignore any patch set instructions in the readme.txt files in the Oracle BI EE Bundle Patch component
patches. The readme.html file in patch 25797429 contains all the installation instructions and list of bugs
fixed.

Section 8.3: Unzip Utility Cannot Extract Oracle BI EE Suite Bundle

Patch 11.1.1.9.170418
If you are using an unzip utility to extract Oracle BI EE Suite Bundle Patch 11.1.1.9.170418, note that some
versions of the utility cannot extract files greater than 2 GB. Therefore, when extracting files greater than 2
GB, ensure that the unzip utility has a GNU Compiler Collection (GCC) version of 4.1.2 20080704 or greater.

Section 8.4: Upgrade WebLogic Demo Certificates for New OpenSSL

Version
In 11.1.1.9.160119, the OpenSSL version is upgraded to 1.0.1p 9 Jul 2015 (bug 2919700). Because of this
change, if you use WebLogic demo certificates you must upgrade them by applying WebLogic patch
13964737 (if the patch is not already applied).

Note:
Presentation Services (OBIPS) displays a HTTP 500 error without the Oracle Weblogic
Server Interim one-off patch 13964737.
To apply the WebLogic patch, navigate to SSL Configuration Changes Required Due to New JDK Version in
Release Notes for Oracle Business Intelligence .

Section 8.5: For HP-UX Itanium Customers

You must run the chmod 755 command on each of the following files to set the correct permissions in your
11.1.1.9.0 patched installation:

prod_mwhome/Oracle_BI1/clients/bipresentationserver/catalogapmextension
/oracle.bi.catalog.apm.extension.slib.war
prod_mwhome/Oracle_BI1/common/templates/applications
/oracle.jbips.common.slib_template_11.1.1.jar
prod_mwhome/Oracle_BI1/common/templates/applications
/oracle.jbips.slib_template_11.1.1.jar
prod_mwhome/Oracle_BI1/common/templates
/was/oracle.jbips.common.slib_template_11.1.1.jar
prod_mwhome/Oracle_BI1/common/templates/was/oracle.jbips.slib_template_11.1.1.jar

To set the correct permissions to avoid a copy issue in your patched application:

Run the chmod 755 command on each of the files in their specified locations: chmod 755 <filename> For
example: chmod 755 prod_mwhome/Oracle_BI1/clients/bipresentationserver
/catalogapmextension/oracle.bi.catalog.apm.extension.slib.war

25797429 - Oracle Business Intelligence Enterprise Edition Suite Bundle Patch 11.1.1.9.170418

Copyright 2016, 2017, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify,
license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.
Reverse engineering, disassembly, or decompilation of this software, unless required by law for
interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free.
If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it
on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any
programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-
specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then
you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure
its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content,
products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and
expressly disclaim all warranties of any kind with respect to third-party content, products, and services
unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its
affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of
third-party content, products, or services, except as set forth in an applicable agreement between you and
Oracle.

Copyright 2017, Oracle and/or its affiliates. All rights reserved.