This chapter includes details about patch requirements and Release Notes for Oracle Business Intelligence Applications and Oracle Business Intelligence Data Warehouse Administration Console (DAC) for Releases 11.1.1.5.x, 11.1.1.6.x, and 11.1.1.7.0.

Sometimes, there can be a delay before revised Release Notes are published on the Oracle Technology Network (OTN). To get access to Oracle Business Intelligence Release Note items as soon as they are available, go to the Oracle BI Documentation wiki at https://wikis.oracle.com/display/oraclebidocumentation/Home

42.1 Patch Requirements

This section describes patch requirements for Oracle Business Intelligence Applications.

42.1.1 Obtaining Patches from My Oracle Support

Periodically, Oracle Business Intelligence patches are released. Some patches are mandatory, other patches are optional.

To see the patches that are available, go to My Oracle Support (formerly OracleMetaLink) using the following URL:

Oracle Business Intelligence, Oracle Transactional Business Intelligence, and Oracle BI Applications patches are applied automatically. An Oracle BI Applications patch for the Informatica Repository is not applied automatically but must be applied manually using OPatch. This patch is located at:

<your Repository root>/installers/biappsshiphome/metadata/12937967

Apply the patch and instructions following instructions documented in the Reference Guide for Oracle Business Intelligence Applications > Chapter 5, "Oracle BI Applications Patching". Before applying this patch, shut down the Administration Server and Managed Server in the BI Domain. Shut down OPMN processes. Informatica Services must be running. Running of this patch requires input of following information:

#Informatica Home Directory (under which server/bin/pmrep lives)
#infa.home = The location of the Informatica Home directory. This is the path to the Informatica binaries located under server/bin/pmrep. Example, /Informatica8.6.1.
#Informatica Repository Name
#infa.repo.name = The name of the Informatica Repository Service which manages the Informatica Repository. The name of the Informatica Repository Service can be viewed through Informatica Administration Console.
#Informatica Repository Domain
#infa.repo.domain = The name of the Informatica Domain. The name of the Informatica Domain can be viewed through Informatica Administration Console.
#Informatica Repository Username
#infa.repo.username = The Informatica Repository User that has appropriate privileges to execute workflows (for example, Administrator).
#Informatica Repository Password
#infa.repo.password = The Informatica Repository user password.
#Informatica Repository Hostname
#infa.repo.hostname = The name of the machine where Informatica Services has been installed (Informatica Gateway host name).
#Informatica Repository Server Port (default is 6001)
#infa.repo.port = Informatica Gateway port number. For example, 6001.

42.2.2.2 About Issues For Both Oracle Fusion Transactional Business Intelligence and Oracle Business Intelligence Applications

Some issues that apply to Oracle Fusion Transactional Business Intelligence may also apply to Oracle Business Intelligence Applications. Such issues and their workarounds, if any, are documented in the Oracle Fusion Applications release notes and not in this chapter. To quickly locate issues that apply to both Oracle Fusion Transactional Business Intelligence and Oracle Business Intelligence Applications, you can search the Oracle Fusion Applications release notes for the text string "This issue also applies to Oracle Business Intelligence Applications."

The setup script configure_rpd.py does not configure the connection pool for Oracle BI Applications Configuration Manager in the Oracle BI Applications RPD file. You must configure the connection pool manually, as described in the workaround below.

Workaround

Use Oracle BI Administration Tool to open the repository.

From the Manage menu, select Variables.

Locate and provide values for the variables CM_DSN and CM_USER.

For CM_DSN, provide the complete connect string in the Default Initializer box.

For CM_USER, provide the same information as the Data Warehouse Schema user in the Default Initializer box, enclosed in single quotation marks.

In the Physical layer, navigate to and click on BI Applications Configuration Data Source, and then click on Catalog.

Provide the password of the Configuration Manager schema user in the dialog that opens.

42.2.2.4 Using Multiple Execution Plans Using Different Source Connection Names But Running On The Same BI Server

This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6.

In DAC, if you have multiple Execution Plans using different source connection names but running on the same BI Server, then DAC should first run a Full load, then an Incremental load for common dimensions. In Releases 11.1.1.5.1 and 11.1.1.5.2, this will not execute correctly if you have specified a different Physical Data Source value in the DAC Connectivity Parameters for the Execution Plans.

Workaround

