1-12 Upgrade Guide for Oracle Business Intelligence
In addition to the validation rules described in the previous table, bear the following in mind:
■
The Consistency Check Manager now provides a warning when the same connection pool is being used for both queries and initialization blocks. This
configuration is not recommended. Instead, create a dedicated connection pool for initialization blocks. Otherwise, query performance might suffer, or user logins
might hang if authorization initialization blocks cannot run. These warnings are displayed similar to the following:
[39062] Initialization Block Authorization uses Connection Pool My_DB. My_CP which is used for report queries. This may impact query performance.
■
Invalid objects are now deleted during consistency checks. This behavior might result in deleted expressions and filters on logical table sources and logical
columns. Invalid references can occur when objects were deleted in the Physical layer without properly accounting for the references in the Business Model and
Mapping layer objects.
1.2.1.2 Oracle BI Server Query Changes
This section describes changes to queries in the Oracle BI Server.
1.2.1.2.1 Integer Division Note the following for integer division:
■
In 10g, the behavior for division between two integers was inconsistent depending on whether the expression was evaluated internally, or whether the expression
[39059] Logical dimension table MY_DIM has a source MY_DIM_
DAILY at level Daily that joins to a higher level fact source MY_FACT_
SUM.MTHLY_SUM Warning
Even though this fact logical table source has an aggregate grain set in this dimension, no join was found that connects to
any logical table source in this dimension or a potentially invalid join was found.
This means that either no join exists at all, or it does exist but is potentially invalid because it connects a higher-level fact
source to a lower-level dimensional source. Such joins are potentially invalid because if followed, they might lead to
double counting in query answers.
For example, consider Select year, yearlySales. Even if a join exists between monthTable and yearlySales table on yearId, it
should not be used because such a join would overstate the results by a factor of 12 the number of months in each year.
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. [39054] Fact table Sales -
STAR.Fact - STAR Statistics is not joined to logical dimension table
Sales - STAR.Dim - Plan. This will cause problems when
extracting projects. Warning
This warning indicates that the aggregation content filter Group by Level in the logical table source of a fact table
references logical dimension tables that are not joined to that fact table. If that fact table is extracted in the extractMUD
process, the dimensions that are not joined will not be extracted. In this case, the aggregation content of the extracted
logical table source would not be the same as in the original logical table source.
[39057] There are physical tables mapped in Logical Table Source
HR.Dim - Schedule.SCH_ DEFN that are not used in any
column mappings or expressions. Warning
This warning indicates that the given logical table source has irrelevant tables added that are not used in any mapping. This
situation will not cause any errors.
Validation Rule Example Type
Description
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,
