41.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: To obtain patches:. Log in to My Oracle Support. Display the Patches & Updates tab. Use the Patch Search area to locate patches.
For example, you might search using a specific patch number or patch name, or search for patches related to one or more product families within the 'Oracle BI Applications' product. On the Patch Search Results page, select a patch and click Download to download the patch. Install the patch by following the instructions in the README file that is included with the patch. 41.2.1 Oracle Business Intelligence Applications Issues and Workarounds Identified Since the Previous Revision The issues and workarounds related to Oracle Business Intelligence that have been identified since the previous revision of the Release Notes include:. New entry Duplicate Rows in GL Account Segment Hierarchy Tables - for more information, see. New entry for documentation errata for Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications - for more information see.
41.2.2.1 Patch Installation Instructions for Informatica Repository in Oracle BI Applications Release 11.1.1.5.2 This issue applies to Release 11.1.1.5.2. Oracle Business Intelligence, Oracle Transactional Business Intelligence, and Oracle BI Applications patches for Release 11.1.1.5.2 are provided in the RUP Installer for Fusion Applications 11.1.2.
The Fusion Applications media pack on Oracle Delivery Cloud includes the RUP installer. Run this installer by following instructions documented in the Oracle Fusion Applications Patching Guide 11g Release 1 (11.1.2), Chapter 5, 'Installing Release Update Patches'. 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: /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.
41.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.' 41.2.2.3 CONFIGURERPD.PY Script Does Not Set Connection Pool for Oracle BI Applications Configuration Manager This issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2. The setup script configurerpd.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 the Oracle BI Server Administration Tool to open the repository. From the Manage menu, select Variables. Locate and provide values for the variables CMDSN and CMUSER. For CMDSN, provide the complete connect string in the Default Initializer box. For CMUSER, 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. 41.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 DBConnectionOLTP. Make sure that the Value is the same as for the other Execution Plans (for example, FUSIONV1FSCM or FUSIONV1CRM). 41.2.2.5 NLS:SDEFUSIONDOMAINGENERALSALESINVOICESOURCEFULL Failed With Syntax Error This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6. When you run ETL, the Task SDEFUSIONDomainGeneralSalesInvoiceSourceFULL in the Execution Plan 'Domains – Fusion 1.0' fails with a syntax error. This error occurs because the $$LANGUAGELIST's precision is defined as 4 in mpltBCFUSIONDomainGeneralSalesinvoiceSource. The $$LANGUAGELIST's precision should be corrected to 255. Workaround.
In Informatica Mapping Designer, check out the Mapplet 'mpltBCFUSIONDomainGeneralSalesinvoiceSource'. From the Mapplets menu, choose 'Parameters and Variables'. Select the $$LANGUAGELIST 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:. SDEFUSIONDomainGeneralSalesInvoiceSourceFULL. SDEFUSIONDomainGeneralSalesInvoiceSource.
Check in both the Session Tasks. 41.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 issue applies to Release 11.1.1.6.2. The WCA error log will report an error similar to the following: Error log: exec Using INFAHOME: /scratch/aime/work/Informatica/Infa910 echo Now creating the repository: repservice for license: exec Result: 255 BUILD FAILED.
Workaround. Delete the Repository Service created by WCA (if it exists). 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 '910License42571'. Use Informatica Administrator to manually create a repository with exactly the same name specified in wcaparams.properties (by the INFARSNAME parameter value). Use the license name specified in Step 2. Remove any createRepositoryservice.err files from in wca/logs/ folder, and create a file named createRepositoryservice.succ. Restart WCA. 41.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:. WCOSTCENTERDH.
WBALANCING SEGMENTDH. WNATURALACCOUNTSEGMENTDH. WGLSEGMENTDH 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: DELETE FROM WHERE (hierarchyid, hierarchyversion, datasourcenumid) in ( SELECT hierarchyid, hierarchyversion, datasourcenumid FROM GROUP BY integrationid, hierarchyversion, datasourcenumid HAVING COUNT (1) 1 ). 41.2.3.1 Installing Informatica PowerCenter 8.6.1 On Mount Points with Free Disk Space in Terabytes This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6 (for UNIX and Linux) with Informatica PowerCenter 8.6.1 Hot Fix 11. 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. Workaround Reduce the free space on the mount point to 200 GB or less.
41.2.3.2 Restarting Components After Completing The Post-Installation Setup Steps This issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2. 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). 41.2.3.3 Customer Cost Lines and Product Cost Lines Configuration is Missing From FSM Tasks for Oracle Financial Analytics This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2 and 11.1.1.6. 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 ORACLEHOME biapps etl biappsetl datafiles universalsampledata folder to the INFAHOME server infashared SrcFiles folder on the Informatica Server machine.
Filecustomercostline.csv fileproductcostline.csv filexacttype.csv filechnltype.csv FILEDOMAIN.csv You can omit this step if the configuration files have already been copied to the INFAHOME server infashared SrcFiles folder on the Informatica Server machine. Open the filecustomercostline.csv file in the INFAHOME server infashared 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 fileproductcostline.csv file in the INFAHOME server infashared 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 filexacttype.csv, filechnltype.csv, and FILEDOMAIN.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 SDEUniversalAdaptor.
If the above configuration steps are not completed, then the mappings will fail. 41.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 daysfrom value and daysto value for a bucket are defined so that it takes either due or overdue transactions, but not both.
To do this, make sure the daysfrom 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.
![Administration Administration](/uploads/1/2/3/9/123928549/869198928.png)
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. 41.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.
41.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)). 41.2.5.10 Issues for Oracle Supply Chain and Order Management Analytics Offering This section describes issues and workarounds related to Oracle Supply Chain and Order Management Analytics Offering. Obsolete Task in Supply Chain and Order Management Analytics Fusion Edition in Releases 11.1.1.5.1 and 11.1.1.5.2. In Functional Setup Manager for Oracle BI Applications, the 'Supply Chain and Order Management Analytics Fusion Edition' task list 'Order Management Functional Area Specific Configurations' task list displays the following task: 'Configure Reporting Parameters for Default Aging Method displayed in AR Aging Reports' This task is obsolete and should be ignored. No functional configuration is required for this task. Invoking this task via the 'Go to Task' button displays the Reporting Parameters UI with no rows.
41.2.6 Oracle Business Intelligence Applications Configuration Manager and FSM Issues This section describes issues and workarounds related to Oracle Business Intelligence Applications Configuration Manager. The following tasks in FSM for Oracle BI Applications are not translated: This issue applies to Release 11.1.1.6. For language FINNISH (Finland) LANGUAGECODE = 'SF', un-translated FSM task name - 'Manage Domains and Member Mappings for Employee Dimension', description - 'Manage Domains and Member Mappings for Employee Dimension'. For language CZECH (Czech Republic) LANGUAGECODE = 'CS', un-translated FSM task name - 'How to Integrate Procurement and Spend Analytics with Spend Classification', description - 'How to Integrate Procurement with Spend Analytics with Spend Classification'. For language BRAZILLIAN PORTUGUESE (Brazil) LANGUAGECODE = 'PTB', un-translated FSM task name - 'Manage Domains and Member Mappings for Employee Dimension', description - 'Manage Domains and Member Mappings for Employee Dimension'. For language TURKISH (Turkey) LANGUAGECODE = 'TR', un-translated FSM task name - 'Manage Domains and Member Mappings for Transaction Type Dimension' and description = 'Configure Domain and Member Mappings for Transaction Type Dimension'. For language NORWEGIAN (Norway) LANGUAGECODE = 'N', un-translated FSM task name - 'Manage Domains and Member Mappings for Employee Dimension' and description = 'Manage Domains and Member Mappings for Employee Dimension'.
For language HEBREW (Israel) LANGUAGECODE = 'IW', un-translated FSM task name - 'Overview of Human Resources Analytics Fusion Edition' and description = 'Overview of Human Resources Analytics Fusion Edition'. For language GREEK (Greece) LANGUAGECODE = 'EL', un-translated FSM filter name - 'Payroll Functional Area' and description = 'Enables Payroll Functional Area'. 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.
![Tool Tool](/uploads/1/2/3/9/123928549/321816854.jpg)
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. Workaround There is no workaround for this issue. Edit Icon Enabled Without Parameter Selection on Data Load Parameters Dialog This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6. 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.
![Oracle Bi Administration Tool 11.1.1.5 Oracle Bi Administration Tool 11.1.1.5](/uploads/1/2/3/9/123928549/856485241.jpg)
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. Duration (ms) Column For Import/Export Dialogs Not Formatted With Browser Language Setting This issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2. 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. Workaround There is no workaround for this issue. Search Pane Dropdown Selection List If Dropdown List Is Still Refreshing This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6. 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. Date Format On Manage Data Load Parameter Does Not Honor Browser Language Setting This issue applies to Releases 11.1.1.5.1, 11.1.1.5.2, and 11.1.1.6. This issue affects the Manage Data Load Parameters option on the Tasks bar.
The Date format for Date parameters on the Manage Date Load Parameters' dialog always displays as 'yyyy-mm-dd' irrespective of current browser language settings. Workaround There is no workaround for this issue. 41.2.8.2 Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications This section describes documentation errata in Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications. Note: In Release 11.1.1.5.2, the equivalent guide is named Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Applications. 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.
Section B.27.1 Configuring the BI Extender includes an erroneous cross-reference to Oracle Business Intelligence Server Administration Guide. This cross-reference should link to the Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (Oracle Fusion Applications Edition). 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. Informatica PowerCenter Services Version 9.1 Hotfix 2 (OS-specific files). Informatica PowerCenter Services Version 9.1 Hotfix 2 (Windows only). Informatica Documentation. Informatica License Key.
In Section 3.4.8.1 'How to Install DAC Client', the location of the Oracle BI Applications Client Installer is stated as /clients/biappsclients. This location should be: - On Windows, in the folder biappsshiphome shiphome. On Linux and UNIX. In the folder /biappsshiphome/dist/stage/clients/biappsclients. In Section 3.4.2.1 'Creating Oracle BI Applications Schemas Using Oracle BI Applications RCU', Step 10 should read as follows: 10. In the Schema Passwords screen, specify and confirm a password for the schemas. Note: It is not necessary to select the Use same password for all schemas option.
In Section 3.4.8.3 'How to log into DAC Client for the first time', Step 7 should read as follows: 7. Use the User name and Password fields to specify the credentials of a user that has been granted the role 'BI Applications Administrator Duty'. Note: Users are set up with appropriate roles in step Section 3.4.7, 'Setup Step: Grant User Access to Oracle BI Applications Components'. 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/biappsrcu/. (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, BIARCUHOME.
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-011of2.zip. The HotFix 11 files for PowerCenter Client Tools are available in V22464-012of2.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 bieeclientinstall.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 FUSIONAPPSOBIABIEEAPPID 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 FUSIONAPPSOBIABIEEAPPID is provisioned during install with the appropriate ETL security privileges (by default, this Group is mapped to the Duty Role named OBIAEXTRACTTRANSFORMLOADDUTY). 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 OBIAETLUSER. Make the user a member of the Group FUSIONAPPSOBIABIEEAPPID.
For example, you might assign the user OBIAETLUSER to the group FUSIONAPPSOBIABIEEAPPID. 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 DWDBCONNECT value includes a JDBC string as an example. This example should include the following OCI/TNS string: (DESCRIPTION=(ADDRESSLIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECTDATA=(SERVICENAME=orcl))). The issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2. In Section 4.5.8 Extending the BI Domain, the parameter descriptions for MDSDBSCHEMA and MDSDBURL for the installdwtools.py script should refer to the Fusion Applications schema, not the platform MDS schema. These parameter descriptions should read: MDSDBSCHEMA 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, DEV11GMDS.
MDSDBURL 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. 41.2.8.4 Oracle Fusion Middleware Reference Guide for Oracle Business Intelligence Applications This section describes documentation errata in Oracle Fusion Middleware Reference Guide for Oracle Business Intelligence Applications. Section B.27.1 Configuring the BI Extender includes an erroneous cross-reference to Oracle Business Intelligence Server Administration Guide.
This cross-reference should link to the Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (Oracle Fusion Applications Edition). 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.
Informatica PowerCenter Services Version 9.1 Hotfix 2 (OS-specific files). Informatica PowerCenter Services Version 9.1 Hotfix 2 (Windows only).
Informatica Documentation. Informatica License Key.
In Section 3.4.8.1 'How to Install DAC Client', the location of the Oracle BI Applications Client Installer is stated as /clients/biappsclients. This location should be: - On Windows, in the folder biappsshiphome shiphome. On Linux and UNIX. In the folder /biappsshiphome/dist/stage/clients/biappsclients. In Section 3.4.2.1 'Creating Oracle BI Applications Schemas Using Oracle BI Applications RCU', Step 10 should read as follows: 10. In the Schema Passwords screen, specify and confirm a password for the schemas. Note: It is not necessary to select the Use same password for all schemas option.
In Section 3.4.8.3 'How to log into DAC Client for the first time', Step 7 should read as follows: 7. Use the User name and Password fields to specify the credentials of a user that has been granted the role 'BI Applications Administrator Duty'.
Note: Users are set up with appropriate roles in step Section 3.4.7, 'Setup Step: Grant User Access to Oracle BI Applications Components'. 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/biappsrcu/. (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, BIARCUHOME. 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-011of2.zip. The HotFix 11 files for PowerCenter Client Tools are available in V22464-012of2.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 bieeclientinstall.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 FUSIONAPPSOBIABIEEAPPID 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 FUSIONAPPSOBIABIEEAPPID is provisioned during install with the appropriate ETL security privileges (by default, this Group is mapped to the Duty Role named OBIAEXTRACTTRANSFORMLOADDUTY). 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 OBIAETLUSER. Make the user a member of the Group FUSIONAPPSOBIABIEEAPPID. For example, you might assign the user OBIAETLUSER to the group FUSIONAPPSOBIABIEEAPPID. 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 DWDBCONNECT value includes a JDBC string as an example. This example should include the following OCI/TNS string: (DESCRIPTION=(ADDRESSLIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECTDATA=(SERVICENAME=orcl))). The issue applies to Releases 11.1.1.5.1 and 11.1.1.5.2. In Section 4.5.8 Extending the BI Domain, the parameter descriptions for MDSDBSCHEMA and MDSDBURL for the installdwtools.py script should refer to the Fusion Applications schema, not the platform MDS schema. These parameter descriptions should read: MDSDBSCHEMA 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, DEV11GMDS. MDSDBURL 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:':. OS-specific Server install file - 910HF2ServerInstaller.
910HF2ClientInstallerwin32-x86.zip (Windows only). Informatica Documentation (Infa91Docs.zip). Informatica License Key.
This tutorial covers using the Oracle Business Intelligence (BI) Administration Tool (11.1.1.7) to build, modify, enhance, and manage an Oracle BI repository. You learned how to import metadata from a data source, simplify and reorganize the imported metadata into a business model, and then structure the business model for presentation to users who request business intelligence information via Oracle BI user interfaces. Duration: 240 minutes This content is intended for the following job role(s): Data Modeler, Business Administrator, Business Intelligence Developer Release Date: 20-JUN-2014.
E.1.3 Set up ODBC Connection to Fusion Applications To set up the ODBC connection from the Windows machine, you must locate the correct port on the Fusion Applications BI Server. Typically it is 10206, but if ports were changed as part of the FA install, perform the following steps:. Log in to the BI Server's Enterprise Manager Console. Expand Business Intelligence within the FarmBIDomain and select coreapplication. Select Overview and the sub tab Processes. Expand the BI Servers, and make a note of the port number.
Armed with the correct port, you are ready to create a new ODBC connection. Select Oracle BI Server Driver on the Windows machine.
Enter the Server name for the host that contains the BI Domain. (If necessary, add an entry to the windows/system32/drivers/etc file, so that the windows machine can resolve the host name.). On the resulting screen, enter the BI Server port (either 10205 or derived above) and the user name/password with which you plan to connect. E.1.4 Connect to RPD in BI Admin Tool The user could now connect to the BI Server in On-Line mode and could update the live RPD. Depending on network speed and the size of the RPD, this can be both slow and dangerous.
How To Open Oracle Bi Administration Tool
Updating a live RPD while Fusion Applications users and reports are working with it is not advised. A better solution is to copy the RPD file from the BI Server to a local or shared drive the Windows client can access, updating the RPD in off-line mode, and then publishing it through the BI Server's Enterprise Manager console.
The RPD files are stored in the following path on the BI Server: BIInstance/bifoundation/OracleBIServerComponent/coreapplicationobis1/repository. To find the correct version:. Log in to Enterprise Manager, go to the Business Intelligence / coreapplication section, and select the Deployment / Repository tabs. This will identify the current version of the RPD. Copy that version locally or to the shared directory, to ensure you are working with the most current RPD.
For those that saw my presentation yesterday, you may have noticed that I didn't actually import Oracle OLAP metadata. I was working with a local install of BI Admininistrator Tool and importing OLAP metadata wasn't working. I was getting the error ' nQSError:77005 An invalid parameter was passed to the nQWebIBotAPI.dll. Verify that the Agent configuration is correct.' When trying to import the metadata.
Hmmm.not a very helpful error message. I asked Bob Ertl after the presentation and got a very helpful reply. Apparently, BI Admin Tool needs to be able to talk to a JAVAHOST. Since BI Admin Tool is installed locally, there's no JAVAHOST installed with it.
So we need to modify the NQSConfig.ini for BI Admin Tool to point to a JAVAHOST that can provide the services to BI Admin Tool. I shut down BI Admin Tool and found my NQSConfig.ini at 'C: Program Files (x86) Oracle Business Intelligence Enterprise Edition Plus Client oraclebi orainst config OracleBIServerComponent coreapplication NQSConfig.INI'. Vlamis Software Solutions, Inc. Is an independent consulting company and is not affiliated with Oracle, Microsoft, or other entities mentioned on this web site, except as noted. Oracle and Express are trademarks of Oracle Corporation; Microsoft and SQLServer are Trademarks of Microsoft Corporation; all other products are trademarks of their respective owners.
Vlamis Software Solutions, Inc. Provides this material 'as is' and makes no warranty or representation as to the quality or accuracy of the content of this web site.