Specify the same Physical Data Source value in the DAC Connectivity Parameters for the Execution Plans. For example, when you create the Execution Plans, you must do the following:

Specify the Connectivity Parameters tab, and locate the parameter named DBConnection_OLTP.

Make sure that the Value is the same as for the other Execution Plans (for example, FUSION_V1_FSCM or FUSION_V1_CRM).

When you run ETL, the Task SDE_FUSION_DomainGeneral_SalesInvoiceSource_FULL in the Execution Plan 'Domains – Fusion 1.0' fails with a syntax error. This error occurs because the $$LANGUAGE_LIST's precision is defined as 4 in mplt_BC_FUSION_DomainGeneral_SalesinvoiceSource. The $$LANGUAGE_LIST's precision should be corrected to 255.

Workaround

In Informatica Mapping Designer, check out the Mapplet 'mplt_BC_FUSION_DomainGeneral_SalesinvoiceSource".

From the Mapplets menu, choose 'Parameters and Variables'.

Select the $$LANGUAGE_LIST parameter (it will have the a precision value set to 4), and change the value to 255.

Save the mapplet and 'Check in'.

In Informatica Workflow Designer, check out the following session tasks, then Refresh and validate the maps:

SDE_FUSION_DomainGeneral_SalesInvoiceSource_FULL.

SDE_FUSION_DomainGeneral_SalesInvoiceSource.

Check in both the Session Tasks.

42.2.2.6 Informatica License Dis-associating After Installation

If the Informatica PowerCenter license is dis-associated after installation and an error is reported by WCA, then you need to re-associate the license and manually create a Repository Service. This issue is an intermittent issue in Informatica PowerCenter V9.1.

This Repository Service is not associated with a license and therefore should be deleted. You can do this using Informatica Administrator, by right clicking on the Repository Service name and selecting the delete option.

Add license to the node using Informatica Administrator (that is, choose Action, then New, then License).

For example, add the license '910_License_<HostName>42571'.

Use Informatica Administrator to manually create a repository with exactly the same name specified in wca_params.properties (by the INFA_RS_NAME parameter value).

Use the license name specified in Step 2.

Remove any create_Repository_service.err files from in wca/logs/ folder, and create a file named create_Repository_service.succ.

Restart WCA.

42.2.2.7 JAZN File Not Translated

This issue applies to Release 11.1.1.6.2.

The JAZN file is not translated in this release. There is no work-around for this issue.

42.2.2.8 Duplicate Rows in GL Account Segment Hierarchy Tables

This issue applies to Release 11.1.1.6.3.

Trees containing nodes with multiple parents cannot be used for reporting. The SILO mappings to populate the following tables potentially fail when such tree nodes exist:

W_COST_CENTER_DH

W_BALANCING _SEGMENT_DH

W_NATURAL_ACCOUNT_SEGMENT_DH

W_GL_SEGMENT_DH

Workaround

To workaround this issue, remove the trees from the hierarchy tables in the Oracle Business Analytics Warehouse.

Back up the DH table.

Delete the trees with duplicate rows, using the following SQL statement:

The Informatica PowerCenter Services installation requires 1,386 MB of free space. If the free disk space size is in the order of Terabytes, then the Installer does not recognize the free space and the following message on installation is received:

The installation requires 1,386 MB of free disk space, but there are only 0 MB available at: /Informatica/PowerCenter8.6.1. Free at least 1,386 MB to continue with the installation. Type 'Quit' to cancel this installation.

After completing the high-level setup tasks as described in Section 4.2.4 Overview of Tasks for Setting Up Oracle Business Intelligence Applications (Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Applications), before you start ETL processes you must start or restart the following components: Node Manager, Admin Server, Managed Server, and BI services (that is, OPMN).

The following steps are required if you would like to enable and use the Customer Cost Lines and Product Cost Lines feature in Profitability Analytics. On installation, Oracle provides default configuration files and the sample data for Customer Cost lines and Product Cost lines in CSV files. The content of data CSV files need to be replaced with your actual cost line data.

To configure the Customer Costs Lines and Product Costs Lines:

Copy the following configuration and sample data files from the ORACLE_HOME\biapps\etl\biapps_etl\data_files\universal_sample_data folder to the INFA_HOME\server\infa_shared\SrcFiles folder on the Informatica Server machine.

