10g Allowed Invalid Joins That Resulted in Double Counting Note the following for

1-14 Upgrade Guide for Oracle Business Intelligence so that the Oracle BI Server can retrieve the password to load the repository. See Changing the Repository Password in Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for more information. Note that a blank repository password is not allowed in 11g. – Groups no longer exist in the repository as objects. Instead, you implement data access security based on the application roles to which a user belongs. Application roles are managed in an external policy store. Application role objects exist in the repository, but these objects are pointers references to the externally managed roles. – Users are managed in an external authentication provider and are no longer managed in the repository. User objects exist in the repository, but these objects are pointers references to the externally managed users. See Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition for information about these and other security changes. See Applying Data Access Security to Repository Objects in Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for more information.

1.2.2.3 Changes Related to ODBC DSN

The connection parameters in the default ODBC DSN for the Oracle BI Server are now centrally managed by Fusion Middleware Control and cannot be manually changed. In addition, Oracle BI EE is now deployed in a clustered configuration by default. Because of this, the default ODBC DSN for the Oracle BI Server points to the Cluster Controller by default, rather than to the Oracle BI Server. See Integrating Other Clients with Oracle Business Intelligence in Oracle Fusion Middleware Integrators Guide for Oracle Business Intelligence Enterprise Edition for more information about ODBC DSNs for the Oracle BI Server.

1.2.2.4 Changes Related to the Dependencies for a Running System

Oracle BI EE 11g has additional dependencies for a running system, including: ■ The relational database that was specified upon installation must be running. This database must contain required Oracle BI EE schemas loaded using the Repository Creation Utility RCU. ■ If you selected the Simple Installation option for the 11g installation, then the Administration Server in Oracle WebLogic Server must be running before you start Upgrade Assistant. If you selected the Enterprise Installation option, then the Administration Server and any Managed Servers must be running before you start Upgrade Assistant.

1.2.2.5 Changes Related to Running Command-Line Utilities

Before you can run any of the Oracle BI Server command-line utilities, you must run bi-init.cmd or bi-init.sh on UNIX to launch a command prompt or shell window that is initialized to the Oracle instance. You can find this utility in: ORACLE_INSTANCEbifoundationOracleBIApplicationcoreapplicationsetup