Planning to Upgrade from Oracle BI 10g to BI 11g 1-13
was shipped to a data source that followed the ANSI standard for division between integers.
– If shipped to Microsoft SQL Server or evaluated internally, such as when
queries were returned from the Oracle BI Server results cache, then 7 2 = 3
– If shipped to Oracle Database, then 7 2 = 3.5
■
In 11g, division between integers always results in an integer even if the division is shipped to Oracle Database the result is truncated. If decimal division is
required, then follow the instructions in Appendix B, Possible Changes in Oracle
BI Enterprise Edition Appearance and Behavior After Upgrade to cast the values.
1.2.1.2.2 10g Allowed Invalid Joins That Resulted in Double Counting Note the following for
joins:
■
In 10g, the Oracle BI Server allowed joins between fact logical table sources such as Month level and lower-level dimension logical table sources such as Day
level. Typically, these joins result in double counting.
■
In 11g, a new consistency check warning 39059 highlights when a fact logical table source joins to a lower-level dimension logical table source, resulting in a
potentially invalid join. If you get a 39059 warning after upgrade, verify that the join is as intended and does not result in incorrect double counting. If the join is as
intended, then ignore the 39059 warning.
1.2.2 Repository Metadata: Other Upgrade Considerations
Keep the following considerations in mind when upgrading a repository:
1.2.2.1 Changes Related to the Use of Fusion Middleware Control in Oracle BI 11g
Note the following changes in Oracle BI 11g that are related to use of Fusion Middleware Control:
■
Many configuration settings that affect repository development, including the default published repository, are now centrally managed in Fusion Middleware
Control. You can no longer manually change these configuration settings in NQSConfig.INI. See Oracle Fusion Middleware System Administrators Guide for
Oracle Business Intelligence Enterprise Edition for more information.
■
You can no longer restart the Oracle BI Server using the Administration Tool in online mode. Instead, you can restart the Oracle BI Server and other system
components using Fusion Middleware Control.
You can also use the BI Systems Management API to programmatically start and stop Oracle BI EE.
For more information, see Starting and Stopping Oracle Business Intelligence and Starting and Stopping Oracle Business Intelligence Using the BI Systems
Management API in Oracle Fusion Middleware System Administrators Guide for Oracle Business Intelligence Enterprise Edition.
1.2.2.2 Changes Related to Security
Note the following changes in Oracle BI 11g related to security:
■
Be aware of the following security-related changes:
– Repositories now have repository-specific passwords that are used to encrypt
the repository contents. The repository password is stored in an external credential store when you publish a repository in Fusion Middleware Control,
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
