Changes Related to the Dependencies for a Running System

Planning to Upgrade from Oracle BI 10g to BI 11g 1-15 For more information, see Running bi-init to Launch a Shell Window Initialized to Your Oracle Instance in Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition.

1.2.2.6 Changes Related to Data Source Connectivity

This section describes changes to data source connectivity in 11g. Setting Up Oracle Database Data Sources If you want to use a net service name in a connection pool for an Oracle Database data source, you must set up a tnsnames.ora file in the following location within the Oracle BI EE environment, so that the Oracle BI Server can locate the entry: ORACLE_HOMEnetworkadmin Setting Up Essbase Data Sources The recommended client version for Essbase connectivity in 11g is the 11.1.2.x client bundled with Oracle BI EE in ORACLE_ HOMEclientsepmEssbaseEssbaseRTC. See Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for additional configuration steps, such as adding Essbase variables to bi-init.cmd for Administration Tool connectivity. Setting Up Teradata Data Sources For connectivity to Teradata on Windows, you must manually edit opmn.xml to include required Teradata variables. See Oracle Fusion Middleware Release Notes for more information.

1.2.2.7 Administration Tool Changes

Note the following changes in Oracle BI 11g related to the Administration Tool: ■ You can no longer open the Administration Tool by double-clicking a repository file. The resulting Administration Tool window is not initialized to the Oracle instance, and errors result later in your session. Instead, always use the Start menu to open the Administration Tool, or launch the Administration Tool from the command line using bi-init.cmd. For information, see Opening the Administration Tool in Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition. ■ Joins in the Physical and Business Model Diagrams are represented by a line with an arrow at the one end of the join, rather than the line with crow’s feet at the many end of the join that was used in previous releases. For example, the following image shows a join in the diagram as it was represented in previous releases: This join is represented as follows in 11g Release 1 11.1.1.5: ■ When creating joins in the Physical and Business Model Diagrams, you now select the many end of the join first, and then select the one end of the join. In previous releases, joins in the diagrams were created by selecting the one end of the join first.