You can omit this step if the configuration files have already been copied to the INFA_HOME\server\infa_shared\SrcFiles folder on the Informatica Server machine.

Open the file_customer_cost_line.csv file in the INFA_HOME\server\infa_shared\SrcFiles folder.

Replace and fill in the customer costing transactions that you want to load into the Customer Cost fact table, and save the file.

Open the file_product_cost_line.csv file in the INFA_HOME\server\infa_shared\SrcFiles folder.

Replace and fill in the product costing transactions that you want to load into the Product Cost fact table, and save the file.

The other files file_xact_type.csv, file_chnl_type.csv, and FILE_DOMAIN.csv file contain the default values of transaction types, channel types, and related domain values. You can leave these files untouched unless you want to customize the values.

Note: These CSV files are the source data for the Customer / Product Cost Line mappings in SDE_Universal_Adaptor. If the above configuration steps are not completed, then the mappings will fail.

42.2.4 Upgrade Issues and Workarounds for Oracle Business Intelligence Applications

This section describes issues and workarounds related to upgrading Oracle Business Intelligence from previous releases.

42.2.5.2 Issues for Oracle Financial Analytics Offering

42.2.5.2.1 Overlapping Aging Bucket Ranges in AP/AR Aging

This issue applies to Releases 11.1.1.5.0 and 11.1.1.5.2.

Oracle Financial Analytics Fusion Edition does not support overlapping aging bucket ranges. When you set up aging buckets in Fusion Applications, you must use only non-overlapping aging buckets for AP and AR aging analysis in Financial Analytics. Also, when buckets are defined to separate out due and overdue amounts in different buckets, make sure that the days_from value and days_to value for a bucket are defined so that it takes either due or overdue transactions, but not both. To do this, make sure the days_from for overdue buckets start from 1 or a positive number, not from 0 or a negative number. Here are few examples to illustrate the supported aging bucket ranges.

Supported:

a) -60 days to -31 days
b) -30 days to -11 days
c) -10 days to 0 days
d) 1 days to 10 days
e) 11 days to 30 days
f) 31 days to 60 days and so on.

In this example, a/b/c are 'due' buckets and d/e/f are 'overdue' buckets. The bucket ranges are defined correctly with no overlaps and all overdue buckets start from 1 or above.

Not Supported:

a) -60 days to -31 days
b) -30 days to -11 days
c) -10 days to -1 days
d) 0 days to 10 days
e) 9 days to 30 days
f) 31 days to 60 days and so on.

In this example, the bucket ranges are not defined correctly. Note that bucket d starts from 0. So this bucket could hold some invoices that are due and some that are overdue. Thus a report that shows only overdue buckets could include some invoices that are not overdue. Furthermore, buckets d and e are overlapping. Therefore, some invoices could be reported in both buckets, thus making the total outstanding amount appear larger than it is.

Not Supported:

a) -60 days to -31 days
b) -30 days to -11 days
c) -10 days to -6 days
d) -5 days to 5 days
e) 6 days to 30 days
f) 31 days to 60 days and so on.

In this example, the bucket ranges are not defined correctly. Here, bucket d starts from a negative number and ends with a positive number. Similar to the previous example, this bucket could hold some invoices that are due and some that are overdue.

Workaround

There is no workaround for this issue. Defining aging buckets in any of these "Not Supported" patterns could show misleading numbers in aging reports that use these aging buckets.

42.2.5.3.1 Incorrect Metrics Showing Current Year

The following metrics are incorrectly showing the current year, not the prior year value:

Length of Service (Years) YAGO

Average Length of Service (Years) YAGO

% Change Average Length of Service (Years) YAGO

Workaround

There is no workaround for this issue.

42.2.5.3.2 Member Mappings Not Displayed For FSM Tasks Relating to Ranged Domains

This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2 and 11.1.1.6.

In FSM, if you click Go to Task for a Task that is related to a ranged Domain for the first time in a browser session, then the Domain Member Mappings are not displayed, and the message 'No rows returned' is displayed. For example, in Human Resources Analytics Fusion Edition, the Task 'Manage Domains and Member Mappings for Age Band Dimension'.

Workaround

Close the Manage Domain and Mappings dialog, then re-select the Task in FSM by clicking Go to Task.

42.2.5.7 Issues for Oracle Procurement and Spend Analytics Offering

42.2.5.7.1 Null Values Included In Level-Based Metric Report

This issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2.

If you create a report that includes a level-based metric, then the report might include null records. For example, when reporting the level-based metric 'Agreed Amount at Header Level' with 'Product Name', the filter of "Product Name" LIKE '%zBIA%' does not filter out the records with Product Name as null.

Workaround

Add an extra filter IS NOT NULL to exclude null records. For example, if you report against the level based metric 'Agreed Amount at Header Level' with 'Product Name', add the following filter:

...
WHERE (("Product"."Product Name" LIKE '%zBIA%') AND ("Product"."Product Name" IS NOT NULL))
...

On First Login Task Pane Options Are Inactive When Overview Page Is Loading

This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6.

When a user first user logs into Oracle BI Applications Configuration Manager, the options on the Tasks pane are inactive while the Overview page is loading.

Workaround

There is no workaround for this issue.

However, once a user is logged in and navigates back to the Overview page, the options on the Task pane are active while the Overview page is loading.

Cancel Option On Export and Import Dialog Does Not Cancel The Process

This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6.

This issue affects the Setup Data Export\Export Setup Data option and the Setup Data Export\Import Setup Data option that are available on the Tasks pane. If you click Cancel on the Export Data dialog after first clicking Export, then the dialog is cancelled but the Export process continues. If you click Cancel on the Import Data dialog after first clicking OK, then the dialog is cancelled but the Import process continues.

Clicking the 'Go to Task' icon for a Task for Data Load Parameters in Functional Setup Manager (FSM) displays the Task pane with the Data Load Parameters displayed in the master table. A Parameter row in the Master table is not selected by default but the Edit icon is enabled. On clicking the Edit Icon, the Edit dialog is launched with no parameter details.

Workaround

Before clicking the Edit icon, select a parameter in the Master table.

Import Of Incorrect Zip File Reports No Error

This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6.

This issue applies to the Setup Data Export and Import\Import Setup Data option on the Tasks bar of Oracle BI Applications Configuration Manager. Importing a zip file that is not related to export/import data does not result in an error message.

Workaround

Before you import Setup Data, make sure the Zip file that you import contains valid Setup Data.

This issue affects the Setup Data Export\Export Setup Data option and the Setup Data Export\Import Setup Data option that are available on the Tasks pane. The Export Duration (ms) column on the Export Setup Data page and Import Duration (ms) column on the Import Setup Data page are not formatted as per current browser language settings.

On the Search pane of BI Applications Configuration Manager, when you select a BI Application in the BI Application drop-down list, you can still select options in other search fields while those fields are being refreshed, even though the busy hour glass cursor is displayed.

Workaround

Oracle recommends that you always wait for fields to refresh before selecting values.

In Release 11.1.1.6.2 of the Oracle Business Intelligence Applications Installation Guide, content is missing from Appendix A, Section 7.3, Locations of Installation Files for Informatica PowerCenter and Hotfix 2. After the sentence "The PowerCenter folder contains the following files:" the following four points were omitted from the documentation.

In Section 4.2.4 Overview of Tasks for Setting Up Oracle Business Intelligence Applications, after completing the high-level tasks in this section, before you start ETL processes you must start or restart the following components: Node Manager, Admin Server, Managed Server, and BI services (that is, OPMN).

Section 4.3.2.1 'Creating Oracle BI Applications Schemas Using Oracle BI Applications RCU' should include the following information about the location of the Oracle BI Applications RCU zip file:

The Oracle BI Applications RCU zip file named rcuHomeBIApps.zip is located in the Fusion Applications software repository under installers/biapps_rcu/<OS - either Linux or Window>. (The Fusion Applications software repository is obtained when you download and unzip the Oracle Fusion Applications 11g parts available in the Oracle Fusion Applications Media Pack on the Oracle Software Delivery Cloud.) Extract this zip file into a folder, for example, BIA_RCU_HOME.

Section 4.3.4.2 'Locations of Installation Files for Informatica PowerCenter and Hotfix 11' should read as follows:

The Informatica PowerCenter 8.6.1 and HotFix 11 installation files, license key, and user documentation are provided as zip files. These zip files are located in the Fusion Applications software repository under /installers/powercenter. (The Fusion Applications software repository is obtained when you download and unzip the Oracle Fusion Applications 11g parts available in the Oracle Fusion Applications Media Pack on the Oracle Software Delivery Cloud.)

The powercenter folder contains four Informatica PowerCenter zip files. Informatica PowerCenter 8.6.1 Client Tools install files are available in V22464-01_1of2.zip. The HotFix 11 files for PowerCenter Client Tools are available in V22464-01_2of2.zip. The other two zip files contain the operating system-specific files for Informatica PowerCenter Services. The first of these zip files in each media pack (1of2.zip) includes the Informatica PowerCenter Services 8.6.1 install files. The second of the zip files (2of2.zip) includes the Informatica documentation, the license key, and the HotFix 11 installation file for PowerCenter Services.

Section 4.3.5 'Step 5: Install Oracle BI Administration Tool', should include the following information about the location of the Oracle BI Client Installer executable:

You install Oracle BI Administration Tool using the Oracle Business Intelligence Enterprise Edition Plus Client Installer. The Oracle BI Client Installer executable is named biee_client_install.exe and this file is available in the installed BI Middleware Home: bi/clients/biserver.

This issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2.

Section 4.3.9 'Step 9: Create a User for ETL' refers erroneously to FUSION_APPS_OBIA_BIEE_APPID as a User instead of a Group, and should read as follows:

The Extract Transform and Load (ETL) process must be run by a user with appropriate data security privileges granted on the Fusion Application tables from which data is extracted into Oracle Business Analytics Warehouse. For this purpose, the Group named FUSION_APPS_OBIA_BIEE_APPID is provisioned during install with the appropriate ETL security privileges (by default, this Group is mapped to the Duty Role named OBIA_EXTRACT_TRANSFORM_LOAD_DUTY).

To create a user for ETL:

Use Oracle Identity Management (or an appropriate security tool) to create a new user and password.

For example, you might create a new user named OBIA_ETL_USER.

Make the user a member of the Group FUSION_APPS_OBIA_BIEE_APPID.

For example, you might assign the user OBIA_ETL_USER to the group FUSION_APPS_OBIA_BIEE_APPID.

Make a note of the user's credentials.

These credentials are used to configure connections in DAC and Informatica later in the setup process.

Section 4.3.12 'Step 12: Install DAC Client' should include the following information about the location of the Oracle BI Applications Client installer:

Step 1 should be: Download the part for the Oracle BI Applications Client Installer from the Oracle Fusion Applications Media Pack on Oracle Software Delivery Cloud.

In Section 4.3.7 Step 7: Configure the Oracle BI Repository File (RPD), the description for the DW_DB_CONNECT value includes a JDBC string as an example. This example should include the following OCI/TNS string:

In Section 4.5.8 Extending the BI Domain, the parameter descriptions for MDS_DB_SCHEMA and MDS_DB_URL for the install_dwtools.py script should refer to the Fusion Applications schema, not the platform MDS schema. These parameter descriptions should read:

MDS_DB_SCHEMA is the schema for the Fusion Applications schema (that is, not the platform MDS schema). This schema was created during the provisioning of Oracle Business Intelligence, as part of the Oracle Fusion Applications installation process. For example, DEV11G_MDS.

MDS_DB_URL is the connection string for the Fusion Applications schema (that is, not the platform MDS schema). This schema was created during the provisioning of Oracle Business Intelligence, as part of the Oracle Fusion Applications installation process. For example, machine12345.company.com.example:1521:BIA11G.

This issue applies to Releases 11.1.1.5.2, 11.1.1.6.0, and 11.1.1.6.2 and to the Oracle Business Intelligence Applications Configuration Manager and Functional Setup Manager Help for those releases.

In Release 11.1.1.6.2 of the Oracle Business Intelligence Applications Installation Guide, content is missing from Appendix A, Section 7.3, Locations of Installation Files for Informatica PowerCenter and Hotfix 2. After the sentence "The PowerCenter folder contains the following files:" the following four points were omitted from the documentation.

In Section 4.2.4 Overview of Tasks for Setting Up Oracle Business Intelligence Applications, after completing the high-level tasks in this section, before you start ETL processes you must start or restart the following components: Node Manager, Admin Server, Managed Server, and BI services (that is, OPMN).

Section 4.3.2.1 'Creating Oracle BI Applications Schemas Using Oracle BI Applications RCU' should include the following information about the location of the Oracle BI Applications RCU zip file:

The Oracle BI Applications RCU zip file named rcuHomeBIApps.zip is located in the Fusion Applications software repository under installers/biapps_rcu/<OS - either Linux or Window>. (The Fusion Applications software repository is obtained when you download and unzip the Oracle Fusion Applications 11g parts available in the Oracle Fusion Applications Media Pack on the Oracle Software Delivery Cloud.) Extract this zip file into a folder, for example, BIA_RCU_HOME.

Section 4.3.4.2 'Locations of Installation Files for Informatica PowerCenter and Hotfix 11' should read as follows:

The Informatica PowerCenter 8.6.1 and HotFix 11 installation files, license key, and user documentation are provided as zip files. These zip files are located in the Fusion Applications software repository under /installers/powercenter. (The Fusion Applications software repository is obtained when you download and unzip the Oracle Fusion Applications 11g parts available in the Oracle Fusion Applications Media Pack on the Oracle Software Delivery Cloud.)

The powercenter folder contains four Informatica PowerCenter zip files. Informatica PowerCenter 8.6.1 Client Tools install files are available in V22464-01_1of2.zip. The HotFix 11 files for PowerCenter Client Tools are available in V22464-01_2of2.zip. The other two zip files contain the operating system-specific files for Informatica PowerCenter Services. The first of these zip files in each media pack (1of2.zip) includes the Informatica PowerCenter Services 8.6.1 install files. The second of the zip files (2of2.zip) includes the Informatica documentation, the license key, and the HotFix 11 installation file for PowerCenter Services.

Section 4.3.5 'Step 5: Install Oracle BI Administration Tool', should include the following information about the location of the Oracle BI Client Installer executable:

You install Oracle BI Administration Tool using the Oracle Business Intelligence Enterprise Edition Plus Client Installer. The Oracle BI Client Installer executable is named biee_client_install.exe and this file is available in the installed BI Middleware Home: bi/clients/biserver.

Section 4.3.12 'Step 12: Install DAC Client' should include the following information about the location of the Oracle BI Applications Client installer:

Step 1 should be: Download the part for the Oracle BI Applications Client Installer from the Oracle Fusion Applications Media Pack on Oracle Software Delivery Cloud.

This issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2.

Section 4.3.9 'Step 9: Create a User for ETL' refers erroneously to FUSION_APPS_OBIA_BIEE_APPID as a User instead of a Group, and should read as follows:

The Extract Transform and Load (ETL) process must be run by a user with appropriate data security privileges granted on the Fusion Application tables from which data is extracted into Oracle Business Analytics Warehouse. For this purpose, the Group named FUSION_APPS_OBIA_BIEE_APPID is provisioned during install with the appropriate ETL security privileges (by default, this Group is mapped to the Duty Role named OBIA_EXTRACT_TRANSFORM_LOAD_DUTY).

To create a user for ETL:

Use Oracle Identity Management (or an appropriate security tool) to create a new user and password.

For example, you might create a new user named OBIA_ETL_USER.

Make the user a member of the Group FUSION_APPS_OBIA_BIEE_APPID.

For example, you might assign the user OBIA_ETL_USER to the group FUSION_APPS_OBIA_BIEE_APPID.

Make a note of the user's credentials.

These credentials are used to configure connections in DAC and Informatica later in the setup process.

In Section 4.3.7 Step 7: Configure the Oracle BI Repository File (RPD), the description for the DW_DB_CONNECT value includes a JDBC string as an example. This example should include the following OCI/TNS string:

In Section 4.5.8 Extending the BI Domain, the parameter descriptions for MDS_DB_SCHEMA and MDS_DB_URL for the install_dwtools.py script should refer to the Fusion Applications schema, not the platform MDS schema. These parameter descriptions should read:

MDS_DB_SCHEMA is the schema for the Fusion Applications schema (that is, not the platform MDS schema). This schema was created during the provisioning of Oracle Business Intelligence, as part of the Oracle Fusion Applications installation process. For example, DEV11G_MDS.

MDS_DB_URL is the connection string for the Fusion Applications schema (that is, not the platform MDS schema). This schema was created during the provisioning of Oracle Business Intelligence, as part of the Oracle Fusion Applications installation process. For example, machine12345.company.com.example:1521:BIA11G.

The section A.7.3 'Locations of Installation Files for Informatica PowerCenter and Hotfix 2' is missing the following information after the sentence "The PowerCenter folder contains the following files:":